Inspect incoming telemetry
Purpose
Section titled “Purpose”Telemetry viewer captures a short diagnostic window and compares decoded incoming values with processing and storage evidence.
Before you start
Section titled “Before you start”You need device viewing and management permissions. Choose a gateway and optionally an onboarded device. Captures are temporary, not a historical archive.
- Open Telemetry viewer, choose a gateway, and start a 1, 5, or 10 minute capture.
- In Live stream, filter topics, metrics, values, or message types and select a packet.
- Use Processing stages to inspect mappings, conversion, validation, derived readings, and persistence.
- Pause view freezes the list while capture continues; Follow newest returns to recent packets.
- Use AI troubleshoot only when you want the selected sample and processing evidence explained. Export JSON if you need to retain evidence.
Expected result
Section titled “Expected result”You can compare the received metric with its processing result. stored means the observation/diagnostic transaction committed; decoding alone does not prove storage.
Troubleshooting
Section titled “Troubleshooting”pending is a handoff in progress, storage_retry is a retryable storage failure, and discarded means storage did not accept the batch. Raw here means received by the platform; it cannot reconstruct values before gateway-side processing. Captures expire and old messages leave the buffer.