Why do my hosts send a notification when set to downtime after being added freshly and waiting for the periodic service discovery to run and activate services?

Hey guys, it’s me, the guy who is trying to achive a stateless deploy with checkmk-raw.
I have found a really strange problem, which would like to fix before our setup goes productive.
I add hosts during API in a deploy script.
Then those hosts exist in the monitoring, and a service discovery is executed. In the next 5 minutes, the periodic service discovery runs and adds all new services and labels.
During this time, the hosts send a notification, that looks like this:
image

Now I can silence the notifications for the Check_MK service, but this is just wrong. My idea was to set all hosts I add through the deploy script in downtime, which works. A 10-minute downtime is scheduled and set during the discovery period, it shows up on each host when I click on downtimes of this host.

But the notification is sent anyway.

How can I stop this when those hosts are freshly added?

checkmk-raw
2.1.0p25


Both hosts send such a notification, before all services are added. No matter if set to downtime or not.

I just tend to silence the Check_MK notifications for our dev instance. Our prd instance is not sending notifications when Check_MK alerts, because we decided to go host only.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.