Data Quality
Telemetry quality codes, device liveness, and adapter health.
Every telemetry event carries a quality field. The console uses quality and recency to show whether data is trustworthy.
Quality values
| Quality | Meaning |
|---|---|
| GOOD | Normal reading |
| BAD | Invalid or failed read |
| UNCERTAIN | Questionable value |
| TIMEOUT | Read timed out |
| DISCONNECTED | Source unreachable |
| CONFIG_ERROR | Tag or connection misconfiguration |
Quality appears in UNS Explorer, Operations Center timeline, and stored history.
Device liveness (CONNECTED)
A device shows CONNECTED when any tag on that device received telemetry within the last 15 seconds. If telemetry stops:
- Check adapter orchestrator status (RUNNING, ERROR, NOT_IMPLEMENTED)
- Verify network and connection config
- See No telemetry troubleshooting
Adapter status vs CONNECTED
| Signal | What it tells you |
|---|---|
| Orchestrator RUNNING | In-process driver process is up |
| CONNECTED | Data actually arriving at the platform |
| ERROR | Driver failed — check logs |
| NOT_IMPLEMENTED | No live driver — pick another adapter or use external iot/ |