Trace an MQTT telemetry path
Diagnose publisher, broker, consumer and timestamp issues without mistaking transport for quality.
Before using this guide
Confirm your site, role and source revision. Follow the local procedure and responsible engineer for physical actions.
Trace the path
- Identify the publishing gateway and approved topic convention.
- Check broker connectivity and certificate status.
- Compare source, gateway and server timestamps and sequence numbers.
- Inspect consumer lag, duplicate handling and the last good quality state.
- Verify the value in the Nexus snapshot and Historian.
Meaning
A delivered MQTT message confirms transport, not sensor calibration, unit correctness or freshness. Keep those checks separate.
Source references
These official references provide additional context. Confirm the current edition and your site requirements.