Introduction
Shinken allows you to schedule periods of planned downtime for hosts and check that you're monitoring. This is useful in the event that you actually know you're going to be taking a server down for an upgrade, etc.
Scheduling Downtime
You can schedule downtime with your favorite UI or as an external command in cli.
Once you schedule downtime for a host or check, Shinken will add a comment to that host/check indicating that it is scheduled for downtime during the period of time you indicated. When that period of downtime passes, Shinken will automatically delete the comment that it added. Nice, huh?
Enterprise permet de définir la planification de périodes de mise sous maintenance des hôtes et checks que vous supervisez.
Planifier une maintenance
Vous pouvez le faire soit dans l'UI du portail soit en ligne de commande en .cli.
Dès qu'une maintenance est planifiée, un commentaire sera visible sur l'hôte ou le check. Celui-ci sera automatiquement supprimée dès que la période sera passée.
How Scheduled Downtime Affects Notifications
When a host or check is in a period of scheduled downtime, Shinken will not allow normal notifications to be sent out for the host or check. However, a "DOWNTIMESTART" notification will get sent out for the host or check, which will serve to put any admins on notice that they won't receive upcoming problem alerts.
...
If the scheduled downtime is cancelled prematurely (before it expires), a "DOWNTIMECANCELLED" notification will get sent out to the appropriate admins.
Overlapping Scheduled Downtime
I like to refer to this as the "Oh crap, its not working" syndrome. You know what I'm talking about. You take a server down to perform a "routine" hardware upgrade, only to later realize that the OS drivers aren't working, the RAID array blew up, or the drive imaging failed and left your original disks useless to the world. Moral of the story is that any routine work on a server is quite likely to take three or four times as long as you had originally planned...
...