en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |Debian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=9_stretch&db=mysql)| |Debian 8 (Jessie)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=8_jessie&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian (Buster)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=raspbian&os_version=10_buster&db=mysql)| |Raspbian (Stretch)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=raspbian&os_version=9_stretch&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.  ::: noteimportant Zabbix 5.4 is not released yet. The download links lead to pre-5.4 packages. :::  
zh-cn	### 概述  Zabbix官方软件包适用于：  |   |   | |---|---| |Debian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=9_stretch&db=mysql)| |Debian 8 (Jessie)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=debian&os_version=8_jessie&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian (Buster)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=raspbian&os_version=10_buster&db=mysql)| |Raspbian (Stretch)|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=raspbian&os_version=9_stretch&db=mysql)|  安装包适用于 MySQL/PostgreSQL 数据库和 Apache/Nginx 网络服务器支持.  ::: noteimportant Zabbix 6.0 还未发布。下载链接转至5.4版本。 :::

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |Debian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11_bullseye&db=mysql)| |Debian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=9_stretch&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11_bullseye&db=mysql)| |Raspbian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10_buster&db=mysql)| |Raspbian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=9_stretch&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.
zh-cn	### 概述  官方 Zabbix 软件包可用于：  |   |   | |---|---| |Debian 11 (Bullseye)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11_bullseye&db=mysql)| |Debian 10 (Buster)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=9_stretch&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian 11 (Bullseye)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11_bullseye&db=mysql)| |Raspbian 10 (Buster)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10_buster&db=mysql)| |Raspbian 9 (Stretch)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=9_stretch&db=mysql)|  软件包可用于 MySQL/PostgreSQL 数据库和 Apache/Nginx 网络服务器支持。  ::: Attention Zabbix 6.2 尚未发布。下载链接指向 6.2 之前的软件包。 ::: 

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |Debian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11_bullseye&db=mysql)| |Debian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=9_stretch&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian 11 (Bullseye)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11_bullseye&db=mysql)| |Raspbian 10 (Buster)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10_buster&db=mysql)| |Raspbian 9 (Stretch)|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=9_stretch&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.  ::: noteimportant Zabbix 6.0 is not released yet. The download links lead to pre-6.0 packages. :::  
zh-cn	＃＃＃ 概述  官方 Zabbix 软件包可用于：  | | | |---|---| |Debian 11 (Bullseye)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=11_bullseye&db=mysql)| |Debian 10 (Buster)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=10_buster&db=mysql)| |Debian 9 (Stretch)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=debian&os_version=9_stretch&db=mysql)| |Ubuntu 20.04 (Focal Fossa) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=20.04_focal&db=mysql)| |Ubuntu 18.04 (Bionic Beaver) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=18.04_bionic&db=mysql)| |Ubuntu 16.04 (Xenial Xerus) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=16.04_xenial&db=mysql)| |Ubuntu 14.04 (Trusty Tahr) LTS|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=ubuntu&os_version=14.04_trusty&db=mysql)| |Raspbian 11 (Bullseye)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=11_bullseye&db=mysql)| |Raspbian 10 (Buster)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=10_buster&db=mysql)| |Raspbian 9 (Stretch)|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=raspberry_pi_os&os_version=9_stretch&db=mysql)|  软件包可用于 MySQL/PostgreSQL 数据库和Apache/Nginx 网络服务器支持。  ::: 注意 Zabbix 6.0 尚未发布。下载链接链至6.0 之前的软件包。 :::  

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |RHEL 8, CentOS 8 and Oracle Linux 8|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.  ::: noteimportant Zabbix 6.0 is not released yet. The download links lead to pre-5.4 packages. :::  ::: noteclassic  *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) doesn't work on RHEL 7 with MySQL due to older MySQL libraries.  :::  *Zabbix ​agent* packages and utilities *Zabbix get* and *Zabbix sender* are available for [RHEL 7](https://​repo.zabbix.com/​zabbix/​5.4/​rhel/​7/​x86_64/​), [RHEL 6](https://​repo.zabbix.com/​zabbix/​5.4/​rhel/​6/​x86_64/​) and [RHEL 5](https://​repo.zabbix.com/zabbix/​5.4/​rhel/​5/​x86_64) as well.  Zabbix official repository provides fping and libssh2 packages as well. These packages are located in the [non-supported](https://repo.zabbix.com/non-supported/) directory.  
zh-cn	### 概述  Zabbix官方发行包适用于:  |   |   | |---|---| |RHEL 8, CentOS 8 和 Oracle Linux 8|[Download](https://www.zabbix.com/download?zabbix=5.4&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  软件包适用于 MySQL/PostgreSQL 数据和Apache/Nginx 网络服务器支持.  ::: noteimportant Zabbix 6.0版本还未发布。下载链接目前转至5.4版本。 :::  ::: noteclassic 由于旧版本MySQL库不支持 *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) 在MySQL RHEL 7中无法运行。  :::  *Zabbix ​agent* 包和实用程序 *Zabbix get* and *Zabbix sender* 适用于 [RHEL 7](https://​repo.zabbix.com/​zabbix/​5.4/​rhel/​7/​x86_64/​), [RHEL 6](https://​repo.zabbix.com/​zabbix/​5.4/​rhel/​6/​x86_64/​) 和 [RHEL 5](https://​repo.zabbix.com/zabbix/​5.4/​rhel/​5/​x86_64) 。  Zabbix 官方存储库还提供fping和libssh2包。 这些包可在此查询[non-supported](https://repo.zabbix.com/non-supported/) 。  

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |RHEL 8, CentOS 8 and Oracle Linux 8|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.  ::: noteclassic  *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) doesn't work on RHEL 7 with MySQL due to older MySQL libraries.  :::  *Zabbix agent* packages and utilities *Zabbix get* and *Zabbix sender* are available for [RHEL 7](https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/), [RHEL 6](https://repo.zabbix.com/zabbix/6.0/rhel/6/x86_64/) and [RHEL 5](https://repo.zabbix.com/zabbix/6.0/rhel/5/x86_64) as well.  Zabbix official repository provides fping and libssh2 packages as well. These packages are located in the [non-supported](https://repo.zabbix.com/non-supported/) directory.
zh-cn	### 概述  官方 Zabbix 软件包可用于：  |   |   | |---|---| |RHEL 8, CentOS 8 and Oracle Linux 8|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  软件包可用于 MySQL/PostgreSQL 数据库和 Apache/Nginx 网络服务器支持。  ::: Attention Zabbix 6.2 尚未发布。下载链接指向 6.2 之前的软件包。 :::   ::: noteclassic 由于 MySQL 库较旧，验证 *Verify CA* [加密模式](/manual/appendix/install/db_encrypt/mysql)不适用于带有 MySQL 库的 RHEL 7。 :::  *Zabbix agent* 软件包和实用程序 *Zabbix get* 和 *Zabbix sender* 也可用于 [RHEL 7](https://repo.zabbix.com/zabbix/6.0/rhel/7/x86_64/)、[RHEL 6](https://repo.zabbix.com/zabbix/6.0/rhel/6/x86_64/) 和 [RHEL5](https://repo.zabbix.com/zabbix/6.0/rhel/5/x86_64)。  Zabbix 官方仓库也提供 fping 和 libssh2 包。这些包位于[不受支持的](https://repo.zabbix.com/non-supported/) 目录中。

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |RHEL 8, CentOS 8 and Oracle Linux 8|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.  ::: noteimportant Zabbix 6.0 is not released yet. The download links lead to pre-6.0 packages. :::  ::: noteclassic  *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) doesn't work on RHEL 7 with MySQL due to older MySQL libraries.  :::  *Zabbix agent* packages and utilities *Zabbix get* and *Zabbix sender* are available for [RHEL 7](https://repo.zabbix.com/zabbix/5.5/rhel/7/x86_64/), [RHEL 6](https://repo.zabbix.com/zabbix/5.5/rhel/6/x86_64/) and [RHEL 5](https://repo.zabbix.com/zabbix/5.5/rhel/5/x86_64) as well.  Zabbix official repository provides fping and libssh2 packages as well. These packages are located in the [non-supported](https://repo.zabbix.com/non-supported/) directory.  
zh-cn	### 概述  官方Zabbix软件包可应用于：  |   |   | |---|---| |RHEL 8, CentOS 8 和 Oracle Linux 8|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8&db=mysql)|  软件包可用于 MySQL/PostgreSQL 数据库和Apache/Nginx 网络服务器支持。  ::: 注意 Zabbix 6.0 还未发布。下载链接会链至6.0之前的版本。 :::  ::: 注意  *验证 CA* [加密模式](/manual/appendix/install/db_encrypt/mysql) 在RHEL 7上不适用 根据旧的MySQL库，可使用MySQL。 :::  *Zabbix agent* 包和实用程序 *Zabbix get* 和 *Zabbix sender* 可用于 [RHEL 7](https://repo.zabbix.com/zabbix/5.5/rhel/7/x86_64/), [RHEL 6](https://repo.zabbix.com/zabbix/5.5/rhel/6/x86_64/) 和 [RHEL 5](https://repo.zabbix.com/zabbix/5.5/rhel/5/x86_64) 。  Zabbix 官方仓库也提供 fping 和 libssh2 包。 这些软件包位于 [不支持](https://repo.zabbix.com/non-supported/) 目录。  

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |SUSE Linux Enterprise Server 15|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=15&db=mysql)| |SUSE Linux Enterprise Server 12|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=12&db=mysql)|  ::: noteclassic  *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) doesn't work on SLES 12 (all minor OS versions) with MySQL due to older MySQL libraries.  :::
zh-cn	### 概述  官方 Zabbix 软件包可用于：  |   |   | |---|---| |SUSE Linux 企业服务器 15|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=15&db=mysql)| |SUSE Linux 企业服务器12|[下载](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=12&db=mysql)|  ::: noteclassic 由于 MySQL 库较旧，验证 *Verify CA* [加密模式](/manual/appendix/install/db_encrypt/mysql)不适用于带有 MySQL库 的 SLES 12 （和所有次要操作系统版本） 。   :::

en-us	### Overview  Official Zabbix packages are available for:  |   |   | |---|---| |SUSE Linux Enterprise Server 15|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=15&db=mysql)| |SUSE Linux Enterprise Server 12|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=12&db=mysql)|  ::: noteimportant Zabbix 6.0 is not released yet. The download links lead to pre-6.0 packages. :::  ::: noteclassic  *Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) doesn't work on SLES 12 (all minor OS versions) with MySQL due to older MySQL libraries.  :::  
zh-cn	### 概述  Zabbix官方包适用于：  |   |   | |---|---| |SUSE Linux Enterprise Server 15|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=15&db=mysql)| |SUSE Linux Enterprise Server 12|[Download](https://www.zabbix.com/download?zabbix=6.0&os_distribution=suse_linux_enterprise_server&os_version=12&db=mysql)|  ::: 注意 Zabbix 6.0 还未发布。 下载链接目前链至6.0之前的版本。 :::  ::: 注意 由于旧版本MySQL库不支持*Verify CA* [encryption mode](/manual/appendix/install/db_encrypt/mysql) 在SLES 12 （所有次要操作系统版本）中不支持。  :::  

en-us	#### Overview of files  If you obtained Java gateway from sources, you should have ended up with a collection of shell scripts, JAR and configuration files under $PREFIX/sbin/zabbix\_java. The role of these files is summarized below.      bin/zabbix-java-gateway-$VERSION.jar  Java gateway JAR file itself.      lib/logback-core-0.9.27.jar     lib/logback-classic-0.9.27.jar     lib/slf4j-api-1.6.1.jar     lib/android-json-4.3_r3.1.jar  Dependencies of Java gateway: [Logback](http://logback.qos.ch/), [SLF4J](http://www.slf4j.org/), and [Android JSON](https://android.googlesource.com/platform/libcore/+/master/json) library.      lib/logback.xml       lib/logback-console.xml  Configuration files for Logback.      shutdown.sh       startup.sh  Convenience scripts for starting and stopping Java gateway.      settings.sh  Configuration file that is sourced by startup and shutdown scripts above.
zh-cn	#### 文件概述  如果你从源码中获得Java网关，那么您最终会得到 $PREFIX/sbin/zabbix_java 下的Shell脚本、JAR和配置文件的集合。这些文件的作用总结如下。      bin/zabbix-java-gateway-$VERSION.jar  Java 网关自身JAR 文件。      lib/logback-core-0.9.27.jar     lib/logback-classic-0.9.27.jar     lib/slf4j-api-1.6.1.jar     lib/android-json-4.3_r3.1.jar  Java 网关依赖于: [Logback](http://logback.qos.ch/), [SLF4J](http://www.slf4j.org/), 和[Android JSON](https://android.googlesource.com/platform/libcore/+/master/json) 库。      lib/logback.xml       lib/logback-console.xml  Logback的配置文件。      shutdown.sh       startup.sh  用于启动和停止Java网关的便捷脚本。      settings.sh  用于控制上述启动和停止脚本的配置文件。

