Zabbix has functions that will allow tracking of uptime data for use in ITIL service level agreement. This involves 2 tabs on the main screen, Configuration/Maintenance and Configuration/IT Services. Maintenance is used to define maintenance windows so that planned outages can be ignored in the calculation of service uptime and IT Services is used to consolidate ITEMS that make up a Service in ITIL terms. IT Services section also provides boolean logic that may be required to define the definition of service uptime among a group of redundant ITEM that make up a service offering.
Maintenance
Define a maintenance window name. Rice IT does not generally allow piggy backing of maintenance due to confounding problems when diagnosing post maintenance problems. Each window should be defined around a service if possible i.e. Calendar,Owlspace, Exchange, Cyrus, Stoarge ....etc. As a general rule, the service maintenance window is defined around a number of criteria. Low utilization time frame as documented from usage trending (available in Zabbix), campus impact and off hour support availability. Maintenance windows are a pre-defined reservation for maintenance work, but they do not have to be used only set aside in case they are needed.
IT recommends that data collection be allowed during a maintenance window. Notifications should be turned off during actual outages.
Define the active dates for the maintenance window
Add Maintenance periods
Include all HOSTS that provide the service or groups that will be involved in the maintenance
IT Services