Data Monitor
Node ID: dataMonitor · Role: Sink · Realtime config: no
Description
Internal monitoring sink that tracks data flow rates, sample counts, and quality metrics for all connected sources.
Inputs / Outputs
- Inputs: (none)
- Outputs: (none)
Config aliases
DataMonitor, dataMonitor
Properties
No user-facing properties.
Example node definition
A full node definition in config.json looks like the block below. Paste it under the sinks key of your config, keyed by the node’s instance name (any identifier; it doesn’t have to match the node ID).
{
"sinks": {
"dataMonitor": {
"inputEndpoints": [],
"settings": {}
}
}
}
Field reference
| Field | Purpose |
|---|---|
inputEndpoints | List of upstream endpoints this node connects to (outEndpoint / dataEndpoint values from upstream nodes). |
inputDataFilter | Optional whitelist of data types. Messages whose type isn’t in the list are dropped at the subscriber. |
settings | All user-configurable fields — see the Properties table above. |
Connections can also be declared at the top-level
connectionsarray whensettings.explicitConnectionsistrue, as an alternative to fillinginputEndpointson each node.
Loading documentation…