en-us	### Overview  Once the [services](/manual/it_services/services_tree) are created, you can start monitoring whether their performance is on track with service level agreement (SLA).    *Services->SLA* menu section allows to configure SLAs for various services. An SLA in Zabbix defines service level objective (SLO), expected uptime schedule and planned downtimes.   SLAs and services are matched by [service tags](/manual/it_services/services_tree#tags). The same SLA may be applied to multiple services - performance will be measured for each matching service separately. A single service may have multiple SLAs assigned - data for each of the SLAs will be displayed separately.  In SLA reports Zabbix provides Service level indicator (SLI) data, which measures real service availability. Whether a service meets the SLA targets is determined by comparing SLO (expected availability in %) with SLI (real-life availability in %). 
zh-cn	### 概述  创建 [服务](/manual/it_services/services_tree) 后, 就可以开始监控其性能是否满足服务级别协议(SLA)。    可以在*服务->SLA* 界面配置SLA。SLA定义了服务级别目标(SLO)、预期正常运行时间和计划内的停机时间。  SLA和服务通过 [服务标签](/manual/it_services/services_tree#tags)匹配。同一个SLA可用于多个服务 - 其中每个服务的性能会进行分别测量。单一服务可以匹配多个SLA - 其中每个SLA的数据会各自独立显示。  SLA报告包含服务级别指标(SLI)数据，该数据表示实际的服务可用性。把SLO(预期的可用性，以百分比%显示)和SLI(真实的可用性，以百分比%显示)进行比较，可以确定服务是否满足SLA目标。

en-us	### Overview  Packages for minor Zabbix version (i.e. Zabbix 6.0.x) release candidates are provided starting with Zabbix 6.0.9.  The instructions below are for enabling unstable Zabbix release repositories (disabled by default).  First, install or update to the latest zabbix-release package. To enable rc packages on your system do the following:
zh-cn	### 概述  从 Zabbix 6.0.9 开始提供次要 Zabbix 版本（即 Zabbix 6.0.x）候选发布包。  以下说明用于启用不稳定的 Zabbix 发布存储库（默认情况下禁用）。  首先，安装或更新到最新的 zabbix-release 包。 要在您的系统上启用 rc 包，请执行以下操作：

en-us	#### Overview  [Perl Compatible Regular Expressions](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions) (PCRE, PCRE2) are supported in Zabbix.  There are two ways of using regular expressions in Zabbix:  -   manually entering a regular expression -   using a global regular expression created in Zabbix
zh-cn	#### 概述  Zabbix支持 [Perl兼容正则表达式](https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expressions)（PCRE, PCRE2）。  Zabbix 中使用正则表达式有两种方式：  -   手动输入正则表达式 -   使用在 Zabbix 中创建的全局正则表达式

en-us	### Overview  Plugins provide an option to extend the monitoring capabilities of Zabbix. Plugins are written in Go programming language and are supported by Zabbix agent 2 only.  Plugins provide an alternative to [loadable modules](/manual/config/items/loadablemodules) (written in C), and other methods for extending Zabbix functionality, such as [user parameters](userparameters) (agent metrics), [external checks](/manual/config/items/itemtypes/external) (agent-less monitoring), and `system.run[]` Zabbix [agent item](/manual/config/items/itemtypes/zabbix_agent).  The following features are specific to Zabbix agent 2 and its plugins:  -   support of scheduled and flexible intervals for both passive and     active checks; -   task queue management with respect to schedule and task concurrency; -   plugin-level timeouts; -   compatibility check of Zabbix agent 2 and its plugin on start up.  Since Zabbix 6.0.0, plugins don't have to be integrated into the agent 2 directly and can be added as loadable plugins, thus making the creation process of additional plugins for gathering new monitoring metrics easier.  This page lists Zabbix native and loadable plugins, and describes plugin configuration principles from the user perspective. For instructions about writing your own plugins, please see [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/en/plugins).
zh-cn	#### 概览  插件提供了扩展Zabbix监控功能的选项。插件是用 Go 语言编写的，并且只有 Zabbix agent2 支持。  插件提供了[可加载模块](/manual/config/items/loadablemodules) (由 C 编写)，以及其他扩展 Zabbix 功能的方法，例如 [用户参数](用户参数)(agent指标),[外部检查](/manual/config/items/itemtypes/external) (无代理监控)和`system.run[]` Zabbix [agent监控项](/manual/config/items/itemtypes/zabbix_agent)。  以下功能特定于agent 2 及其插件：  -   被动、主动检查都支持定期和灵活采集间隔； -   与调度和任务并发相关的任务队列管理； -   插件级超时； -   Zabbix agent 2 及其插件在启动时的兼容性检查。  从 Zabbix 6.0.0 开始，插件不必直接集成到agent2 中，并且可以作为单独的外部插件添加，从而使得创建额外的插件来收集新的监控指标更加容易。  本页列出了 Zabbix 原生插件，并从用户角度描述了插件配置原则。有关编写自己的插件的说明，请参阅[插件开发指南](https://www.zabbix.com/documentation/guidelines/en/plugins)。

en-us	#### Overview  Plugins provide an option to extend the monitoring capabilities of Zabbix. Plugins are written in the Go programming language and are supported by Zabbix agent 2 only.  Plugins provide an alternative to [loadable modules](/manual/config/items/loadablemodules) (written in C), and other methods for extending Zabbix functionality, such as [user parameters](userparameters) (agent metrics), [external checks](/manual/config/items/itemtypes/external) (agent-less monitoring), and `system.run[]` Zabbix [agent item](/manual/config/items/itemtypes/zabbix_agent).  The following features are specific to agent 2 and its plugins:  -   support of scheduled and flexible intervals for both passive and     active checks; -   task queue management with respect to schedule and task concurrency; -   plugin-level timeouts.  
zh-cn	#### Overview  Plugins provide an option to extend the monitoring capabilities of Zabbix. Plugins are written in the Go programming language and are supported by Zabbix agent 2 only.  Plugins provide an alternative to [loadable modules](/manual/config/items/loadablemodules) (written in C), and other methods for extending Zabbix functionality, such as [user parameters](userparameters) (agent metrics), [external checks](/manual/config/items/itemtypes/external) (agent-less monitoring), and `system.run[]` Zabbix [agent item](/manual/config/items/itemtypes/zabbix_agent).  The following features are specific to agent 2 and its plugins:  -   support of scheduled and flexible intervals for both passive and     active checks; -   task queue management with respect to schedule and task concurrency; -   plugin-level timeouts.  

en-us	#### Overview  Preprocessing allows to define transformation rules for the received item values. One or several transformations are possible before saving to the database.  Transformations are executed in the order in which they are defined. Preprocessing is done by Zabbix server or proxy (if items are monitored by proxy).  Note that all values passed to preprocessing are of the string type, conversion to desired value type (as defined in item configuration) is performed at the end of the preprocessing pipeline; conversions, however, may also take place if required by the corresponding preprocessing step. See [preprocessing details](/manual/config/items/preprocessing/preprocessing_details) for more technical information.  See also: [Usage examples](/manual/config/items/preprocessing/examples)
zh-cn	#### 概述  预处理允许为接收到的监控项值定义转换规则。 在将值保存到数据库之前，可以进行一次或多次转换。   转换按照它们定义的顺序执行。预处理是由Zabbix server或者Zabbix proxy (如果监控项通过proxy进行监控)执行。  请注意，转换成所需要的值类型是在预处理步骤的后期执行的，如果有需要，转换也可以进行相应的预处理步骤。详见 [preprocessing details](/manual/config/items/preprocessing/preprocessing_details)了解更多技术细节。  还可以参考: [Usage examples](/manual/config/items/preprocessing/examples)

en-us	#### Overview  Preprocessing allows to define transformation rules for the received item values. One or several transformations are possible before saving to the database.  Transformations are executed in the order in which they are defined. Preprocessing is done by Zabbix server or proxy (if items are monitored by proxy).  Note that the conversion to desired value type (as defined in item configuration) is performed at the end of the preprocessing pipeline; conversions, however, may also take place if required by the corresponding preprocessing step. See [preprocessing details](/manual/config/items/preprocessing/preprocessing_details) for more technical information.  See also: [Usage examples](/manual/config/items/preprocessing/examples)
zh-cn	#### 概述  预处理允许为接收到的监控项值定义转换规则。 在将值保存到数据库之前，可以进行一次或多次转换。   转换按照它们定义的顺序执行。预处理是由Zabbix server或者Zabbix proxy (如果监控项通过proxy进行监控)执行。  请注意，转换成所需要的值类型是在预处理步骤的后期执行的，如果有需要，转换也可以进行相应的预处理步骤。详见 [preprocessing details](/manual/config/items/preprocessing/preprocessing_details)了解更多技术细节。  还可以参考: [Usage examples](/manual/config/items/preprocessing/examples)

en-us	#### Overview  Problem events in Zabbix can be acknowledged by users.  If a user gets notified about a problem event, they can go to Zabbix frontend, open the problem update popup window of that problem using one of the ways listed below and acknowledge the problem. When acknowledging, they can enter their comment for it, saying that they are working on it or whatever else they may feel like saying about it.  This way, if another system user spots the same problem, they immediately see if it has been acknowledged and the comments so far.  This way the workflow of resolving problems with more than one system user can take place in a coordinated way.  Acknowledgment status is also used when defining [action operations](/manual/config/notifications/action/operation). You can define, for example, that a notification is sent to a higher level manager only if an event is not acknowledged for some time.  To acknowledge events and comment on them, a user must have at least read permissions to the corresponding triggers. To change problem severity or close problem, a user must have read-write permissions to the corresponding triggers.  There are **several** ways to access the problem update popup window, which allows acknowledging a problem.  -   You may select problems in *Monitoring* → *Problems* and then click     on *Mass update* below the list -   You can click in the *Ack* column showing the acknowledgment status     of problems in:     -   *Monitoring → Dashboard* (*Problems* and *Problems by severity*         widgets)     -   *Monitoring → Problems*     -   *Monitoring → Problems → Event details*  The *Ack* column contains either a 'Yes' or a 'No' link, indicating an acknowledged or an unacknowledged problem respectively. Clicking on the links will take you to the problem update popup window.  -   You can click on an unresolved problem cell in:     -   *Monitoring → Dashboard* (*Trigger overview* widget)  The popup menu contains an *Acknowledge* option that will take you to the problem update window.
zh-cn	#### 概览  Zabbix中的问题事件可以由用户确认。  如果用户收到关于问题事件的通知，他可以转到Zabbix前端，使用下面列出的方式之一打开该问题的问题更新弹出窗口并确认问题。同时他们可以输入对这条事件的评论，说他们正在处理或者任何他们想说的内容。  通过这种方式，如果另一个系统用户发现了相同的问题，他们就会立即看到这个问题是否得到了确认以及到目前为止的评论。  这样，与多个系统用户协同解决问题的工作流程便得以进行。  确认状态也可以被定义 [动作操作](/manual/config/notifications/action/operation)。例如你可以定义，仅当事件在一段时间内未得到确认时才向更高级别的管理员发送通知。  要确认事件并对其进行评论，用户必须至少对相应的触发器具有读权限。 若要更改问题的严重性或关闭问题，用户必须对相应的触发器具有读写权限。  有以下 **几种** 方式来访问问题更新窗口，该窗口允许确认问题。  -   可以在 *监控(Monitoring)*→*问题(Problems)* 中选择问题，然后点击列表下方的 *批量更新(Mass update)* -   你可以点击 *Ack* 列显示问题的确认状态:     -   *监控(Monitoring ) → 仪表盘(Dashboard)* （*问题(Problems)* 和 *问题等级(Problems by severity)* 组件）     -   *监控(Monitoring) → 问题(Problems)*     -   *监控(Monitoring)→ 问题(Problems)→ 事件详细信息(Event details)*  *Ack* 列包含 “Yes” 或“No” 链接，分别表示已确认或未确认的问题。 点击这些链接会跳转到问题更新弹出窗口。  -   你可以单机未解决的问题单元格:     -   *监控(Monitoring)→ 仪表盘(Dashboard)* （*触发器概览(Trigger overview)* 组件）  弹出菜单包含一个 *确认(Acknowledge)* 选项，可跳转至问题更新窗口。

