Historical Playback, Benchmarking, InfluxDB Questions #7445
-
|
Hello! I am part of a software team that has been tasked with developing a visualization application for monitoring telemetry data from multiple sources. We have diligently worked through all of the excellent tutorials and resources you’ve provided to determine that we’d like to proceed forward with using OpenMCT as a real-time data visualization tool. Having said that, we find ourselves with a few questions for our use case:
Thank you so much, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Hi Simon, Great to hear that your team is considering using Open MCT! Please find our responses below-- I'll also tag the POCs who can best answer any follow-ups for those specific questions.
@akhenry:
@unlikelyzero: Consider the following factors:
Just as we offer a platform for building automated acceptance tests for your implementation of Open MCT (openmct-as-a-dependency), we also provide the openmct-performance repository as a universal platform for testing Open MCT performance in the context of your environment. Open MCT has been around for a long time, and when performance issues are reported, we can support the necessary changes. Often, Open MCT becomes the bearer of bad news regarding general performance issues, as it serves as the client interface. We maintain a suite of regression performance tests designed to ensure that our application's client performance does not degrade as we introduce new features. Additionally, this suite helps us detect Chrome Client performance regressions.
@unlikelyzero: Hopefully that demystifies things a bit. Please feel free to comment in this thread with any follow-up questions and we will do our best to answer them in a timely manner. Cheers! Jesse |
Beta Was this translation helpful? Give feedback.
-
|
Sure. So the RemoteClock really just requires something that ticks. You would need to provide a telemetry object that subscribes to some data source providing a ticking value (like a timestamp or ms since epoch for example). You'll also need telemetry providers for both historical and real-time data that support From there, you would install the openmct.install(openmct.plugins.RemoteClock({
namespace: 'myTelemetry',
key: 'myRemoteClock'
}));Then you just need to register the clock with the TimeConductor: openmct.install(openmct.plugins.Conductor({
menuOptions: [
{
name: "Remote",
timeSystem: 'utc',
clock: 'remote-clock',
clockOffsets: {
start: - FIFTEEN_MINUTES,
end: FIFTEEN_SECONDS
}
},
// your other clocks here
]Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, @ozyx . Your examples always help! Can you point out what I am missing here? Thank you |
Beta Was this translation helpful? Give feedback.
-
Yep! So you'll just need to replace "myTelemetry" and "myRemoteClock" with the actual namespace and key for your remote tick source as defined by your object provider. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ozyx , |
Beta Was this translation helpful? Give feedback.
-
|
@ozyx Easier said than done 😅 Here is my code: index.html...
// Remote clock plugins install
openmct.install(openmct.plugins.RemoteClockHistoricalTelemetryPlugin('RemoteClockDomainObject'));
openmct.install(openmct.plugins.RemoteClockRealtimeTelemetryPlugin('RemoteClockDomainObject'));
openmct.install(openmct.plugins.RemoteClockProviderPlugin());
openmct.install(openmct.plugins.RemoteClock({
namespace: 'RemoteClockMainspace',
key: 'RemoteClockKey'
}));
openmct.install(
openmct.plugins.Conductor({
menuOptions: [
{
name: "Remote",
timeSystem: 'utc',
clock: 'remote-clock',
clockOffsets: {
start: - FIFTEEN_MINUTES,
end: THIRTY_SECONDS
}
},
// other clocks...
]
})
)
...Remote Clock Providers pluginlet object_name = 'PredefinedTelemetry';
let object_type = 'RemoteClockDomainObject';
let object_namespace = 'RemoteClockMainspace';
export default function RemoteClockProviderPlugin() {
return function install(openmct) {
// An object provider builds Domain Objects
openmct.objects.addProvider(object_namespace, {
get: function (identifier) {
console.log('provider.get( ' + identifier.key + ' )');
return Promise.resolve({
identifier: identifier,
name: object_name,
type: object_type
});
}
});
// Composition provider
openmct.composition.addProvider({
appliesTo: function (domainObject) {
return false;
},
load: function (domainObject) {
return null;
}
});
// Add RemoteClock type
console.log('AddType ' + object_type);
openmct.types.addType(object_type, {
name: 'RemoteClockTick',
description: 'RemoteClockTick',
cssClass: 'icon-telemetry'
});
};
}RemoteClock Realtime Pluginlet object_key = 'RemoteClockKey';
export default function RemoteClockRealtimeTelemetryPlugin(desired_domain_object_type) {
return function (openmct) {
let listeners = {};
let socket = io();
my_socket.on('realtime-tick', (msg) => {
// Get realtime message
console.log('Tick: ', msg.timestamp); /// This really happens every second
/// TODO How exactly can we inform API about new tick?
});
let provider = {
supportsSubscribe: function (domainObject) {
console.log('supportsSubscribe ', domainObject.identifier.key);
return domainObject.type === desired_domain_object_type;
},
subscribe: function (domainObject, callback, options) {
console.log('Subscribe to RemoteClock', domainObject.identifier.key);
/// This never happens :/
}
};
openmct.telemetry.addProvider(provider);
};
}RemoteClock Historical pluginexport default function RemoteClockHistoricalTelemetryPlugin(desired_domain_object_type) {
return function install(openmct) {
let provider = {
supportsRequest: function (domainObject) {
return domainObject.type === desired_domain_object_type;
},
request: async function (domainObject, options) {
let url = \`/history/${domainObject.identifier.key}/${options.start}/${options.end}/${options.strategy}/${options.size}\`;
const resp = await fetch(url);
const data = await resp.json();
console.log('Got ' + data.length + ' history items for ' + domainObject.identifier.key);
return data;
}
};
openmct.telemetry.addProvider(provider);
};
}What do I get: The problem that As a result |
Beta Was this translation helpful? Give feedback.
Hi Simon,
Great to hear that your team is considering using Open MCT! Please find our responses below-- I'll also tag the POCs who can best answer any follow-ups for those specific questions.
@akhenry:
The answer to this question kind of depends on what you're using to feed the data into Open MCT. Open MCT is primarily a visualization tool, so it will display whatever data is fed into it. As long as your backend can play back historical data, Open MCT can display it. We do support a "remote clock" which can be configured…