Why we can´t set notifications like this:
if error send notification and only send a notification after state is gone to ok.
Now we have to setup a notification for warning AND error - so we have two notifications. Also we have notifications if the state is no longer in warning or error.
So we got two notifications if a sensor goes from warning to error or from error to warning.
"sensor state warning ended (now error)" "sensor state error (before: warning)"
the warning ended ist not needed if it goes to error. We only need a notification if it goes back to OK.
Article Comments
Why don't you use Threshold triggers instead of State triggers then? There are many type of sensors that can rapidly change from warning to error and back sometimes, especially networking sensors during peak hour.
Threshold Sensors can tell you if something happened regardless of the state of the sensor itself - For example - I ahve a WMI sensor that follows the size of a certain log file - and whenever that file reaches a certain size, I get a mail - the sensor only changes to error if I lose connection with the machine or tot he file I'm monitoring - in which case but even then I don't get state change notification as I didn't set one up.
If you can tell me exactly what are you trying to configure, maybe I can help you out.
Feb, 2015 - Permalink
Hello,
Thank you for your KB-Post. While you do have a point (every now and then, the current system may create a notification too much), the system behind the notifications already if very complex, and we do not want to make it even more complex with fixed "target states". So there are no changes planned for this, sorry.
best regards.
Feb, 2015 - Permalink