![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
On 2014-04-23 02:12, Bastiaan Topper wrote:
Hi,
We have 2 strange things with the alerting system since a few days.
The frontpage displays ports up/down, even when the alerting for that port is disabled in the device settings. Is this normal? Because this wasn't till a few days ago.
This should be fixed now.
Some alert checks worked fine for months, but now they fail. (I only have the database output, because the http://observium/alert_checks/ [1] links returns a blank page, maybe because the result is too big?):
I attached the debug poll of one of the devices. The polling debug output returns:
Checking alert 4 associated by 4
replaced @sensor_limit with 5.92 from entity. Testing: sensor_value greater 5.92 (value: 5.187) FAIL replaced @sensor_limit_low with 4.37 from entity. Testing: sensor_value less 4.37 (value: 5.187) OK Checks failed. Generate alert.
What I expect (and what it did for the last months) this alert rule to do, is to fail when the sensor value is not between the threshold ranges. It looks like it is only for the voltage and current sensors.
When I check the settings and alerting thresholds, they look fine to me.
Am I doing something wrong? Or is this some kind of bug?
I'm not sure why this is happening. I there were some changes to the parsing of the "less/greater/etc" part of the test, but it looks ok and works fine for me.
You probably need to increase the amount of memory PHP is allowed to use to see the entire alert_checks page.
adam.