en-us	#### Overview  Receiving notifications on unsupported items is supported since Zabbix 2.2.  It is part of the concept of internal events in Zabbix, allowing users to be notified on these occasions. [Internal events](/manual/config/events/sources#internal-events) reflect a change of state:  -   when items go from 'normal' to 'unsupported' (and back) -   when triggers go from 'normal' to 'unknown' (and back) -   when low-level discovery rules go from 'normal' to 'unsupported'     (and back)  This section presents a how-to for **receiving notification** when an item turns unsupported.
zh-cn	#### 概述  从 Zabbix 2.2 开始支持接收关于不受支持的监控项的通知。  它是 Zabbix 内部事件概念的一部分，允许在这些场合通知用户。 [内部事件](/manual/config/events/sources#internal-events) 反映了状态的变化：  - 当监控项从“正常”变为“不受支持”（并返回） - 当触发器从“正常”变为“未知”（并返回） - 当底层自动发现规则从“正常”变为“不受支持”（并返回）  本节介绍如何在监控项变得不受支持时**接收通知**。

en-us	#### Overview  Receiving SNMP traps is the opposite to querying SNMP-enabled devices.  In this case, the information is sent from an SNMP-enabled device and is collected or "trapped" by Zabbix.  Usually, traps are sent upon some condition change and the agent connects to the server on port 162 (as opposed to port 161 on the agent side that is used for queries). Using traps may detect some short problems that occur amidst the query interval and may be missed by the query data.  Receiving SNMP traps in Zabbix is designed to work with **snmptrapd** and one of the mechanisms for passing the traps to Zabbix - either a Bash or Perl script or SNMPTT.  ::: noteclassic The simplest way to set up trap monitoring after configuring Zabbix is to use the Bash script solution, because Perl and SNMPTT are often missing in modern distributions and require more complex configuration. However, this solution uses a script configured as `traphandle`. For better performance on production systems, use the embedded Perl solution (either script with `do perl` option or SNMPTT). :::  The workflow of receiving a trap:  1.  `snmptrapd` receives a trap 2.  `snmptrapd` passes the trap to the receiver script (Bash, Perl)      or SNMPTT 3.  The receiver parses, formats and writes the trap to     a file 4.  Zabbix SNMP trapper reads and parses the trap file 5.  For each trap Zabbix finds all "SNMP trapper" items with host     interfaces matching the received trap address. Note that only the     selected "IP" or "DNS" in host interface is used during the     matching. 6.  For each found item, the trap is compared to regexp in     `snmptrap[regexp]`. The trap is set as the value of **all**     matched items. If no matching item is found and there is an     `snmptrap.fallback` item, the trap is set as the value of that. 7.  If the trap was not set as the value of any item, Zabbix by default     logs the unmatched trap. (This is configured by "Log unmatched SNMP     traps" in Administration → General → Other.)
zh-cn	#### 概述  接收 SNMP 陷阱与查询启用 SNMP 的设备相反。  在这种情况下，信息是从支持 SNMP 的设备发送的，并且是被 Zabbix 收集或“捕获”。  通常，在某些条件更改时会发送陷阱，并且客户端的 162端口 连接到服务器（与用于查询客户端的端口 161 不同）。使用陷阱可能会检测到在查询间隔中发生的一些短期问题，并且可能会遗漏查询数据。  在 Zabbix 中接收 SNMP 陷阱要与 **snmptrapd** 一起使用，以及将snmp陷阱传递给 Zabbix 的机制之一，Bash 或 Perl 脚本或 SNMPTT 。  ::: noteclassic 配置Zabbix后设置trap监控最简单的方法是使用Bash脚本方案，因为Perl和SNMPTT在现代发行版中经常缺失，需要更复杂的配置。但是，该方案使用配置为`traphandle`的脚本。为了在生产系统上获得更好的性能，请使用嵌入式 Perl 解决方案（带有“do perl”选项的脚本或 SNMPTT）。 ::::  接收陷阱的工作流程：  1. `snmptrapd` 收到陷阱 2. `snmptrapd` 将陷阱传递给接收器脚本（Bash、Perl）或 SNMPTT 3. 接收方解析、格式化并将trap写入文件 4. Zabbix SNMP trapper读取并解析trap文件 5. 对于每个陷阱，Zabbix 会找到主机接口与接收到的陷阱地址匹配的所有“SNMP trapper”监控项。 请注意，在匹配过程中，只会使用在主机界面中选择的“IP”或“DNS”。 6. 对于每个找到的项目，将陷阱与 `snmptrap[regexp]` 中的正则表达式进行比较。陷阱设置为 **all** 的匹配的监控项值。如果没有找到匹配的监控项并且有“snmptrap.fallback”监控项，陷阱设置为那个值。 7. 如果陷阱没有设置为任何项的值，Zabbix 默认记录不匹配的陷阱。 （这是通过管理 → 一般 → 其他中的“记录不匹配的 SNMP 陷阱”配置的。）

en-us	### Overview  Recovery operations allow you to be notified when problems are resolved.  Both messages and remote commands are supported in recovery operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously.
zh-cn	### 概述  恢复操作允许您在问题得到解决时收到通知。  恢复操作支持消息和远程命令。 虽然可以添加多个操作，但不支持升级 - 所有操作都分配给一个步骤，因此将同时执行。

en-us	#### Overview  Sending a message is one of the best ways of notifying people about a problem. That is why it is one of the primary actions offered by Zabbix.  
zh-cn	#### 概述   Zabbix 提供发送消息作为主要操作之一的原因是，发送消息是通知人们有关某问题的最佳方式。

en-us	#### Overview  Server - proxy data exchange is based on JSON format.  Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen).
zh-cn	#### 概述  Server - proxy 数据交换基于 JSON 格式.  请求和响应消息必须以[header头部与数据长度](/manual/appendix/protocols/header_datalen)开头.

en-us	#### Overview  Service monitoring functionality is intended for those who want to get a high-level (business) view of monitored infrastructure. In many cases, we are not interested in low-level details, like the lack of disk space, high processor load, etc. What we are interested in is the availability of service provided by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information of a higher level.  Zabbix service monitoring provides answers to all mentioned questions.  Services is 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. Mapping to problems is done using tags.  
zh-cn	# 8. Service monitoring  ::: noteimportant Zabbix 4.0.0 正式版目前，暂未发布，敬请期待，目前阶段\*\* alpha9\*\* 。 :::  

en-us	#### 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. Since Zabbix 6.0, 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.   - [Service actions](/manual/it_services/service_actions)  In this section you can configure service actions. 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.  - [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_report)  In this section you can view SLA reports.   **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 基础设施的薄弱环节、各种 IT 服务的 SLA、现有 IT 基础设施的结构以及其他更高级别的信息。  Zabbix 服务监控为所有提到的问题提供了答案。  服务监控允许创建监控数据的层次结构表示。  一个非常简单的服务结构可能如下所示：      Service     |     |-Workstations     | |     | |-Workstation1     | |     | |-Workstation2     |     |-Servers  结构的每个节点都有属性状态。根据所选算法计算状态并将其传输到上层。各个节点的状态受映射问题状态的影响。问题映射是通过 [标签](/manual/it_services/service_tree#problem-tags) 完成的。  如果检测到服务状态发生变化，Zabbix 可以在 Zabbix server 上发送通知或自动执行脚本。可以根据子服务的状态来定义父服务是否应该进入 '问题状态' 的灵活规则。然后可以使用服务问题数据来计算 SLA 并根据灵活的条件集发送 SLA 报告。  服务监控在 Services 菜单中配置，该菜单由以下部分组成：  - [Services（服务）](/manual/it_services/service_tree)   服务部分允许通过添加父服务来构建受监控基础架构的层次结构，然后将子服务添加到父服务。  除了配置服务树之外，本节还提供了整个基础架构的概述，并允许快速识别导致服务状态更改的问题。  - [Service actions（服务动作）](/manual/it_services/service_actions)  在本节中，您可以配置服务动作。服务动作是可选的，并允许： - 发送服务宕机的通知； - 在服务状态发生变化时在 Zabbix server 上执行远程命令； - 当服务再次启动时发送恢复通知。  - [SLA](/manual/it_services/sla)  在本节中，您可以定义服务水平协议并为特定服务设置服务水平目标。  - [SLA report（SLA报告）](/manual/it_services/sla_report)  在此部分中，您可以查看 SLA 报告。  **可以参照：**     - SLA 监控配置 [示例](/manual/it_services/example)   - Zabbix 6.0以下版本 [升级服务](/manual/appendix/services_upgrade) 注意事项

en-us	#### Overview  Several configuration [parameters](/manual/appendix/config/zabbix_server) define how Zabbix server should behave when an agent check (Zabbix, SNMP, IPMI, JMX) fails and a host interface becomes unreachable.
zh-cn	#### 概述  当agent检查(Zabbix, SNMP, IPMI, JMX)失败并且主机变得不可达时，一些配置  [参数](/manual/appendix/config/zabbix_server) 定义了 Zabbix server 作何反应。

en-us	#### Overview  Simple checks are normally used for remote agent-less checks of services.  Note that Zabbix agent is not needed for simple checks. Zabbix server/proxy is responsible for the processing of simple checks (making external connections, etc).  Examples of using simple checks:      net.tcp.service[ftp,,155]     net.tcp.service[http]     net.tcp.service.perf[http,,8080]     net.udp.service.perf[ntp]  ::: noteclassic *User name* and *Password* fields in simple check item configuration are used for VMware monitoring items; ignored otherwise. :::
zh-cn	#### 概述  简单检查通常用于检查远程未安装Zabbix agent的服务。  请注意，简单检查不需要Zabbix agent，由Zabbix server和Zabbix proxy来负责处理（例如创建外部连接等）。  简单检查使用示例:      net.tcp.service[ftp,,155]     net.tcp.service[http]     net.tcp.service.perf[http,,8080]     net.udp.service.perf[ntp]  ::: noteclassic 在简单检查项的配置中，*User name* 和 *Password*字段用于Vmware的监控项；非VMware监控项则可忽略。 :::

en-us	#### Overview  Simple graphs are provided for the visualization of data gathered by items.  No configuration effort is required on the user part to view simple graphs. They are freely made available by Zabbix.  Just go to *Monitoring → Latest data* and click on the Graph link for the respective item and a graph will be displayed.  ![](../../../../../assets/en/manual/config/simple_graph.png){width="600"}  ::: noteclassic Simple graphs are provided for all numeric items. For textual items, a link to History is available in *Monitoring → Latest data*. :::
zh-cn	#### 概览  提供了简单的图表，用于可视化监控项收集的数据。  用户部分无需配置工作即可查看简单图表。它们由 Zabbix 免费提供。  只需转到 *监控→ 最新数据* 并单击图表 链接将显示相应的监控项和图表。  ![](../../../../../assets/en/manual/config/simple_graph.png){width="600"}  ::: noteclassic 为所有数值型监控项提供了简单的图表。为了文本监控项，历史链接在 *监控 → 最新数据*中是可用的。 :::

en-us	### Overview  Since Zabbix 6.0, primary keys are used for all tables in  new installations.  This section provides instructions for manually upgrading the history tables in existing installations to primary keys.  Instructions are available for:  * [MySQL](#mysql) * [PostgreSQL](#postgresql) * [TimescaleDB](#postgresql-timescaledb) * [Oracle](#oracle)
zh-cn	#### 概述  自Zabbix 6.0起，主键会应用于新安装 Zabbix 数据库的所有表。  在这之前安装过的Zabbix，本章节将提供手动升级所有表主键的说明。  此章节适用于如下数据库:  * [MySQL](#mysql) * [PostgreSQL](#postgresql) * [TimescaleDB](#postgresql-timescaledb) * [Oracle](#oracle)

