Alerting Too Early?

[mkeey]

Coded our Monitoring for Memory to execute every 10 minutes. It will recheck every 5 minutes and Alert after 24 times. The Warning is set at 15 and the Critical is set to 5 (see screen print "Thresholds").

Yet the monitors appear in the Service Problems display.

Shouldn't the monitor wait until 1 hour before issuing the alert?

[scottwilkerson]

It waits to send a notification, but it will still show it's current status in the UI and be in a SOFT state. After all your retries, it will send a notification and change into a HARD state.

[mkeey]

Thank you... that was my assumption. But, you know what happens when you assume!
Follow up question, can you prevent the service from appearing in the service problems display? AKA don't do anything until all the retries are exhausted.

[scottwilkerson]

Thank you... that was my assumption. But, you know what happens when you assume!
Follow up question, can you prevent the service from appearing in the service problems display? AKA don't do anything until all the retries are exhausted.

No this is not possible, simply because the truth is, the plugin did return a non-OK state

[scottwilkerson]

On the "Operations Center" screen you can select a filter to hide soft states, which would accomplish your goal

[mkeey]

Thanks - not quite what I was looking for, but I'll see what the business says. Thanks for the help & please close the case as resolved.