Zabbix Documentation 2.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:it_services

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:it_services [2014/09/25 15:20]
sasha Links adapted because of a move operation
manual:it_services [2015/07/28 07:35] (current)
martins-v information on service availability is being inserted into database regardless of service times
Line 47: Line 47:
 |//​Calculate SLA//  |Enable SLA calculation and display. ​ | |//​Calculate SLA//  |Enable SLA calculation and display. ​ |
 |//​Acceptable SLA (in %)//  |SLA percentage that is acceptable for this service. Used for reporting. ​ | |//​Acceptable SLA (in %)//  |SLA percentage that is acceptable for this service. Used for reporting. ​ |
-|//​Trigger// ​ |Linkage to trigger:\\ **None** - no linkage\\ **trigger name** - linked to the trigger, thus depends on the trigger status\\ Services of the lowest level must be linked to triggers. (Otherwise their state will not be represented accurately.) ​ |+|//​Trigger// ​ |Linkage to trigger:\\ **None** - no linkage\\ **trigger name** - linked to the trigger, thus depends on the trigger status\\ Services of the lowest level must be linked to triggers. (Otherwise their state will not be represented accurately.)\\ When triggers are linked, their state prior to linking is not counted. ​ |
 |//Sort order// ​ |Sort order for display, lowest comes first. ​ | |//Sort order// ​ |Sort order for display, lowest comes first. ​ |
  
Line 66: Line 66:
 ^Parameter^Description^ ^Parameter^Description^
 |//Service times// ​ |By default, all services are expected to operate 24x7x365. If exceptions needed, add new service times. ​ | |//Service times// ​ |By default, all services are expected to operate 24x7x365. If exceptions needed, add new service times. ​ |
-|//New service time// ​ |Service times:\\ **Uptime** - service uptime\\ **Downtime** - service state within this period does not affect SLA.\\ **One-time downtime** - a single downtime. Service state within this period does not affect SLA.\\ Add the respective hours.\\ //Note//: Service times affect only the service they are configured for. Thus, a parent service will not take into account the service time configured on a child service (unless a corresponding service time is configured on the parent service as well). ​ |+|//New service time// ​ |Service times:\\ **Uptime** - service uptime\\ **Downtime** - service state within this period does not affect SLA.\\ **One-time downtime** - a single downtime. Service state within this period does not affect SLA.\\ Add the respective hours.\\ //Note//: Service times affect only the service they are configured for. Thus, a parent service will not take into account the service time configured on a child service (unless a corresponding service time is configured on the parent service as well).\\ Service times are taken into account when calculating IT service status and SLA by the frontend. However, information on service availability is being inserted into database continuously,​ regardless of service times.  |
  
 === Display === === Display ===