en-us	#### Overview  Some new items are automatically added for monitoring when web scenarios are created.  All items inherit tags from the web scenario.
zh-cn	#### 概述  创建 Web 场景时会自动添加一些新的监控项以进行监控。  所有监控项都从 Web 场景继承标签。

en-us	#### Overview  Sometimes there are signs of the upcoming problem. These signs can be spotted so that actions may be taken in advance to prevent or at least minimize the impact of the problem.  Zabbix has tools to predict the future behavior of the monitored system based on historic data. These tools are realized through predictive trigger functions.
zh-cn	#### 概述  有时会有即将出现问题的迹象。可以通过这些迹象，来提前采取措施防止或至少将问题的影响降至最低。  Zabbix 有可以根据历史数据预测被监控系统未来行为的工具。这些工具是通过预测触发功能实现的。

en-us	#### Overview  Sometimes you may want to change some attribute for a number of hosts at once. Instead of opening each individual host for editing, you may use the mass update function for that.
zh-cn	#### 概述  有时你可能想要一次更改多个主机的某些属性。那么你可以使用批量更新功能来实现，而不是打开每个主机页面进行编辑。

en-us	#### Overview  Sometimes you may want to change some attribute for a number of items at once. Instead of opening each individual item for editing, you may use the mass update function for that.
zh-cn	#### 概览  有时你可能想要一次更改多个监控项的某些属性。你可以使用批量更新功能，而不是打开每个独立的监控项进行编辑。\

en-us	#### Overview  Sometimes you may want to change some attribute for a number of templates at once. Instead of opening each individual template for editing, you may use the mass update function for that.
zh-cn	 #### 概览  有时您可能想要同时更改多个模板的某些属性。您可以使用批量更新功能，无需打开每个模板进行独立编辑。

en-us	#### Overview  SSH checks are performed as agent-less monitoring. Zabbix agent is not needed for SSH checks.  To perform SSH checks Zabbix server must be initially [configured](/manual/installation/install#from_the_sources) with SSH2 support (libssh2 or libssh). See also: [Requirements](/manual/installation/requirements#server).  ::: noteimportant Only libssh is supported starting with RHEL 8. :::
zh-cn	#### 概述  SSH检查作为一种agent-less 监控，不依赖于Zabbix agent执行。  要执行SSH检查，Zabbix服务器必须首先[配置](/manual/installation/install#from_the_sources) SSH2支持(libssh2或libssh)。参考:[要求](/manual/installation/requirements#server)。  ::: noteimportant 从RHEL 8 开始只支持libssh.  :::

en-us	### Overview  Starting from version 5.0, Zabbix frontend requires PHP version 7.2 or later. Unfortunately, older versions of Debian & Ubuntu provide only PHP versions below 7.2.
zh-cn	### 概述  自Zabbix 5.0 版本开始，Zabbix 前端需 PHP 7.2 及以上版本。 不幸的是，老版本的 Debian 和 Ubuntu 只提供 PHP 低于 7.2 的版本。

en-us	#### Overview  Support of monitoring VMware environments is available in Zabbix starting with version 2.2.0.  Zabbix can use low-level discovery rules to automatically discover VMware hypervisors and virtual machines and create hosts to monitor them, based on pre-defined host prototypes.  The default dataset in Zabbix offers several ready-to-use templates for monitoring VMware vCenter or ESX hypervisor.  The minimum required VMware vCenter or vSphere version is 5.1.
zh-cn	#### 概述  Zabbix 从 2.2.0 版开始支持对 VMware 环境的监控。  Zabbix 可以使用低级别发现规则自动发现 VMware 宿主机（即 VMware hypervisors）和虚拟机，并根据预定义的主机原型创建主机来监控它们。  Zabbix 中的默认数据集提供了几个现成的模板，用于监控 VMware vCenter 或 ESX 宿主机。  所需的最低 VMware vCenter 或 vSphere 版本为 5.1。

en-us	#### Overview  Telnet checks are performed as agent-less monitoring. Zabbix agent is not needed for Telnet checks.
zh-cn	#### 概述  Telnet检查不需要安装Zabbix agent，可对未安装代理的主机进行监控。

en-us	#### Overview  Templates are [exported](/manual/xml_export_import) with many related objects and object relations.  Template export contains:  -   linked host groups -   template data -   linkage to other templates -   linkage to host groups -   directly linked items -   directly linked triggers -   directly linked graphs -   directly linked dashboards -   directly linked discovery rules with all prototypes -   directly linked web scenarios -   value maps
zh-cn	 #### 概览  模板 [导出](/manual/xml_export_import) 带有许多相关对象和对象关系。  模板导出包含:  -   被链接的主机群组 -   模板数据 -   链接到其他模板 -   链接到其它主机群组 -   直接链接监控项 -   直接链接触发器 -   直接链接图形 -   直接链接仪表盘 -   直接链接自动发现规则及其所有原型（监控项原型、触发器原型、图形原型等等） -  直接链接web监控场景 -  值映射

en-us	### Overview  The *Administration → Authentication* section allows to specify the global user authentication method to Zabbix and internal password requirements. The available methods are internal, HTTP, LDAP, and SAML authentication.
zh-cn	### 概述  *Administration → Authentication* 部分允许指定Zabbix 的全局用户认证方法和内部密码要求。 可用internal、HTTP、LDAP 和 SAML方式进行验证。 

en-us	#### Overview  The *Administration → General* section contains a number of subsections for setting frontend-related defaults and customizing Zabbix.  The list of available subsections appears upon pressing on *General* in the *Administration* menu section. It is also possible to switch between subsections by using the title dropdown in the top left corner.
zh-cn	#### 概述  *Administration → General* 部分包含许多子部分，用于设置与前端相关的默认值和自定义 Zabbix。  按下 *Administration* 菜单部分中的 *General* 后，可用子部分的列表出现。 也可以使用左上角的标题下拉菜单在小节之间切换。

en-us	#### Overview  The Administration menu is for administrative functions of Zabbix. This menu is available to users of [Super Administrators](/manual/config/users_and_usergroups/permissions) type only.
zh-cn	#### 概述  管理主菜单用于 Zabbix 的管理功能。 此菜单仅适用于 [超级管理员组](/manual/config/users_and_usergroups/permissions) 类型的用户。

en-us	#### Overview  The aggregation functions, available in the graph widget of the dashboard, allow displaying an aggregated value for the chosen interval (5 minutes, an hour, a day), instead of all values.  The aggregation options are as follows:  -   min -   max -   avg -   count -   sum -   first (first value displayed) -   last (last value displayed)  The most exciting use of data aggregation is the possibility to create nice side-by-side comparisons of data for some period:  ![](../../../../../assets/en/manual/config/visualization/aggregate_graph.png){width="600"}  When hovering over a point in time in the graph, date and time is displayed, in addition to items and their aggregated values. Items are displayed in parentheses, prefixed by the aggregation function used. Note that this is the date and time of the point in the graph, not of the actual values.
zh-cn	#### 概述  在仪表板中的图形组件中可用的聚合函数，允许显示所选间隔的聚合值（5 分钟、一小时、一天），而不是所有值。  聚合选项如下：  - 最小 - 最大 - 平均 - 计数 - 总和 - 第一个（显示的第一个值） - 最后一个（显示的最后一个值）  数据聚合最令人兴奋的用途是可以对一段时间内的并行数据进行比较:：  ![](../../../../../assets/en/manual/config/visualization/aggregate_graph.png){width="600"}  将鼠标悬停在图表中的某个时间点上时，会显示日期和时间，监控项及其聚合值。监控项是显示在括号中，括号前面是对应的聚合函数。请注意，这是图中的日期和时间，而不是实际时间。

en-us	#### Overview  The Configuration menu contains sections for setting up major Zabbix functions, such as hosts and host groups, data gathering, data thresholds, sending problem notifications, creating data visualization and others.
zh-cn	#### 概述  “配置”菜单包含设置Zabbix的主要功能，例如主机和主机组，数据收集，数据阈值，发送问题通知，创建数据可视化等。

en-us	#### Overview  The custom graph list for a host can be accessed from *Configuration → Hosts* by clicking on *Graphs* for the respective host.  A list of existing graphs is displayed.  ![](../../../../../../assets/en/manual/web_interface/graphs_conf.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the custom graph, displayed as a blue link to graph details.<br>Clicking on the graph name link opens the graph [configuration form](/manual/config/visualization/graphs/custom#configuring_custom_graphs).<br>If the host graph belongs to a template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph list on the template level.<br>If the graph has been created from a graph prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the graph prototype list.| |*Width*|Graph width is displayed.| |*Height*|Graph height is displayed.| |*Graph type*|Graph type is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Info*|If the graph is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|  To configure a new graph, click on the *Create graph* button at the top right corner.
zh-cn	#### 概述  主机的自定义图形列表可在*配置→主机*中点击相应主机的*Graphs*查看。  显示现有图形的列表。 ![](../../../../../../assets/en/manual/web_interface/graphs_conf.png){width="600"}  显示数据:  |列|描述是| |------|-----------| |*名称*|自定义图形名称，以蓝色链接显示，链接到图形的详细信息。<br>点击图形名称链接打开图形[配置窗体](/manual/config/visualization/graphs/custom#configuring_custom_graphs)。<br>如果主机图属于某个模板，则模板名以灰色链接显示在图名前面。单击模板链接将打开模板级的图形列表。<br>如果图是从图原型创建的，它的名称前面是低级发现规则名称，用橙色表示。单击发现规则名称将打开图形原型列表| |*宽度*|显示图形的宽度| |*高度*|显示图形高度| |*图类型*|显示图类型- *正常*、*堆叠*、*饼状*或*分解*| |*信息*|图形正常时，此列无图标。如果出现错误，则会显示一个带有字母“i”的方形图标。将鼠标悬停在图标上可以看到一个带有错误描述的工具提示。|  若要配置新图形，请单击右上角的“*创建图形”按钮。

en-us	#### Overview  The custom graph list for a template can be accessed from *Configuration → Templates* by clicking on *Graphs* for the respective template.  A list of existing graphs is displayed.  ![](../../../../../../assets/en/manual/web_interface/template_graphs.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Template*|Template the graph belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the custom graph, displayed as a blue link to graph details.<br>Clicking on the graph name link opens the graph [configuration form](/manual/config/visualization/graphs/custom#configuring_custom_graphs).<br>If the graph is inherited from another template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph list on that template level.| |*Width*|Graph width is displayed.| |*Height*|Graph height is displayed.| |*Graph type*|Graph type is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.|  To configure a new graph, click on the *Create graph* button at the top right corner.
zh-cn	#### 概述  模板的自定义图形列表可以通过*配置→模板*点击相应模板的*图形*来访问。  显示现有图形的列表。  ![](../../../../../../assets/en/manual/web_interface/template_graphs.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*模板*|图所属模板。<br>当过滤框中选择了多个模板时，此字段才会显示 |*Name*|Name of the custom graph, displayed as a blue link to graph details.<br>Clicking on the graph name link opens the graph [configuration form](/manual/config/visualization/graphs/custom#configuring_custom_graphs).<br>If the graph is inherited from another template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph list on that template level.| |*名称*|自定义图形名称，显示为蓝色链接，指向图形的详细信息。<br>点击图形名称链接打开图形[配置表单](/manual/config/visualization/graphs/custom#configuring_custom_graphs)。<br>如果该图是从其他模板继承的，则模板名以灰色链接显示在图名前面。单击模板链接将打开该模板级别的图形列表 |*Width*|Graph width is displayed.| |*Height*|Graph height is displayed.| |*Graph type*|Graph type is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.|  To configure a new graph, click on the *Create graph* button at the top right corner.  |*宽度*|显示图形的宽度| |*高度*|显示图形高度| |*图类型*|显示图类型- *正常*、*堆叠*、*饼状*或*分解*|  若要配置新图形，请单击右上角的“*创建图形”按钮。

