CMK version: 2.5.0p5
what is best-practice to prevent short living issues (Warning) for a specific service?
I’ve a Teams notification setup, and the service Warning is just for 2 minutes.
Given that I get:
and 2 minutes later OK:
at the moment I set the service check interval to 6 hours, but this doesn’t solve the problem.
here’s the event history:
any idea how to catch this?
The relevant settings are Delayed Host/Service Notification and/or Maximum Number of Check Attempts for Service. I typically rely on the former, configuring the Delayed Service Notification to, for example, 5 minutes. If a service returns to an OK state within that window, no notification will be triggered.
A similar effect can be achieved by adjusting the number of check attempts.
I’d recommend leaving the check interval unchanged and configuring the notification settings accordingly.
perfect! thanks, will try this way ..
I prefer the “Maximum Number of Check Attempts for Service” with soft/hard state.
When using “Delayed Host/Service Notification”, you have to keep in mind that OK messages could be sent without any preceding NOT-OK events because of the notification delay for the NOT-OK state.
thank you Lars for this tipp. I’ll watch this closely if the OK notifications is sent w/o a Warning or Crit before
