Hi,
We have had a configuration for CheckMK working for a long time, however, we are always trying to improve our standard configuration.
We tried to change from retry checks and number of checks before sending notifications to “Delay notifications”
The delay is 10 minutes.
Now we are bombarded with OK messages to our pagerduty integration. This is noise and annoying for our 24/7 which are spammed during the night with OK messages.
Can I get some help fixing this issue? I dont understand why OK is being sent out, instead of silencing the Crit/warn messages.
Hi Elias (great first name, by the way 
)
can you share the configuration of your notification rule here?
Thanks
Elias
1 Like
Hello!
Great name indeed, likewise
This is our 24/7 notification rules.
Further information:
Previously, when an OK is sent out, it resolves and alarm in pagerduty, but sometimes (like now) its not working, and instead is alerting that an event is OK (which we dont want).
I guess this is the culprit:
Why this does not cancel a previous alert, I don’t know. I don’t know if something changed regarding PagerDuty notifications on our side, or maybe on Pagerduty side.
A quick search in our Werks did not show any recent changes.
1 Like
Hi,
I believe Any - > Up and Crit → OK is needed to tell pagerduty that this incident is resolved?
How else is PD notified about the change?
Is there a chance the issues lies on checkmk alerting on the OK, but not the crit before? (as if the alarm is resolved before checkmk sends alert)
1 Like
Is there a chance the issues lies on checkmk alerting on the OK, but not the crit before?
I don’t know, but logically that would make sense. If there is no alert to update, then a new one is created…
1 Like
Are you aware of a setting that prevents OK unless crit or warn has been sent?
