. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 8. Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . available allowing to use the webhook media type for pushing Zabbix notifications to: • Jira • Jira Service Desk • Microsoft Teams • Redmine • ServiceNow • SIGNL4 • Telegram • Zammad • Zendesk Zabbix source host, if such information is detected in the log. Service checks on agent 2 Zabbix agent 2 items net.tcp.service[] and net.tcp.service.perf[] now support HTTPS and LDAP checks on Windows. List

件中指定的用户运行服务。 若要修改 Zabbix Agent 服务运行的用户，请创建新的文件/etc/systemd/system/zabbix-agent.service.d/override.conf 并包含以下内容： [Service] User=root Group=root 重新加载守护程序并重新启动 zabbix-agent 服务： systemctl daemon-reload systemctl edit zabbix-agent Then, add the following content: [Service] User=root Group=root Reload daemons and restart the zabbix-agent service: systemctl daemon-reload systemctl restart zabbix-agent For systemctl edit zabbix-agent2 Then, add the following content: [Service] User=root Group=root Reload daemons and restart the zabbix-agent service: systemctl daemon-reload systemctl restart zabbix-agent2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 9 Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 8 Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 1 Service tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 2 Service actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 9 Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 8 Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 1 Service tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1792 15 Service monitoring upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 9 Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1740 zabbix_web_service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 中受监控基础设施的高级视图。 Zabbix 现在有一个新的服务菜单，包含四个菜单组件： • 服务（Services） - 用于服务概述和服务配置（从 Monitoring 移动到 Services） • 服务动作（Service actions） - 用于服务动作（新操作类型） • SLA - 用于配置 SLA • SLA 报表 - 用于 SLA 报表（也可用作仪表板小部件） 下面概述了对服务功能的其他主要改进。

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 9 Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 8. Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 1 Service tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 2 Service actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 9 Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 8 Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 1 Service tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851 15 Service monitoring upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Windows platform. This affects the following Zabbix agent keys: • net.tcp.port • net.tcp.service • net.tcp.service.perf • web.page.get • web.page.perf • web.page.regexp 5.20.7 Support for IPv6 addresses udp.service and net.udp.service.perf items have been added with the possibility to check NTP service. Before Zabbix 3.0 checking of NTP service was done using net.tcp.service and net.tcp.service.perf perf items. Database upgrade patches automatically convert NTP service checks using net.tcp.service and net.tcp.service.perf to the new item. New internal checks zabbix[host„items] and zabbix[host„items_unsupported]

can itself remotely check networked services (such as web servers and mail servers) using simple service checks. The server is the central repository in which all configuration, statistical and operational package Zabbix server runs as a daemon process. The server can be started by executing: shell> service zabbix-server start This will work on most of GNU/Linux systems. On other systems you may need to stopping/restarting/viewing status, use the following commands: shell> service zabbix-server stop shell> service zabbix-server restart shell> service zabbix-server status Start up manually If the above does not

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 8. Service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . proxy. 9 What’s new in Zabbix 3.4.4 Additional Windows service startup types Since Windows Server 2008 R2 and Windows 7 several more Windows service startup types have been supported: • Automatic (Trigger is a new Windows service discovery macro - {#SERVICE.STARTUPTRIGGER}, which returns 0 if the startup type has no trigger start or 1 if the startup type has trigger start; • The service.info Windows agent