When creating a downtime for a host + all services, the start and end of the downtime will trigger a notification for all Downtimes, which can get super spammy.
I would like to only send one Notification for the “main” downtime, and then just have the children mentioned in the message.
I was thinking of filtering is out in the notification or the notificaiton command object, but for that i need a way to discern the different downtimes. Is there a Variable that i can use to filter out Downtimes that are Children of other downtimes?
I don’t know how things are organised at your place, but here this issue would be tricky to resolve. Let me show with an example:
Host 1 is a server with the following Services:
System disk
CPU load
Memory
HTTPS service
SSL certificate validity
Icinga check
cluster-zone check
Plus of course a (0) “hostalive” (ping) check on the Host itself.
Because of the split of responsibilities, the following downtime start/end notifications should be sent:
To the Servers team: 0, 1
To the Applications team: 0, 2, 3, 4, 5
To the PKI team: 5
To the Icinga administration team: 6, 7
To the Operations team: 0, 4
Suppose a downtime is set on the Host level. How the Service notification script can figure out whether the downtime notification for service 1/2/3/4/5/6/7 needs to be sent to each of the teams will be very difficult to establish.
So my advice would be to be very careful in capturing the business model for these notifications, and having the tools in place for the notification script to handle them.
do you use parent host definitions and the “Schedule triggered downtime for all child hosts” feature?
or is it just the host => all services trigger you use?