Hi, how would I configure hosts that i want to disable host notifications (as they are rebooted a lot or shutdown) BUT I still want service notfications/alerts to be sent when they are online?
It seems using the rule ‘disable host notifications’ still sends a LOT of notifications when the servers are reboot/switched off.
Is there a rule to supress the service alerts when a server is rebooted/shutdown? I can’t see where to do this.
I already have a rule to disable host notifications that’s fine.
It’s when a server is rebooted I don’t want to be flooded with all the services going into a critical state when the host is rebooted or shutdown.
But I do want the services to alert as critical when these servers are online if that makes sense?
AI tells me this but I can’t find this rule.
I presume and it looks like from the checkmk documentation there is built in funtionality where services shouldn’t alert when a host goes down.
Is this built around the microcore or normal check intervals? As in the host microcore and normal check intervals need to be smaller than the services ones?
Hi Marc,
Thank you for your patience and explaining me the problem more in detail.
I double checked on our prod system and can confirm that there is no notification sent out for service alerts in case a host is down.
Basically an active service becomes CRITICAL but no notification is sent even that service state is HARD. Any passive service becomes stale.
You find the part in the doc here:
For now I didnt found neither a global setting nor a rule with which this method could be altered but maybe the described problem is what you are currently facing.
regards
Mike
Ok, I’ve raised then with technical support because I am getting a lot of service alerts becoming critical for hosts that I’ve configured the rule to disable host notifications for. I performed a reboot on these hosts to see what happens.
Although it may be the case just to expect service notification alerts during a reboot unless scheduled downtime has been applied?
And disabling host notifications only prevents service notifications when a host has been shutdown?
This being the case if we should expect service notifications during a reboot then maybe the way around that would be to setup the ‘cancel’ notifications rule somehow?
I tested shutting two of them down and we didn’t receive any service alerts or host alerts (which is the intended purpose).
Re-testing rebooting them.
Rebooting returned service alerts for them. So my question is this normal and expected behaviour during a reboot?
And if so is the way to prevent this then to enable service notification delays for a few minutes maybe?
Testing the rule to delay service notifications, but it isn’t ideal and I thought it was built into the intelligence to not notify on service alerts.
I setup a rule to delay service notifications by 10 minutes, but the service alerts are still coming through after a reboot.
Can you share the service events related to that particular service? In there you will find all details of what happened from the detection to the notification.