en-us	#### Overview  The expressions used in [triggers](/manual/config/triggers) are very flexible. You can use them to create complex logical tests regarding monitored statistics.  A simple expression uses a **function** that is applied to the item with some parameters. The function returns a result that is compared to the threshold, using an operator and a constant.  The syntax of a simple useful expression is `function(/host/key,parameter)<operator><constant>`.  For example:        min(/Zabbix server/net.if.in[eth0,bytes],5m)>100K  will trigger if the number of received bytes during the last five minutes was always over 100 kilobytes.  While the syntax is exactly the same, from the functional point of view there are two types of trigger expressions:  -   problem expression - defines the conditions of the problem -   recovery expression (optional) - defines additional conditions of     the problem resolution  When defining a problem expression alone, this expression will be used both as the problem threshold and the problem recovery threshold. As soon as the problem expression evaluates to TRUE, there is a problem. As soon as the problem expression evaluates to FALSE, the problem is resolved.  When defining both problem expression and the supplemental recovery expression, problem resolution becomes more complex: not only the problem expression has to be FALSE, but also the recovery expression has to be TRUE. This is useful to create [hysteresis](#hysteresis) and avoid trigger flapping.
zh-cn	 #### 概览  [triggers(触发器)](/manual/config/triggers) 中使用的表达式非常灵活。 您可以使用它们来创建复杂的逻辑测试 监控统计。  一个简单的表达式使用 **function（函数）** 应用于监控项的 一些参数。该函数返回一个与阈值比较后的结果，使用运算符和常数。  一个简单有用的表达式的语法是 `function(/host/key,parameter)<operator><constant>`.  例如:        min(/Zabbix server/net.if.in[eth0,bytes],5m)>100K 如果在最后五分钟期间接收到的网络字节数最小值超过 100 KB 将触发。  虽然语法完全相同，但从功能的角度来看 有两种类型的触发器表达式：  -  问题表达 - 定义问题的条件 -  恢复表达式（可选） - 定义附加条件 问题解决  当单独定义问题表达式时，该表达式将同时用作问题阈值和问题恢复阈值。只要问题表达式的计算结果为TRUE，就会出现问题。只要问题表达式的计算结果为FALSE，问题就解决了。  当定义问题表达式和补充恢复表达式时，问题解决将变得更加复杂:不仅问题表达式必须为FALSE，而且恢复表达式也必须为TRUE。这对于创建[hysteresis滞后](#hysteresis)和避免触发器振荡非常有用。

en-us	#### Overview  The graph widget provides a modern and versatile way of visualizing data collected by Zabbix using a vector image drawing technique. This graph widget is supported since Zabbix 4.0. Note that the graph widget supported before Zabbix 4.0 can still be used as [Graph (classic)](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic).
zh-cn	＃＃＃＃ 概述  图表组件提供了一种现代的、多功能的方式，借助矢量图像绘制技术将Zabbix收集的数据可视化。这个图表组件从Zabbix 4.0开始被支持。请注意，Zabbix 4.0之前支持的图表部件仍然可以作为[图表（经典）](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph_classic)使用。

en-us	#### Overview  The header is present in all request and response messages between Zabbix components.  It is required to determine the message length, if it is compressed or not, if it is a large packet or not.  Zabbix communications protocol has 1GB packet size limit per connection. The limit of 1GB  is applied to both the received packet data length and the uncompressed data length.  When sending configuration to Zabbix proxy, the packet size limit is increased to 4GB to allow  syncing large configurations. When data length before compression exceeds 4GB, Zabbix server automatically  starts using the large packet format (0x04 flag) which increases the packet size limit to 16GB.  Note that while a large packet format can be used for sending any data, currently only the Zabbix proxy  configuration syncer can handle packets that are larger than 1GB.
zh-cn	#### 概述  标头存在于Zabbix组件之间的所有请求和响应消息中。需要确定消息长度，是否压缩，是否为大数据包。  Zabbix 通信协议每个连接的数据包大小限制为 1GB。 1GB 的限制适用于接收到的数据包数据长度和未压缩的数据长度。  将配置发送到 Zabbix 代理时，数据包大小限制增加到 4GB 以允许同步大型配置。 当压缩前的数据长度超过 4GB 时，Zabbix 服务器自动开始使用大数据包格式（0x04 标志），将数据包大小限制增加到 16GB。  请注意，虽然大数据包格式可用于发送任何数据，但目前只有 Zabbix 代理配置同步器可以处理大于 1GB 的数据包。

en-us	#### Overview  The Inventory menu features sections providing an overview of host inventory data by a chosen parameter as well as the ability to view host inventory details.
zh-cn	#### 概览  "资产清单"菜单的特点是，通过选择的参数提供主机资产数据的概览，以及查看主机资产详细信息的能力。

en-us	#### Overview  The *Inventory → Overview* section provides ways of having an overview of [host inventory](/manual/config/hosts/inventory) data.  For an overview to be displayed, choose host groups (or none) and the inventory field by which to display data. The number of hosts corresponding to each entry of the chosen field will be displayed.  ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  The completeness of an overview depends on how much inventory information is maintained with the hosts.  Numbers in the *Host count* column are links; they lead to these hosts being filtered out in the *Host Inventories* table.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}
zh-cn	#### 概览 *资产记录 →  概览*部分提供了有关[主机资产](/manual/config/hosts/inventory)数据概览的方法。  要显示的概览，请选择一个主机组（或所有组）和显示数据的资产字段。将显示与所选字段的每个条目相对应的主机数量。 ![](../../../../../assets/en/manual/web_interface/inventory_overview.png){width="600"}  概览的完整性取决于维护了多少主机资产信息。  *主机计数* 列中的数字是链接; 它们导致这些主机在 *主机资产* 表中被过滤掉。 ![](../../../../../assets/en/manual/web_interface/inventory_filtered1.png){width="600"}

en-us	#### Overview  The item list for a host can be accessed from *Configuration → Hosts* by clicking on *Items* for the respective host.  A list of existing items is displayed.  ![](../../../../../../assets/en/manual/web_interface/items.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Item menu*|Click on the three-dot icon to open the menu for the specific item with these options:<br>**Latest data** - see latest data of the item<br>**Create trigger** - create a trigger based on this item<br>**Triggers** - click to see a list with links to already-configured trigger of this item<br>**Create dependent item** - create a dependent item for this item<br>**Create dependent discovery rule** - create a dependent discovery rule for this item | |*Host*|Host of the item.<br>This column is displayed only if multiple hosts are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the host item belongs to a template, the template name is displayed before the item name as a gray link. Clicking on the template link will open the item list on the template level.<br>If the item has been created from an item prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the item prototype list.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.<br>*Note* that passive items can also be checked immediately by pushing the *Check now* [button](#mass_editing_options).| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled*, *Disabled* or *Not supported*. You can change the status by clicking on it - from Enabled to Disabled (and back); from Not supported to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| |*Info*|If the item is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|  To configure a new item, click on the *Create item* button at the top right corner.
zh-cn	#### 概述  在“*配置→主机*”中，点击相应主机的“*项目*”，可访问相应主机的项目列表。  将显示现有项目的列表。  ![](../../../../../../assets/en/manual/web_interface/items.png){width="600"}  显示数据:  |列|描述| |------|-----------| | *监控项菜单* |单击三个点图标，打开带有这些选项的特定项目的菜单：<br>**最新数据**,看到最新的数据项<br> **创建触发器** —基于这个监控项创建一个触发器<br> **触发器** - 单击此处可查看包含指向此监控项的已配置的触发器的链接的列表<br>**新建依赖监控项** - 在该监控项基础上新建依赖监控项<br>**新建依赖自动发现规则** - 在该监控项基础上新建依赖自动发现规则 | |*主机*|监控项所在主机。<br>当过滤框中选择了多个主机时，此字段才会显示| |*名称*|监控项名称，显示为项目详细信息的蓝色链接。<br>点击监控项名称链接打开监控项[配置表单](/manual/config/items/item#configuration)。<br>如果主机条目属于某个模板，则在条目名称前以灰色链接的形式显示模板名称。单击模板链接将打开模板级的项目列表。<br>如果项目是从项目原型创建的，其名称前面是低级发现规则名称，用橙色表示。单击发现规则名称将打开项目原型列表 |*触发器*|将鼠标移到触发器上，会显示一个信息框，显示与该监控项相关的触发器。<br>触发器个数以灰色显示| |*键*|显示监控项的键| |*间隔*|检查频率。<br>*注意*被动监控项也可以通过按下*立即检查*[按钮](#mass_editing_options)来立即检查| |*历史*|项目数据历史将保留多少天| |*趋势*|项目趋势历史将保留多少天显示| |*类型*|显示项目类型(Zabbix agent、SNMP agent、simple check等) |*状态*|显示项目状态- *启用*，*禁用*或*不支持*。你可以通过点击它来改变状态-从启用到禁用(或反过来);从不支持到禁用(或反过来)| |*标签*|显示项目标签。<br>最多可以显示三个标签(名称:值对)。如果有更多的标签，一个“…”链接显示，允许看到所有的标签鼠标悬停。| |*信息*|正常显示，此栏无图标。如果出现错误，则会显示一个带有字母“i”的方形图标。将鼠标悬停在图标上可以看到一个带有错误描述的工具提示。|  要配置新项目，请单击右上角的*创建项目*按钮。

en-us	#### Overview  The item list for a host can be accessed from *Configuration → Hosts* by clicking on *Items* for the respective host.  A list of existing items is displayed.  ![](../../../../../../assets/en/manual/web_interface/items.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Wizard*|The wizard icon is a link to a wizard for creating a trigger based on the item.| |*Host*|Host of the item.<br>This column is displayed only if multiple hosts are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the host item belongs to a template, the template name is displayed before the item name as a gray link. Clicking on the template link will open the item list on the template level.<br>If the item has been created from an item prototype, its name is preceded by the low-level discovery rule name, in orange. Clicking on the discovery rule name will open the item prototype list.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.<br>*Note* that passive items can also be checked immediately by pushing the *Check now* [button](#mass_editing_options).| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled*, *Disabled* or *Not supported*. You can change the status by clicking on it - from Enabled to Disabled (and back); from Not supported to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.| |*Info*|If the item is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|  To configure a new item, click on the *Create item* button at the top right corner.  
zh-cn	#### 概览  可以从*配置 - >模板*中访问模板的项目列表 ，然后单击相应模板的项目。  在*配置 - >主机*中可以访问主机的项目列表，然后单击相应主机的项目。  现有项目的列表：  ![](../../../../../../assets/en/manual/web_interface/items.png){width="600"}  显示数据：  |列|述| |---|---| |*Wizard*|向导图标是指向向导的链接，用于根据项目创建触发器。| |*Name*|项目的名称，显示为项目详细信息的蓝色链接。<br>单击项目名称链接将打开该项目[配置表](/manual/config/items/item#configuration).<br>如果主机项目属于模板，模板名称将显示在项目名称之前，作为灰色链接。 单击模板链接将打开模板级别的项目列表。<br>如果项目是从项目原型创建的，则其名称前面是低级别的发现规则名称，以橙色显示。 单击发现规则名称将打开项目原型列表。| |*触发器*     将鼠|移动到触发器上将显示一个信息框，显示与该项目相关联的触发器。<br>触发器的数量以灰色显示。| |*Key*|显示项目键。| |*间隔*       显|检查频率。| |*历史*       将|示项目数据记录将保留多少天。| |*趋势*       将|示将保留多少天的项目趋势记录。| |*类型*       显|项目类型（Zabbix代理，SNMP代理，简单检查等）。| |*应用程序*   项目应|程序显示。| |*状态*       显|项目状态 - *启用*, *禁用* 或者 *不支持*.通过点击状态，您可以更改它 - 从启用到禁用（反之亦然）; 从不支持到禁用（反之亦然）。| |*Info*|如果一切正常，此列中不会显示图标。 如果有错误，将显示带有十字架的红色方形图标。 将鼠标移动到图标上方，您将看到带有错误描述的工具提示。|  点击右上角 *创建项目* 按钮配置新项目。  

