I have turned notifications on for my distributed set up and i am getting swamped with notifications, i have been tweaking the notification rules as I go to reduce some of the unnecessary noise.
However, i am yet to find the best way to set up a rule to send a notification when a host is rebooted.
MY current uptime rule is shown below ;
The above works to a degree, if i reboot a host it will send a notification showing a critical alert for uptime. However, is there a way to change the wording that is emailed out, for example NODE TEST123 has rebooted. It is almost like I need a description added to the rule. So, when our engineers look at the alert its clear what is happening and what the rule has alerted for. Does Anyone have any ideas or solutions that have worked for you in terms of capturing a host that rebooted?
You can replace the subject and body of an alert email, however if you make many of these rules it can become difficult to troubleshoot future issues, manage the rules, and scale out your monitor. Just a note from personal experience.
You can then scope this notification rule down as with any other CheckMK rule. It’s possible to change all your Uptime Crit in your entire environment to your desired format with the right combination of options and scoping
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.
