The Difference Between Monitoring and Arbitration (And Why It's Costing You)

There is a distinction in IoT reliability engineering that I rarely see discussed clearly, and I think the lack of clarity around it is responsible for a significant percentage of production incidents that get misdiagnosed as hardware failures. The distinction is between monitoring and arbitration. Monitoring Monitoring tells you what your devices reported. It captures events, logs state changes, triggers alerts when thresholds are crossed, and gives you a dashboard showing the last known status of every device in your fleet. Monitoring is well understood. The tooling is mature. Most production IoT stacks have some version of it. Arbitration Arbitration tells you what your devices' state actually was. That sounds like the same thing. It is not. Arbitration is the process of taking multiple signals — a reported status, a timestamp, a signal strength reading, a sequence number, a reconnect window — and determining which combination of those signals represents ground truth. It handles the