The Zephyr agent (Aeolus) publishes periodic telemetry with system metrics every telemetry_interval seconds (src/telemetry/telemetry.c):
[
{"n":"temperature","u":"Cel","v":22.7},
{"n":"humidity","u":"%RH","v":48.3},
{"n":"pressure","u":"hPa","v":1003.4}
]
The Linux agent is purely command-driven — it only publishes responses to commands. There is no periodic telemetry.
What to implement:
- Optional periodic telemetry publish (disabled by default)
- Linux-relevant system metrics:
- CPU usage percentage
- Memory used/free
- Disk usage
- Uptime
- Network interface stats
- Configurable interval via
MG_AGENT_TELEMETRY_INTERVAL env var
- Publish to telemetry topic in SenML format
- Enable/disable via config
Reference: Aeolus telemetry module — src/telemetry/telemetry.c, docs/telemetry.md
The Zephyr agent (Aeolus) publishes periodic telemetry with system metrics every
telemetry_intervalseconds (src/telemetry/telemetry.c):[ {"n":"temperature","u":"Cel","v":22.7}, {"n":"humidity","u":"%RH","v":48.3}, {"n":"pressure","u":"hPa","v":1003.4} ]The Linux agent is purely command-driven — it only publishes responses to commands. There is no periodic telemetry.
What to implement:
MG_AGENT_TELEMETRY_INTERVALenv varReference: Aeolus telemetry module —
src/telemetry/telemetry.c,docs/telemetry.md