HTTP code 503 immediately notified without check attempts

Troubleshooting
12

Solution found, based on the info in this post;

I had my rule “Notified events for services” set to “Service goes into critical state”
When my service goes to critical and after a few checks to OK, the CMC is not notified about this so the SERVICENOTIFICATIONNUMBER was still at x and was never reset.

I updated the rule “Notified events for services” and added “Service goes into OK state”
I triggered an CRIT and after a few times service was OK and now the SERVICENOTIFICATIONNUMBER was reset to 1.
Triggered an error again and now it started 3 check attempts and then notification.

Finally solved my issue.

1 Like