en	# 8 Service monitoring
zh-cn	# 8. 服务监控

en	#### Overview Service monitoring is a business-level monitoring that can be used to get an overview of the entire IT infrastructure service tree, identify weak places of the infrastructure, calculate SLA of various IT services, and check out other information at a higher level. Service monitoring focuses on the overall availability of a service instead of low-level details, such as the lack of disk space, high processor load, etc. Service monitoring also provides functionality to find the root cause of a problem if a service is not performing as expected. Service monitoring allows to create a hierarchy representation of monitored data. A very simple service structure may look like: Service | |-Workstations | | | |-Workstation1 | | | |-Workstation2 | |-Servers Each node of the structure has attribute status. The status is calculated and propagated to upper levels according to the selected algorithm. The status of individual nodes is affected by the status of the mapped problems. Problem mapping is accomplished with [tagging](/manual/it_services/service_tree#problem-tags). Zabbix can send notifications or automatically execute a script on the Zabbix server in case service status change is detected. It is possible to define flexible rules whether a parent service should go into a 'Problem state' based on the statuses of child services. Services problem data can then be used to calculate SLA and send SLA reports based on the flexible set of conditions. Service monitoring is configured in the Services menu, which consists of the following sections: - [Services](/manual/it_services/service_tree) Services section allows to build a hierarchy of your monitored infrastructure by adding parent services, and then - child services to the parent services. In addition to configuring service tree, this section provides an overview of the whole infrastructure and allows to quickly identify the problems that led to a service status change. - [SLA](/manual/it_services/sla) In this section you can define service level agreements and set service level objectives for specific services. - [SLA report](/manual/it_services/sla#sla-reports) In this section you can view SLA reports. **Service actions** You may also configure service [actions](/manual/config/notifications/action). Service actions are optional and allow to: - send a notification that a service is down - execute a remote command on a Zabbix server upon a service status change - send a recovery notification when a service is up again. **See also:** - SLA monitoring configuration [example](/manual/it_services/example) - Notes about [upgrading services](/manual/appendix/services_upgrade) from Zabbix versions below 6.0
zh-cn	#### 概览 服务监控，作为业务级别的监控功能，可以帮助用户获得有关IT设施的整体服务架构信息、鉴别设施的薄弱之处、计算多种IT服务的SLA以及具备在更高层级查看更多信息的能力。相较于一些基础信息，诸如硬盘空间的不足，处理器过载等，业务监控更专注于业务的整体可用性。若一项业务并没有如用户所期望的那样正常运转，服务监控功能同样可以帮助用户找到引发问题的根本原因。 服务监控具备对监控数据创建层级展示的能力。 如下所示，展示了一个非常简单的服务结构： Service | |-Workstations | | | |-Workstation1 | | | |-Workstation2 | |-Servers 在上述结构中的每个节点都具备属性状态。这些属性状态都是通过筛选的算法经过计算并传输至更高层级的。各个节点的状态受映射问题状态的影响而问题映射是通过 [标签](/manual/it_services/service_tree#problem-tags)来实现的。 如果检测到服务状态发生变化，Zabbix 可以在 Zabbix server 上发送通知或自动执行脚本。用户可以根据子服务的状态来灵活定义父服务是否应该进入 '问题状态' 。服务问题数据可以用来计算 SLA 并灵活的设定发送 SLA 报告的条件。 业务监控在 Services（服务） 菜单中配置，该菜单由以下部分组成： - [Services](/manual/it_services/service_tree) （服务） 服务板块允许通过添加父服务来构建用户所监控的基础架构的层次结构，然后将子服务添加至父服务中。 除了配置服务树之外，本板块还提供了整体基础架构的概述，并允许快速识别导致服务状态更改的问题。 - [SLA](/manual/it_services/sla) 在本板块中，用户可以定义服务等级协议并为特定服务设置服务等级目标。 - [SLA report](/manual/it_services/sla#sla-reports)（SLA报告） 在此板块，用户可以查看 SLA 报告。 **服务动作** 用户同样可以配置服务[动作](/manual/config/notifications/action)。 服务动作作为可选功能具备： - 当服务宕掉则发送通知； - 当服务状态发生改变可以在 Zabbix 服务器端远程执行命令； - 当服务恢复则发送恢复通知。 **可参考内容：** - SLA监控监控配置[示例](/manual/it_services/example) - 若用户所使用的 Zabbix 的版本低于6.0at=refs%2Fheads%2Frelease%2F7.0](https://git.zabbix.com/projects/WEB/repos/documentation/browse/en/manual/it_services.md?at=refs%2Fheads%2Frelease%2F7.0)，请参考有关[升级服务](/manual/appendix/services_upgrade) 的内容。