en-us	#### Overview  The item list for a template can be accessed from *Configuration → Templates* by clicking on *Items* for the respective template.  A list of existing items is displayed.  ![](../../../../../../assets/en/manual/web_interface/template_items.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Item menu*|Click on the three-dot icon to open the menu for this specific item with these options:<br>**Create trigger** - create a trigger based on this item<br>**Triggers** - click to see a list with links to already-configured trigger of this item<br>**Create dependent item** - create a dependent item for this item<br>**Create dependent discovery rule** - create a dependent discovery rule for this item| |*Template*|Template the item belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the item is inherited from another template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item list on that template level.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.|  To configure a new item, click on the *Create item* button at the top right corner.
zh-cn	#### 概览  要查看模板的监控项列表，可以点击*配置 → 模板*，再点击相应模板的*监控项*  将会显示存在的监控项列表。  ![](../../../../../../assets/en/manual/web_interface/template_items.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*监控项菜单*|点击三个点图标，打开这个特定项目的菜单，有以下选项:<br>**新建触发器** - 基于本监控项新建触发器<br>**触发器** - 点击可以看见该监控项的已配置的触发器列表<br>**新建依赖监控项** - 新建一个依赖此监控项的监控项<br>**新建依赖自动发现规则** - 新建一个依赖此监控项的自动发现规则| |*模板*|该监控项属于的模板。<br>仅当筛选器中选择了多个模板时，此列才会显示。| |*名称*|监控项的名称显示为蓝色链接，包含监控项详细信息。<br>单击监控项名称链接将打开该监控项[配置表单](/manual/config/items/item#configuration).<br>如果监控项是从另一个模板继承的，则模板名会以灰色链接的形式显示在项名之前。单击模板链接将打开该模板的监控项列表。| |*触发器*|将鼠标移到触发器上将显示一个信息框，显示与该监控项相关的触发器。<br>触发器个数以灰色显示。| |*键值*|显示监控项键值。| |*时间间隔*|显示监测频率。| |*历史*|显示监控项数据历史记录保存的天数。| |*趋势*|显示监控项趋势历史数据将保存多少天的。| |*类型*|显示监控项类型 (Zabbix agent, SNMP agent, 简单监测，等等)。| |*状态*|显示监控项状态 - *启用* or *禁用*. 通过点击状态，您可以改变它-从启用到禁用（或者从禁用到启用）。| |*标签*|显示监控项标签<br>最多可以显示三个标记(名称:值对)。如果有更多的标签，会显示成一个“…”链接，鼠标悬停上面就能看到所有的标签。|  要配置新监控项，请单击右上角的*新建监控项*按钮。

en-us	#### Overview  The item list for a template can be accessed from *Configuration → Templates* by clicking on *Items* for the respective template.  A list of existing items is displayed.  ![](../../../../../../assets/en/manual/web_interface/template_items.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Wizard*|The wizard icon is a link to a wizard for creating a trigger based on the item.| |*Template*|Template the item belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the item is inherited from another template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item list on that template level.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.|  To configure a new item, click on the *Create item* button at the top right corner.  
zh-cn	#### Overview  The item list for a template can be accessed from *Configuration → Templates* by clicking on *Items* for the respective template.  A list of existing items is displayed.  ![](../../../../../../assets/en/manual/web_interface/template_items.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Wizard*|The wizard icon is a link to a wizard for creating a trigger based on the item.| |*Template*|Template the item belongs to.<br>This column is displayed only if multiple templates are selected in the filter.| |*Name*|Name of the item displayed as a blue link to item details.<br>Clicking on the item name link opens the item [configuration form](/manual/config/items/item#configuration).<br>If the item is inherited from another template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item list on that template level.| |*Triggers*|Moving the mouse over Triggers will display an infobox displaying the triggers associated with the item.<br>The number of the triggers is displayed in gray.| |*Key*|Item key is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days item data history will be kept is displayed.| |*Trends*|How many days item trends history will be kept is displayed.| |*Type*|Item type is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Status*|Item status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).| |*Tags*|Item tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.|  To configure a new item, click on the *Create item* button at the top right corner.  

en-us	#### Overview  The list of low-level discovery rules for a host can be accessed from *Configuration → Hosts* by clicking on *Discovery* for the respective host.  A list of existing low-level discovery rules is displayed. It is also possible to see all discovery rules independently of the host, or all discovery rules of a specific host group by changing the filter settings.  ![](../../../../../../assets/en/manual/web_interface/lld_rules.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Host*|The visible host name is displayed.<br>In the absence of a visible host name, the technical host name is displayed.| |*Name*|Name of the rule, displayed as a blue link.<br>Clicking on the rule name opens the low-level discovery rule [configuration form](/manual/discovery/low_level_discovery#discovery_rule).<br>If the discovery rule belongs to a template, the template name is displayed before the rule name, as a gray link. Clicking on the template link will open the rule list on the template level.| |*Items*|A link to the list of item prototypes is displayed.<br>The number of existing item prototypes is displayed in gray.| |*Triggers*|A link to the list of trigger prototypes is displayed.<br>The number of existing trigger prototypes is displayed in gray.| |*Graphs*|A link to the list of graph prototypes is displayed.<br>The number of existing graph prototypes is displayed in gray.| |*Hosts*|A link to the list of host prototypes is displayed.<br>The number of existing host prototypes is displayed in gray.| |*Key*|The item key used for discovery is displayed.| |*Interval*|The frequency of performing discovery is displayed.<br>*Note* that discovery can also be performed immediately by pushing the *Check now* button below the list.| |*Type*|The item type used for discovery is displayed (Zabbix agent, SNMP agent, etc).| |*Status*|Discovery rule status is displayed - *Enabled*, *Disabled* or *Not supported*. By clicking on the status you can change it - from Enabled to Disabled (and back); from Not supported to Disabled (and back).| |*Info*|If everything is fine, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|  To configure a new low-level discovery rule, click on the *Create discovery rule* button at the top right corner.
zh-cn	#### 概述  单击主机的“自动发现”，可在“*配置→主机*”中查看主机的低级别自动发现规则列表。  显示已存在的低级别自动发现规则列表。也可以独立于主机查看所有自动发现规则，或者通过更改过滤器设置，查看特定主机组的所有自动发现规则。  ![](../../../../../../assets/en/manual/web_interface/lld_rules.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*Host*|显示可见的主机名。<br>如果没有可见的主机名，则显示技术主机名| |*名称*|规则名称，显示为蓝色链接。<br>单击规则名打开低级发现规则[配置表单](/manual/discovery/low_level_discovery#discovery_rule)。<br>如果发现规则属于某个模板，则模板名称以灰色链接显示在规则名称前面。单击模板链接将打开模板级别的规则列表。| |*监控项*|显示到监控项原型列表的链接。<br>已存在的监控项原型数量以灰色显示| |*触发器*|显示触发器原型列表的链接。<br>已存在的触发器原型数量以灰色显示| |*图形*|显示图形原型列表的链接。<br>当前已有的图形原型数量，以灰色显示| |*主机*|显示主机原型列表链接。<br>当前主机原型数量以灰色显示| |*键*|显示发现的监控项的键 |*时间间隔*|显示发现频率。<br>*注意*发现也可以通过按列表下方的*现在检查*按钮立即执行 |*类型*|显示发现的项目类型(Zabbix agent、SNMP agent等)| |*状态*|发现规则状态- *已启用*、*未启用*或*不支持*。通过点击状态，您可以改变它-从启用到禁用(或反过来);从不支持到禁用(或反过来) |*信息*|正常情况下，此列无图标。如果出现错误，则会显示一个带有字母“i”的方形图标。将鼠标悬停在图标上可以看到一个带有错误描述的工具提示。|  单击右上角的“*创建发现规则*”按钮，可以配置新的低级别发现规则。

en-us	#### Overview  The list of low-level discovery rules for a template can be accessed from *Configuration → Templates* by clicking on *Discovery* for the respective template.  A list of existing low-level discovery rules is displayed. It is also possible to see all discovery rules independently of the template, or all discovery rules of a specific host group by changing the filter settings.  ![](../../../../../../assets/en/manual/web_interface/template_lld_rules.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Template*|The template discovery rule belongs to.| |*Name*|Name of the rule, displayed as a blue link.<br>Clicking on the rule name opens the low-level discovery rule [configuration form](/manual/discovery/low_level_discovery#discovery_rule).<br>If the discovery rule is inherited from another template, the template name is displayed before the rule name, as a gray link. Clicking on the template link will open the discovery rule list on that template level.| |*Items*|A link to the list of item prototypes is displayed.<br>The number of existing item prototypes is displayed in gray.| |*Triggers*|A link to the list of trigger prototypes is displayed.<br>The number of existing trigger prototypes is displayed in gray.| |*Graphs*|A link to the list of graph prototypes displayed.<br>The number of existing graph prototypes is displayed in gray.| |*Hosts*|A link to the list of host prototypes displayed.<br>The number of existing host prototypes is displayed in gray.| |*Key*|The item key used for discovery is displayed.| |*Interval*|The frequency of performing discovery is displayed.| |*Type*|The item type used for discovery is displayed (Zabbix agent, SNMP agent, etc).| |*Status*|Discovery rule status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it - from Enabled to Disabled (and back).|  To configure a new low-level discovery rule, click on the *Create discovery rule* button at the top right corner.
zh-cn	#### 概述  模板的低级发现规则列表可以在*配置成→模板*中通过点击* 自动发现 *访问。  显示已存在的低级别自动发现规则列表。也可以独立于模板查看所有自动发现规则，或者通过更改过滤器设置查看特定主机组的所有自动发现规则。  ![](../../../../../../assets/en/manual/web_interface/template_lld_rules.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*模板*|自动发现规则属于哪个模板。| |*名称*|规则名称，显示为蓝色链路。<br>单击规则名打开低级自动发现规则[配置表单](/manual/discovery/low_level_discovery#discovery_rule)。<br>如果自动发现规则是从其他模板继承的，则模板名称以灰色链接显示在规则名称前面。单击模板链接将打开该模板级别的自动发现规则列表| |*监控项*|显示到监控项原型列表的链接。<br>已存在的监控项原型数量以灰色显示| |*触发器*|显示触发器原型列表的链接。<br>已存在的触发器原型数量以灰色显示| |*图形*|显示图形原型列表的链接。<br>当前已有的图形原型数量，以灰色显示| |*主机*|显示的主机原型列表链接。<br>当前主机原型数量以灰色显示| |*键*|显示自动发现的监控项的键| |*时间间隔*|显示自动发现频率| |*类型*|显示自动发现的项目类型(Zabbix agent、SNMP agent等)| |*状态*|自动发现规则状态- *已启用*或*禁用*。通过单击状态，您可以更改它-从启用到禁用（或者反过来)|  单击右上角的“*创建自动发现规则*”按钮，可以配置新的低级别发现规则。

en-us	#### Overview  The **memtype** parameter is supported on Linux, AIX, FreeBSD, and Solaris platforms.  Three common values of 'memtype' are supported on all of these platforms: `pmem`, `rss` and `vsize`. Additionally, platform-specific 'memtype' values are supported on some platforms.
zh-cn	#### 概述  Linux, AIX, FreeBSD 和 Solaris 都支持**memtype**参数。  'memtype' 参数的三个常用值  `pmem`,  `rss`  和  `vsize`在所有系统中都适用。另外, 在一些系统中只支持该系统下的 'memtype' 值。

en-us	#### Overview  The *Monitoring → Dashboard* section is designed to display summaries of all the important information in a **dashboard**.  While only one dashboard can displayed at one time, it is possible to configure several dashboards. Each dashboard may contain one or several pages that can be rotated in a slideshow.  A dashboard page consists of widgets and each widget is designed to display information of a certain kind and source, which can be a summary, a map, a graph, the clock, etc.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard.png){width="600"}  Pages and widgets are added to the dashboard and edited in the dashboard editing mode. Pages can be viewed and rotated in the dashboard viewing mode.  The time period that is displayed in graph widgets is controlled by the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) located above the widgets. The time period selector label, located to the right, displays the currently selected time period. Clicking the tab label allows expanding and collapsing the time period selector.  Note that when the dashboard is displayed in kiosk mode and widgets only are displayed, it is possible to zoom out the graph period by double-clicking in the graph.
zh-cn	#### 概述  *监测 → 仪表盘* 组件是用于显示在**仪表盘**中所有重要信息的概览。  尽管一次只能显示一个仪表盘，配置多个仪表盘是可行的。每个仪表盘可以包含一个或可滑动显示的多个页面。  一个仪表盘页面可包含多个组件，每个组件是用于显示一种特定类型和来源的信息，可以是摘要，地图，图表或时钟等。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard.png){width="600"}  页面和组件在仪表盘编辑模式可以被添加到仪表盘或修改。页面可以在查看模式查看和轮换。  在图表组件中显示的时间区间是被组件上方的[时间区间选择器](/manual/config/visualization/graphs/simple#time_period_selector)控制的。 右侧的时间区间选择器标签显示了当前选择的时间区间。点击tab标签允许扩展和折叠时间区间选择器。  请注意当仪表盘在kiosk模式显示并且仅显示组件时，可在图表中双击来缩小图表时间区间。

