1 min read

Note: debugging a tricky reading bug

[template]

Symptom: the dashboard showed occasional spikes that the machines were not actually producing.

Cause: the collector was counting a duplicate reading as a new one whenever the hardware resent a value.

Fix: I deduplicated on the reading timestamp before storing anything.

Lesson: when data looks wrong, suspect the ingestion path before the display. That is where the noise usually enters.