Yes, I was a bit hasty with undetected. The situation is complex.
I have a site which has sensors that go off for various reasons. I add heartbeats to detect this. Now I have a site with sensors that may go off for a number of reasons, and an alert panel telling me they are off all the time.
As the alerts aren't actionable (ie, I expect sensor Y to go off every day in the winter around midnight and come back again when it warms up) I add a filter to ignore the alert from it around midnight.
I now have to make sure I handle all the other edge cases - how long is it safe to have this sensor off? 50% of the sensors off? Every third sensor off? What if there is a really cold/hot snap lasting through the day or several days?
All of these questions are edge cases, and they require complexity to solve them. Complexity means bugs. The most common bug by far is that situation X was detected by the sensor, but didn't make its way to us for edge cases.
I have a site which has sensors that go off for various reasons. I add heartbeats to detect this. Now I have a site with sensors that may go off for a number of reasons, and an alert panel telling me they are off all the time.
As the alerts aren't actionable (ie, I expect sensor Y to go off every day in the winter around midnight and come back again when it warms up) I add a filter to ignore the alert from it around midnight.
I now have to make sure I handle all the other edge cases - how long is it safe to have this sensor off? 50% of the sensors off? Every third sensor off? What if there is a really cold/hot snap lasting through the day or several days?
All of these questions are edge cases, and they require complexity to solve them. Complexity means bugs. The most common bug by far is that situation X was detected by the sensor, but didn't make its way to us for edge cases.