en-us	#### Overview  The *Monitoring → Hosts* section displays a full list of monitored hosts with detailed information about host interface, availability, tags, current problems, status (enabled/disabled), and links to easily navigate to the host's latest data, problem history, graphs, dashboards and web scenarios.  ![](../../../../../assets/en/manual/web_interface/monitoring_hosts.png){width="600"}  |Column|Description| |--|--------| |*Name*|The visible host name. Clicking on the name brings up the [host menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).<br>An orange wrench icon ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png) after the name indicates that this host is in maintenance.<br>Click on the column header to sort hosts by name in ascending or descending order.| |*Interface*|The main interface of the host is displayed.| |*Availability*|Host [availability](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability) per configured interface.<br>Icons represent only those interface types (Zabbix agent, SNMP, IPMI, JMX) that are configured. If you position the mouse on the icon, a popup list of all interfaces of this type appears with each interface details, status and errors.<br>The column is empty for hosts with no interfaces.<br>The current status of all interfaces of one type is displayed by the respective icon color:<br>**Green** - all interfaces available<br>**Yellow** - at least one interface available and at least one unavailable; others can have any value including 'unknown'<br>**Red** - no interfaces available<br>**Gray** - at least one interface unknown (none unavailable)<br>Note that active Zabbix agent items do not affect host availability.| |*Tags*|[Tags](/manual/config/tagging) of the host and all linked templates, with macros unresolved.| |*Status*|Host status - *Enabled* or *Disabled*.<br>Click on the column header to sort hosts by status in ascending or descending order.| |*Latest data*|Clicking on the link will open the *Monitoring - Latest data* page with all the latest data collected from the host.<br> The number of items with latest data is displayed in gray (displayed since Zabbix 6.0.5).| |*Problems*| The number of open host problems sorted by severity. The color of the square indicates problem severity. The number on the square means the number of problems for the given severity.<br>Clicking on the icon will open *Monitoring - Problems* page for the current host. <br>If a host has no problems, a link to the Problems section for this host is displayed as text. <br>Use the filter to select whether suppressed problems should be included (not included by default).| |*Graphs*|Clicking on the link will display graphs configured for the host. The number of graphs is displayed in gray.<br>If a host has no graphs, the link is disabled (gray text) and no number is displayed.| |*Dashboards*|Clicking on the link will display dashboards configured for the host. The number of dashboards is displayed in gray.<br>If a host has no dashboards, the link is disabled (gray text) and no number is displayed.| |*Web*|Clicking on the link will display web scenarios configured for the host. The number of web scenarios is displayed in gray.<br>If a host has no web scenarios, the link is disabled (gray text) and no number is displayed.|
zh-cn	#### 概述  *监控→ 主机* 部分显示受监控主机的完整列表，其中包含有关主机接口、可用性、标签、 当前问题、状态（启用/禁用）的详细信息，以及轻松导航到主机的最新数据、问题历史记录、图表、仪表板的链接和WEB场景。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/monitoring_hosts.png){width="600"}  |列|描述| |------|-----------| |*名称*|可见的主机名。单击名称将显示  [主机菜单](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu).<br>名称后面的橙色扳手图标  ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png) 表示此主机正在维护中。<br>单击列标题可按名称升序或降序对主机进行排序。| |*接口*|显示主机的主界面。| |*可用性*|每个已配置接口的主机[可用性](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability)<br>图标仅表示已配置的接口类型 (Zabbix 代理、SNMP、IPMI、JMX) 如果将鼠标放在图标上，则会显示此类型所有接口的弹出列表，其中包含每个接口的详细信息、状态和错误。<br>对于没有接口的主机，该列为空。<br>一种类型的所有接口的当前状态由相应的图标颜色显示：<br>**绿色** - 所有接口可用<br>**黄色** - 至少一个接口可用同时至少一个不可用;其他可以具有任何值，包括 '未知'<br>**红色** - 没有可用的接口<br>**灰色** - 至少一个接口未知 (无可用)<br>请注意，活动的 Zabbix 代理项目不会影响主机可用性。| |*标签*|主机和所有链接模板的[标记](/manual/config/tagging) ，宏未解析。| |*状态*|主机状态 - *启用* 或 *禁用*。<br>单击列标题可按状态以升序或降序对主机进行排序。| |*最新数据*|单击该链接将打开 *监测- 最新数据* 页面，其中包含从主机收集的所有最新数据。<br> 具有最新数据的监控项数以灰色显示（自 Zabbix 6.0.5 起显示）。| |*问题*| 按严重性排序的打开的主机问题数。正方形的颜色表示问题的严重性。方块上的数字表示给定严重性下的问题数。<br>单击该图标将打开当前主机的 *监测 - 问题* 页面。 <br>如果主机没有问题，则指向此主机的问题部分的链接将显示为文本。<br>使用过滤器选择是否应包括隐含的问题（默认情况下不包括）。| |*图形*|单击该链接将显示主机配置的图形。图形的数量以灰色显示。<br>如果主机没有图形，则禁用链接（灰色文本）并且不显示任何数字。| |*仪表板*|单击该链接将显示主机配置的仪表板。仪表板的数量以灰色显示。<br>如果主机没有仪表板，则链接将被禁用（灰色文本），并且不显示任何数字。| |*WEB监测*|单击该链接将显示为主机配置的 Web 监测方案。Web监测方案的数量以灰色显示。<br>如果主机没有 Web 监测方案，则链接将被禁用（灰色文本），并且不显示任何数字。|

en-us	#### Overview  The Monitoring menu is all about displaying data. Whatever information Zabbix is configured to gather, visualize and act upon, it will be displayed in the various sections of the Monitoring menu.  
zh-cn	#### 概述  监测菜单的作用是显示数据。任何Zabbix采集、可视化和操作的信息都会在监测菜单的各个部件中显示。

en-us	#### Overview  The queue displays items that are waiting for a refresh. The queue is just a **logical** representation of data. There is no IPC queue or any other queue mechanism in Zabbix.  Items monitored by proxies are also included in the queue - they will be counted as queued for the proxy history data update period.  Only items with scheduled refresh times are displayed in the queue. This means that the following item types are excluded from the queue:  -   log, logrt and event log active Zabbix agent items -   SNMP trap items -   trapper items -   web monitoring items -   dependent items  Statistics shown by the queue is a good indicator of the performance of Zabbix server.  The queue is retrieved directly from Zabbix server using JSON protocol. The information is available only if Zabbix server is running.
zh-cn	#### 概览  队列显示正在等待刷新的监控项。队列只是数据的一种 **逻辑**上表现。ZABBIX中并没有IPC队列或者其它任何队列的机制。\  由Proxy们监控的监控项也会被包含在队列中 -这些监控项将按Proxy历史数据更新周期被计数为队列。  只有具有刷新时间计划的监控项才会记录在队列中。也就是说队列中将不包含以下的监控项类型：  -   log, logrt 和event log (Active Agent) -   SNMP trap 监控项 -   trapper 监控项 -   web监控监控项 -   有依赖的监控项  队列显示的统计信息是ZABBIX Server是否健康的指标。  使用JSON协议直接从ZABBIX Server 检索队列。这个页面的信息只在ZABBIX Server运行时可用。

en-us	#### Overview  There are four ways of getting Zabbix:  -   Install it from the [distribution     packages](install_from_packages#From_distribution_packages) -   Download the latest source archive and [compile it     yourself](install#Installation_from_sources) -   Install it from the [containers](containers) -   Download the [virtual appliance](/manual/appliance)  To download the latest distribution packages, pre-compiled sources or the virtual appliance, go to the [Zabbix download page](https://www.zabbix.com/download), where direct links to latest versions are provided.
zh-cn	#### 概述  获取 Zabbix 安装介质有四种方法：  -   从 [发行包](install_from_packages#From_distribution_packages) 安装； -   下载最新的归档源码包并 [编译它](install#Installation_from_sources)； -   从 [容器](containers) 中安装； -   下载 [Zabbix 应用](/manual/appliance)。  请转到 [Zabbix 下载页面](https://www.zabbix.com/download) 下载最新的源码包或应用，此页面提供最新版本的直接链接。 如果要下载旧版本，请参阅以下稳定版本下载链接。

en-us	#### Overview  There are several types of events generated in Zabbix:  -   trigger events - whenever a trigger changes its status     (*OK→PROBLEM→OK*) -   service events - whenever a service changes its status     (*OK→PROBLEM→OK*) -   discovery events - when hosts or services are detected -   autoregistration events - when active agents are auto-registered by     server -   internal events - when an item/low-level discovery rule becomes     unsupported or a trigger goes into an unknown state  ::: noteclassic Internal events are supported starting with Zabbix 2.2 version. :::  Events are time-stamped and can be the basis of actions such as sending notification e-mail etc.  To view details of events in the frontend, go to *Monitoring* → *Problems*. There you can click on the event date and time to view details of an event.  More information is available on:  -   [trigger events](/manual/config/events/trigger_events) -   [other event sources](/manual/config/events/sources)
zh-cn	#### 概述  Zabbix中生成的事件有以下几种类型：  -   触发器事件—无论何时一个触发器的状态发生改变（*OK→问题→OK*） -   服务事件—无论何时服务的状态发生改变（*OK→问题→OK*） -   发现事件—当检测到主机或服务时 -   自动注册事件—当主动agent被服务器自动注册时 -   内部事件—当一个监控项目或低级别自动发现规则变得不受支持或一个触发器进入未知状态时  ::: noteclassic 从Zabbix 2.2开始支持内部事件。 :::  事件是有时间戳的，可以作为动作的基础，例如发送通知电子邮件等。  要在前端查看事件的详细信息，点击*监控* →*问题*。在那里你可以单击事件的日期和时间查看事件的详细信息。  更多信息请查看：  -   [触发器事件](/manual/config/events/trigger_events) -   [其他事件源](/manual/config/events/sources)

en-us	#### Overview  There are several ways in which you can customize and rebrand your Zabbix frontend installation:  -   replace the Zabbix logo with a desired one -   hide links to Zabbix Support and Zabbix Integrations -   set a custom link to the Help page -   change copyright in the footer
zh-cn	#### 概述  您可以通过多种方式自定义和重新命名 Zabbix 前端安装：  -   将 Zabbix 徽标替换为所需的logo -   隐藏指向 Zabbix 支持和 Zabbix 集成的链接 -   设置自定义链接到帮助页面 -   更改页脚的版权

en-us	#### Overview  There are situations when one item gathers multiple metrics at a time or it even makes more sense to collect related metrics simultaneously, for example:  -   CPU utilization of individual cores -   Incoming/outgoing/total network traffic  To allow for bulk metric collection and simultaneous use in several related items, Zabbix supports dependent items. Dependent items depend on the master item that collects their data simultaneously, in one query. A new value for the master item automatically populates the values of the dependent items. Dependent items cannot have a different update interval than the master item.  Zabbix preprocessing options can be used to extract the part that is needed for the dependent item from the master item data.  Preprocessing is managed by a `preprocessing manager` process, which has been added in Zabbix 3.4, along with workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is used between data gatherers (pollers, trappers, etc) and the preprocessing process.  Zabbix server or Zabbix proxy (if host is monitored by proxy) are performing preprocessing steps and processing dependent items.  Item of any type, even dependent item, can be set as master item. Additional levels of dependent items can be used to extract smaller parts from the value of an existing dependent item.
zh-cn	#### 概述  有时一个监控项一次会收集多个指标，或者同时收集相关的指标会更有意义，例如：  -   单个内核的CPU利用率 -   输入/输出的总网络流量  为了允许进行批量指标收集和同时使用几个相关监控项，Zabbix支持从属监控项。从属监控项依赖于主要监控项包含从属监控项的一次查询，主要监控项的新值会用于自动填充从属监控项的值。从属监控项的更新间隔与主要监控项相同且不可变。  Zabbix预处理选项可用于从主要监控项的数据中，提取从属监控项所需部分的值。  预处理是由一个“预处理管理器”进程管理的，它被添加于Zabbix 3.4版本中，与worker进程一起执行预处理步骤。所有来自不同数据收集器的值（不管是否有预处理步骤），在添加到历史缓存之前，都要经过预处理管理器。基于套接字的IPC连接用于数据收集器(pollers, trappers等)和预处理进程之间的通讯。  只有Zabbix server 或 Zabbix proxy ( 如果主机被Zabbix proxy 监控) 执行预处理步骤，并处理从属监控项。  任何类型的监控项，甚至是从属监控项，都可以设置为主要监控项。额外级别的从属监控项可以被用来从现有的从属监控项中提取出更小的值。

