Embedded engineer with 7 years of industry experience and a passion for developer tools. Worked at Pebble and Fitbit helping them ship and maintain millions of wearable devices running RTOS-level firmware. Now a co-founder at Memfault, which is building monitoring tools for the IoT space. You can find some of the articles I've written at: https://interrupt.memfault.com/blog/authors/tyler/.
Monitoring IoT Devices At Scale
I'd like to talk about how companies should think about and build out their IoT monitoring solutions using metrics. The differences between logs, metrics, and traces have been talked about at length in the software engineering space, but not for firmware. Using metrics to monitor a fleet of devices allows for assessing the health of thousands to millions of devices, even across groups of devices or firmware versions, all while keeping complexity, bandwidth, and power consumption to a minimum.Takeaways:
- Know how to think about and build a metrics library for gathering compressed and aggregated metrics on devices
- Understand the differences between logs, metrics, and traces, and why using metrics is the best way to monitor fleets of devices post-deployment.
- Know the next steps on how to ingest the data in a server under their control to do monitoring analysis.
- Learn some formulas for calculating fleet health, such as expected battery life, crash free hours, and average connectivity per hour.