Hi, I’m not sure to understand Icinga2's behavior with downtimes.
I would say this should prevents notifications to be sent to the admins during a period that is planned for maintenance. Let's see a concrete case : We reboot a server and make a cold image (Clonezilla). a) we declare a downtime for the host in question and "All Services". b) we reboot the server c) we receive one email for the host with "DOWNTIMESTART - host is DOWN" d) we receive one email per service on the host with "DOWNTIMESTART - host - service is CRITICAL" e) we process with or without network (that depends if we drop the clonezilla image on a local or a network storage) f) when maintenance is done, we reboot the server as soon as downtime reaches the end g) we receive one email for the host with "DOWNTIMEEND - host is UP" h) we receive one email per service on the host with "DOWNTIMEEND - host - service is OK" i) we even receive some emails with "RECOVERY host - service is OK" (duplicates with h) ) That's a huge verbose for a planned downtime. What we'd expect would be a maximum of receiving the c) and g) emails ... and probably have the possibility not to receive any since we knew the problem before Icinga even found it. I've read http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/advanced-topics but couldn't find anything that could help. Are we missing something about downtime? Thanks Samuel -- Samuel Bancal ENAC-IT EPFL _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