en-us	#### Overview  There is an option to tag various entities in Zabbix. Tags can be defined for:  -   templates -   hosts -   items -   web scenarios -   triggers -   services -   template items and triggers -   host, item and trigger prototypes  Tags have several uses, most notably, to mark events. If entities are tagged, the corresponding new events get marked accordingly:  -   with tagged templates - any host problems created by relevant     entities (items, triggers, etc) from this template will be marked -   with tagged hosts - any problem of the host will be marked -   with tagged items, web scenarios - any data/problem of this item or     web scenario will be marked -   with tagged triggers - any problem of this trigger will be marked  A problem event inherits all tags from the whole chain of templates, hosts, items, web scenarios, triggers. Completely identical `tag:value` combinations (after resolved macros) are merged into one rather than being duplicated, when marking the event.  Having custom event tags allows for more flexibility. Importantly, events can be [correlated](/manual/config/event_correlation) based on event tags. In other uses, actions can be defined based on tagged events. Item problems can be grouped based on tags. Problem tags can also be used to map problems to [services](/manual/it_services/service_tree#problem-tags).  Tagging is realized as a pair of *tag name* and *value*. You can use only the name or pair it with a value:      MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High   An entity (template, host, item, web scenario, trigger or event) may be tagged with the same name, but different values - these tags will not be considered 'duplicates'. Similarly, a tag without value and the same tag with value can be used simultaneously.
zh-cn	#### 概览  Zabbix 中有一个选项可以标记各种实体。标签可以定义为：  - 模板 - 主机 -  监控项 - 网络场景 - 触发器 - 模板项目和触发器 - 主机、监控项和触发器原型  标签有多种用途，最明显的是标记事件。如果实体被标记，相应的新事件也会被标记：  - 带有标记的模板 - 所有由此模板相关实例(监控项、触发器等)创建的主机问题都会被标记。 - 带有标记的主机 - 主机的所有问题都将被标记 - 带有标记的项目、网络场景 - 该监控项的所有数据/问题或web场景将被标记 - 带有标记的触发器 - 此触发器的所有问题都将被标记  一个问题事件继承了整个模板链中的所有标签，主机、监控项、Web 场景、触发器。当标记事件时，完全相同的`tag:value`组合（在解析宏之后）合并为一个而不是被复制。  拥有自定义事件标签可以提供更大的灵活性。特别是事件可以基于 [相关](/manual/config/event_correlation)事件标签。在其他用途中，可以根据标记定义操作事件。监控项问题可以根据标签进行分组。  标记实现为一对 *tag name* 和 *value*。您可以仅使用名称或将其与值配对：     MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High  一个实体（模板、主机、监控项、Web 场景、触发器或事件）可能是使用相同名称但值不同的标签 - 这些标签不会被认为是“重复”。同样，一个没有值的标签和同一个标签值可以同时使用。

en-us	#### Overview  There is an option to tag various entities in Zabbix. Tags can be defined for:  -   templates -   hosts -   items -   web scenarios -   triggers -   template items and triggers -   host, item and trigger prototypes  Tags have several uses, most notably, to mark events. If entities are tagged, the corresponding new events get marked accordingly:  -   with tagged templates - any host problems created by relevant     entities (items, triggers, etc) from this template will be marked -   with tagged hosts - any problem of the host will be marked -   with tagged items, web scenarios - any data/problem of this item or     web scenario will be marked -   with tagged triggers - any problem of this trigger will be marked  A problem event inherits all tags from the whole chain of templates, hosts, items, web scenarios, triggers. Completely identical `tag:value` combinations (after resolved macros) are merged into one rather than being duplicated, when marking the event.  Having custom event tags allows for more flexibility. Importantly, events can be [correlated](/manual/config/event_correlation) based on event tags. In other uses, actions can be defined based on tagged events. Item problems can be grouped based on tags.  Tagging is realized as a pair of *tag name* and *value*. You can use only the name or pair it with a value:      MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High   An entity (template, host, item, web scenario, trigger or event) may be tagged with the same name, but different values - these tags will not be considered 'duplicates'. Similarly, a tag without value and the same tag with value can be used simultaneously.
zh-cn	#### 概览  Zabbix 中有一个选项可以标记各种实体。标签可以定义为：  - 模板 - 主机 -  监控项 - 网络场景 - 触发器 - 模板项目和触发器 - 主机、监控项和触发器原型  标签有多种用途，最明显的是标记事件。如果实体被标记，相应的新事件也会被标记：  - 带有标记的模板 - 所有由此模板相关实例(监控项、触发器等)创建的主机问题都会被标记。 - 带有标记的主机 - 主机的所有问题都将被标记 - 带有标记的项目、网络场景 - 该监控项的所有数据/问题或web场景将被标记 - 带有标记的触发器 - 此触发器的所有问题都将被标记  一个问题事件继承了整个模板链中的所有标签，主机、监控项、Web 场景、触发器。当标记事件时，完全相同的`tag:value`组合（在解析宏之后）合并为一个而不是被复制。  拥有自定义事件标签可以提供更大的灵活性。特别是事件可以基于 [相关](/manual/config/event_correlation)事件标签。在其他用途中，可以根据标记定义操作事件。监控项问题可以根据标签进行分组。  标记实现为一对 *tag name* 和 *value*。您可以仅使用名称或将其与值配对：     MySQL, Service:MySQL, Services, Services:Customer, Applications, Application:Java, Priority:High  一个实体（模板、主机、监控项、Web 场景、触发器或事件）可能是使用相同名称但值不同的标签 - 这些标签不会被认为是“重复”。同样，一个没有值的标签和同一个标签值可以同时使用。

en-us	#### Overview  The Reports menu features several sections that contain a variety of predefined and user-customizable reports focused on displaying an overview of such parameters as system information, triggers and gathered data.
zh-cn	#### 概览  “报表”菜单包含多个部分，其中包含各种预定义和用户可自定义的报告，这些报告侧重于显示系统信息，触发器和收集数据等参数的概括。

en-us	#### Overview  The required libraries for the MongoDB loadable plugin are listed in this page.
zh-cn	#### 概述  本页列出了 MongoDB 可加载插件所需的库。

en-us	#### Overview  The required libraries for the PostgreSQL loadable plugin are listed in this page.
zh-cn	#### 概述  本页列出了 PostgreSQL 可加载插件所需的库。

en-us	#### Overview  These checks use the communication with Zabbix agent for data gathering.  There are [passive and active](/manual/appendix/items/activepassive) agent checks. When configuring an item, you can select the required type:  -   *Zabbix agent* - for passive checks -   *Zabbix agent (active)* - for active checks
zh-cn	#### 概述  这些检查与Zabbix agent进行通信，实现数据的采集  有 [被动和主动](/manual/appendix/items/activepassive)两种 agent 检查模式 ， 在配置监控项时，你可以选择所需的类型:  -   *Zabbix agent* - 被动检查 -   *Zabbix agent(主动)* - 主动检查

en-us	#### Overview  The section in *Monitoring → Latest data* can be used to view latest values gathered by items as well as to access various graphs for the items.  ![](../../../../../assets/en/manual/web_interface/latest_data.png){width="600"}  Items are displayed with their name, time since last check, last value, change amount, tags, and a link to a simple graph/history of item values.   To view last received data in raw format (without unit conversion and value mapping applied), hover over the value displayed in the *Last value* column.  If an item has errors, for example, has become unsupported, an information icon will be displayed in the *Info* column ![](../../../../../assets/en/manual/web_interface/info_icon.png) . Hover over the icon for details.  An icon with a question mark ![](../../../../../assets/en/manual/web_interface/item_description_icon.png) is displayed next to the item name for all items that have a description. If you position the mouse cursor on this icon, the item description is displayed as a tooltip.  *Note*: The name of a disabled host is displayed in red. Data of disabled hosts, including graphs and item value lists, is also accessible in *Latest data*.  By default, only values that fall within the last 24 hours are displayed. This limit has been introduced with the aim of improving initial loading times for large pages of the latest data. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration→General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.  ::: noteimportant For items with an update frequency of 1 day or more the change amount will never be displayed (with the default setting). Also in this case the last value will not be displayed at all if it was received more than 24 hours ago. :::  
zh-cn	#### 简介  *监测 → 最新数据* 可以用来查看监控项收集的最新值，以及访问各种项目图表。  第一次打开此页面时，不显示任何内容。  ![](../../../../../assets/en/manual/web_interface/latest_data_default1.png){width="600"}  要访问数据，您需要在过滤器中进行选择，例如主机组，主机，应用程序或项目名称。  ![](../../../../../assets/en/manual/web_interface/latest_data1.png){width="600"}  在显示的列表中，单击 ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/expand.png) 在主机和相关应用程序之前显示该主机和应用程序的最新值。 您可以展开所有主机和所有应用程序，从而通过单击显示所有项目 ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/expand.png) 在标题行中。  *注意*：被禁用主机的名称显示为红色。从Zabbix2.2.0起，被禁用主机数据（包括图表和项目值列表）在*最新数据*页可以被访问。  本页面的列表针对监控项展示以下列：监控项名称、最近检查记录、最后一个值、更改量(Change)以及一个跳转到项目值的简单图表/历史记录的链接。  默认情况下仅显示最近24小时内的数据。这样设置是为了优化页面加载数据的时间。 如果你想查看更多数据也可以到前端文件*include/defines.inc.php* 中更改 ZBX\_HISTORY\_PERIOD的[常量值](/manual/web_interface/definitions) 。  **使用筛选器**  您可以使用筛选器只显示您感兴趣的监控项。*筛选器* 链接位于表格上方中部。您可以使用它来过滤主机群组、主机、应用集、取自监控项名称中的字符串；还可以选择是否显示没有收集到数据的项目（查看无资料项目）。  指定一个父主机组，隐式选择所有嵌套的主机组。  *显示详细信息* 会增加显示监控项相关的以下项目：该监控项的键值、间隔设置、历史记录及趋势的保存时间设置、监控项的类型和监控项的错误（良好/不支持）等详细信息，同时键值是一个链接到监控项配置的超链接。  ![](../../../../../assets/en/manual/web_interface/latest_data21.png){width="600"}  默认情况下，会显示没有数据的项目，但不显示详细内容。  **比较项目图表**  可以在第二列的复选框选择几个监控，然后用 [简单图形或堆叠图](/manual/config/visualization/graphs/adhoc)比较它们的数据。选择感兴趣的监控项，然后单击表下所需图形的按钮，即可查看图形。  **链接到值的历史/简单图形**  提供最新值列表中的最后一列：  -   一个 \*\* 历史链接 \*\* （用于所有文本项）-链接到的列表（values/     500个最新values）显示前一个项目值的历史记录。  ```{=html} <!-- --> ``` -   一个 **图表连接** （用于所有数字项）-链接到一个     [简单图形](/manual/config/visualization/graphs/simple)。     图形被调用出来后，从右上角的下拉框也可以切换为显示值(values)或最新*500个值*(500     latest values)。  ![](../../../../../assets/en/manual/web_interface/values1.png){width="600"}  此列表中显示的是“原始的”值，即指未经处理的指。  ::: noteclassic 显示的总值由“搜索限制”和“过滤结果”参数值定义，在[管理→ 一般](/manual/web_interface/frontend_sections/administration/general)中设置。 :::  

en-us	#### Overview  The Services menu is for the [service monitoring](/manual/it_services) functions of Zabbix.
zh-cn	#### 概述  本菜单是展示 Zabbix  Services [service monitoring](/manual/it_services) 功能。