en-us	# Zabbix agent 2 template operation  Steps to ensure correct operation of templates that collect metrics with [Zabbix agent 2](/manual/concepts/agent2):  1\. Make sure that the agent 2 is installed on the host, and that the installed version contains the required plugin. In some cases, you may need to [upgrade](https://www.zabbix.com/documentation/current/manual/installation/upgrade) the agent 2 first.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to a target host (if the template is not available in your Zabbix installation, you may need to import the template's import file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\ 3. Adjust the values of mandatory macros as needed. Note, that user macros can be used to override configuration parameters.\ 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column.  ::: noteimportant  Zabbix agent 2 templates work in conjunction with the plugins. While the basic configuration can be done by simply adjusting user macros, the deeper customization can be achieved by [configuring the plugin](/manual/config/items/plugins#named_sessions) itself. For example, if a plugin supports named sessions, it is possible to monitor several entities of the same kind (e.g. MySQL1 and MySQL2) by specifying named session with own URI, username and password for each entity in the configuration file.  :::  ::: notetip  This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name).  :::  |Template name|Mandatory macros|Additional steps/comments| |-------------|----------------|-------------------------| |[Ceph by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/ceph_agent2/README.md)|**{$CEPH.API.KEY}** - the API key (default: `zabbix_pass`).<br>Required, if {$CEPH.CONNSTRING} is a URI.<br>Must be empty, if {$CEPH.CONNSTRING} is a session name.<br>**{$CEPH.CONNSTRING}** - connection string; can be a session name or a URI defined in the following format: <protocol(host:port)>. For URI only HTTPS schema is supported.<br>Examples: Prod, https://localhost:8003 (default)<br>**{$CEPH.USER}** - user to be used for monitoring (default:`zabbix`).<br>Required, if {$CEPH.CONNSTRING} is a URI.<br>Must be empty, if {$CEPH.CONNSTRING} is a session name.|Works with *Ceph* plugin; named sessions are supported.<br><br>1. Configure the Ceph RESTful Module according to [documentation](https://docs.ceph.com/en/latest/mgr/restful/).<br><br>2. Make sure a RESTful API endpoint is available for connection.| |[Docker](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/docker/README.md)|\-|Works with *Docker* plugin; named sessions are not supported.<br><br>To set path to Docker API endpoint edit Plugins.Docker.Endpoint parameter in the agent 2 [configuration file](/manual/appendix/config/zabbix_agent2) (default: `Plugins.Docker.Endpoint=unix:///var/run/docker.sock`).<br><br>To test availability, run:<br>`zabbix_get -s docker-host -k docker.info`| |[Memcached](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/memcached/README.md)|**{$MEMCACHED.CONN.URI}** - connection string in the URI format; port is optional; password is not used.<br>If not set, the plugin's default value is used: tcp://localhost:11211.<br>Examples: tcp://127.0.0.1:11211, tcp://localhost, unix:/var/run/memcached.sock.|Works with *Memcached* plugin; named sessions are supported.<br><br>To test availability, run:<br>`zabbix_get -s memcached-host -k memcached.ping`| |[MongoDB cluster by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mongodb_cluster/README.md)|**{$MONGODB.CONNSTRING}** - connection string in the URI format; password is not used (default: tcp://localhost:27017).<br>Can be a session name or a URI defined in the following format: %% <protocol(host:port)>%%<br>For URI only TCP scheme is supported.<br>Examples: MongoDB1, tcp://172.16.0.10<br>**{$MONGODB.USER}**, **{$MONGODB.PASSWORD}** - MongoDB credentials (default: none).<br>If not set and {$MONGODB.CONNSTRING} is a URI, parameters from the configuration file will be used.<br>Must be empty, if {$MONGODB.CONNSTRING} is a session name.|Works with *MongoDB* plugin; named sessions are supported.<br>For MongoDB configuration instructions, see [plugins](/manual/config/items/plugins).<br>To test availability, run:<br>`zabbix_get -s mongos.node -k 'mongodb.ping["{$MONGODB.CONNSTRING}","{$MONGODB.USER}","{$MONGODB.PASSWORD}"]"`| |[MongoDB node by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mongodb/README.md)|**{$MONGODB.CONNSTRING}** - connection string in the URI format; password is not used (default: tcp://localhost:27017).<br>Can be a session name or a URI defined in the following format: %% <protocol(host:port)>%%<br>For URI only TCP scheme is supported.<br>Examples: MongoDB1, tcp://172.16.0.10<br>**{$MONGODB.USER}**, **{$MONGODB.PASSWORD}** - MongoDB credentials (default: none).<br>If not set and {$MONGODB.CONNSTRING} is a URI, parameters from the configuration file will be used.<br>Must be empty, if {$MONGODB.CONNSTRING} is a session name.|Works with *MongoDB* plugin; named sessions are supported.<br>For MongoDB configuration instructions, see [plugins](/manual/config/items/plugins).<br>To test availability, run:<br>`zabbix_get -s mongodb.node -k 'mongodb.ping["{$MONGODB.CONNSTRING}","{$MONGODB.USER}","{$MONGODB.PASSWORD}"]"`| |[MySQL by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_agent2/README.md)|**{$MYSQL.DSN}** - the system data source name of the MySQL instance (default: <Put your DSN>).<br>Can be a session name or a URI defined in the following format: %% <protocol(host:port or /path/to/socket)/>%%<br>For URI only TCP and Unix schemas are supported.<br>Examples: MySQL1, tcp://localhost:3306, tcp://172.16.0.10, unix:/var/run/mysql.sock<br>**{$MYSQL.USER}**, **{$MYSQL.PASSWORD}** - MySQL credentials (default: none). Required, if {$MYSQL.DSN} is a URI.<br>Must be empty, if {$MYSQL.DSN} is a session name.|Works with *MySQL* plugin; named sessions are supported.<br><br>To grant required privileges to a MySQL user that will be used for monitoring, run:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON *.* TO '<username>'@'%';`<br><br>See MySQL documentation for information about [user privileges](https://dev.mysql.com/doc/refman/8.0/en/grant.html) and [Unix sockets](https://dev.mysql.com/doc/refman/8.0/en/problems-with-mysql-sock.html).| |[Oracle by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2/README.md)|**{$ORACLE.CONNSTRING}** - connection string; can be a session name or a URI defined in the following format: <protocol(host:port or /path/to/socket)/><br>For URI only TCP schema is supported.<br>Examples: Oracle1, tcp://localhost:1521<br><br>**{$ORACLE.SERVICE}** - Oracle Service name (default: ORA). Required, if {$ORACLE.CONNSTRING} is a URI.<br>Must be empty, if {$ORACLE.CONNSTRING} is a session name.<br><br>**{$ORACLE.USER}**, **{$ORACLE.PASSWORD}** - Oracle credentials (default username: zabbix, password: zabbix\_password). Required, if {$ORACLE.CONNSTRING} is a URI.<br>Must be empty, if {$ORACLE.CONNSTRING} is a session name.|Works with *Oracle* plugin; named sessions are supported.<br><br>Install [Oracle Instant Client](https://www.oracle.com/database/technologies/instant-client/downloads.html).<br>To create Oracle user with required privileges, run:<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Grant access to the zabbix_mon user.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br>`GRANT SELECT ON SYS.DBA_DATA_FILES TO zabbix_mon;`<br>`GRANT SELECT ON V$ACTIVE_SESSION_HISTORY TO zabbix_mon;`<br>`GRANT SELECT ON V$ARCHIVE_DEST TO zabbix_mon;`<br>`GRANT SELECT ON V$ASM_DISKGROUP TO zabbix_mon;`<br>`GRANT SELECT ON V$DATABASE TO zabbix_mon;`<br>`GRANT SELECT ON V$DATAFILE TO zabbix_mon;`<br>`GRANT SELECT ON V$INSTANCE TO zabbix_mon;`<br>`GRANT SELECT ON V$LOG TO zabbix_mon;`<br>`GRANT SELECT ON V$OSSTAT TO zabbix_mon;`<br>`GRANT SELECT ON V$PGASTAT TO zabbix_mon;`<br>`GRANT SELECT ON V$PROCESS TO zabbix_mon;`<br>`GRANT SELECT ON V$RECOVERY_FILE_DEST TO zabbix_mon;`<br>`GRANT SELECT ON V$RESTORE_POINT TO zabbix_mon;`<br>`GRANT SELECT ON V$SESSION TO zabbix_mon;`<br>`GRANT SELECT ON V$SGASTAT TO zabbix_mon;`<br>`GRANT SELECT ON V$SYSMETRIC TO zabbix_mon;`<br>`GRANT SELECT ON V$SYSTEM_PARAMETER TO zabbix_mon;`| |[PostgreSQL Agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql_agent2)|**{$PG.URI}** - connection string; can be a session name or a URI defined in the following format:<br>%% <protocol(host:port or /path/to/socket)/>%%. For URI only TCP and Unix schemas are supported.<br>Examples: Postgres1, tcp://localhost:5432, tcp://172.16.0.10<br>**{$PG.USER}**, **{$PG.PASSWORD}** - PostgreSQL credentials (default username: postgres, password:postgres).<br>Required, if {$PG.URI} is a URI. Must be empty, if {$PG.URI} is a session name.|Works with *PostgreSQL* plugin; named sessions are supported.<br><br>To create a user with required privileges, for PostgreSQL 10 and newer, run:<br>`CREATE USER 'zbx_monitor' IDENTIFIED BY '<password>';`<br>`GRANT EXECUTE ON FUNCTION pg_catalog.pg_ls_dir(text) TO zbx_monitor;`\\\\`GRANT EXECUTE ON FUNCTION pg_catalog.pg_stat_file(text) TO zbx_monitor;`<br><br>Edit pg\_hba.conf to allow connections from Zabbix agent (see [PostgreSQL documentation](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html) for details).| |[Redis](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/redis/README.md)|**{$REDIS.CONN.URI}** -connection string in the URI format; port is optional; password is not used.<br>If not set, the plugin's default value is used: tcp://localhost:6379|Works with *Redis* plugin; named sessions are supported.<br><br>To test availability, run:<br>`zabbix_get -s redis-master -k redis.ping`| |[SMART by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/module/smart_agent2/README.md) / [SMART by Zabbix agent 2 active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/module/smart_agent2_active)|\-|Sudo/root access rights to smartctl are required for the user executing Zabbix agent 2. The minimum required smartctl version is 7.1.<br><br>Disk discovery LLD rule finds all HDD, SSD, NVMe disks with S.M.A.R.T. enabled.<br><br>Attribute discovery LLD rule finds all Vendor Specific Attributes for each disk.<br><br>To skip some attributes, set regular expressions with disk names in {$SMART.DISK.NAME.MATCHES} and with attribute IDs in {$SMART.ATTRIBUTE.ID.MATCHES} on the host level.| |[Systemd by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/systemd/README.md)|\-|No specific configuration is required.| |[Website certificate by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/certificate_agent2/README.md)|\*\* {$CERT.WEBSITE.HOSTNAME}\*\* - the website's DNS name for the connection (default: <Put DNS name>).|Works with *WebCertificate* plugin; named sessions are not supported.<br>To test availability, run:<br>`zabbix_get -s <zabbix_agent_addr> -k web.certificate.get[<website_DNS_name>]`<br><br>Create a separate host for the TLS/SSL certificate with Zabbix agent interface and link the template to this host.|
zh-cn	 # Zabbix agent 2 模板操作  确保通过[Zabbix agent 2](/manual/concepts/agent2)收集模板指标的正确步骤:  1\. 确保主机上安装了Zabbix agent 2，并且该版本包含所需的插件。有时候，您需要先[升级](https://www.zabbix.com/文档/current/manual/installation/upgrade) agent 2。\ 2. 将模板[链接](/manual/config/templates/linking#linking_a_template) 到目标主机 (如果模板在您的Zabbix中不可用，您可能需要先导入模板文件.xml文件 - 查看[开箱即用的模板](/manual/config/templates_out_of_the_box) 说明部分）。\ 3. 根据需要调整必配宏的值。注意，用户宏可用于覆盖配置参数。\ 4. 配置要监控的实例允许与Zabbix共享数据- 请参阅 *附加步骤/注释* 字段  ::: noteimportant  Zabbix agent 2 模板与插件一起工作。 基本配置可以通过简单地调整用户宏来完成，更深层次的定制可以参考 [插件配置](/manual/config/items/plugins#named_sessions)本身实现。例如，如果插件支持命名会话，则可以通过在配置文件中为每个实体指定具有自己的 URI、用户名和密码的命名会话，监视多个相同类型的实体（例如 MySQL1 和 MySQL2）。 :::  ::: notetip 该页面仅包含最小的一组宏和正确的模板操作所需的设置步骤。 在模板的Readme.md文件中提供了模板的详细说明，包括宏，项和触发器的完整列表（可通过单击模板名称访问）。 :::  |模板名称|必配宏|附加步骤/注释| |-------------|----------------|-------------------------| |[Ceph by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/ceph_agent2/README.md)|**{\$CEPH.API.KEY}** - Ceph API秘钥 (默认: `zabbix_pass`).<br>如果{\$CEPH.CONNSTRING}为URI，秘钥必须设置。<br>如果{\$CEPH.CONNSTRING} 为会话名，则值为空.<br>**{\$CEPH.CONNSTRING}** - 连接字符串; 会话名或URI的格式: <协议(主机:端口)>. URI只支持 HTTPS 协议 .<br>例如: Prod, https://localhost:8003 (默认)<br>**{\$CEPH.USER}** - Ceph监控用户 (默认:`zabbix`).<br>如果{\$CEPH.CONNSTRING}为URI，用户必须设置.<br如果{\$CEPH.CONNSTRING} 为会话名，则值为空.|与 *Ceph* 插件一起使用; 支持给会话命名.<br><br>1. Ceph RESTful模块配置，参见[文档](https://docs.ceph.com/en/latest/mgr/restful/).<br><br>2. 确保RESTful API端点连接的可用性.| |[Docker](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/docker/README.md)|\-|与 *Docker* 插件一起使用; 不支持给会话命名.<br><br>设置Docker API 端点路径,在agent 2的[配置文件](/manual/appendix/config/zabbix_agent2) 中修改参数`Plugins.Docker.Endpoint` (默认: `Plugins.Docker.Endpoint=unix:///var/run/docker.sock`).<br><br>可用性测试, 执行:<br>`zabbix_get -s docker-host -k docker.info`| |[Memcached](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/memcached/README.md)|**{\$MEMCACHED.CONN.URI}** - URI连接字符串格式; 端口可选; 密码未使用.<br>如果不设置, 插件默认值: tcp://localhost:11211.<br>例子: tcp://127.0.0.1:11211, tcp://localhost, unix:/var/run/memcached.sock.|与 *Memcached* 插件一起使用; 支持给会话命名.<br><br>可用性测试, 执行:<br>`zabbix_get -s memcached-host -k memcached.ping`| |[MongoDB cluster by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mongodb_cluster/README.md)|**{\$MONGODB.CONNSTRING}** - URI连接字符串格式; 密码未使用 (默认: tcp://localhost:27017).<br>支持会话名称或以下格式定义的URI: %% <protocol(host:port)>%%<br>URI仅支持TCP 协议.<br>例子: MongoDB1, tcp://172.16.0.10<br>**{\$MONGODB.USER}**, **{\$MONGODB.PASSWORD}** - MongoDB 凭证(默认: none).<br>如果未设置，同时 {\$MONGODB.CONNSTRING}为URI, 配置文件的参数将被使用.<br> 如果{\$MONGODB.CONNSTRING}为会话名，必须为空.|与 *MongoDB* 插件一起使用; 支持给会话命名.<br>MongoDB 配置说明, 参见[插件](/manual/config/items/plugins).<br>可用性测试, 执行:<br>`zabbix_get -s mongos.node -k 'mongodb.ping["{\$MONGODB.CONNSTRING}","{\$MONGODB.USER}","{\$MONGODB.PASSWORD}"]"`| |[MongoDB node by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mongodb/README.md)|**{\$MONGODB.CONNSTRING}** - URI连接字符串格式; 密码未使用(默认: tcp://localhost:27017).<br>支持会话名称或以下格式定义的URI: %% <protocol(host:port)>%%<br>URI仅支持TCP 协议.<br>例子: MongoDB1, tcp://172.16.0.10<br>**{\$MONGODB.USER}**, **{\$MONGODB.PASSWORD}** - MongoDB 凭证(默认: none).<br>如果未设置，同时 {\$MONGODB.CONNSTRING}为URI, 配置文件的参数将被使用.<br>如果{\$MONGODB.CONNSTRING}为会话名，必须为空.|与 *MongoDB* 插件一起使用; 支持给会话命名.<br>MongoDB 配置说明, 参见 [参见](/manual/config/items/plugins).<br>可用性测试, 执行:<br>`zabbix_get -s mongodb.node -k 'mongodb.ping["{\$MONGODB.CONNSTRING}","{\$MONGODB.USER}","{\$MONGODB.PASSWORD}"]"`| |[MySQL by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_agent2/README.md)|**{\$MYSQL.DSN}** - MySQL实例的系统数据源名称 (默认: <输入您的DSN>).<br>支持会话名称或以下格式定义的URI: %% <protocol(host:port or /path/to/socket)/>%%<br>URI支持 TCP 和 Unix 协议.<br>例子: MySQL1, tcp://localhost:3306, tcp://172.16.0.10, unix:/var/run/mysql.sock<br>**{\$MYSQL.USER}**, **{\$MYSQL.PASSWORD}** - MySQL 凭证(默认: none).如果 {\$MYSQL.DSN} 为URI，必须设置.<br>如果{\$MYSQL.DSN}为会话名，必须为空.|与 *MySQL* 插件一起使用; 支持给会话命名.<br><br>赋予MySQL监控用户必要的权限, 执行:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON *.* TO '<username>'@'%';`<br><br>参见MySQL 文档查看关于  [用户权限](https://dev.mysql.com/doc/refman/8.0/en/grant.html) 和[Unix sockets](https://dev.mysql.com/doc/refman/8.0/en/problems-with-mysql-sock.html)信息.| |[Oracle by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_agent2/README.md)|**{\$ORACLE.CONNSTRING}** - 连接串; 支持会话名称或以下格式定义的URI: <protocol(host:port or /path/to/socket)/><br>URI仅支持TCP 协议.<br>例子: Oracle1, tcp://localhost:1521<br><br>**{\$ORACLE.SERVICE}** - Oracle服务名 (默认: ORA).如果{\$ORACLE.CONNSTRING}为URI，必须设置.<br>如果{\$ORACLE.CONNSTRING}为会话名，必须为空.<br><br>**{\$ORACLE.USER}**, **{\$ORACLE.PASSWORD}** - Oracle 凭证(默认 用户名: zabbix, 密码: zabbix\_password). 如果{\$ORACLE.CONNSTRING}为URI，必须设置.<br>如果{\$ORACLE.CONNSTRING}为会话名，必须为空.|与*Oracle* 插件一起使用; 支持给会话命名.<br><br>安装[Oracle Instant Client](https://www.oracle.com/database/technologies/instant-client/downloads.html).<br>创建并赋予Oracle用户必要的权限, 执行:<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Grant access to the zabbix_mon user.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br>`GRANT SELECT ON SYS.DBA_DATA_FILES TO zabbix_mon;`<br>`GRANT SELECT ON V\$ACTIVE_SESSION_HISTORY TO zabbix_mon;`<br>`GRANT SELECT ON V\$ARCHIVE_DEST TO zabbix_mon;`<br>`GRANT SELECT ON V\$ASM_DISKGROUP TO zabbix_mon;`<br>`GRANT SELECT ON V\$DATABASE TO zabbix_mon;`<br>`GRANT SELECT ON V\$DATAFILE TO zabbix_mon;`<br>`GRANT SELECT ON V\$INSTANCE TO zabbix_mon;`<br>`GRANT SELECT ON V\$LOG TO zabbix_mon;`<br>`GRANT SELECT ON V\$OSSTAT TO zabbix_mon;`<br>`GRANT SELECT ON V\$PGASTAT TO zabbix_mon;`<br>`GRANT SELECT ON V\$PROCESS TO zabbix_mon;`<br>`GRANT SELECT ON V\$RECOVERY_FILE_DEST TO zabbix_mon;`<br>`GRANT SELECT ON V\$RESTORE_POINT TO zabbix_mon;`<br>`GRANT SELECT ON V\$SESSION TO zabbix_mon;`<br>`GRANT SELECT ON V\$SGASTAT TO zabbix_mon;`<br>`GRANT SELECT ON V\$SYSMETRIC TO zabbix_mon;`<br>`GRANT SELECT ON V\$SYSTEM_PARAMETER TO zabbix_mon;`| |[PostgreSQL Agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql_agent2)|**{\$PG.URI}** - 连接串; 支持会话名称或以下格式定义的URI:<br>%% <protocol(host:port or /path/to/socket)/>%%. URI支持 TCP 和 Unix 协议.<br>例子: Postgres1, tcp://localhost:5432, tcp://172.16.0.10<br>**{\$PG.USER}**, **{\$PG.PASSWORD}** - PostgreSQL 凭证(默认 用户: postgres, 密码:postgres).<br>如果 {\$PG.URI}为URI，必须设置. 如果 {\$PG.URI} 为会话名，必须为空.|与 *PostgreSQL* 插件一起使用; 支持给会话命名.<br><br>针对PostgreSQL 10或更新的版本创建并赋予用户必要的权限, 执行:<br>`CREATE USER 'zbx_monitor' IDENTIFIED BY '<password>';`<br>`GRANT EXECUTE ON FUNCTION pg_catalog.pg_ls_dir(text) TO zbx_monitor;`\\\\`GRANT EXECUTE ON FUNCTION pg_catalog.pg_stat_file(text) TO zbx_monitor;`<br><br>编辑 pg\_hba.conf 设置Zabbix agent白名单 (详情参见[PostgreSQL 文档](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html)).| |[Redis](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/redis/README.md)|**{\$REDIS.CONN.URI}** - URI连接串格式; 端口为可选项; 密码未使用.<br>若未设置, 插件默认值: tcp://localhost:6379|与 *Redis* 插件一起使用; 支持给会话命名.<br><br>可用性测试, 执行:<br>`zabbix_get -s redis-master -k redis.ping`| |[SMART by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/module/smart_agent2/README.md) / [SMART by Zabbix agent 2 active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/module/smart_agent2_active)|\-| 执行Zabbix agent 2的用户对smartctl 命令必须能Sudo/root提权. 支持smartctl的最小版本是7.1.<br><br>磁盘发现 LLD 规则查找所有开启 S.M.A.R.T. 的 HDD、SSD、NVMe 磁盘.<br><br>属性发现 LLD 规则查找每个磁盘的所有供应商特定属性.<br><br>要跳过某些属性，请在主机级别使用 {\$SMART.DISK.NAME.MATCHES} 中的磁盘名称和 {\$SMART.ATTRIBUTE.ID.MATCHES} 中的属性 ID 设置正则表达式.| |[Systemd by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/systemd/README.md)|\-|无需特定配置.| |[Website certificate by Zabbix agent 2](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/certificate_agent2/README.md)|**{\$CERT.WEBSITE.HOSTNAME}** - 连接Web站点的DNS名称 (默认: <输入您的DNS名称>).|与*WebCertificate* 插件一起使用; 支持给会话命名.<br>可用性测试, 执行:<br>`zabbix_get -s <zabbix_agent_addr> -k web.certificat e.get[<website_DNS_name>]`<br><br>使用 Zabbix 代理接口为 TLS/SSL 证书创建单独的主机并将模板链接到该主机.|

en-us	#### Zabbix agent checks on Windows  Non-existing DNS entries in a `Server` parameter of Zabbix agent configuration file (zabbix\_agentd.conf) may increase Zabbix agent response time on Windows. This happens because Windows DNS caching daemon doesn't cache negative responses for IPv4 addresses. However, for IPv6 addresses negative responses are cached, so a possible workaround to this is disabling IPv4 on the host.
zh-cn	#### Windows 的 Zabbix agent   Zabbix agent 配置文件  (zabbix\_agentd.conf) 中设置非 DNS 性质的 `Server` 参数可能会增加 Windows 上 Zabbix agent 的响应时间。发生这种情况是因为 Windows DNS 缓存守护程序不会缓存 IPv4 地址的否定响应。但是会缓存  IPv6 地址的否定响应，因此可能的解决方法是在主机上禁用 IPv4。

en-us	# Zabbix agent template operation  Steps to ensure correct operation of templates that collect metrics with [Zabbix agent](/manual/concepts/agent):  1\. Make sure that Zabbix agent is installed on the host. For active checks, also make sure that the host is added to the 'ServerActive' parameter of the agent [configuration file](/manual/appendix/config/zabbix_agentd).\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to a target host (if the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\ 3. Adjust the values of mandatory macros as needed.\ 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column.  ::: notetip  This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name).  :::  |Template name|Mandatory macros|Additional steps/comments| |-------------|----------------|-------------------------| |[Apache by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/apache_agent/README.md)|**{$APACHE.STATUS.HOST}** - the hostname or IP address of Apache status page (default: 127.0.0.1)<br>**{$APACHE.STATUS.PATH}** - the URL path (default: server-status?auto)<br>**{$APACHE.STATUS.PORT}** - the port of Apache status page (default: 80)|Apache module mod\_status should be set (see Apache [documentation](https://httpd.apache.org/docs/current/mod/mod_status.html) for details).<br>To check availability, run:<br>`httpd -M 2>/dev/null \| grep status_module`<br><br>Apache configuration example:<br>`<Location "/server-status">`<br>`SetHandler server-status`<br>`Require host example.com`<br>`</Location>`| |[HAProxy by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/haproxy_agent/README.md)|**{$HAPROXY.STATS.PATH}** - the path of HAProxy Stats page (default: stats)<br>**{$HAPROXY.STATS.PORT}** - the port of HAProxy Stats host or container (default: 8404)<br>**{$HAPROXY.STATS.SCHEME}** - the scheme of HAProxy Stats page. Supported: http (default), https|HAProxy Stats page should be set up (see HAProxy [blog post](https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/) for details or template's Readme.md for configuration example).| |[IIS by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/iis_agent) / [IIS by Zabbix agent active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/iis_agent_active/README.md)|**{$IIS.PORT}** - the port IIS Server listens on (default: 80)<br>**{$IIS.SERVICE}** - the service for port check (default: http). See [net.tcp.service](/manual/config/items/itemtypes/simple_checks) section for details.|The server should have the following roles:<br>[Web Server](https://docs.microsoft.com/en-us/iis/web-hosting/web-server-for-shared-hosting/installing-the-web-server-role)<br>[IIS Management Scripts and Tools](https://docs.microsoft.com/en-us/iis/manage/scripting/managing-applications-and-application-pools-on-iis-with-wmi)<br><br>See IIS documentation for details.| |[Microsoft Exchange Server 2016 by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/exchange/README.md)/[Microsoft Exchange Server 2016 by Zabbix agent active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/exchange_active/README.md)|<|Note, that the template doesn't provide information about Windows services state. It is recommended to use it together with *OS Windows by Zabbix agent* or *OS Windows by Zabbix agent active* template.| |[Nginx by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_agent/README.md)|**{$NGINX.STUB\_STATUS.HOST}** - the hostname or IP address of Nginx stub\_status host or container (default: localhost)<br>**{$NGINX.STUB\_STATUS.PATH}** - the path of Nginx stub\_status page (default: basic\_status)<br>**{$NGINX.STUB\_STATUS.PORT}** - the port of Nginx stub\_status host or container (default: 80)|`ngx_http_stub_status_module` should be set up (see Nginx [documentation](https://nginx.org/en/docs/http/ngx_http_stub_status_module.html) for details or template's Readme.md for configuration example).<br>To check availability, run:<br>`nginx -V 2>&1 \| grep -o with-http_stub_status_module`| |[PHP-FPM by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/php-fpm_agent/README.md)|**{$PHP\_FPM.HOST}** - a hostname or an IP of PHP-FPM status host or container (default: `localhost`)<br>**{$PHP\_FPM.PING.PAGE}** - PHP-FPM ping page path (default:`ping`)<br>**{$PHP\_FPM.PORT}** - the port of PHP-FPM status host or container (default: `80`)<br>**{$PHP\_FPM.PROCESS\_NAME}** - PHP-FPM process name (default:`php-fpm`)<br>**{$PHP\_FPM.STATUS.PAGE}** - PHP-FPM status page path (default:`status`)|1\. Open the php-fpm configuration file and enable the status page:<br>`pm.status_path = /status`<br>`ping.path = /ping`<br><br>2. Validate the syntax: `$ php-fpm7 -t`<br><br>3. Reload the php-fpm service.<br><br>4. In the Nginx Server Block (virtual host) configuration file, add (see template's *Readme.md* for an expanded example with comments):<br>`location ~ ^/(status\|ping)$ {`<br>`access_log off;`<br>`fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;`<br>`fastcgi_index index.php;`<br>`include fastcgi_params;`<br>`fastcgi_pass 127.0.0.1:9000;`<br>`}`<br><br>5. Check the syntax: `$ nginx -t`<br><br>6. Reload Nginx<br><br>7. Verify: `curl -L 127.0.0.1/status`| |[RabbitMQ cluster by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/rabbitmq_agent)|**{$RABBITMQ.API.CLUSTER\_HOST}** - the hostname or IP address of RabbitMQ cluster API endpoint (default:`127.0.0.1`)<br>**{$RABBITMQ.API.USER}**, **{$RABBITMQ.API.PASSWORD}** - RabbitMQ login credentials (default username: zbx\_monitor, password: zabbix)|Enable RabbitMQ management plugin (see [RabbitMQ documentation](https://www.rabbitmq.com/management.html)).<br><br>To create a RabbitMQ user with necessary permissions for monitoring, run:<br>'' rabbitmqctl add\_user zbx\_monitor <PASSWORD> ''<br>`rabbitmqctl set_permissions -p / zbx_monitor %% "" "" ".*"%%`<br>`rabbitmqctl set_user_tags zbx_monitor monitoring`<br><br>If the cluster consists of several nodes, it is recommended to assign the cluster template to a separate balancing host. In case of a single-node installation, the cluster template can be assigned to the host with a node template.| |[MySQL by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_agent/README.md)|**{$MYSQL.HOST}** - the hostname or IP address of MySQL host or container (default: localhost)<br>**{$MYSQL.PORT}** - the database service port (default: 3306)|1\. If necessary, add the path to the mysql and mysqladmin utilities to the global environment variable PATH.<br><br>2. Copy the `template_db_mysql.conf` file from *templates* directory of Zabbix into folder with Zabbix agent configuration (/etc/zabbix/zabbix\_agentd.d/ by default) and restart Zabbix agent.<br><br>3. Create MySQL user `zbx_monitor`. To grant required privileges to the user, run:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br>(see [MYSQL documentation](https://dev.mysql.com/doc/refman/8.0/en/grant.html) for details).<br><br>4. Create `.my.cnf` in the home directory of Zabbix agent for Linux (/var/lib/zabbix by default ) or `my.cnf` in c:\\ for Windows. The file must have three strings:<br>`[client]`<br>''user='zbx\_monitor' ''<br>''password='<password>' ''| |[PostgreSQL](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql/README.md)|**{$PG.DB}** - the database name to connect to the server (default: postgres)<br>**{$PG.HOST}** - the database server host or socket directory (default:127.0.0.1)<br>**{$PG.PORT}** - the database server port (default: 5432)<br>**{$PG.USER}** - the database username (default: zbx\_monitor)|1\. Create a read-only user `zbx_monitor` with proper access to PostgreSQL server. For PostgreSQL 10 and newer, run:<br>`CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>' INHERIT;`<br>`GRANT pg_monitor TO zbx_monitor;`<br>For older PostgreSQL versions, run:<br>`CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>';`<br>`GRANT SELECT ON pg_stat_database TO zbx_monitor;`<br><br>2. Copy `postgresql/` to Zabbix agent home directory (/var/lib/zabbix/).<br><br>3. Copy `template_db_postgresql.conf` from *templates* directory of Zabbix to Zabbix agent configuration directory (/etc/zabbix/zabbix\_agentd.d/) and restart Zabbix agent.<br><br>4. Edit `pg_hba.conf` to allow connections from Zabbix agent (see [PostgreSQL documentation](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html) for details).<br>Row examples:<br>`host all zbx_monitor 127.0.0.1/32 trust`<br>`host all zbx_monitor 0.0.0.0/0 md5`<br>`host all zbx_monitor ::0/0 md5`<br><br>5. To monitor a remote server, create a `.pgpass` file in Zabbix agent home directory (/var/lib/zabbix/) and add rows with the instance, port, database, user and password information (see [PostgreSQL documentation](https://www.postgresql.org/docs/current/libpq-pgpass.html) for details).<br>Row examples:<br>`<REMOTE_HOST1>:5432:postgres:zbx_monitor:<PASSWORD>`<br>`*:5432:postgres:zbx_monitor:<PASSWORD>`|
zh-cn	 # Zabbix agent 模板操作  确保通过[Zabbix agent](/manual/concepts/agent)收集模板指标的正确步骤:  1\. 确保主机上安装了Zabbix agent。对于主动模式 , 还需要确认agent [配置文件](/manual/appendix/config/zabbix_agentd)已添加`ServerActive`参数。\ 2. 将模板[链接](/manual/config/templates/linking#linking_a_template) 到目标主机 (如果模板在您的Zabbix中不可用，您可能需要先导入模板文件.xml文件 - 查看[开箱即用的模板](/manual/config/templates_out_of_the_box) 说明部分）。\ 3.根据需要调整必配宏的值。\ 4. 配置要监控的实例允许与Zabbix共享数据- 请参阅 *附加步骤/注释* 字段。  ::: notetip 该页面仅包含最小的一组宏和正确的模板操作所需的设置步骤。 在模板的Readme.md文件中提供了模板的详细说明，包括宏，项和触发器的完整列表（可通过单击模板名称访问）。 :::  |模板名称|必配宏|附加步骤/注释| |-------------|----------------|-------------------------| |[Apache by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/apache_agent/README.md)|**{\$APACHE.STATUS.HOST}** - Apache状态页面的主机名或IP地址 (默认: 127.0.0.1)<br>**{\$APACHE.STATUS.PATH}** - URL 路径 (默认: server-status?auto)<br>**{\$APACHE.STATUS.PORT}** - Apache状态页面的端口 (默认: 80)|Apache 模块 `mod_status` 应该设置(详情参见 Apache [文档](https://httpd.apache.org/docs/current/mod/mod_status.html)).<br>可用性检查, 执行:<br>`httpd -M 2>/dev/null \| grep status_module`<br><br>Apache 配置样例:<br>`<Location "/server-status">`<br>`SetHandler server-status`<br>`Require host example.com`<br>`</Location>`| |[HAProxy by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/haproxy_agent/README.md)|**{\$HAPROXY.STATS.PATH}** - HAProxy统计页面的路径 (默认: stats)<br>**{\$HAPROXY.STATS.PORT}** - HAProxy的端口统计主机或容器 (默认: 8404)<br>**{\$HAPROXY.STATS.SCHEME}** - HAProxy状态页面支持的协议. 支持: http (默认), https|HAProxy状态页需要设置 (配置案例详情参见 HAProxy[博文](https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/) 或模板的 Readme.md文件).| |[IIS by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/iis_agent) / [IIS by Zabbix agent active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/iis_agent_active/README.md)|**{\$IIS.PORT}** - IIS Server 监听端口 (默认: 80)<br>**{\$IIS.SERVICE}** - 端口检查服务 (默认: http). 详情参见 [net.tcp.service](/manual/config/items/itemtypes/simple_checks)部分.|IIS服务器应具有以下角色:<br>[Web Server](https://docs.microsoft.com/en-us/iis/web-hosting/web-server-for-shared-hosting/installing-the-web-server-role)<br>[IIS Management Scripts and Tools](https://docs.microsoft.com/en-us/iis/manage/scripting/managing-applications-and-application-pools-on-iis-with-wmi)<br><br>详情参见 IIS 文档.| |[Microsoft Exchange Server 2016 by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/exchange/README.md)/[Microsoft Exchange Server 2016 by Zabbix agent active](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/exchange_active/README.md)|<|请注意，该模板不提供有关 Windows 服务状态的信息。 建议与 *OS Windows by Zabbix agent* 或 *OS Windows by Zabbix agent active* 模板一起使用。| |[Nginx by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/nginx_agent/README.md)|**{\$NGINX.STUB\_STATUS.HOST}** - NGINX stub\_status 主机或者容器的主机名或IP地址 (默认: localhost)<br>**{\$NGINX.STUB\_STATUS.PATH}** - NGINX stub\_status 页面访问路径 (默认: basic\_status)<br>**{\$NGINX.STUB\_STATUS.PORT}** - NGINX stub\_status 主机或容器监听端口 (默认: 80)|`ngx_http_stub_status_module` 需要被设置 (配置样例详情参见 Nginx [文档](https://nginx.org/en/docs/http/ngx_http_stub_status_module.html)或模板的 Readme.md文件).<br>可用性检查, 执行:<br>`nginx -V 2>&1 \| grep -o with-http_stub_status_module`| |[PHP-FPM by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/php-fpm_agent/README.md)|**{\$PHP\_FPM.HOST}** - PHP-FPM 主机或容器的主机名或IP地址 (默认: `localhost`)<br>**{\$PHP\_FPM.PING.PAGE}** - PHP-FPM ping页面访问路径 (默认:`ping`)<br>**{\$PHP\_FPM.PORT}** - PHP-FPM 主机或容器的端口号 (默认: `80`)<br>**{\$PHP\_FPM.PROCESS\_NAME}** - PHP-FPM 进程名 (默认:`php-fpm`)<br>**{\$PHP\_FPM.STATUS.PAGE}** - PHP-FPM 状态页面访问路径 (默认:`status`)|1\. 打开配置文件并启用状态页:<br>`pm.status_path = /status`<br>`ping.path = /ping`<br><br>2. 语法验证: `\$ php-fpm7 -t`<br><br>3. 重新加载 php-fpm 服务.<br><br>4. 在Nginx配置文件Server配置块(虚拟主机) 中, 添加 (带注释的扩展样例参见模板的*Readme.md*):<br>`location ~ ^/(status\|ping)\$ {`<br>`access_log off;`<br>`fastcgi_param SCRIPT_FILENAME \$document_root\$fastcgi_script_name;`<br>`fastcgi_index index.php;`<br>`include fastcgi_params;`<br>`fastcgi_pass 127.0.0.1:9000;`<br>`}`<br><br>5. 语法检查: `\$ nginx -t`<br><br>6. 重新加载Nginx<br><br>7. 检查状态页: `curl -L 127.0.0.1/status`| |[RabbitMQ cluster by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/rabbitmq_agent)|**{\$RABBITMQ.API.CLUSTER\_HOST}** - RabbitMQ 集群 API 端点的主机名或IP地址 (默认:`127.0.0.1`)<br>**{\$RABBITMQ.API.USER}**, **{\$RABBITMQ.API.PASSWORD}** - RabbitMQ 登陆凭证 (默认 用户: zbx\_monitor, 密码: zabbix)|启用 RabbitMQ 管理插件(参见 [RabbitMQ 文档](https://www.rabbitmq.com/management.html)).<br><br>创建一个 RabbitMQ监控用户，赋予必要的权限, 执行:<br>'' rabbitmqctl add\_user zbx\_monitor <PASSWORD> ''<br>`rabbitmqctl set_permissions -p / zbx_monitor %% "" "" ".*"%%`<br>`rabbitmqctl set_user_tags zbx_monitor monitoring`<br><br>单节点安装时,可将集群模板分配给已安装节点模板的主机。如果群集由多个节点组成，建议将群集模板分配给一个单独的负载主机使用.| |[MySQL by Zabbix agent](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_agent/README.md)|**{\$MYSQL.HOST}** - MySQL 主机或容器的主机名或IP地址 (默认: localhost)<br>**{\$MYSQL.PORT}** - 数据库服务端口 (默认: 3306)|1\.如有必要，将 mysql 和 mysqladmin的路径添加到全局环境变量 PATH.<br><br>2. 将Zabbix *templates*目录下的 `template_db_mysql.conf`文件复制到Zabbix agent子配置文件目录中(默认为/etc/zabbix/zabbix\_agentd.d/)，并重启Zabbix agent.<br><br>3. 创建MySQL用户 `zbx_monitor`. 赋予该用户必要的权限, 执行:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br>(详情参见 [MYSQL 文档](https://dev.mysql.com/doc/refman/8.0/en/grant.html)).<br><br>4.在Linux主机中，Zabbix agent需要在home目录下创建 `.my.cnf` (默认为/var/lib/zabbix) 或在Windows主机的c:\\中创建`my.cnf`. 该文件必须包含三行字符串:<br>`[client]`<br>''user='zbx\_monitor' ''<br>''password='<password>' ''| |[PostgreSQL](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql/README.md)|**{\$PG.DB}** - 连接到服务器的数据库名称 (默认: postgres)<br>**{\$PG.HOST}** - 数据库服务器主机或套接字目录 (默认:127.0.0.1)<br>**{\$PG.PORT}** - 数据库服务器监听端口 (默认: 5432)<br>**{\$PG.USER}** - 数据库用户名 (默认: zbx\_monitor)|1\. 创建一个只读用户 `zbx_monitor` 以访问 PostgreSQL 服务器。 对于 PostgreSQL 10 和更新版本，执行:<br>`CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>' INHERIT;`<br>`GRANT pg_monitor TO zbx_monitor;`<br>对于老的 PostgreSQL 版本，执行:<br>`CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>';`<br>`GRANT SELECT ON pg_stat_database TO zbx_monitor;`<br><br>2. 复制`postgresql/` 至 Zabbix agent home目录 (/var/lib/zabbix/).<br><br>3. 将Zabbix *templates*目录下的 `template_db_postgresql.conf`文件复制到Zabbix agent子配置文件目录中 (/etc/zabbix/zabbix\_agentd.d/) 并重启 Zabbix agent.<br><br>4. 编辑`pg_hba.conf`为Zabbix agent设置白名单 (详情参见 [PostgreSQL 文档](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html)).<br>例子:<br>`host all zbx_monitor 127.0.0.1/32 trust`<br>`host all zbx_monitor 0.0.0.0/0 md5`<br>`host all zbx_monitor ::0/0 md5`<br><br>5. 监控一个远程服务器, 在创建Zabbix agent home 目录(/var/lib/zabbix/) 中创建`.pgpass` 文件， 并在每一行中添加实例、端口、数据库、用户、密码信息 (详情参见 [PostgreSQL 文档](https://www.postgresql.org/docs/current/libpq-pgpass.html)).<br>例子:<br>`<REMOTE_HOST1>:5432:postgres:zbx_monitor:<PASSWORD>`<br>`*:5432:postgres:zbx_monitor:<PASSWORD>`|

en-us	# Zabbix API changes in 6.0
zh-cn	# Zabbix API 在 6.0 中的变化

en-us	#### Zabbix configuration
zh-cn	#### Zabbix 配置

en-us	#### Zabbix configuration  1\. In Zabbix, go to SAML settings in the *Administration → Authentication* section and copy information from Okta setup instructions into corresponding fields:  -   Identity Provider Single Sign-On URL → SSO service URL -   Identity Provider Issuer → IdP entity ID -   Username attribute → Attribute name (usrEmail) -   SP entity ID → Audience URI  2\. Download the certificate provided in the Okta setup instructions page into *ui/conf/certs* folder as idp.crt, and set permission 644 by running:      chmod 644 idp.crt  Note, that if you have upgraded to Zabbix 5.0 from an older version, you will also need to manually add these lines to zabbix.conf.php file (located in the //ui/conf/ // directory):      // Used for SAML authentication.     $SSO['SP_KEY'] = 'conf/certs/sp.key'; // Path to your private key.     $SSO['SP_CERT'] = 'conf/certs/sp.crt'; // Path to your public key.     $SSO['IDP_CERT'] = 'conf/certs/idp.crt'; // Path to IdP public key.     $SSO['SETTINGS'] = []; // Additional settings  See generic [SAML Authentication](/manual/web_interface/frontend_sections/administration/authentication#saml_authentication) instructions for more details.  3\. If *Assertion Encryption* has been set to Encrypted in Okta, a checkbox "Assertions" of the *Encrypt* parameter should be marked in Zabbix as well.  ![](../../../../assets/en/manual/appendix/install/okta_zabbix.png)  4\. Press the "Update" button to save these settings.  ::: noteclassic  To sign in with SAML, the username in Zabbix should match the Okta e-mail. These settings can be changed in the *Administration → Users* section of Zabbix web interface.  :::
zh-cn	#### Zabbix 配置  1\. 在 Zabbix 中，转到*Administration → Authentication* 中的 SAML 设置，并将 Okta 设置指令中的信息复制到相应的字段中  -   Identity Provider Single Sign-On URL → SSO service URL -   Identity Provider Issuer → IdP entity ID -   Username attribute → Attribute name (usrEmail) -   SP entity ID → Audience URI  2\. 将 Okta 设置说明页面中提供的证书下载到 *ui/conf/certs* 文件夹中，作为 idp.crt，并设置权限为 644：      chmod 644 idp.crt  请注意，如果您已从旧版本升级到Zabbix 5.0，则还需要手动将这些行添加到zabbix.conf.php文件中 (located in the //ui/conf/ // directory):      // Used for SAML authentication.     $SSO['SP_KEY'] = 'conf/certs/sp.key'; // Path to your private key.     $SSO['SP_CERT'] = 'conf/certs/sp.crt'; // Path to your public key.     $SSO['IDP_CERT'] = 'conf/certs/idp.crt'; // Path to IdP public key.     $SSO['SETTINGS'] = []; // Additional settings  有关更多详细信息的说明。请参阅 [SAML Authentication](/manual/web_interface/frontend_sections/administration/authentication#saml_authentication)  3\. 如果*Assertion Encryption*已设置为在 Okta 中加密，则选中 "Assertions" 参数的*Encrypt* 也应在Zabbix中标记  ![](../../../../assets/en/manual/appendix/install/okta_zabbix.png)  4\. 按"Update"按钮保存这些设置。  ::: noteclassic 要使用 SAML 登录，Zabbix 中的用户名应与 Okta 电子邮件匹配。这些设置可以在Zabbix Web界面的*Administration → Users*进行更改。 :::

en-us	#### Zabbix configuration parameters  Many parameters may be tuned to get optimal performance.  To achieve the best performance (i.e. when pollers do not compete with history syncers for common resources in the configuration cache) it is recommended to keep low numbers of history pollers, pollers, unreachable pollers, Java pollers, ODBC pollers on Zabbix server and make them as free as possible by delegating all the polling to Zabbix proxies.
zh-cn	 #### Zabbix  配置参数  可以调整许多参数以获得最佳性能。  为了获得最佳性能（即当轮询器不与历史同步器竞争配置缓存中的公共资源时），建议在 Zabbix server上保留少量的历史轮询器、轮询器、不可达轮询器、Java 轮询器、ODBC 轮询器，并使它们通过将所有轮询委托给 Zabbix 代理来尽可能释放。

en-us	#### - Zabbix configuration  Zabbix appliance setup has the following passwords and configuration changes:
zh-cn	#### - Zabbix 配置  Zabbix Appliance 安装过程中使用了下列密码和配置：

en-us	# Zabbix documentation  These pages contain official Zabbix documentation.  Use the sidebar navigation to browse documentation pages.  To be able to watch pages, log in with your [Zabbix forums](http://www.zabbix.com/forum/) username and password.
zh-cn	 # Zabbix 文档  这些页面包含了Zabbix的官方文档。  使用侧边栏导航来浏览文档页面。  为了能够观看页面，请用您的 [Zabbix 论坛](http://www.zabbix.com/forum/) 用户名和密码。

en-us	#### Zabbix frontend configuration  Depending on the web server used (Apache/Nginx) edit the corresponding configuration file for Zabbix frontend:  -   For Apache the configuration file is located in     `/etc/apache2/conf.d/zabbix.conf`. Some PHP settings are already     configured. But it's necessary to uncomment the "date.timezone"     setting and [set the right     timezone](http://php.net/manual/en/timezones.php) for you.  ```{=html} <!-- --> ```     php_value max_execution_time 300     php_value memory_limit 128M     php_value post_max_size 16M     php_value upload_max_filesize 2M     php_value max_input_time 300     php_value max_input_vars 10000     php_value always_populate_raw_post_data -1     # php_value date.timezone Europe/Riga  -   The zabbix-nginx-conf package installs a separate Nginx server for     Zabbix frontend. Its configuration file is located in     `/etc/nginx/conf.d/zabbix.conf`. For Zabbix frontend to work, it's     necessary to uncomment and set `listen` and/or `server_name`     directives.  ```{=html} <!-- --> ```     # listen 80;     # server_name example.com;  -   Zabbix uses its own dedicated php-fpm connection pool with Nginx:  Its configuration file is located in `/etc/php7/fpm/php-fpm.d/zabbix.conf`. Some PHP settings are already configured. But it's necessary to set the right [date.timezone](http://php.net/manual/en/timezones.php) setting for you.      php_value[max_execution_time] = 300     php_value[memory_limit] = 128M     php_value[post_max_size] = 16M     php_value[upload_max_filesize] = 2M     php_value[max_input_time] = 300     php_value[max_input_vars] = 10000     ; php_value[date.timezone] = Europe/Riga  Now you are ready to proceed with [frontend installation steps](/manual/installation/install#installing_frontend) which will allow you to access your newly installed Zabbix.  Note that a Zabbix proxy does not have a frontend; it communicates with Zabbix server only.
zh-cn	#### Zabbix 前端配置  根据使用的网络服务器 (Apache/Nginx) 为Zabbix前端编辑相应配置文件：  -   对于Apache，配置文件在 `/etc/apache2/conf.d/zabbix.conf`。一些PHP设置已经配置好了。但还是有必要取消 "date.timezone" 设置的注释， [设置正确的时区](http://php.net/manual/en/timezones.php) 。  ```{=html} <!-- --> ```     php_value max_execution_time 300     php_value memory_limit 128M     php_value post_max_size 16M     php_value upload_max_filesize 2M     php_value max_input_time 300     php_value max_input_vars 10000     php_value always_populate_raw_post_data -1     # php_value date.timezone Europe/Riga  -   zabbix-nginx-conf包为Zabbix 前端安装了单独的 Nginx server。它的配置文件位于`/etc/nginx/conf.d/zabbix.conf`。为了运行Zabbix 前端，还是有必要取消注释并设置 `listen` 和/或 `server_name`指令。  ```{=html} <!-- --> ```     # listen 80;     # server_name example.com;  -   Zabbix 为 Nginx 使用自己的专用php-fpm连接池：  它的配置文件位于`/etc/php7/fpm/php-fpm.d/zabbix.conf`。一些PHP设置已经设置好了。但你还是有必要正确设置 [date.timezone](http://php.net/manual/en/timezones.php)。      php_value[max_execution_time] = 300     php_value[memory_limit] = 128M     php_value[post_max_size] = 16M     php_value[upload_max_filesize] = 2M     php_value[max_input_time] = 300     php_value[max_input_vars] = 10000     ; php_value[date.timezone] = Europe/Riga  现在，你可以继续进行 [前端安装步骤](/manual/installation/install#installing_frontend) 以访问新安装的Zabbix。  请注意Zabbix proxy没有前端，只与Zabbix server 通信。

en-us	#### zabbix\_get and zabbix\_sender with encryption  See [zabbix\_get](/manpages/zabbix_get) and [zabbix\_sender](/manpages/zabbix_sender) manpages for using them with encryption.
zh-cn	 #### zabbix\_get and zabbix\_sender与加密  请参阅[zabbix\_get](/manpages/zabbix_get)和[zabbix\_sender](/manpages/zabbix_sender) 操作说明使用加密。

en-us	# Zabbix manpages  These are Zabbix manpages for Zabbix processes.
zh-cn	# Zabbix 手册页  这些是 Zabbix 进程的手册页。

en-us	# Zabbix Manual  Welcome to the user manual for Zabbix software. These pages are created to help users successfully manage their monitoring tasks with Zabbix, from the simple to the more complex ones.
zh-cn	# Zabbix 使用手册  欢迎查阅Zabbix用户使用手册。  Zabbix产品手册由原厂Zabbix技术团队创建、Zabbix中国——上海宏时数据系统有限公司 组织开源社区志愿者翻译并维护。 希望能帮助用户更好地使用Zabbix，解决和管理日常IT运维监控遇到的各种问题。 翻译虽然结束，优化并未停止，如有优化反馈、申请成为译者，欢迎联系小Z 17502189550，market@grandage.cn。

en-us	 ##### Zabbix metrics  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**agent.hostmetadata**|<|<|<| |Agent host metadata.|String||Returns the value of HostMetadata or HostMetadataItem parameters, or empty string if none are defined.<br><br>Supported since Zabbix 6.0.| |**agent.hostname**|<|<|<| |Agent host name.|String| |Returns:<br>As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file;<br>As active check - the name of the current hostname.| |**agent.ping**|<|<|<| |Agent availability check.|Nothing - unavailable<br><br>1 - available| |Use the **nodata()** trigger function to check for host unavailability.| |**agent.variant**|<|<|<| |Variant of Zabbix agent (Zabbix agent or Zabbix agent 2).|Integer| |Example of returned value:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |**agent.version**|<|<|<| |Version of Zabbix agent.|String| |Example of returned value:<br>6.0.3| |**zabbix.stats**\[<ip>,<port>\]|<|<|<| |Return a set of Zabbix server or proxy internal metrics remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).| |**zabbix.stats**\[<ip>,<port>,queue,<from>,<to>\]|<|<|<| |Return number of monitored items in the queue which are delayed on Zabbix server or proxy remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**queue** - constant (to be used as is)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.|
zh-cn	##### Zabbix 指标  |项目键|<|<|<| |---|---|---|---| |说明|返回值|参数|注释| |**agent.hostmetadata**|<|<|<| |代理主机元数据。|字符串||返回 HostMetadata 或 HostMetadataItem 参数的值，如果未定义则返回空字符串。<br><br>自 Zabbix 6.0 起受支持。| |**agent.hostname**|<|<|<| |代理主机名。|字符串| |返回：<br>作为被动检查 - 代理配置文件的主机名参数中列出的第一个主机的名称；<br>作为主动检查 - 当前主机名的名称。| |**agent.ping**|<|<|<| |代理可用性检查。|无 - 不可用<br><br>1 - 可用| |使用**nodata()** 触发器函数检查主机不可用性。| |**agent.variant**|<|<|<| |Zabbix 代理的变体（Zabbix 代理或 Zabbix 代理 2）。|整数| |返回值示例：<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |**agent.version**|<|<|<| |Zabbix agent的版本。|字符串| |返回值示例：<br>6.0.3| |**zabbix.stats**\[<ip>,<port>\]|<|<|<| |远程返回一组 Zabbix 服务器或代理内部指标。|JSON 对象|**ip** - 要远程查询的服务器/代理的 IP/DNS/网络掩码列表（默认为 127.0.0.1）<br>** 端口** - 要远程查询的服务器/代理端口（默认为 10051）|请注意，统计请求只会从“StatsAllowedIP”[服务器]（/manual/appendix/config/zabbix_server）中列出的地址接受 /[proxy](/manual/appendix/config/zabbix_proxy) 目标实例上的参数。<br><br>此监控项返回一组选定的内部指标。 详情参见[Zabbix stats的远程监控](/manual/appendix/items/remote_stats#exposed_metrics)。| |**zabbix.stats**\[<ip>,<port>,queue,<from>,<to>\]|<|<|<| |返回队列中在 Zabbix 服务器或远程代理上延迟的监控项数。|JSON 对象|**ip** - 要远程查询的服务器/代理的 IP/DNS/网络掩码列表（默认为 127.0.0.1 )<br>**port** - 要远程查询的服务器/代理端口（默认为 10051）<br>**queue** - 常量（按原样使用）<br>**from** - 至少延迟（默认为 6 秒）<br>**到** - 最多延迟（默认为无限）|请注意，统计请求只会从“StatsAllowedIP”[服务器]中列出的地址接受 (/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 目标实例上的参数。|

en-us	##### Zabbix packages from OS repositories  Often, OS distributions (in particular, Debian-based distributions) provide their own Zabbix packages.\ Note, that these packages are not supported by Zabbix, they are typically out of date and lack the latest features and bug fixes. Only the packages from [repo.zabbix.com](https://repo.zabbix.com/) are officially supported.  If you are upgrading from packages provided by OS distributions (or had them installed at some point), follow this procedure to switch to official Zabbix packages:  1.  Always uninstall the old packages first. 2.  Check for residual files that may have been left after     deinstallation. 3.  Install official packages following [installation     instructions](https://www.zabbix.com/download) provided by Zabbix.  Never do a direct update, as this may result in a broken installation.
zh-cn	##### 由操作系统存储库中的Zabbix软件包进行升级  通常，发行版本的操作系统（特别是基于 Debian 的发行版）会提供基于自身系统的Zabbix软件包。\ 请注意，Zabbix 不支持这些软件包，它们通常已经过时并且缺乏最新的功能和错误修复。 建议通过由官方支持的 [repo.zabbix.com](https://repo.zabbix.com/) 软件安装包来完成安装。  若需从 OS 发行版提供的软件包进行升级（或在某时已安装），请按照以下步骤换到官方 Zabbix 软件包：  1. 首先，卸载旧版本的安装包。 2. 检查卸载后可能留下的残留文件。 3. 按照Zabbix提供的 [installation instructions](https://www.zabbix.com/download)安装官方包。  切勿进行直接更新，因为这可能会导致安装中断。

en-us	 ### Zabbix Security Advisories and CVE database  See [Zabbix Security Advisories and CVE database](https://www.zabbix.com/security_advisories).
zh-cn	 ### Zabbix 安全公告和 CVE 数据库  请参阅 [Zabbix 安全公告和 CVE 数据库] (https://www.zabbix.com/security_advisories)。

en-us	#### Zabbix sender request  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value"         }     ] } ```
zh-cn	#### Zabbix 发送请求  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value"         }     ] } ```

en-us	#### Zabbix sender request with a timestamp  Alternatively Zabbix sender can send a request with a timestamp and nanoseconds.  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710794,             "ns":592397170         },         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710795,             "ns":192399456         }     ],     "clock":1516712029,     "ns":873386094 } ```
zh-cn	 #### Zabbix sender 带有时间戳的请求  Zabbix sender可以发送一个带有时间戳的请求。  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710794,             "ns":592397170         },         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710795,             "ns":192399456         }     ],     "clock":1516712029,     "ns":873386094 } ```

en-us	##### Zabbix server and frontend  Zabbix server configuration file draft with parameters to be updated:      ### Option: HistoryStorageURL     # History storage HTTP[S] URL.     #     # Mandatory: no     # Default:     # HistoryStorageURL=      ### Option: HistoryStorageTypes     # Comma separated list of value types to be sent to the history storage.     #     # Mandatory: no     # Default:     # HistoryStorageTypes=uint,dbl,str,log,text  Example parameter values to fill the Zabbix server configuration file with:      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text  This configuration forces Zabbix Server to store history values of numeric types in the corresponding database and textual history data in Elasticsearch.  Elasticsearch supports the following item types:      uint,dbl,str,log,text  Supported item type explanation:  |   |   |   | |---|---|---| |**Item value type**|**Database table**|**Elasticsearch type**| |Numeric (unsigned)|history\_uint|uint| |Numeric (float)|history|dbl| |Character|history\_str|str| |Log|history\_log|log| |Text|history\_text|text|  Zabbix frontend configuration file (`conf/zabbix.conf.php`) draft with parameters to be updated:      // Elasticsearch url (can be string if same url is used for all types).     $HISTORY['url']   = [           'uint' => 'http://localhost:9200',           'text' => 'http://localhost:9200'     ];     // Value types stored in Elasticsearch.     $HISTORY['types'] = ['uint', 'text'];  Example parameter values to fill the Zabbix frontend configuration file with:      $HISTORY['url']   = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  This configuration forces to store `Text`, `Character` and `Log` history values in Elasticsearch.  It is also required to make $HISTORY global in `conf/zabbix.conf.php` to ensure everything is working properly (see `conf/zabbix.conf.php.example` for how to do it):      // Zabbix GUI configuration file.     global $DB, $HISTORY;
zh-cn	##### Zabbix 服务端 和 前端  Zabbix 服务器配置文件模板，其中包含要更新的参数：      ### Option: HistoryStorageURL     # History storage HTTP[S] URL.     #     # Mandatory: no     # Default:     # HistoryStorageURL=      ### Option: HistoryStorageTypes     # Comma separated list of value types to be sent to the history storage.     #     # Mandatory: no     # Default:     # HistoryStorageTypes=uint,dbl,str,log,text      用于 Zabbix 服务端配置文件示例的参数值      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text      此配置强制 Zabbix Server 在相应的数据库中存储数字类型的历史值，并在Elasticsearch中存储文本历史数据。  Elasticsearch 支持以下 item 类型:      uint,dbl,str,log,text  支持的 item 类型说明:  |   |   |   | |---|---|---| |**Item 类型**|**数据库表**|**Elasticsearch 类型**| |Numeric (unsigned)|history\_uint|uint| |Numeric (float)|history|dbl| |Character|history\_str|str| |Log|history\_log|log| |Text|history\_text|text|  Zabbix 前端配置文件 (`conf/zabbix.conf.php`) 参数待更新:      // Elasticsearch url (can be string if same url is used for all types).     $HISTORY['url']   = [           'uint' => 'http://localhost:9200',           'text' => 'http://localhost:9200'     ];     // Value types stored in Elasticsearch.     $HISTORY['types'] = ['uint', 'text'];  用于 Zabbix 前端配置文件示例的参数值 :      $HISTORY['url']   = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  此配置强制在Elasticsearch种存储 `Text`, `Character` 及 `Log` 的历史值. 还需要在`conf/zabbix.conf.php`中使用全局变量 $HISTORY，以确保一切正常  (有关如何执行此操作，请参阅`conf/zabbix.conf.php.example` ):      // Zabbix GUI configuration file.     global $DB, $HISTORY;

en-us	#### Zabbix server/proxy configuration  Secure connections to the database can be configured with the respective parameters in the Zabbix [server](/manual/appendix/config/zabbix_server) and/or [proxy](/manual/appendix/config/zabbix_proxy) configuration file.  |Configuration|Result| |--|--| |None|Connection to the database without encryption.| |1\. Set DBTLSConnect=required|Server/proxy make a TLS connection to the database. An unencrypted connection is not allowed.| |1\. Set DBTLSConnect=verify\_ca<br>2. Set DBTLSCAFile - specify the TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate.| |1\. Set DBTLSConnect=verify\_full<br>2. Set DBTLSCAFile - specify TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate and the database host identity.| |1\. Set DBTLSCAFile - specify TLS certificate authority file<br>2. Set DBTLSCertFile - specify the client public key certificate file<br>3. Set DBTLSKeyFile - specify the client private key file|Server/proxy provide a client certificate while connecting to the database.| |1\. Set DBTLSCipher - the list of encryption ciphers that the client permits for connections using TLS protocols up to TLS 1.2<br><br>or DBTLSCipher13 - the list of encryption ciphers that the client permits for connections using TLS 1.3 protocol|(MySQL) TLS connection is made using a cipher from the provided list.<br>(PostgreSQL) Setting this option will be considered as an error.|
zh-cn	#### Zabbix 服务器/代理配置  可以使用 Zabbix [server](/manual/appendix/config/zabbix_server) 和/或 [proxy](/manual/appendix/config/zabbix_proxy) 配置文件中的相应参数配置与数据库的安全连接。  |配置|结果| |--|--| |无|未加密的数据库连接。| |1\.  设置 DBTLSConnect=required|服务器/代理与数据库建立 TLS 连接。 不允许未加密的连接。| |1\.  设置 DBTLSConnect=verify\_ca<br>2.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件|服务器/代理在验证数据库证书后与数据库建立 TLS 连接。| |1\. 设置 DBTLSConnect=verify\_full<br>2.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件|服务器/代理在验证数据库证书和数据库主机身份后与数据库建立 TLS 连接。| |1\.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件<br>2.  设置 DBTLSCertFile - 指定客户端公钥证书文件<br>3. 设置 DBTLSKeyFile - 指定客户端私钥文件|服务器/代理在连接到数据库时提供客户端证书。| |1\. 设置 DBTLSCipher - 客户端允许使用最高 TLS 1.2 的 TLS 协议进行连接的加密密码列表<br><br>或 DBTLSCipher13 - 客户端允许使用 TLS 1.3 协议进行连接的加密密码列表|(MySQL) TLS 使用提供的列表中的密码建立连接。<br>(PostgreSQL) 设置此选项将被视为错误。|

en-us	##### Zabbix server/proxy  See an example of a script running on Zabbix server and the result window below:      sleep 11     df -h  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/script_timeout_3.png)  It is also advised to optimize the script itself (instead of adjusting TrapperTimeout parameter to a corresponding value (in our case, > ‘11’) by modifying the [Zabbix server configuration](/manual/appendix/config/zabbix_server)).
zh-cn	##### Zabbix server/proxy  查看在 Zabbix server上运行的脚本示例和下面的结果窗口：      sleep 11     df -h   ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/script_timeout_3.png)  还建议优化脚本本身（而不是通过修改[Zabbix server configuration]（/manual/appendix/config/zabbix_server）将 TrapperTimeout 参数调整为相应的值（在我们的例子中，>'11'））。

en-us	#### Zabbix server response  ``` {.javascript} {     "response":"success",     "info":"processed: 1; failed: 0; total: 1; seconds spent: 0.060753" } ```
zh-cn	#### Zabbix server 响应  ``` {.javascript} {     "response":"success",     "info":"processed: 1; failed: 0; total: 1; seconds spent: 0.060753" } ```

en-us	#### Zabbix server response  ``` {.javascript} {     "response":"success",     "info":"processed: 2; failed: 0; total: 2; seconds spent: 0.060904" } ```
zh-cn	#### Zabbix服务器响应  ``` {.javascript} {     "response":"success",     "info":"processed: 2; failed: 0; total: 2; seconds spent: 0.060904" } ```

en-us	##### zabbix\_server  **StartPollers**  General rule - keep value of this parameter as low as possible. Every additional instance of zabbix\_server adds known overhead, at the same time, parallelism is increased. Optimal number of instances is achieved when the item queue, on average, contains minimum number of parameters (ideally, 0 at any given moment). This value can be monitored by using internal check zabbix\[queue\].  ::: noteclassic See the ["See also"](#see_also) section at the bottom of this page to find out how to configure optimal count of zabbix processes. :::  **StartHistoryPollers**  This value should be kept as low as possible to avoid unnecessary connections to database. Each history poller requires a connection to the database.  See also: [Server process types](/manual/concepts/server#server_process_types)  **DebugLevel**  Optimal value is 3.  **DBSocket**  MySQL only. It is recommended to use DBSocket for connection to the database. That is the fastest and the most secure way.
zh-cn	##### zabbix\_server  **启动轮询**  一般规则 - 保持此参数的值尽可能低。每个额外的zabbix\_server实例都会增加已知开销，同时增加并行度。当监控项队列平均包含最少的参数（理想情况下，在任何给定时刻为 0）时，实例数达到最佳。这个值可以通过内部检查zabbix\[queue\]来监控。  ::: noteclassic 请参阅本页底部的 ["另请参阅"](#see_also) 部分，了解如何配置 zabbix 进程的最佳数量。 :::  **开始历史轮询**  该值应保持尽可能低，以避免不必要的数据库连接。每个历史轮询器都需要连接到数据库。  另请参阅：[服务区进程类型](/manual/concepts/server#server_process_types)  **调试级别**  最佳值为 3。  **DBSocket**  仅限 MySQL。推荐使用 DBSocket 连接数据库。这是最快最安全的方式。

en-us	#### Zabbix settings  By default, Zabbix is configured with *X-Frame-Options HTTP response header* set to `SAMEORIGIN`, meaning that content can only be loaded in a frame that has the same origin as the page itself.  Zabbix frontend elements that pull content from external URLs (namely, the URL [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)) display retrieved content in a sandbox with all sandboxing restrictions enabled.  These settings enhance the security of the Zabbix frontend and provide protection against XSS and clickjacking attacks. Super Admins can [modify](/manual/web_interface/frontend_sections/administration/general#security) *iframe sandboxing* and *X-Frame-Options HTTP response header* parameters as needed. Please carefully weigh the risks and benefits before changing default settings. Turning sandboxing or X-Frame-Options off completely is not recommended.
zh-cn	#### Zabbix 设置  在默认情况下，Zabbix 配置了 *X-Frame-Options HTTP 响应头 * 设置为 `SAMEORIGIN`，这意味着内容只能加载到与页面本身具有相同来源的框架中。  从外部 URL 中提取内容的 Zabbix 前端元素（即 URL [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)）在启用了所有沙盒限制的沙盒中显示检索到的内容。  这些设置增强了 Zabbix 前端的安全性，并提供针对 XSS 和点击劫持攻击的保护。 超级管理员可以根据需要[修改](/manual/web_interface/frontend_sections/administration/general#security) *iframe sandboxing* 和 *X-Frame-Options HTTP response header* 参数。 在更改默认设置之前，请仔细权衡风险和效果。 不建议完全关闭沙盒及 X-Frame-Options。

en-us	#### Zabbix settings  By default, Zabbix is configured with *X-Frame-Options HTTP response header* set to `SAMEORIGIN`, meaning that content can only be loaded in a frame that has the same origin as the page itself.  Zabbix frontend elements that pull content from external URLs (namely, the URL [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)) display retrieved content in a sandbox with all sandboxing restrictions enabled.  These settings enhance the security of the Zabbix frontend and provide protection against XSS and clickjacking attacks. Super Admins can [modify](/manual/web_interface/frontend_sections/administration/general#security) *iframe sandboxing* and *X-Frame-Options HTTP response header* parameters as needed. Please carefully weigh the risks and benefits before changing default settings. Turning sandboxing or X-Frame-Options off completely is not recommended.  
zh-cn	#### Zabbix 设置  在默认情况下，Zabbix 配置了 *X-Frame-Options HTTP 响应头 * 设置为 `SAMEORIGIN`，这意味着内容只能加载到与页面本身具有相同来源的框架中。  从外部 URL 中提取内容的 Zabbix 前端元素（即 URL [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#url)）在启用了所有沙盒限制的沙盒中显示检索到的内容。  这些设置增强了 Zabbix 前端的安全性，并提供针对 XSS 和点击劫持攻击的保护。 超级管理员可以根据需要[修改](/manual/web_interface/frontend_sections/administration/general#security) *iframe sandboxing* 和 *X-Frame-Options HTTP response header* 参数。 在更改默认设置之前，请仔细权衡风险和效果。 不建议完全关闭沙盒及 X-Frame-Options。

en-us	#### Zabbix  The Zabbix object provides interaction with the internal Zabbix functionality.  |Method|Description| |------|-----------| |`log(loglevel, message)`|Writes <message> into Zabbix log using <loglevel> log level (see configuration file DebugLevel parameter).|  Example:      Zabbix.log(3, "this is a log entry written with 'Warning' log level")  You may use the following aliases:  |Alias|Alias to| |-----|--------| |console.log(object)|Zabbix.log(4, JSON.stringify(object))| |console.warn(object)|Zabbix.log(3, JSON.stringify(object))| |console.error(object)|Zabbix.log(2, JSON.stringify(object))|  
zh-cn	#### Zabbix  The Zabbix object provides interaction with the internal Zabbix functionality.  |Method|Description| |------|-----------| |`log(loglevel, message)`|Writes <message> into Zabbix log using <loglevel> log level (see configuration file DebugLevel parameter).|  Example:      Zabbix.log(3, "this is a log entry written with 'Warning' log level")  You may use the following aliases:  |Alias|Alias to| |-----|--------| |console.log(object)|Zabbix.log(4, JSON.stringify(object))| |console.warn(object)|Zabbix.log(3, JSON.stringify(object))| |console.error(object)|Zabbix.log(2, JSON.stringify(object))|  

en-us	#### Zabbix  The Zabbix object provides interaction with the internal Zabbix functionality.  |Method|Description| |------|-----------| |`log(loglevel, message)`|Writes <message> into Zabbix log using <loglevel> log level (see configuration file DebugLevel parameter).|  Example:      Zabbix.log(3, "this is a log entry written with 'Warning' log level")  You may use the following aliases:  |Alias|Alias to| |-----|--------| |console.log(object)|Zabbix.log(4, JSON.stringify(object))| |console.warn(object)|Zabbix.log(3, JSON.stringify(object))| |console.error(object)|Zabbix.log(2, JSON.stringify(object))|  |Method|Description| |------|-----------| |`sleep(delay)`|Delay JavaScript execution by `delay` milliseconds. |  Example (delay execution by 15 seconds):      Zabbix.sleep(15000)     
zh-cn	#### Zabbix  Zabbix 对象提供与 Zabbix内部功能的交互。  |方法|描述| |------|-----------| |`log(loglevel, message)`|使用 <loglevel> 日志级别将 <message> 写入 Zabbix 日志（参见配置文件 DebugLevel 参数）。|  示例:      Zabbix.log(3, "this is a log entry written with 'Warning' log level")  你可以使用以下别名：  |别名|原义| |-----|--------| |console.log(object)|Zabbix.log(4, JSON.stringify(object))| |console.warn(object)|Zabbix.log(3, JSON.stringify(object))| |console.error(object)|Zabbix.log(2, JSON.stringify(object))|  |方法|描述| |------|-----------| |`sleep(delay)`|将 JavaScript 执行延迟 `delay` 毫秒。|  示例（延迟执行 15 秒）：      Zabbix.sleep(15000)

en-us	#### Zabbix Windows agent with OpenSSL  Zabbix Windows agent compiled with OpenSSL will try to reach the SSL configuration file in c:\\openssl-64bit. The "openssl-64bit" directory on disk C: can be created by non-privileged users.  So for security hardening, it is required to create this directory manually and revoke write access from non-admin users.  Please note that the directory names will be different on 32-bit and 64-bit versions of Windows.
zh-cn	#### 带有 OpenSSL 的在Windows上的zabbix agent  使用 OpenSSL 编译的 Zabbix Windows agent将尝试访问 c:\\openssl-64bit 中访问SSL配置文件。磁盘C上的“ openssl-64bit”目录可以由非特权用户创建。  因此，为了加强安全性，需手动创建此目录并撤销非管理员用户的写访问权限。  请注意，在Windows的32位和64位版本上，目录名称将有所不同。

en-us	###     
zh-cn	 ###     

en-us	# 10 Cookies used by Zabbix
zh-cn	# 10 Zabbix使用的cookie

en-us	# 10 Inclusion
zh-cn	# 10 包含

en-us	# 10 Notifications upon events
zh-cn	# 10 事件通知 

en-us	# 10. Virtual machine monitoring
zh-cn	# 10. 虚拟机监控

en-us	# 11 Macros
zh-cn	#  11 宏变量

en-us	# 11. Maintenance
zh-cn	# 11. 维护期

en-us	# 11 Time zones
zh-cn	# 11 时区

en-us	# 11 Version compatibility
zh-cn	# 11 版本兼容性

en-us	# 12 Database error handling  If Zabbix detects that the backend database is not accessible, it will send a notification message and continue the attempts to connect to the database. For some database engines, specific error codes are recognized.
zh-cn	# 12 数据库错误处理  如果 Zabbix 检测到后端数据库不可访问，它将发送一条通知消息并继续尝试连接到数据库。 对于某些数据库引擎，可以识别特定的错误代码。

en-us	# 12. Regular expressions
zh-cn	# 12. 正则表达式

en-us	# 12 Trapper items
zh-cn	# 12 采集器监控项

en-us	# 12 Users and user groups
zh-cn	#  12 用户和用户组

en-us	# 13 JMX monitoring
zh-cn	# 13 JMX监控

en-us	# 13 Storage of secrets
zh-cn	# 13 存储密钥 

en-us	# 14. Configuration export/import
zh-cn	# 14. 配置 导出/导入

en-us	# 14 ODBC monitoring
zh-cn	# 14 ODBC监控

en-us	# 14 Scheduled reports
zh-cn	# 14 定时报表

en-us	# 15 Dependent items
zh-cn	# 15 从属监控项

en-us	# 15. Discovery  Please use the sidebar to access content in the Discovery section.
zh-cn	# 15. 发现 请使用侧边栏访问本章内容。

en-us	# 16 Creating custom performance counter names for VMware
zh-cn	# 16 为 VMware 创建自定义性能计数器名称

en-us	# 16. Distributed monitoring
zh-cn	# 16. 分布式监控

en-us	# 16 HTTP agent
zh-cn	# 16 HTTP 代理

en-us	# 17. Encryption
zh-cn	# 17. 加密

en-us	# 17 Prometheus checks
zh-cn	# 17 Prometheus 数据处理

en-us	# 18. Web interface
zh-cn	# 18. Web 界面

en-us	# 19. API
zh-cn	# 19. API

en-us	# 1 Ceph plugin
zh-cn	# 1 Ceph 插件

en-us	# 1 Configuring a network discovery rule
zh-cn	# 1 配置网络发现规则

en-us	# 1 Configuring a network map
zh-cn	# 1 配置网络地图

en-us	# 1 Configuring a template
zh-cn	# 1 配置模板

en-us	# 1 Configuring a trigger
zh-cn	# 1 配置一个触发器

en-us	# 1 Configuring a user
zh-cn	# 1 配置用户

en-us	# 1 Connection type or permission problems
zh-cn	# 1 连接类型或权限问题

en-us	# 1 Creating an item
zh-cn	# 1 创建监控项

en-us	# 1 Database creation
zh-cn	# 1 创建数据库

en-us	# 1 Discovery of mounted filesystems
zh-cn	# 1 自动发现已挂载的文件系统

en-us	# 1 Extending Zabbix agents  This tutorial provides step-by-step instructions on how to extend the functionality of Zabbix agent with the use of a [user parameter](/manual/config/items/userparameters).
zh-cn	# 1 扩展Zabbix Agents  本教程提供了如何使用用户自定义参数扩展Zabbix agent[用户自定义参数](/manual/config/items/userparameters)功能的详细步骤。\

en-us	# 1 Foreach functions
zh-cn	# 1 Foreach 函数

en-us	# 1 General
zh-cn	# 1 常规

en-us	# 1 Getting Zabbix
zh-cn	# 1 获取 Zabbix

en-us	# 1 Global notifications
zh-cn	# 1 全局通知

en-us	# 1 Graphs
zh-cn	# 1 图表

en-us	# 1 Graphs
zh-cn	# 1 图表

en-us	# 1 High availability
zh-cn	# 1 高可用

en-us	# 1 Hosts and host groups
zh-cn	# 1 主机和主机组

en-us	# 1. Introduction  Please use the sidebar to access content in the Introduction section.
zh-cn	# 1. 简介  请使用侧边栏访问简介部分中的内容。

en-us	# 1 Login and configuring user
zh-cn	# 1 登录和配置用户

en-us	# 1 Macro functions
zh-cn	# 1 宏函数

en-us	# 1 Manual structure
zh-cn	# 1 手册结构

en-us	# 1 Media types
zh-cn	# 1 媒介类型

en-us	# 1 Menu
zh-cn	# 1 菜单

en-us	# 1 Network discovery
zh-cn	# 1 网络发现

en-us	# 1 Overview
zh-cn	# 1 概览

en-us	# 1 Proxies
zh-cn	# 1 proxy代理

en-us	# 1 Red Hat Enterprise Linux
zh-cn	# 1 Red Hat 企业版 Linux

en-us	# 1 Red Hat Enterprise Linux
zh-cn	# 1 Red Hat 企业版 Linux

en-us	# 1 Server
zh-cn	# 1 Server

en-us	# 1 Server-proxy data exchange protocol
zh-cn	# 1 Server-proxy 数据交换协议

en-us	# 1 Service tree  Service tree is configured in the *Services->Services* menu section.  In the upper right corner, switch from [View](/manual/web_interface/frontend_sections/services/service) to the Edit mode.   ![](../../../assets/en/manual/config/service_config.png){width=600}   To [configure](#service_configuration) a new service, click on the *Create service* button in the top right-hand corner.  To quickly add a child service, you can alternatively press a plus icon next to the parent service. This will open the same service configuration form, but the Parent services parameter will be pre-filled. 
zh-cn	# 1 服务树  服务树在 *Services->Services* 菜单部分配置。在右上角，从 [View](/manual/web_interface/frontend_sections/services/service) 切换到 Edit 模式。  ![](../../../assets/en/manual/config/service_config.png){width=600}   要 [配置](#服务配置) 新服务，请单击右上角的 *Create service* 按钮。  要快速添加子服务，您也可以按父服务旁边的加号图标。这将打开相同的服务配置表单，但将预先填写父服务参数。

en-us	# 1 Simple graphs
zh-cn	# 1 简单的图表

en-us	##### 1 Stop Zabbix processes  Stop Zabbix server to make sure that no new data is inserted into database.      # service zabbix-server stop  If upgrading Zabbix proxy, stop proxy too.      # service zabbix-proxy stop
zh-cn	##### 1 停止 Zabbix 进程  用户需要停止 Zabbix server服务，以确保没有新数据写入数据库。      # service zabbix-server stop  若需要升级 Zabbix proxy，同样需要先停止 Zabbix proxy 进程。      # service zabbix-proxy stop

en-us	# 1 System information
zh-cn	# 1 系统信息

en-us	# 1 Trigger event generation
zh-cn	# 1 触发器事件生成

en-us	# 1 Using certificates
zh-cn	# 1 使用证书

en-us	# 1 Web monitoring items
zh-cn	# 1 Web 监控项

en-us	# 1 Zabbix agent
zh-cn	# 1 Zabbix agent

en-us	# 1 Zabbix server
zh-cn	# 1 Zabbix 服务器

en-us	# 21. Appendixes  Please use the sidebar to access content in the Appendixes section.
zh-cn	# 21. 附录  请使用侧边栏访问附录中的内容。

en-us	# 2 Active agent autoregistration
zh-cn	# 2 agent（主动模式） 自动注册

en-us	# 2 Agent
zh-cn	# 2 Agent

en-us	##### 2 Back up configuration files and Zabbix agent binaries  Make a backup copy of the Zabbix agent binary and configuration file.
zh-cn	##### 2 备份配置文件和 Zabbix agent 程序文件  备份配置文件和 Zabbix agent 程序文件。

en-us	##### 2 Back up configuration files and Zabbix proxy binaries  Make a backup copy of the Zabbix proxy binary and configuration file.
zh-cn	##### 2 备份配置文件和 Zabbix Proxy 旧版本程序  备份配置文件和 Zabbix Proxy 旧版本程序。

en-us	##### 2 Back up the existing Zabbix database  This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem).
zh-cn	##### 2 备份当前的数据库  请用户确认，在升级前备份了数据库，这是非常关键的一步。如果升级失败（因磁盘空间不足、断电或其他意外导致的升级失败），备份的数据库将大有帮助。

en-us	##### 2 Back up the existing Zabbix database  This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem).
zh-cn	##### 2 备份已有的Zabbix数据库  这是非常重要的一步。 确保您有数据库的备份。 如果升级过程失败（磁盘空间不足、电源关闭、任何意外问题），这将有所帮助。

en-us	# 2 Certificate problems
zh-cn	# 2 证书问题

en-us	##### 2 Create user account  For all of the Zabbix daemon processes, an unprivileged user is required. If a Zabbix daemon is started from an unprivileged user account, it will run as that user.  However, if a daemon is started from a 'root' account, it will switch to a 'zabbix' user account, which must be present. To create such a user account (in its own group, "zabbix"),  on a RedHat-based system, run:      groupadd --system zabbix     useradd --system -g zabbix -d /usr/lib/zabbix -s /sbin/nologin -c "Zabbix Monitoring System" zabbix  on a Debian-based system, run:      addgroup --system --quiet zabbix     adduser --quiet --system --disabled-login --ingroup zabbix --home /var/lib/zabbix --no-create-home zabbix  ::: noteimportant Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e. g. store MySQL credentials in `$HOME/.my.cnf`) you are free to create it using the following commands.\ \  On RedHat-based systems, run:      mkdir -m u=rwx,g=rwx,o= -p /usr/lib/zabbix     chown zabbix:zabbix /usr/lib/zabbix  On Debian-based systems, run:      mkdir -m u=rwx,g=rwx,o= -p /var/lib/zabbix     chown zabbix:zabbix /var/lib/zabbix   :::  A separate user account is not required for Zabbix frontend installation.  If Zabbix [server](/manual/concepts/server) and [agent](/manual/concepts/agent) are run on the same machine it is recommended to use a different user for running the server than for running the agent. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password.  ::: noteimportant Running Zabbix as `root`, `bin`, or any other account with special rights is a security risk. :::
zh-cn	 ##### 2 创建用户账户  所有的Zabbix守护进程都必须要一个非特权用户。如果一个非特权用户启动了一个Zabbix守护进程，它就会以这个用户运行。  然而，如果一个守护进程以‘root’账户运行，它会切换到一个‘zabbix‘用户，这个用户是必须存在的。要创建这样一个用户（在它自己的“zabbix”组里），  在基于RedHat的系统里，运行：      groupadd --system zabbix     useradd --system -g zabbix -d /usr/lib/zabbix -s /sbin/nologin -c "Zabbix Monitoring System" zabbix  在基于Debian的系统里，运行：      addgroup --system --quiet zabbix     adduser --quiet --system --disabled-login --ingroup zabbix --home /var/lib/zabbix --no-create-home zabbix  ::: noteimportant Zabbix进程不许要home目录，因此我们不推荐创建它。然而，如果你将要使用的某些功能需要它（比如在`$HOME/.my.cnf`里存放MySQL凭证) ，你可以使用如下命令去创建home目录。\ \  在基于RedHat的系统里，运行：      mkdir -m u=rwx,g=rwx,o= -p /usr/lib/zabbix     chown zabbix:zabbix /usr/lib/zabbix  在基于Debian的系统里，运行：      mkdir -m u=rwx,g=rwx,o= -p /var/lib/zabbix     chown zabbix:zabbix /var/lib/zabbix  :::  安装Zabbix前端不许要单独的用户。  如果Zabbix [server](/manual/concepts/server)和[agent](/manual/concepts/agent)运行在同一台机器上，建议使用与agent不同的用户来运行。否则，如果两者使用相同的用户，agent可以访问server的配置文件，Zabbix里任何Admin级别的用户可以轻易地获取诸如数据可密码等信息。  ::: noteimportant 以`root`、`bin`或者其他任何有特殊权限的账户运行Zabbix都有安全风险。 :::

en-us	# 2 Custom graphs
zh-cn	# 2 自定义图表

en-us	# 2 Custom intervals
zh-cn	# 2 自定义间隔

en-us	# 2 Debian/Ubuntu
zh-cn	# 2 Debian/Ubuntu

en-us	# 2 Debian/Ubuntu/Raspbian
zh-cn	 # 2 Debian/Ubuntu/Raspbian

en-us	# 2. Definitions
zh-cn	# 2. 定义

en-us	# 2 Discovery of network interfaces  In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover network interfaces.
zh-cn	# 2 网络接口的自动发现  对网络接口进行自动发现与对 [文件系统](/manual/discovery/low_level_discovery#configuring_low-level_discovery) 进行自动发现的工作方式类似。

en-us	# 2 Docker plugin
zh-cn	# 2 Docker 插件

en-us	# 2 Frontend sections
zh-cn	# 2 前端部件

en-us	# 2 Global event correlation
zh-cn	# 2 全局事件关联

en-us	# 2 Host group elements
zh-cn	# 2 主机组元素

en-us	# 2 Hosts
zh-cn	# 2 主机

en-us	# 2 Inventory
zh-cn	# 2 资产管理

en-us	# 2 Items
zh-cn	# 2 监控项

en-us	# 2 Linking/unlinking
zh-cn	# 2 链接/取消链接

en-us	# 2 New host
zh-cn	# 2 新建主机

en-us	# 2 Permissions
zh-cn	# 2 权限

en-us	# 2 Remote commands
zh-cn	# 2 远程命令

en-us	# 2 Repairing Zabbix database character set and collation
zh-cn	# 2 修复Zabbix 数据库的字符集及字符序

en-us	# 2 Requirements
zh-cn	# 2 安装要求

en-us	# 2 Scheduled reports
zh-cn	# 2 计划报表

en-us	# 2 SMS
zh-cn	# 2 短信

en-us	# 2 Sound in browsers
zh-cn	# 2 浏览器提示音

en-us	# 2 Special OIDs  Some of the most used SNMP OIDs are translated automatically to a numeric representation by Zabbix. For example, **ifIndex** is translated to **1.3.6.1.2.1.2.2.1.1**, **ifIndex.0** is translated to **1.3.6.1.2.1.2.2.1.1.0**.  The table contains list of the special OIDs.  |Special OID|Identifier|Description| |--|--|------| |ifIndex|1.3.6.1.2.1.2.2.1.1|A unique value for each interface.| |ifDescr|1.3.6.1.2.1.2.2.1.2|A textual string containing information about the interface.This string should include the name of the manufacturer, the product name and the version of the hardware interface.| |ifType|1.3.6.1.2.1.2.2.1.3|The type of interface, distinguished according to the physical/link protocol(s) immediately 'below' the network layer in the protocol stack.| |ifMtu|1.3.6.1.2.1.2.2.1.4|The size of the largest datagram which can be sent / received on the interface, specified in octets.| |ifSpeed|1.3.6.1.2.1.2.2.1.5|An estimate of the interface's current bandwidth in bits per second.| |ifPhysAddress|1.3.6.1.2.1.2.2.1.6|The interface's address at the protocol layer immediately \`below' the network layer in the protocol stack.| |ifAdminStatus|1.3.6.1.2.1.2.2.1.7|The current administrative state of the interface.| |ifOperStatus|1.3.6.1.2.1.2.2.1.8|The current operational state of the interface.| |ifInOctets|1.3.6.1.2.1.2.2.1.10|The total number of octets received on the interface, including framing characters.| |ifInUcastPkts|1.3.6.1.2.1.2.2.1.11|The number of subnetwork-unicast packets delivered to a higher-layer protocol.| |ifInNUcastPkts|1.3.6.1.2.1.2.2.1.12|The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.| |ifInDiscards|1.3.6.1.2.1.2.2.1.13|The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.| |ifInErrors|1.3.6.1.2.1.2.2.1.14|The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.| |ifInUnknownProtos|1.3.6.1.2.1.2.2.1.15|The number of packets received via the interface which were discarded because of an unknown or unsupported protocol.| |ifOutOctets|1.3.6.1.2.1.2.2.1.16|The total number of octets transmitted out of the interface, including framing characters.| |ifOutUcastPkts|1.3.6.1.2.1.2.2.1.17|The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.| |ifOutNUcastPkts|1.3.6.1.2.1.2.2.1.18|The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.| |ifOutDiscards|1.3.6.1.2.1.2.2.1.19|The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.| |ifOutErrors|1.3.6.1.2.1.2.2.1.20|The number of outbound packets that could not be transmitted because of errors.| |ifOutQLen|1.3.6.1.2.1.2.2.1.21|The length of the output packet queue (in packets).|
zh-cn	# 2 特殊 OIDs  一些最常用的 SNMP OIDs 会自动转换为Zabbix 的数字表示。例如，**ifIndex** 被解析成 **1.3.6.1.2.1.2.2.1.1**，**ifIndex.0** 被解析成**1.3.6.1.2.1.2.2.1.1.0**。  该表包含特殊 OIDs 的列表。  |特殊OID|标识符|描述| |-----------|---------|------------| |ifIndex|1.3.6.1.2.1.2.2.1.1|每个接口的唯一值。| |ifDescr|1.3.6.1.2.1.2.2.1.2|包含接口信息的文本字符串。该字符串应包括制造商名称、产品名称和硬件接口版本。| |ifType|1.3.6.1.2.1.2.2.1.3|接口类型，根据协议栈中网络层“下方”的物理/链路协议进行区分。| |ifMtu|1.3.6.1.2.1.2.2.1.4|可以在接口上发送/接收的最大数据报的大小，以八位字节指定。| |ifSpeed|1.3.6.1.2.1.2.2.1.5|接口当前带宽的估计值，以比特/秒为单位。| |ifPhysAddress|1.3.6.1.2.1.2.2.1.6|协议层的接口地址紧挨着协议栈中网络层的“下方”。| |ifAdminStatus|1.3.6.1.2.1.2.2.1.7|接口的当前管理状态。| |ifOperStatus|1.3.6.1.2.1.2.2.1.8|接口的当前操作状态。| |ifInOctets|1.3.6.1.2.1.2.2.1.10|接口接收到的八位字节总数，包括帧字符。| |ifInUcastPkts|1.3.6.1.2.1.2.2.1.11|传送到更高层协议的子网单播数据包的数量。| |ifInNUcastPkts|1.3.6.1.2.1.2.2.1.12|传送到更高层协议的非单播（即子网广播或子网多播）数据包的数量。| |ifInDiscards|1.3.6.1.2.1.2.2.1.13|被选择丢弃的入站数据包的数量，即使没有检测到错误以阻止它们被传递到更高层的协议。丢弃此类数据包的一个可能原因是释放缓冲区空间。 |ifInErrors|1.3.6.1.2.1.2.2.1.14|包含错误的入站数据包的数量，这些错误阻止它们被传递到更高层的协议。| |ifInUnknownProtos|1.3.6.1.2.1.2.2.1.15|通过接口接收到的由于未知或不受支持的协议而被丢弃的数据包的数量。| |ifOutOctets|1.3.6.1.2.1.2.2.1.16|从接口传出的八位字节总数，包括帧字符。| |ifOutUcastPkts|1.3.6.1.2.1.2.2.1.17|高层协议请求传输的数据包的总数，这些数据包没有发送到该子层的多播或广播地址，包括那些被丢弃或未发送。| |ifOutNUcastPkts|1.3.6.1.2.1.2.2.1.18|高层协议请求传输的包的总数，在这个子层被寻址到多播或广播地址，包括那些被丢弃或未被丢弃的包已发送。| |ifOutDiscards|1.3.6.1.2.1.2.2.1.19|被选择丢弃的出站数据包的数量，即使没有检测到错误以阻止它们被传输。丢弃此类数据包的一个可能原因是释放缓冲区空间。 |ifOutErrors|1.3.6.1.2.1.2.2.1.20|由于错误而无法传输的出站数据包数。| |ifOutQLen|1.3.6.1.2.1.2.2.1.21|输出包队列的长度（以包为单位）。|

en-us	# 2 Trigger expression
zh-cn	# 2 触发器表达式

en-us	# 2 Triggers
zh-cn	# 2 触发器

en-us	# 2 Triggers
zh-cn	# 2 触发器

en-us	# 2 User macros
zh-cn	# 2 用户宏

en-us	# 2 Using pre-shared keys
zh-cn	# 2 使用预共享秘钥

en-us	# 2 Web scenarios
zh-cn	# 2 Web场景

en-us	# 2 What is Zabbix
zh-cn	# 2 什么是 Zabbix

en-us	# 2 Zabbix agent protocol  Please refer to [Passive and active agent checks](/manual/appendix/items/activepassive) page for more information.
zh-cn	# 2 Zabbix agent 协议  有关详细信息，请参阅 [Passive and active agent checks](/manual/appendix/items/activepassive).

en-us	# 2 Zabbix proxy
zh-cn	# 2 Zabbix proxy

en-us	# 3 Additional operations
zh-cn	# 3 附加操作

en-us	# 3 Ad-hoc graphs
zh-cn	# 3 Ad-hoc图表

en-us	# 3 Agent 2
zh-cn	# 3 Agent 2

en-us	# 3 Availability report
zh-cn	 # 3 可用性报表

en-us	##### 3 Back up configuration files, PHP files and Zabbix binaries  Make a backup copy of Zabbix binaries, configuration files and the PHP file directory.
zh-cn	##### 3 备份配置文件、PHP 文件和 Zabbix 程序文件  备份 Zabbix 程序文件、配置文件和 PHP 文件目录。

en-us	##### 3 Back up configuration files, PHP files and Zabbix binaries  Make a backup copy of Zabbix binaries, configuration files and the PHP file directory.  Configuration files:      # mkdir /opt/zabbix-backup/     # cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/     # cp /etc/httpd/conf.d/zabbix.conf  /opt/zabbix-backup/  PHP files and Zabbix binaries:      # cp -R /usr/share/zabbix/ /opt/zabbix-backup/     # cp -R /usr/share/zabbix-* /opt/zabbix-backup/
zh-cn	##### 3 备份配置文件、PHP文件和Zabbix二进制文件  制作 Zabbix 二进制文件、配置文件和 PHP 文件目录的备份副本。  配置文件：    · # mkdir /opt/zabbix-backup/   · # cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/   · # cp /etc/httpd/conf.d/zabbix.conf · /opt/zabbix-backup/  PHP 文件和 Zabbix 二进制文件：    · # cp -R /usr/share/zabbix/ /opt/zabbix-backup/   · # cp -R /usr/share/zabbix-* /opt/zabbix-backup/

en-us	##### 3 Create Zabbix database  For Zabbix [server](/manual/concepts/server) and [proxy](/manual/concepts/proxy) daemons, as well as Zabbix frontend, a database is required. It is not needed to run Zabbix [agent](/manual/concepts/agent).  SQL [scripts are provided](/manual/appendix/install/db_scripts) for creating database schema and inserting the dataset. Zabbix proxy database needs only the schema while Zabbix server database requires also the dataset on top of the schema.  Having created a Zabbix database, proceed to the following steps of compiling Zabbix.
zh-cn	 ##### 3 创建Zabbix数据库  对Zabbix[server](/manual/concepts/server)和[proxy](/manual/concepts/proxy)守护进程，还有Zabbix前端，必须要有一个数据库。但运行Zabbix[agent](/manual/concepts/agent)不需要。  此处SQL[脚本](/manual/appendix/install/db_scripts)用于创建数据库模式和插入数据集。Zabbix proxy数据库只需要数据库模式，而Zabbix server数据库在数据库模式之上还需要数据集。  创建了Zabbix数据库之后，执行以下步骤来编译Zabbix。

en-us	# 3 Database upgrade to primary keys
zh-cn	# 3 为数据库升级主键

en-us	# 3 Discovery of CPUs and CPU cores  In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover CPUs and CPU cores.
zh-cn	# 3 CPU和CPU核心的自动发现  CPU和CPU核心的自动发现与 [文件系统](/manual/discovery/low_level_discovery#configuring_low-level_discovery) 的自动发现工作方式相似。

en-us	# 3 Graphs
zh-cn	# 3 图形

en-us	# 3 Graphs
zh-cn	# 3 图形

en-us	# 3 Installation from sources  You can get the very latest version of Zabbix by compiling it from the sources.  A step-by-step tutorial for installing Zabbix from the sources is provided here.
zh-cn	 # 3 从源代码安装  你可以通过从源代码编译获得最新的Zabbix版本。  这里教程提供了从源代码安装Zabbix的详细步骤。

en-us	##### 3 Install new agent binaries  Use these [instructions](/manual/installation/install#installing_zabbix_daemons) to compile Zabbix agent from sources.  Alternatively, you may download pre-compiled Zabbix agents from the [Zabbix download page](http://www.zabbix.com/download.php).
zh-cn	##### 3 安装新的 agent 程序文件  参考源码编译安装 Zabbix agent 的 [说明](/manual/installation/install#installing_zabbix_daemons)。

en-us	# 3 Item types
zh-cn	# 3 监控项类型

en-us	# 3 JSONPath functionality
zh-cn	# 3 JSONPath 功能

en-us	# 3 Link indicators
zh-cn	# 3 链接指标

en-us	# 3 Low-level discovery
zh-cn	# 3 底层自动发现

en-us	# 3 Mass update
zh-cn	# 3 批量更新

en-us	# 3 Memcached plugin
zh-cn	# 3 Memcached 插件

en-us	# 3 New item
zh-cn	# 3 新增监控项

en-us	# 3 Receiving notification on unsupported items
zh-cn	# 3 接收不受支持的项目的通知

en-us	# 3 Recommended UnixODBC settings for Oracle
zh-cn	# 3 Oracle推荐的UnixODBC设置

en-us	# 3 Recovery operations
zh-cn	# 3 恢复操作

en-us	# 3 SUSE Linux Enterprise Server
zh-cn	 # 3 SUSE Linux 企业服务器

en-us	# 3 Triggers
zh-cn	# 3 触发器

en-us	# 3 Troubleshooting
zh-cn	# 3 故障排除

en-us	# 3 User groups
zh-cn	# 3 用户组

en-us	# 3 User macros with context
zh-cn	# 3 带有上下文的用户宏

en-us	# 3 User settings
zh-cn	# 3 用户设置

en-us	# 3 Zabbix agent 2 protocol
zh-cn	# 3 Zabbix agent 2 protocol

en-us	# 3 Zabbix agent (UNIX)
zh-cn	# 3 Zabbix agent (UNIX)

en-us	# 3 Zabbix features
zh-cn	# 3 Zabbix 功能

en-us	# 3. Zabbix processes  Please use the sidebar to access content in the Zabbix process section.
zh-cn	# 3. Zabbix 进程  请使用侧边导航栏来访问此章节中的内容。

en-us	# 4 Aggregation in graphs
zh-cn	# 4 聚合图形

en-us	# 4 Discovery rules
zh-cn	# 4 自动发现规则

en-us	# 4 Discovery rules
zh-cn	# 4 自动发现规则

en-us	# - \#4 Events
zh-cn	 # - \#4 事件

en-us	# 4 History and trends
zh-cn	# 4 历史数据与趋势数据

en-us	# 4 Host dashboards
zh-cn	# 4 主机仪表盘

en-us	# 4 Host prototypes
zh-cn	# 4 主机原型

en-us	# 4 Host prototypes
zh-cn	# 4 主机原型

en-us	# 4 Installation from packages
zh-cn	#  4 从二进制包安装

en-us	# 4. Installation  Please use the sidebar to access content in the Installation section.
zh-cn	# 4. 安装  请使用侧边栏访问安装部分的内容。

en-us	##### 4 Install new server binaries  Use these [instructions](/manual/installation/install#installing_zabbix_daemons) to compile Zabbix server from sources.
zh-cn	##### 4 安装新的server程序文件  查看从源代码编译 Zabbix Server 的 [说明](/manual/installation/install#installing_zabbix_daemons)  。

en-us	# 4 IPMI checks
zh-cn	# 4 IPMI 检查

en-us	# 4 Mass update
zh-cn	# 4 批量更新

en-us	# 4 Modbus plugin
zh-cn	# 4 Modbus 插件

en-us	# 4 Recommended UnixODBC settings for MSSQL
zh-cn	# 4 MSSQL数据库推荐的UnixODBC设置

en-us	# 4 Secure connection to the database
zh-cn	# 4 安全的连接数据库

en-us	# 4 Triggers top 100
zh-cn	 # 4 触发器前100

en-us	# 4 Update operations
zh-cn	# 4 更新操作

en-us	# 4 Webhook
zh-cn	# 4 Webhook

en-us	# 4 Zabbix agent 2 plugin protocol  Zabbix agent 2 protocol is based on code, size and data model.
zh-cn	# 4 Zabbix agent 2 plugin protocol  Zabbix agent 2 protocol is based on code, size and data model.

en-us	# 4 Zabbix agent 2 (UNIX)
zh-cn	# 4 Zabbix agent 2 (UNIX)

en-us	# 4 Zabbix overview
zh-cn	# 4 Zabbix 概述

en-us	# 5 Customizing trigger severities  Trigger severity names and colors for severity related GUI elements can be configured in *Administration → General → Trigger displaying options*. Colors are shared among all GUI themes.
zh-cn	# 5 自定义触发器严重性  可以在 *管理→常规 → 触发器严重性* 中配置触发器严重性名称和严重性颜色相关的GUI主题。颜色在所有GUI主题之间共享。

en-us	# 5 Escalations
zh-cn	#  5 通知升级

en-us	# 5 Event correlation
zh-cn	# 5 事件关联

en-us	# 5 Frontend maintenance mode
zh-cn	# 5 前端维护模式

en-us	# 5 Java gateway
zh-cn	# 5 Java gateway

en-us	# 5 MongoDB plugin
zh-cn	# 5 MongoDB 插件

en-us	# 5. Quickstart  Please use the sidebar to access content in the Quickstart section.
zh-cn	# 5. 快速入门  请使用侧边栏访问快速入门部分的内容。

en-us	# 5 Receiving problem notification
zh-cn	# 5 接收问题通知

en-us	# 5 Simple checks
zh-cn	 # 5 简单检查

en-us	# 5 TimescaleDB setup
zh-cn	# 5 TimescaleDB 配置

en-us	# 5 User parameters
zh-cn	# 5 用户自定义参数

en-us	# 5 Web scenarios
zh-cn	# 5 Web 场景

en-us	# 5 Web scenarios
zh-cn	# 5 Web 场景

en-us	# 5 Zabbix agent (Windows)
zh-cn	# 5 Zabbix agent (Windows)

en-us	# 5 Zabbix sender protocol  Please refer to the [trapper item](/manual/appendix/items/trapper) page for more information.
zh-cn	# 5 Zabbix sender 协议  有关详细信息，请参阅[trapper item](/manual/appendix/items/trapper) 。

en-us	##### 64 bit  Open MinGW environment (Windows command prompt) and navigate to *build/mingw* directory in the Zabbix source tree.  Run:      mingw32-make clean     mingw32-make PCRE=c:\dev\pcre OPENSSL=c:\dev\openssl  ::: noteclassic  Both 32- and 64- bit versions can be built on a 64-bit platform, but only a 32-bit version can be built on a 32-bit platform. When working on the 32-bit platform, follow the same steps as for 64-bit version on 64-bit platform.  :::
zh-cn	##### 64位  打开MinGW环境（Windows命令提示符）并导航至Zabbix源树目录中的*build/mingw*。  运行：      mingw32-make clean     mingw32-make PCRE=c:\dev\pcre OPENSSL=c:\dev\openssl  ::: noteclassic 32和64位 版本都可以构建在64位的平台上，但是32位平台只能构建32位版本。 在32位平台上运行时，请遵循64位版本在64位平台上运行的步骤。 :::

en-us	# 6 Action log
zh-cn	 # 6 动作日志

en-us	# 6 Elasticsearch setup  ::: noteimportant  Elasticsearch support is experimental!  :::  Zabbix supports the storage of historical data by means of Elasticsearch instead of a database. Users can choose the storage place for historical data between a compatible database and Elasticsearch. The setup procedure described in this section is applicable to Elasticsearch version 7.X. In case an earlier or later version of Elasticsearch is used, some functionality may not work as intended.  ::: notewarning  If all history data is stored in Elasticsearch, trends are **not** calculated nor stored in the database. With no trends calculated and stored, the history storage period may need to be extended. :::
zh-cn	# 6 Elasticsearch 配置  ::: noteimportant  对 Elasticsearch 的支持仍在试验阶段！ ::: Zabbix支持Elasticsearch代替数据库存储历史数据。用户可以在兼容的数据库和 Elasticsearch 之间选择存储历史数据的位置。本章节描述的设置适用于 Elasticsearch version 7.X。如果使用早期或更高版本的 Elasticsearch，某些功能可能无法使用。  ::: notewarning 如果所有历史数据都存储在 Elasticsearch 中，则不会计算趋势，也不会将其存储在数据库中。由于没有计算和存储任何趋势，则可能需要延长历史记录存储期。 :::

en-us	# 6 Header
zh-cn	# 6 Header标头

en-us	# 6 MQTT plugin
zh-cn	# 6 MQTT 插件

en-us	# 6 New template
zh-cn	# 6 新建模板

en-us	# 6 Page parameters
zh-cn	# 6 页面参数

en-us	# 6 Sender
zh-cn	# 6 Sender

en-us	##### 6 Start new Zabbix binaries  Start new binaries. Check log files to see if the binaries have started successfully.  Zabbix server will automatically upgrade the database. When starting up, Zabbix server reports the current (mandatory and optional) and required database versions. If the current mandatory version is older than the required version, Zabbix server automatically executes the required database upgrade patches. The start and progress level (percentage) of the database upgrade is written to the Zabbix server log file. When the upgrade is completed, a "database upgrade fully completed" message is written to the log file. If any of the upgrade patches fail, Zabbix server will not start. Zabbix server will also not start if the current mandatory database version is newer than the required one. Zabbix server will only start if the current mandatory database version corresponds to the required mandatory version.      8673:20161117:104750.259 current database version (mandatory/optional): 03040000/03040000     8673:20161117:104750.259 required mandatory version: 03040000  Before you start the server:  -   Make sure the database user has enough permissions (create table,     drop table, create index, drop index) -   Make sure you have enough free disk space.
zh-cn	##### 6 启动新的 Zabbix 程序文件  启动新的程序文件。检查日志以确认程序文件是否成功启动。  Zabbix server 会自动升级数据库。服务启动时，Zabbix server 会报告当前的（包括强制和可选）和所需要的数据库版本。如果当前强制版本比要求的版本低，Zabbix Server 会自动执行所要求的数据库版本升级补丁。数据库升级进度（百分比）被写入 Zabbix server 的日志。当日志出现 “database upgrade fully completed” 表示数据库升级成功。如果有任何补丁升级失败，Zabbix server 将不会启动。如果当前强制数据库版本比要求的更新，Zabbix server 也不会启动。仅当当前强制数据库版本对应于所需数据库版本时，Zabbix server 才会启动。     8673:20161117:104750.259 current database version (mandatory/optional): 03040000/03040000    8673:20161117:104750.259 required mandatory version: 03040000    在启动 server 服务之前：  -   确保数据库用户有足够的权限（创建表、删除表、创建索引、删除索引）； -   确保您有足够的可用磁盘空间。

en-us	# 6 Tagging
zh-cn	# 6 标记

en-us	# 6 Unstable releases
zh-cn	# 6 不稳定版本

en-us	# 6 Zabbix agent 2 (Windows)
zh-cn	# 6 Zabbix agent 2 （Windows系统）

en-us	# 7 Calculated items
zh-cn	# 7 可计算监控项

en-us	# 7. Configuration  Please use the sidebar to access content in the Configuration section.
zh-cn	# 7. 配置  请使用左侧导航栏来访问“配置”这一章节的内容。

en-us	# 7 Definitions
zh-cn	# 7 定义

en-us	# 7 Get
zh-cn	# 7 Get

en-us	# 7 Notifications
zh-cn	 # 7 通知

en-us	##### 7 Start Zabbix processes  Start the updated Zabbix components.      # systemctl start zabbix-server     # systemctl start zabbix-proxy     # systemctl start zabbix-agent     # systemctl start zabbix-agent2
zh-cn	##### 7 启动Zabbix进程  启动更新后的 Zabbix 组件。    · # systemctl start zabbix-server   · # systemctl start zabbix-proxy   · # systemctl start zabbix-agent   · # systemctl start zabbix-agent2

en-us	# 7 Visualization
zh-cn	# 7 可视化

en-us	# 7 Zabbix agent 2 plugins
zh-cn	# 7 Zabbix agent 2 插件

en-us	##### 8 Clear web browser cookies and cache  After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly.
zh-cn	##### 8 清除网络浏览器 cookie 和缓存  升级后，您可能需要清除网络浏览器 cookie 和网络浏览器缓存，以便 Zabbix web界面正常工作。

en-us	# 8 Creating your own theme
zh-cn	# 8 定制主题风格

en-us	# 8 Internal checks
zh-cn	 # 8 内部检查

en-us	# 8 JS
zh-cn	# 8 JS

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

en-us	# 8 Unit symbols
zh-cn	# 8 单位符号

en-us	# 8 Zabbix Java gateway  If you use `startup.sh` and `shutdown.sh` scripts for starting [Zabbix Java gateway](/manual/concepts/java), then you can specify the necessary configuration parameters in the `settings.sh` file. The startup and shutdown scripts source the settings file and take care of converting shell variables (listed in the first column) to Java properties (listed in the second column).  If you start Zabbix Java gateway manually by running `java` directly, then you specify the corresponding Java properties on the command line.  |Variable|Property|Mandatory|Range|Default|Description| |--------|--------|---------|-----|-------|-----------| |LISTEN\_IP|zabbix.listenIP|no| |0.0.0.0|IP address to listen on.| |LISTEN\_PORT|zabbix.listenPort|no|1024-32767|10052|Port to listen on.| |PID\_FILE|zabbix.pidFile|no| |/tmp/zabbix\_java.pid|Name of PID file. If omitted, Zabbix Java Gateway is started as a console application.| |PROPERTIES\_FILE|zabbix.propertiesFile|no| | |Name of properties file. Can be used to set additional properties using a key-value format in such a way that they are not visible on a command line or to overwrite existing ones.<br>For example: "javax.net.ssl.trustStorePassword=<password>"| |START\_POLLERS|zabbix.startPollers|no|1-1000|5|Number of worker threads to start.| |TIMEOUT|zabbix.timeout|no|1-30|3|How long to wait for network operations.|  ::: notewarning Port 10052 is not [IANA registered](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). :::
zh-cn	# 8 Zabbix Java网关  如果使用`startup.sh`和`shutdown.sh`脚本启动和停止[Zabbix Java 网关](/manual/concepts/java), 则可以在`settings.sh`文件中指定必要的配置参数。启动和关闭脚本以配置文件为输入源 ，并且将shell 变量 (第一列) 转换为相应的Java 属性 (第二列)。  如果通过手动运行`java`命令来起动Zabbix Java 网关, 可以通过命令行方式来指定Java属性。  |变量|属性|是否必须|范围|默认值|描述| |--------|--------|---------|-----|-------|-----------| |LISTEN\_IP|zabbix.listenIP|否| |0.0.0.0|监听IP地址。| |LISTEN\_PORT|zabbix.listenPort|否|1024-32767|10052|监听端口。| |PID\_FILE|zabbix.pidFile|否| |/tmp/zabbix\_java.pid|PID文件的名称。如果省略，Zabbix Java gateway将作为控制台应用程序启动。| |PROPERTIES\_FILE|zabbix.propertiesFile|否| | |属性文件的名称。可用于使用键值格式设置其他属性，以使其在命令行上不可见或覆盖现有属性。<br>示例: "javax.net.ssl.trustStorePassword=<password>"| |START\_POLLERS|zabbix.startPollers|否|1-1000|5|启动的线程数。| |TIMEOUT|zabbix.timeout|否|1-30|3|等待超时的时间。|  ::: notewarning 10052端口没有在 [IANA注册](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). :::

en-us	# 9 Debug mode
zh-cn	# 9 调试模式

en-us	# 9 Templates out of the box
zh-cn	 # 9 开箱即用的模板

en-us	# 9 Time period syntax
zh-cn	# 9 时间段语法

en-us	# 9. Web monitoring
zh-cn	# 9. Web 监控

en-us	# 9 Web service
zh-cn	#  9 Web service

en-us	# 9 Zabbix web service
zh-cn	# 9 Zabbix web 服务

en-us	#### Absence of data  For items with a regular update interval, nothing is displayed in the graph if item data are not collected.  However, for trapper items and items with a scheduled update interval (and regular update interval set to 0), a straight line is drawn leading up to the first collected value and from the last collected value to the end of graph; the line is on the level of the first/last value respectively.
zh-cn	#### 数据缺失  对于具有定期更新间隔的监控项，在如果未收集项目数据，则图表展示为空。  但是，对于trapper监控项和具有计划更新间隔的项（但是定期更新间隔设置为 0），在第一个收集的值和最后一个收集的值之间是一条直线；这条线分别位于第一个/最后一个值的级别上 。

en-us	### Access control
zh-cn	### 访问控制

en-us	#### Access permissions  Make sure that the 'zabbix' user has execute permissions for configured commands. One may be interested in using **sudo** to give access to privileged commands. To configure access, execute as root:      # visudo  Example lines that could be used in *sudoers* file:      # allows 'zabbix' user to run all commands without password.     zabbix ALL=NOPASSWD: ALL      # allows 'zabbix' user to restart apache without password.     zabbix ALL=NOPASSWD: /etc/init.d/apache restart  ::: notetip On some systems *sudoers* file will prevent non-local users from executing commands. To change this, comment out **requiretty** option in */etc/sudoers*. :::
zh-cn	#### 访问权限  确保‘zabbix’用户拥有执行配置的命令的权限。用户可能有兴趣使用**sudo**给特权命令访问权限。要配置访问权限，用root执行以下命令：      # visudo  可以在*sudoers*文件使用示例的几行：      # allows 'zabbix' user to run all commands without password.     zabbix ALL=NOPASSWD: ALL      # allows 'zabbix' user to restart apache without password.     zabbix ALL=NOPASSWD: /etc/init.d/apache restart  ::: notetip 在有些操作系统中，*sudoers*文件禁止非本地用户执行命令，可以在*/etc/sudoers*文件中取消注释**requiretty**选项。 :::

en-us	# action.create
zh-cn	# 创建

en-us	# action.delete
zh-cn	# 删除

en-us	# action.get
zh-cn	# 获取

en-us	# > Action object  The following objects are directly related to the `action` API.
zh-cn	# > 动作对象  以下对象与`动作` API 直接相关。

en-us	#### Actions and alerts  Define actions and operations to notify users about certain events or automatically execute remote commands. Gain access to information about generated alerts and their receivers.  [Action API](/manual/api/reference/action) | [Alert API](/manual/api/reference/alert)
zh-cn	#### 动作和警报  定义动作和报警，以通知用户某些事件或自动执行远程命令。获取有关生成的警报及其接收者的信息。  [Action API](/manual/api/reference/action) | [Alert API](/manual/api/reference/alert)

en-us	#### Actions  Discovery events can be the basis of relevant [actions](/manual/config/notifications/action), such as:  -   Sending notifications -   Adding/removing hosts -   Enabling/disabling hosts -   Adding hosts to a group -   Removing hosts from a group -   Linking hosts to/unlinking from a template -   Executing remote scripts  These actions can be configured with respect to the device type, IP, status, uptime/downtime, etc. For full details on configuring actions for network-discovery based events, see action [operation](/manual/config/notifications/action/operation) and [conditions](/manual/config/notifications/action/conditions) pages.  Since network discovery actions are event-based, they will be triggered both when a discovered host is online and when it is offline. It is highly  recommended to add an action [condition](/manual/config/notifications/action/conditions) *Discovery status: up* to avoid such actions as *Add host* being triggered upon *Service Lost*/*Service Down* events.  Otherwise, if a discovered host is manually removed, it will still generate *Service Lost*/*Service Down* events and will be recreated during the next discovery cycle.  ::: noteclassic Linking a discovered host to templates will fail collectively if any of the linkable templates has a unique entity (e.g. item key) that is the same as a unique entity (e.g. item key) already existing on the host or on another of the linkable templates. :::
zh-cn	#### 动作  发现事件可触发相关[动作](/manual/config/notifications/action)，例如：  -   发送通知 -   添加/删除主机 -   启用/禁用主机 -   添加主机到组 -   从组中移除主机 -   链接/取消链接主机到模板 -   执行远程脚本  这些动作可基于设备类型、IP、状态、运行时长(uptime)/停机时长(downtime)等条件来配置。欲了解如何配置这些动作，参阅动作的[操作](/manual/config/notifications/action/operation) 和[条件](/manual/config/notifications/action/conditions) 页面获取完整细节。  ::: noteclassic 通过网络发现添加的主机，如果其链接的模板中有一个唯一属性(如监控项的键)与该主机上的唯一属性相同，或与该模板链接的其它主机上的唯一属性相同，则这台主机上的所有模板均会链接失败。 :::

en-us	#### Actions  In [actions](/manual/config/notifications/action), user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Trigger-based notifications and commands|<|yes| |Trigger-based internal notifications|<|yes| |Problem update notifications|<|yes| |Service-based notifications and commands|<|yes| |Service update notifications|<|yes| |Time period condition|<|no| |*Operations*|<|<| | |Default operation step duration|no| |^|Step duration|no|
zh-cn	#### 动作  在 [动作](/manual/config/notifications/action)中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |基于触发器的通知和命令|<|支持| |基于触发器的内部通知|<|支持| |问题更新通知|<|支持| |基于服务的通知和命令|<|支持| |服务更新通知|<|支持| |时间段条件|<|不支持| |*操作*|<|<| | |默认操作步骤持续时间|不支持| |^|步骤持续时间|不支持|

en-us	# Action  This class is designed to work with actions.  Object references:\  -   [Action](/manual/api/reference/action/object#action) -   [Action     condition](/manual/api/reference/action/object#action_condition) -   [Action     operation](/manual/api/reference/action/object#action_operation)  Available methods:\  -   [action.create](/manual/api/reference/action/create) - create new     actions -   [action.delete](/manual/api/reference/action/delete) - delete     actions -   [action.get](/manual/api/reference/action/get) - retrieve actions -   [action.update](/manual/api/reference/action/update) - update     actions
zh-cn	# 动作  这个类用于操作动作。  对象引用：\  -   [动作](/manual/api/reference/action/object#动作) -   [动作条件](/manual/api/reference/action/object#动作条件) -   [动作操作](/manual/api/reference/action/object#动作操作)  可用方法：\  -   [action.create](/manual/api/reference/action/create) - 创建新的动作 -   [action.delete](/manual/api/reference/action/delete) - 删除动作 -   [action.get](/manual/api/reference/action/get) - 获取动作 -   [action.update](/manual/api/reference/action/update) - 更新动作

en-us	# action.update
zh-cn	# 更新

en-us	#### Active proxy
zh-cn	#### 主动代理

en-us	##### Adding host  Hosts are added during the discovery process, as soon as a host is discovered, rather than at the end of the discovery process.  ::: notetip As network discovery can take some time due to many unavailable hosts/services having patience and using reasonable IP ranges is advisable. :::  When adding a host, its name is decided by the standard **gethostbyname** function. If the host can be resolved, resolved name is used. If not, the IP address is used. Besides, if IPv6 address must be used for a host name, then all ":" (colons) are replaced by "\_" (underscores), since colons are not allowed in host names.  ::: noteimportant If performing discovery by a proxy, currently hostname lookup still takes place on Zabbix server. :::  ::: noteimportant If a host already exists in Zabbix configuration with the same name as a newly discovered one, versions of Zabbix prior to 1.8 would add another host with the same name. Zabbix 1.8.1 and later adds **\_N** to the hostname, where **N** is increasing number, starting with 2. :::
zh-cn	##### 添加主机  主机在发现过程中中添加，一旦发现立即添加，而非在发现过程结束后添加。  ::: notetip 网络发现会因为太多不可达的主机或服务而用时很长，请耐心等待或使用合理IP地址范围。 :::  添加主机时，其名称由标准的** gethostbyname **函数决定。如果可以解析主机，则使用解析名称。如果没有，则使用IP地址。此外，如果必须使用IPv6地址作为主机名，则所有“：”（冒号）将被替换为“\_”（下划线），因为主机名中不允许冒号。  ::: noteimportant 如果通过代理执行发现，当前主机名查找仍然发生在Zabbix服务器上。 :::  ::: noteimportant 如果一个新发现的主机与Zabbix的配置中已有的主机同名，1.8之前的版本将添加一个同名的主机。Zabbix 1.8.1及更高版本将** \_ N **添加到主机名中，** N**是从2开始递增的正整数。 :::

en-us	##### Adding JMX agent item  For each JMX counter you are interested in you add **JMX agent** item attached to that interface.\  The key in the screenshot below says `jmx["java.lang:type=Memory","HeapMemoryUsage.used"]`.  ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_item.png)  All mandatory input fields are marked with a red asterisk.  The fields that require specific information for JMX items are:  |   |   | |--|--------| |*Type*|Set **JMX agent** here.| |*Key*|The `jmx[]` item key contains three parameters:<br>**object name** - the object name of an MBean<br>**attribute name** - an MBean attribute name with optional composite data field names separated by dots<br>**unique short description** - a unique description that allows multiple JMX items with the same object name and attribute name on the host (optional)<br>See below for more detail on JMX item keys.<br>Since Zabbix 3.4, you may discover MBeans and MBean attributes using a `jmx.discovery[]` [low-level discovery](/manual/discovery/low_level_discovery/examples/jmx) item.| |*JMX endpoint*|You may specify a custom JMX endpoint. Make sure that JMX endpoint connection parameters match the JMX interface. This can be achieved by using {HOST.\*} macros as done in the default JMX endpoint.<br>This field is supported since 3.4.0. {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) and user macros are supported.| |*User name*|Specify the user name, if you have configured authentication on your Java application.<br>User macros are supported.| |*Password*|Specify the password, if you have configured authentication on your Java application.<br>User macros are supported.|  If you wish to monitor a Boolean counter that is either "true" or "false", then you specify type of information as "Numeric (unsigned)" and select "Boolean to decimal" preprocessing step in the Preprocessing tab. Server will store Boolean values as 1 or 0, respectively.
zh-cn	##### 添加 JMX 代理监控项  对于您感兴趣的每个 JMX 计数器，您添加附加到该接口的 **JMX 代理** 监控项。\  下面屏幕截图中的键表示 `jmx["java.lang:type=Memory","HeapMemoryUsage.used"]`。  ![](../../../../../assets/en/manual/config/items/itemtypes/jmx_item.png)  所有必填输入字段都标有红色星号。   JMX 监控项需要的特定信息字段是：  | · | · | |--|--------| |*类型*|在这里设置**JMX代理**。| |*键值*|`jmx[]` 监控项键包含三个参数：<br>**对象名称** - MBean 的对象名称<br>**属性名称** - 一个 MBean 属性名称，带有由点分隔的可选复合数据字段名称<br>**唯一简短描述** - 允许主机上具有相同对象名称和属性名称的多个 JMX 监控项的唯一描述（可选）<br>有关 JMX 监控项的更多详细信息，请参见下文 <br>从 Zabbix 3.4 开始，您可以使用 `jmx.discovery[]` [低级发现](/manual/discovery/low_level_discovery/examples/jmx) 项来发现 MBean 和 MBean 属性。| |*JMX 端点*|您可以指定自定义 JMX 端点。 确保 JMX 端点连接参数与 JMX 接口匹配。 这可以通过在默认 JMX 端点中使用 {HOST.\*} 宏来实现。<br>此字段自 3.4.0 起受支持。 {HOST.\*} [macros](/manual/appendix/macros/supported_by_location) 和用户宏被支持。| |*用户名*|如果您在 Java 应用程序上配置了身份验证，请指定用户名。<br>支持用户宏。| |*密码*|指定密码，如果您已在 Java 应用程序上配置身份验证。<br>支持用户宏。|  如果您希望监视“真”或“假”的布尔计数器，则将信息类型指定为“数字（无符号）”并在“预处理”选项卡中选择“布尔到十进制”预处理步骤。 服务器将布尔值分别存储为 1 或 0。

en-us	#### Adding lines  In addition to shapes, it is also possible to add some lines. Lines can be used to link elements or shapes in a map.  To add a line, click on *Add* next to Shape. A new shape will appear at the top left corner of the map. Select it and click on *Line* in the editing form to change the shape into a line. Then adjust line properties, such as line type, width, color, etc.  ![map\_line.png](../../../../../assets/en/manual/config/visualization/map_line.png){width="600"}
zh-cn	#### 添加行  除了形状之外，还可以添加一些线。线可以用于链接地图中的元素或形状。  要添加线，请单击形状旁边的*添加*。一个新的形状将出现在地图的左上角。选择它并点击*线*编辑表格以将形状更改为线条。然后调整线属性，例如线型、宽度、颜色等。  ![map\_line.png](../../../../../assets/en/manual/config/visualization/map_line.png){width="600"}

en-us	#### Adding shapes  In addition to map elements, it is also possible to add some shapes. Shapes are not map elements; they are just a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Rectangle and ellipse shapes can be added.  To add a shape, click on *Add* next to Shape. The new shape will appear at the top left corner of the map. Drag and drop it wherever you like.  A new shape is added with default colors. By clicking on the shape, a form is displayed and you can customize the way a shape looks, add text, etc.  ![](../../../../../assets/en/manual/config/visualization/map_shape.png){width="600"}  To select shapes, select one and then hold down *Ctrl* to select the others. With several shapes selected, common properties can be mass updated, similarly as with elements.  Text can be added in the shapes. Expression [macros](/manual/appendix/macros/supported_by_location) are supported in the text, but only with `avg`, `last`, `min` and `max` functions, with time as parameter (for example, `{?avg(/host/key,1h)}`).  To display text only the shape can be made invisible by removing the shape border (select 'None' in the *Border* field). For example, take note of how the {MAP.NAME} macro, visible in the screenshot above, is actually a rectangle shape with text, which can be seen when clicking on the macro:  ![](../../../../../assets/en/manual/config/visualization/map_name_macro.png)  {MAP.NAME} resolves to the configured map name when viewing the map.  If hyperlinks are used in the text, they become clickable when viewing the map.  Line wrapping for text is always "on" within shapes. However, within an ellipse, the lines are wrapped as though the ellipse were a rectangle. Word wrapping is not implemented, so long words (words that do not fit the shape) are not wrapped, but are masked (constructor page) or clipped (other pages with maps).
zh-cn	#### 添加形状  除了地图元素，还可以添加一些形状。形状不是地图元素；它们只是一种视觉表现。例如，可以使用矩形作为背景来分组一些主机。可以添加矩形和椭圆形。  要添加形状，请单击形状旁边的*添加*。新形状将出现在地图的左上角。将其拖放到您喜欢的任何位置。  添加了具有默认颜色的新形状。通过单击形状，窗体显示，您可以自定义形状的外观，添加文本，等等。  ![](../../../../../assets/en/manual/config/visualization/map_shape.png){width="600"}  要选择形状，请选择一个，然后按住 *Ctrl* 选择其他。选择几种形状后，常见的属性可以是质量更新，与元素类似。  可以在形状中添加文本。表达[宏](/manual/appendix/macros/supported_by_location) 支持文本，但只有 `avg`、`last`、`min` 和 `max` 函数，有时间作为参数（例如，`{?avg(/host/key,1h)}`）。  要仅显示文本，可以通过删除形状边框（在 *边框* 字段中选择“无”）。例如，取请注意上面屏幕截图中可见的 {MAP.NAME} 宏是如何实现的实际上是一个带有文本的矩形形状，单击时可以看到宏：  ![](../../../../../assets/en/manual/config/visualization/map_name_macro.png)  {MAP.NAME} 在查看地图时解析为配置的地图名称。  如果文本中使用了超链接，则它们在查看时变为可点击的地图。  文本的换行始终在形状内“开启”。然而，在一椭圆，线条被包裹起来，好像椭圆是一个矩形。没有实现自动换行，所以长词（不适合的词形状）没有被包裹，而是被屏蔽（构造器页面）或被剪裁（其他页面有地图）。

en-us	##### Additional parameters  A third optional parameter is supported by the *bucket\_rate\_foreach* function:      bucket_rate_foreach(item filter,time period,<parameter number>)  where <parameter number> is the position of the "bucket" value in the item key. For example, if the "bucket" value in myItem\[aaa,0.2\] is '0.2', then its position is 2.  The default value of <parameter number> is '1'.  See [aggregate calculations](/manual/config/items/itemtypes/calculated/aggregate) for more details and examples on using foreach functions.
zh-cn	##### 附加参数  *bucket\_rate\_foreach* 支持第三个可选参数 功能：      bucket_rate_foreach(item filter,time period,<parameter number>)  其中 <parameter number> 是“bucket”值在 监控项键。例如，如果 myItem\[aaa,0.2\] 中的“bucket”值为 '0.2'，则其位置为 2。  <parameter number> 的默认值为“1”。

en-us	##### Agent configuration  HA cluster nodes (servers) must be listed in the configuration of  Zabbix agent or Zabbix agent 2.  ![](../../../../assets/en/manual/config/zabbix_ha_agent.png)  To enable passive checks, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_agentd), separated by a **comma**.  ``` Server=zabbix-node-01,zabbix-node-02 ```  To enable active checks, the node names must be listed in the ServerActive [parameter](/manual/appendix/config/zabbix_agentd). Note that for  active checks the nodes must be separated by a comma from any other  servers, while the nodes themselves must be separated by a **semicolon**, e.g.:  ``` ServerActive=zabbix-node-01;zabbix-node-02 ```
zh-cn	 ##### Agent 配置  Zabbix agent 或者 Zabbix agent 2.必须将HA 集群节点列入配置文件。  ![](../../../../assets/en/manual/config/zabbix_ha_agent.png)  启用被动检查agent, 节点名称必须列入Server[参数](/manual/appendix/config/zabbix_agentd), 使用**逗号**分隔.  ``` Server=zabbix-node-01,zabbix-node-02 ```  启用主动检查agent, 节点名称必须列入ServerActive[参数](/manual/appendix/config/zabbix_agentd). 注意，对于主动检查agent，节点与其他server之间必须用逗号分隔，而节点本身必须用**分号**分隔，例如:  ``` ServerActive=zabbix-node-01;zabbix-node-02 ```

en-us	 ### Agent data request  The agent data request contains the gathered item values.  | Field |<| Type | Mandatory | Value | |-|------|--|-|-----------------------| | request |<| _string_ | yes | `agent data` | | host |<| _string_ | yes | Host name. | | version |<| _string_ | yes | The agent version: \<major>.\<minor>. | | session |<| _string_ | yes | Unique session identifier generated each time when agent is started. | | data |<| _array of objects_ | yes | Item values. | | | id | _number_ | yes | The value identifier (incremental counter used for checking duplicated values in the case of network problems). | |^| itemid | _number_ | yes | Item identifier. | |^| value | _string_ | no | The item value. | |^| lastlogsize | _number_ | no | The item lastlogsize. | |^| mtime | _number_ | no | The item mtime. | |^| state | _number_ | no | The item state. | |^| source | _string_ | no | The value event log source. | |^| eventid | _number_ | no | The value event log eventid. | |^| severity | _number_ | no | The value event log severity. | |^| timestamp | _number_ | no | The value event log timestamp. | |^| clock | _number_ | yes | The value timestamp (seconds since Epoch). | |^| ns | _number_ | yes | The value timestamp nanoseconds. |  Example: ```json {   "request": "agent data",   "data": [     {       "id": 1,       "itemid": 5678,       "value": "2.4.0",       "clock": 1400675595,       "ns": 76808644     },     {       "id": 2,       "itemid": 1234,       "lastlogsize": 112,       "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).",       "clock": 1400675595,       "ns": 77053975     }   ],   "host": "Zabbix server",   "version": "6.0",   "session": "1234456akdsjhfoui" } ```
zh-cn	### Agent数据请求  Agent数据请求包含收集的监控项值。  | 字段|<| 类型 | 必填 | 值 | |-|------|--|-|------------------------| | request |<| _字符串_ | 是 | `agent数据` | | host|<| _字符串_ | 是 | 主机名。 | | version|<| _字符串_ | 是 | agent版本：\<major>.\<minor>。 | | session|<| _字符串_ | 是 | 每次启动agent时生成的唯一会话标识符。 | | data |<| _对象数组_ | 是 | 监控项值。 | | | id | 数字 | 是 | 值标识符（用于在出现网络问题时检查重复值的增量计数器）。 | |^| itemid | 数字 | 是 | 监控项标识符。 | |^| value | _字符串_ | 否 | 物品价值。 | |^| lastlogsize | 数字 | 否 | 该监控项最后日志大小。 | |^| mtime | 数字 | 否 | 监控项时间。 | |^| state | 数字 | 否 | 监控项状态。 | |^| source | _字符串_ | 否 | 事件日志源。 | |^| eventid | 数字 | 否 | 事件日志eventid。 | |^| severity | 数字 | 否 | 事件日志严重性。 | |^| timestamp | 数字 | 否 | 事件日志时间戳。 | |^| clock | 数字 | 是 | 时间戳（自纪元以来的秒数）。 | |^| ns | 数字 | 是 | 时间戳纳秒。 |  示例： ```json {  · "request": "agent data",  · "data": [  · {  · "id": 1,  · "itemid": 5678,  · "value": "2.4.0",  · "clock": 1400675595,  · "ns": 76808644  · },  · {  · "id": 2,  · "itemid": 1234,  · "lastlogsize": 112,  · "value": " 19845:20140621:141708.521 Starting Zabbix Agent [<hostname>]. Zabbix 2.4.0 (revision 50000).",  · "clock": 1400675595,  · "ns": 77053975  · }  · ],  · "host": "Zabbix server",  · "version": "6.0",  · "session": "1234456akdsjhfoui" } ```

en-us	 ### Agent data response  The agent data response is sent by the server back to agent after processing the agent data request.  | Field | Type | Mandatory | Value | |-|-|-|--------| | response | _string_ | yes | `success` \| `failed` | | info | _string_ | yes | Item processing results. |  Example: ```json {   "response": "success",   "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ```
zh-cn	### Agent数据响应  agent数据响应在处理agent数据请求后由服务器发送回agent。  | 字段 | 类型 | 必填 | 值 | |-|-|-|--------| | response | _字符串_ | 是 | `成功`\| `失败` | | info | _字符串_ | 是 | 监控项处理结果。 |  例子： ```json {  · "response": "success",  · "info": "processed: 2; failed: 0; total: 2; seconds spent: 0.003534" } ```

en-us	#### Agent on UNIX-like systems  Zabbix agent on UNIX-like systems is run on the host being monitored.
zh-cn	#### 类 UNIX 系统上的 Agent  类 UNIX 系统上的 Zabbix agent 运行在被监控的主机上。

en-us	#### Agent on Windows systems  Zabbix agent on Windows runs as a Windows service.
zh-cn	 #### Windows 系统上的 Agent  Windows 系统上的 Zabbix agent 作为一个Windows服务运行。

en-us	##### Agent operation with persistent file  On startup Zabbix agent knows nothing about persistent files. Only after receiving a list of active checks from Zabbix server \(proxy\) the agent sees that some log items should be backed by persistent files under specified directories.  During agent operation the persistent files are opened for writing (with fopen(filename, "w")) and overwritten with the latest data.  The chance of losing persistent file data if the overwriting and file system mirror split happen at the same time is very small, no special handling for it.  Writing into persistent file is NOT followed by enforced synchronization to storage media \(fsync\(\) is not called\).  Overwriting with the latest data is done after successful reporting of matching log file record or metadata \(processed log size and modification time\) to Zabbix server. That may happen as often as every item check if log file keeps changing.  No special actions during agent shutdown.
zh-cn	##### 持久文件的代理操作  在启动时 Zabbix agent 对持久文件一无所知。只有在收到来自 Zabbix server \(proxy\)的活动检查列表后，代理才会看到某些日志项应该由指定目录下的持久文件支持。  在代理操作期间，持久文件被打开以进行写入（使用 fopen(filename, "w")）并用最新数据覆盖。如果同时发生覆盖和文件系统镜像拆分，丢失持久文件数据的机会非常小，无需特殊处理。写入持久文件后不会强制同步到存储介质（不调用  \(fsync\(\)\)。  在成功向 Zabbix server报告匹配的日志文件记录或元数据\(处理的日志大小和修改时间\)后，使用最新数据覆盖。这可能与每个监控项检查日志文件是否不断变化一样频繁。  代理关闭期间没有特殊操作。

en-us	#### Agent process types  -   `active checks` - process for performing active checks -   `collector` - process for data collection -   `listener` - process for listening to passive checks  The agent log file can be used to observe these process types.
zh-cn	 #### Agent 进程类型  -   `active checks` - 执行主动检查的进程 -   `collector` - 执行数据收集的进程 -   `listener` - 执行被动监控监听的进程  Agent日志文件可用于观察这些进程类型。

en-us	#### AIX  See values supported for 'memtype' parameter on AIX in the table.  |Supported value|Description|Source in procentry64 structure|Tries to be compatible with| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|pi\_size| | |pmem|Percentage of real memory|pi\_prm|ps -o pmem| |rss|Resident set size|pi\_trss + pi\_drss|ps -o rssize| |size|Size of process (code + data)|pi\_dvm|"ps gvw" SIZE column| |dsize|Data size|pi\_dsize|<| |tsize|Text (code) size|pi\_tsize|"ps gvw" TSIZ column| |sdsize|Data size from shared library|pi\_sdsize|<| |drss|Data resident set size|pi\_drss| | |trss|Text resident set size|pi\_trss| |
zh-cn	#### AIX  请参阅表中 AIX 上“memtype”参数支持的值。  |支持值|说明|procentry64结构中来源|尽量兼容| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|虚拟内存大小|pi\_size| | |pmem|实际内存百分比|pi\_prm|ps -o pmem| |rss|常驻集大小|pi\_trss + pi\_drss|ps -o rssize| |size|进程大小（代码 + 数据）|pi\_dvm|“ps gvw”SIZE column| |dsize|数据大小|pi\_dsize|<| |tsize|文本（代码）大小|pi\_tsize|“ps gvw” TSIZ column| |sdsize|共享库的数据大小|pi\_sdsize|<| |drss|数据常驻集大小|pi\_drss| | |trss|文本常驻集大小|pi\_trss| |

en-us	# alert.get
zh-cn	# 获取

en-us	# > Alert object  The following objects are directly related to the `alert` API.
zh-cn	# > 告警对象  以下对象与 `alert` API 直接相关。

en-us	# Alert  This class is designed to work with alerts.  Object references:\  -   [Alert](/manual/api/reference/alert/object#alert)  Available methods:\  -   [alert.get](/manual/api/reference/alert/get) - retrieve alerts
zh-cn	# 告警  这个对象用于操作告警。  对象参考：\  -   [Alert](/manual/api/reference/alert/object#告警)  可用方法：\  -   [alert.get](/manual/api/reference/alert/get) - 获取告警

en-us	##### Allow specific check, deny others  -   Whitelist specific checks with AllowKey parameters, deny others with     `DenyKey=*`  For example:      # Allow reading logs:     AllowKey=vfs.file.*[/var/log/*]      # Allow localtime checks     AllowKey=system.localtime[*]      # Deny all other keys     DenyKey=*
zh-cn	##### 允许特定检查，拒绝其他检查  - 使用 AllowKey 参数将特定检查列入白名单，使用DenyKey=*拒绝其他检查     `DenyKey=*`  例如：      # 允许阅读日志：     AllowKey=vfs.file.*[/var/log/*]      # 允许本地时间检查     AllowKey=system.localtime[*]      # 拒绝所有其他键     DenyKey=*

en-us	##### Another example with an inline regex modifier  Use of the following regular expression including multiple inline modifiers to match the characters after a specific line:      (?<=match (?i)everything(?-i) after this line\n)(?sx).*# we add s modifier to allow . match newline characters  ![regexp\_expr\_4\_new.png](../../assets/en/manual/regular_expressions/regexp_expr_4_new.png)  Chosen Expression type: "Result is TRUE". Characters after a specific line are matched.  ::: noteimportant  **g** modifier can't be specified in line. The list of available modifiers can be found in [pcresyntax man page](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16). For more information about PCRE syntax please refer to [PCRE HTML documentation](https://www.pcre.org/original/doc/html/pcrepattern.html).  :::
zh-cn	##### 另一个使用内联正则表达式修饰符的示例  使用以下包含多个内联修饰符的正则表达式来匹配特定行之后的字符：      (?<=match (?i)everything(?-i) after this line\n)(?sx).*# we add s modifier to allow . match newline characters  ![regexp\_expr\_4\_new.png](../../assets/en/manual/regular_expressions/regexp_expr_4_new.png)  选择的表达式类型："Result is TRUE（结果为真）"。匹配特定行之后的字符。  ::: noteimportant  **g** 修饰符不能在行中指定。可用修饰符列表可以参考 [pcresyntax 手册页](https://www.pcre.org/original/doc/html/pcresyntax.html#SEC16)。有关 PCRE 语法的更多信息，请参阅 [PCRE HTML文档](https://www.pcre.org/original/doc/html/pcrepattern.html)。 :::

en-us	### API information  Retrieve the version of the Zabbix API so that your application could use version-specific features.  [API info API](/manual/api/reference/apiinfo)
zh-cn	### API 信息  检索Zabbix API的版本，以便应用程序可以使用特定于版本的功能。  [API info API](/manual/api/reference/apiinfo)

en-us	# API info  This class is designed to retrieve meta information about the API.  Available methods:\  -   [apiinfo.version](/manual/api/reference/apiinfo/version) -     retrieving the version of the Zabbix API
zh-cn	# API 信息  此类用于检索有关 API 的元信息。  可用方法：\  -   [apiinfo.version](/manual/api/reference/apiinfo/version) - 检索 Zabbix API 版本

en-us	# apiinfo.version
zh-cn	# 版本

en-us	#### API Tokens  Manage authorization tokens.  [Token API](/manual/api/reference/token)
zh-cn	#### API Tokens  管理认证 tokens.  [Token API](/manual/api/reference/token)

en-us	# Appendix 1. Reference commentary
zh-cn	 # 附录 1. 参考说明

en-us	#### Architecture  Zabbix consists of several major software components. Their responsibilities are outlined below.
zh-cn	#### 结构体系  Zabbix 由几个主要的软件组件组成。他们的职责概述如下。

en-us	#### A real life scenario  In this example, we would like to set up network discovery for the local network having an IP range of 192.168.1.1-192.168.1.254.  In our scenario we want to:  -   discover those hosts that have Zabbix agent running -   run discovery every 10 minutes -   add a host to monitoring if the host uptime is more than 1 hour -   remove hosts if the host downtime is more than 24 hours -   add Linux hosts to the "Linux servers" group -   add Windows hosts to the "Windows servers" group -   use the template *Linux* for Linux hosts -   use the template *Windows* for Windows hosts
zh-cn	#### 一个真实场景  在这个例子中，会演示如何给本地IP地址范围192.168.1.1-192.168.1.254设置网络发现规则。  需要在这个场景中实现：  -   发现运行了Zabbix agent的主机 -   每十分钟执行一次发现 -   如果主机运行时长大于一小时，添加该主机到监控中 -   如果主机停机时长大于二十四小时，则删除主机 -   添加Linux主机到"Linux服务器"组中 -   添加Windows主机到"Windows服务器"组中 -   给Linux主机使用 *Linux* 模板 -   给Windows主机使用 *Windows* 模板

en-us	#### Attempting to use Zabbix sender compiled with TLS support to send data to Zabbix server/proxy compiled without TLS
zh-cn	#### 尝试使用使用 TLS 支持编译的 Zabbix sender将数据发送到在没有 TLS 的情况下编译的 Zabbix Server/proxy

en-us	##### Attributes returning composite data  It becomes more complicated when your attribute returns composite data. For example: your attribute name is "apple" and it returns a hash representing its parameters, like "weight", "color" etc. Your key may look like this:      jmx[com.example:Type=Hello,apple.weight]  This is how an attribute name and a hash key are separated, by using a dot symbol. Same way, if an attribute returns nested composite data the parts are separated by a dot:      jmx[com.example:Type=Hello,fruits.apple.weight]
zh-cn	##### 属性返回复合数据  当您的属性返回复合数据时，它变得更加复杂。 例如：您的属性名称是"apple"，它返回一个表示其参数的哈希，如“重量”、“颜色”等。您的密钥可能看起来像这样：      jmx[com.example:Type=Hello,apple.weight]  这就是使用"."符号将属性名称和哈希键是如何分隔开。同样，如果一个属性返回嵌套的复合数据，那部分由"."分隔：      jmx[com.example:Type=Hello,fruits.apple.weight]

en-us	##### Attributes returning tabular data  Tabular data attributes consist of one or multiple composite attributes. If such an attribute is specified in the attribute name parameter then this item value will return the complete structure of the attribute in JSON format. The individual element values inside the tabular data attribute can be retrieved using preprocessing.  Tabular data attribute example:       jmx[com.example:type=Hello,foodinfo]  Item value:  ``` {.javascript} [   {     "a": "apple",     "b": "banana",     "c": "cherry"   },   {     "a": "potato",     "b": "lettuce",     "c": "onion"   } ] ```
zh-cn	##### 返回表格数据的属性  表格数据属性由一个或多个复合属性组成。 如果在属性名参数中指定了这样一个属性，那么这个监控项值将以JSON格式返回该属性的完整结构。 表格数据属性中的单个元素值可以使用预处理来检索。  表格数据属性示例:       jmx[com.example:type=Hello,foodinfo]  监控项值示例:  ``` {.javascript} [   {     "a": "apple",     "b": "banana",     "c": "cherry"   },   {     "a": "potato",     "b": "lettuce",     "c": "onion"   } ] ```

en-us	# auditlog.get
zh-cn	# 获取

en-us	# > Audit log object  The following objects are directly related to the `auditlog` API.
zh-cn	# > 审计日志对象  以下对象与 `auditlog` API 直接相关。

en-us	# Audit log  This class is designed to work with audit log.  Object references:\  -   [Audit log object](/manual/api/reference/auditlog/object)  Available methods:\  -   [auditlog.get](/manual/api/reference/auditlog/get) - retrieve audit     log records
zh-cn	# 审计日志  这个类用于操作审计日志。  对象参考：\  -   [Audit log object](/manual/api/reference/auditlog/object)  可用方法：\  -   [auditlog.get](/manual/api/reference/auditlog/get) - 获取审计日志记录

en-us	#### Authentication  Change authentication configuration options.  [Authentication API](/manual/api/reference/authentication)
zh-cn	#### 认证  更改身份认证配置选项。  [Authentication API](/manual/api/reference/authentication)

en-us	# authentication.get
zh-cn	# 获取

en-us	# > Authentication object  The following objects are directly related to the `authentication` API.
zh-cn	# > 认证对象  以下对象与 `authentication` API  直接相关。

en-us	# Authentication  This class is designed to work with authentication settings.  Object references:\  -   [Authentication](/manual/api/reference/authentication/object#authentication)  Available methods:\  -   [authentication.get](/manual/api/reference/authentication/get) -     retrieve authentication -   [authentication.update](/manual/api/reference/authentication/update) -     update authentication
zh-cn	# 认证  此类用于操作认证设置。  对象引用：\  -   [Authentication](/manual/api/reference/authentication/object#认证)  可用方法：\  -   [authentication.get](/manual/api/reference/authentication/get) - 获取认证 -   [authentication.update](/manual/api/reference/authentication/update) - 更新认证

en-us	# authentication.update
zh-cn	# 更新

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Alexei Vladishev <<alex@zabbix.com>>  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	## 作者  Zabbix 有限责任公司  ------------------------------------------------------------------------  [ ]{#index}

en-us	## AUTHOR  Zabbix LLC  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 作者  Zabbix 有限责任公司  ------------------------------------------------------------------------  [ ]{#index}

en-us	#### Autoregistration actions  The following conditions can be used in actions based on active agent autoregistration:  |Condition type|Supported operators|Description| |--|--|------| |*Host metadata*|contains<br>does not contain<br>matches<br>does not match|Specify host metadata or host metadata to exclude.<br>**contains** - host metadata contains the string.<br>**does not contain** - host metadata does not contain the string.<br>Host metadata can be specified in an [agent configuration file](/manual/appendix/config/zabbix_agentd).<br>**matches** - host metadata matches regular expression.<br>**does not match** - host metadata does not match regular expression.| |*Host name*|contains<br>does not contain<br>matches<br>does not match|Specify a host name or a host name to exclude.<br>**contains** - host name contains the string.<br>**does not contain** - host name does not contain the string.<br>**matches** - host name matches regular expression.<br>**does not match** - host name does not match regular expression.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|
zh-cn	#### 自动注册操作  以下条件可用于基于活动agent自动注册的操作：  |条件类型|支持的运算符|说明| |--|--|------| |*Host metadata*|包含<br>不包含<br>匹配<br>不匹配|指定主机元数据或要排除的主机元数据。<br>**包含** - 主机元数据包含字符串。<br >**不包含** - 主机元数据不包含字符串。<br>主机元数据可以在[agent配置文件](/manual/appendix/config/zabbix_agentd)中指定。<br>**匹配* * - 主机元数据与正则表达式匹配。<br>**不匹配** - 主机元数据与正则表达式不匹配。| |*Host name*|包含<br>不包含<br>匹配<br>不匹配|指定主机名或要排除的主机名。<br>**包含** - 主机名包含字符串。 <br>**不包含** - 主机名不包含字符串。<br>**匹配** - 主机名匹配正则表达式。<br>**不匹配** - 主机名与正则表达式不匹配。| |*Proxy*|等于<br>不等于|指定代理或要排除的代理。<br>**等于** - 使用此代理。<br>**不等于** - 使用除此之外的任何其他代理。|

en-us	# autoregistration.get
zh-cn	# 获取

en-us	# > Autoregistration object  The following objects are directly related to the `autoregistration` API.
zh-cn	# > 自动注册对象  以下对象与 `自动注册` API直接相关。

en-us	# Autoregistration  This class is designed to work with autoregistration.  Object references:\  -   [Autoregistration](/manual/api/reference/autoregistration/object#autoregistration)  Available methods:\  -   [autoregistration.get](/manual/api/reference/autoregistration/get) -     retrieve autoregistration -   [autoregistration.update](/manual/api/reference/autoregistration/update) -     update autoregistration
zh-cn	# 自动注册  该方法用于自动注册  对象引用:\  -   [自动注册](/manual/api/reference/autoregistration/object#autoregistration)  可用方法:\  -   [autoregistration.get](/manual/api/reference/autoregistration/get) -     检索自动注册 -   [autoregistration.update](/manual/api/reference/autoregistration/update) -     更新自动注册

en-us	# autoregistration.update
zh-cn	# 更新

en-us	##### Average request count to Nginx server  View the average request count per second per day to the Nginx server:  -   add the request count per second item to the data set -   select the aggregate function `avg` and specify interval `1d` -   a bar graph is displayed, where each bar represents the average     number of requests per second per day
zh-cn	##### Nginx 服务器的平均请求数  查看每天每秒对 Nginx 服务器的平均请求数：  - 将每秒项的请求计数添加到数据集中 - 选择聚合函数“avg”并指定区间“1d” - 显示一个条形图，其中每个条形图代表平均值每天每秒的请求数

en-us	#### Building inventory
zh-cn	#### 构建资产库

en-us	##### Buttons  *Create host* allows to create a [new host](/manual/config/hosts/host). This button is available for Admin and Super Admin users only.  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  *创建主机* 允许创建 [新主机](/manual/config/hosts/host)。此按钮仅对管理员和超级管理员用户可用。  [监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页介绍了所有部分通用的视图模式按钮。

en-us	##### Buttons  The button to the right offers the following option:  |   |   | |--|--------| |![](../../../../../assets/en/manual/web_interface/button_csv.png)|Export content from all pages to a CSV file.|  View mode buttons, being common for all sections, are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  右侧的按钮提供以下选项：  | · | · | |---|---| |![](../../../../../assets/en/manual/web_interface/button_csv.png)|将页面所有内容导出到CSV文件。|  在[监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页面介绍了所有通用的查看模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监控](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)中介绍了通用的显示模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监视](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页上介绍了所有部分通用的显示模式按钮。

en-us	##### Buttons  View mode buttons being common for all sections are described on the [Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons) page.
zh-cn	##### 按钮  [监控](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)页介绍了所有部分通用的监控模式按钮。

en-us	#### Calculation time  A trigger is recalculated every time Zabbix server receives a new value that is part of the expression. When a new value is received, each function that is included in the expression is recalculated (not just the one that received the new value).  Additionally, a trigger is recalculated each time when a new value is received **and** every 30 seconds if time-based functions are used in the expression.  Time-based functions are **nodata()**, **date()**, **dayofmonth()**, **dayofweek()**, **time()**, **now()**; they are recalculated every 30 seconds by the Zabbix history syncer process.  Triggers that reference trend functions **only** are evaluated once per  the smallest time period in the expression. See also [trend functions](/manual/appendix/functions/trends).
zh-cn	#### 计算时间  每次 Zabbix 服务器收到作为表达式一部分的新值时，都会重新计算触发器。 当接收到新值时，表达式中包含的每个函数都会重新计算（不仅仅是接收到新值的函数）。  此外，如果在表达式中使用了基于时间的函数，则每次接收到新值**和**每 30 秒重新计算一次触发器。  基于时间的函数是 **nodata()**、**date()**、**dayofmonth()**、**dayofweek()**、**time()**、**now() **; Zabbix 历史同步器进程每 30 秒重新计算一次。  引用趋势函数的触发器**only**在表达式中的每个最小时间段评估一次。 另见 [趋势函数](/manual/appendix/functions/trends)。

en-us	#### Certificate Revocation Lists (CRL)  If a certificate is compromised CA can revoke it by including in CRL. CRLs can be configured in server, proxy and agent configuration file using parameter `TLSCRLFile`. For example:      TLSCRLFile=/home/zabbix/zabbix_crl_file  where `zabbix_crl_file` may contain CRLs from several CAs and look like:      -----BEGIN X509 CRL-----     MIIB/DCB5QIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixkARkWA2Nv     ...     treZeUPjb7LSmZ3K2hpbZN7SoOZcAoHQ3GWd9npuctg=     -----END X509 CRL-----     -----BEGIN X509 CRL-----     MIIB+TCB4gIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQBGRYDY29t     ...     CAEebS2CND3ShBedZ8YSil59O6JvaDP61lR5lNs=     -----END X509 CRL-----  CRL file is loaded only on Zabbix start. CRL update requires restart.  ::: noteimportant  If Zabbix component is compiled with *OpenSSL* and CRLs are used then each top and intermediate level CA in certificate chains must have a corresponding CRL (it can be empty) in `TLSCRLFile`.  :::
zh-cn	#### 证书撤销列表(CRL) 如果证书被破坏，CA可以通过将其包含在CRL中来撤销它。 CRLs 可以通过“TLSCRLFile”参数在server、proxy和agent配置文件中配置。 例如:      TLSCRLFile=/home/zabbix/zabbix_crl_file  其中' zabbix_crl_file '可能包含来自多个CAs的CRLs，如下所示:      -----BEGIN X509 CRL-----     MIIB/DCB5QIBATANBgkqhkiG9w0BAQUFADCBgTETMBEGCgmSJomT8ixkARkWA2Nv     ...     treZeUPjb7LSmZ3K2hpbZN7SoOZcAoHQ3GWd9npuctg=     -----END X509 CRL-----     -----BEGIN X509 CRL-----     MIIB+TCB4gIBATANBgkqhkiG9w0BAQUFADB/MRMwEQYKCZImiZPyLGQBGRYDY29t     ...     CAEebS2CND3ShBedZ8YSil59O6JvaDP61lR5lNs=     -----END X509 CRL-----  CRL文件只在Zabbix启动时加载。 更新CRL需要重新启动。  ::: noteimportant  如果Zabbix组件是用*OpenSSL*编译的，并且使用了CRLs，那么证书链中的每个顶级和中级CA必须在' TLSCRLFile'中有一个对应的CRL(可以为空)。  :::

en-us	#### - Changes to AlmaLinux 8 configuration  The appliance is based on AlmaLinux 8. There are some changes applied to the base AlmaLinux configuration.
zh-cn	#### - 对 AlmaLinux 8 配置的更改  Appliance 基于 AlmaLinux 8。有一些配置与基本的 AlmaLinux 设置有一定区别。

en-us	#### Changing proxy setting  The hosts discovered by different proxies are always treated as different hosts. While this allows to perform discovery on matching IP ranges used by different subnets, changing proxy for an already monitored subnet is complicated because the proxy changes must be also applied to all discovered hosts.  For example the steps to replace proxy in a discovery rule:  1.  disable discovery rule 2.  sync proxy configuration 3.  replace the proxy in the discovery rule 4.  replace the proxy for all hosts discovered by this rule 5.  enable discovery rule
zh-cn	#### 更改proxy设置  通过不同的proxy发现的主机始终被视为不同的主机。即便这种操作可以对不同的子网执行自动发现，但是为一个已纳入监控的子网替换proxy也很复杂，因为proxy的变更会同时应用到所有已发现的主机上。  比如下面在发现规则中替换proxy的步骤：  1.  禁用规则 2.  同步proxy配置 3.  替换规则中的proxy 4.  替换此规则发现的所有主机的proxy 5.  启用规则

en-us	#### Chromium for Zabbix web service on Ubuntu 20  Though in most cases, Zabbix web service can run with Chromium, on Ubuntu 20.04 using Chromium causes the following error:      Cannot fetch data: chrome failed to start:cmd_run.go:994:     WARNING: cannot create user data directory: cannot create      "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied     Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details.  This error occurs because `/var/lib/zabbix` is used as a home directory of user 'zabbix'.
zh-cn	#### 在 Ubuntu 20 上使用 Chromium 运行 Zabbix web  尽管在大多数情况下，Zabbix Web 服务可以使用 Chromium 运行，但在 Ubuntu 20.04 上使用 Chromium 会导致以下错误：      Cannot fetch data: chrome failed to start:cmd_run.go:994:     WARNING: cannot create user data directory: cannot create "/var/lib/zabbix/snap/chromium/1564": mkdir /var/lib/zabbix: permission denied     Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details.  发生此错误是因为 `/var/lib/zabbix` 已经被用作用户 'zabbix' 的主目录。

en-us	#### Common agent items supported on Windows  |Item key|User group|<| |--------|----------|-| | |Recommended|Minimum technically acceptable (functionality is limited)| |agent.hostname|Guests|Guests| |agent.ping|Guests|Guests| |agent.variant|Guests|Guests| |agent.version|Guests|Guests| |log|Administrators|Guests| |log.count|Administrators|Guests| |logrt|Administrators|Guests| |logrt.count|Administrators|Guests| |net.dns|Guests|Guests| |net.dns.record|Guests|Guests| |net.if.discovery|Guests|Guests| |net.if.in|Guests|Guests| |net.if.out|Guests|Guests| |net.if.total|Guests|Guests| |net.tcp.listen|Guests|Guests| |net.tcp.port|Guests|Guests| |net.tcp.service|Guests|Guests| |net.tcp.service.perf|Guests|Guests| |net.udp.service|Guests|Guests| |net.udp.service.perf|Guests|Guests| |proc.num|Administrators|Guests| |system.cpu.discovery|Performance Monitor Users|Performance Monitor Users| |system.cpu.load|Performance Monitor Users|Performance Monitor Users| |system.cpu.num|Guests|Guests| |system.cpu.util|Performance Monitor Users|Performance Monitor Users| |system.hostname|Guests|Guests| |system.localtime|Guests|Guests| |system.run|Administrators|Guests| |system.sw.arch|Guests|Guests| |system.swap.size|Guests|Guests| |system.uname|Guests|Guests| |system.uptime|Performance Monitor Users|Performance Monitor Users| |vfs.dir.count|Administrators|Guests| |vfs.dir.get|Administrators|Guests| |vfs.dir.size|Administrators|Guests| |vfs.file.cksum|Administrators|Guests| |vfs.file.contents|Administrators|Guests| |vfs.file.exists|Administrators|Guests| |vfs.file.md5sum|Administrators|Guests| |vfs.file.regexp|Administrators|Guests| |vfs.file.regmatch|Administrators|Guests| |vfs.file.size|Administrators|Guests| |vfs.file.time|Administrators|Guests| |vfs.fs.discovery|Administrators|Guests| |vfs.fs.size|Administrators|Guests| |vm.memory.size|Guests|Guests| |web.page.get|Guests|Guests| |web.page.perf|Guests|Guests| |web.page.regexp|Guests|Guests| |zabbix.stats|Guests|Guests|
zh-cn	 #### Windows 上支持的常用 agent 监控项  |监控项 key|用户组|<| |--------|----------|-| | |推荐的|技术上可接受的最低权限组 (功能有限)| |agent.hostname|Guests|Guests| |agent.ping|Guests|Guests| |agent.variant|Guests|Guests| |agent.version|Guests|Guests| |log|Administrators|Guests| |log.count|Administrators|Guests| |logrt|Administrators|Guests| |logrt.count|Administrators|Guests| |net.dns|Guests|Guests| |net.dns.record|Guests|Guests| |net.if.discovery|Guests|Guests| |net.if.in|Guests|Guests| |net.if.out|Guests|Guests| |net.if.total|Guests|Guests| |net.tcp.listen|Guests|Guests| |net.tcp.port|Guests|Guests| |net.tcp.service|Guests|Guests| |net.tcp.service.perf|Guests|Guests| |net.udp.service|Guests|Guests| |net.udp.service.perf|Guests|Guests| |proc.num|Administrators|Guests| |system.cpu.discovery|Performance Monitor Users|Performance Monitor Users| |system.cpu.load|Performance Monitor Users|Performance Monitor Users| |system.cpu.num|Guests|Guests| |system.cpu.util|Performance Monitor Users|Performance Monitor Users| |system.hostname|Guests|Guests| |system.localtime|Guests|Guests| |system.run|Administrators|Guests| |system.sw.arch|Guests|Guests| |system.swap.size|Guests|Guests| |system.uname|Guests|Guests| |system.uptime|Performance Monitor Users|Performance Monitor Users| |vfs.dir.count|Administrators|Guests| |vfs.dir.get|Administrators|Guests| |vfs.dir.size|Administrators|Guests| |vfs.file.cksum|Administrators|Guests| |vfs.file.contents|Administrators|Guests| |vfs.file.exists|Administrators|Guests| |vfs.file.md5sum|Administrators|Guests| |vfs.file.regexp|Administrators|Guests| |vfs.file.regmatch|Administrators|Guests| |vfs.file.size|Administrators|Guests| |vfs.file.time|Administrators|Guests| |vfs.fs.discovery|Administrators|Guests| |vfs.fs.size|Administrators|Guests| |vm.memory.size|Guests|Guests| |web.page.get|Guests|Guests| |web.page.perf|Guests|Guests| |web.page.regexp|Guests|Guests| |zabbix.stats|Guests|Guests|

en-us	##### Common parameters  -   `/host/key` is a common mandatory first parameter for the functions     referencing the host item history -   `(sec|#num)<:time shift>` is a common second parameter for the     functions referencing the host item history, where:     -   **sec** - maximum [evaluation         period](/manual/config/triggers#evaluation_period) in seconds         (time [suffixes](/manual/appendix/suffixes) can be used), or     -   **\#num** - maximum [evaluation         range](/manual/config/triggers#evaluation_period) in latest         collected values (if preceded by a hash mark)     -   **time shift** (optional) allows to move the evaluation point         back in time. See [more         details](/manual/config/triggers/expression#time_shift) on         specifying time shift.
zh-cn	##### 常用参数  -   `/host/key` 是引用主机监控项历史记录函数的常用强制性首选参数 -   `(sec|#num)<:time shift>` 是引用主机监控项历史记录函数的常用强制性次选参数 ，其中：     -   **sec** - 以秒为单位的最大 [评估周期](/manual/config/triggers#evaluation_period)  (可以使用时间 [后缀](/manual/appendix/suffixes) )，或者     -   **\#num** - 最新收集值最大 [评估范围](/manual/config/triggers#evaluation_period)(如果前面有井号)     -   **time shift** (可选) 允许将评估点及时移回。参阅有关指定时间偏移 [更多详细内容](/manual/config/triggers/expression#time_shift)

en-us	##### Common use cases of global and host macros  -   use a global macro in several locations; then change the macro value     and apply configuration changes to all locations with one click -   take advantage of templates with host-specific attributes:     passwords, port numbers, file names, regular expressions, etc.
zh-cn	##### 全局和宿主宏的常见用例  - 在多个位置使用全局宏；然后更改宏值并一键将配置更改应用于所有位置 - 利用具有主机特定属性的模板：密码、端口号、文件名、正则表达式等。

en-us	#### Compiling OpenSSL  The following steps will help you to compile OpenSSL from sources on MS Windows 10 (64-bit).  1.  For compiling OpenSSL you will need on Windows machine:     1.  C compiler (e.g. VS 2017 RC),     2.  NASM (<https://www.nasm.us/>),     3.  Perl (e.g. Strawberry Perl from <http://strawberryperl.com/>),     4.  Perl module Text::Template (cpan Text::Template). 2.  Get OpenSSL sources from <https://www.openssl.org/>. OpenSSL 1.1.1     is used here. 3.  Unpack OpenSSL sources, for example, in E:\\openssl-1.1.1. 4.  Open a commandline window e.g. the x64 Native Tools Command Prompt     for VS 2017 RC. 5.  Go to the OpenSSL source directory, e.g. E:\\openssl-1.1.1.     1.  Verify that NASM can be found:`e:\openssl-1.1.1> nasm --version         NASM version 2.13.01 compiled on May  1 2017         ` 6.  Configure OpenSSL, for     example:`e:\openssl-1.1.1> perl E:\openssl-1.1.1\Configure VC-WIN64A no-shared no-capieng no-srp no-gost no-dgram no-dtls1-method no-dtls1_2-method  --api=1.1.0 --prefix=C:\OpenSSL-Win64-111-static --openssldir=C:\OpenSSL-Win64-111-static     `     -   Note the option 'no-shared': if 'no-shared' is used then the         OpenSSL static libraries libcrypto.lib and libssl.lib will be         'self-sufficient' and resulting Zabbix binaries will include         OpenSSL in themselves, no need for external OpenSSL DLLs.         Advantage: Zabbix binaries can be copied to other Windows         machines without OpenSSL libraries. Disadvantage: when a new         OpenSSL bugfix version is released, Zabbix agent needs to         recompiled and reinstalled.     -   If 'no-shared' is not used, then the static libraries         libcrypto.lib and libssl.lib will be using OpenSSL DLLs at         runtime. Advantage: when a new OpenSSL bugfix version is         released, probably you can upgrade only OpenSSL DLLs, without         recompiling Zabbix agent. Disadvantage: copying Zabbix agent to         another machine requires copying OpenSSL DLLs, too. 7.  Compile OpenSSL, run tests, install:`e:\openssl-1.1.1> nmake     e:\openssl-1.1.1> nmake test     ...     All tests successful.     Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr +  0.61 sys =  1.28 CPU)     Result: PASS     e:\openssl-1.1.1> nmake install_sw     `'install\_sw' installs only software components (i.e. libraries,     header files, but no documentation). If you want everything, use     "nmake install".
zh-cn	 #### 编译OpenSSL  接下来的步骤将助你在MS Windows 10（64位）的源中编译OpenSSL。  1.  编译OpenSSL你需要在Windows机器上安装：     1.  C compiler (e.g. VS 2017 RC),     2.  NASM (<https://www.nasm.us/>),     3.  Perl (e.g. Strawberry Perl from <http://strawberryperl.com/>),     4.  Perl module Text::Template (cpan Text::Template). 2.  获取 OpenSSL 源代码 <https://www.openssl.org/>。这里用OpenSSL 1.1.1 版本。 3.  解压 OpenSSL 源，例如，解压在 E:\\openssl-1.1.1。 4.  打开命令行窗口。例如，VS 2017 RC的 x64 原生工具命令提示符。 5.  至 OpenSSL 源目录, 例如，E:\\openssl-1.1.1。     1.  验证 NASM 能被找到：`e:\openssl-1.1.1> nasm --version         NASM version 2.13.01 compiled on May  1 2017         ` 6.  配置OpenSSL，例如：`e:\openssl-1.1.1> perl E:\openssl-1.1.1\Configure VC-WIN64A no-shared no-capieng no-srp no-gost no-dgram no-dtls1-method no-dtls1_2-method  --api=1.1.0 --prefix=C:\OpenSSL-Win64-111-static --openssldir=C:\OpenSSL-Win64-111-static     `     -   请注意选项 'no-shared'：如果使用 'no-shared' 那么OpenSSL静态库 libcrypto.lib和libssl.lib 将         '自给自足'，生成的Zabbix二进制文件本身将包含OpenSSL ，不需要外部的OpenSSL DLLs。         优点： Zabbix二进制文件可以复制到其他没有OpenSSL库的Windows机器上。          缺点：当新的OpenSSL bugfix 版本发布时，需要重新编译并安装Zabbix agent。     -   如果不使用'no-shared'，那么静态库 libcrypto.lib和 libssl.lib 会在运行时使用OpenSSL DLLs 。     - 优点：当新的OpenSSL bugfix版本发布时，你可能只需要升级OpenSSL DLLs不用重新编译Zabbix agent。     - 缺点：复制Zabbix agent到另一个机器时，需要同时复制OpenSSL DLLs。 7.  编译OpenSSL，运行测试，安装：`e:\openssl-1.1.1> nmake     e:\openssl-1.1.1> nmake test     ...     All tests successful.     Files=152, Tests=1152, 501 wallclock secs ( 0.67 usr +  0.61 sys =  1.28 CPU)     Result: PASS     e:\openssl-1.1.1> nmake install_sw     `'install\_sw' 仅安装软件组件（例如 库，头文件，但不安装文档）。如果你希望安装所有的文件，请用 "nmake install"。

en-us	#### Compiling Zabbix agent on HP-UX  If you install the PCRE library from a popular HP-UX package site <http://hpux.connect.org.uk>, for example from file `pcre-8.42-ia64_64-11.31.depot`, you get only the 64-bit version of the library installed in the /usr/local/lib/hpux64 directory.  In this case, for successful agent compilation customized options need to be used for the "configure" script, e.g.:      CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64
zh-cn	#### 在 HP-UX 上编译 Zabbix agent  如果从常规的 HP-UX 软件包站点 http://hpux.connect.org.uk 安装 PCRE 库（例如 `pcre-8.42-ia64_64-11.31.depot` 文件），你将仅获得安装在 /usr/local/lib/hpux64 路径下的 64 位版本的库。  在这种情况下，为了成功编译 agent，需要为“配置”脚本使用自定义选项，例如：      CFLAGS="+DD64" ./configure --enable-agent --with-libpcre-include=/usr/local/include --with-libpcre-lib=/usr/local/lib/hpux64

en-us	#### Configurable fields  Actual command(s) to be executed must be placed in the **Executed script** field in the item configuration.\ Multiple commands can be executed one after another by placing them on a new line. In this case returned value also will be formatted as multilined.  Supported characters that the shell prompt can end with:  -   $ -   \# -   \> -   %  ::: noteclassic A telnet prompt line which ended with one of these characters will be removed from the returned value, but only for the first command in the commands list, i.e. only at a start of the telnet session. :::  |Key|Description| |--|------| |**telnet.run\[<unique short description>,<ip>,<port>,<encoding>\]**|Run a command on a remote device using telnet connection||  ::: noteimportant If a telnet check returns a value with non-ASCII characters and in non-UTF8 encoding then the *<encoding>* parameter of the key should be properly specified. See [encoding of returned values](/manual/appendix/items/encoding_of_values) page for more details. :::
zh-cn	#### 可配置字段  要执行的实际命令必须放在监控项配置中的 **执行的脚本**  字段中。如果要执行多条命令，一行写一条，命令将逐条执行。这种情况下，返回值也将为多行显示。  支持的 shell 提示符结尾的字符：  - $ - \# - > - %  ::: noteclassic 以上结束符的telnet提示行将从返回值中删除，但仅针对命令列表中的第一个命令，即仅在telnet会话开始处。 :::  |键值|描述| |---|-----------| |**telnet.run\[<unique short description>,<ip>,<port>,<encoding>\]**|使用 telnet 连接在远程设备上运行命令|<|  ::: noteimportant 如果telnet检查返回一个非ascii字符和非utf8编码的值,那应该正确的指定<encoding>参数。有关详细信息，请参阅[编码返回值](/manual/appendix/items/encoding_of_values) 页面。 :::

en-us	#### Configuration
zh-cn	 #### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	#### Configuration
zh-cn	#### 配置

en-us	 ### Configuration  1. Create disabled Script item on the main VMware host (where the **eventlog[]** item is present) with the following parameters:  ![](../../../../assets/en/manual/appendix/items/perf_counter_item.png)  - *Name*:  VMware metrics - *Type*: Script - *Key*: vmware.metrics - *Type of information*: Text - *Script*: copy and paste the [script](#script) provided below - *Timeout*: 10 - *History storage period*: Do not keep history - *Enabled*: unmarked   #### Script      try {         Zabbix.log(4, 'vmware metrics script');          var result, resp,         req = new HttpRequest();         req.addHeader('Content-Type: application/xml');         req.addHeader('SOAPAction: "urn:vim25/6.0"');          login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\         <soapenv:Header/>\         <soapenv:Body>\             <urn:Login>\                 <urn:_this type="SessionManager">SessionManager</urn:_this>\                 <urn:userName>{$VMWARE.USERNAME}</urn:userName>\                 <urn:password>{$VMWARE.PASSWORD}</urn:password>\             </urn:Login>\         </soapenv:Body>\     </soapenv:Envelope>'         resp = req.post("{$VMWARE.URL}", login);         if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }          query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\     <soapenv:Header/>\         <soapenv:Body>\             <urn:RetrieveProperties>\                 <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\                 <urn:specSet>\                     <urn:propSet>\                        <urn:type>PerformanceManager</urn:type>\                        <urn:pathSet>perfCounter</urn:pathSet>\                     </urn:propSet>\                     <urn:objectSet>\                        <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\                     </urn:objectSet>\                 </urn:specSet>\             </urn:RetrieveProperties>\         </soapenv:Body>\     </soapenv:Envelope>'         resp = req.post("{$VMWARE.URL}", query);         if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }         Zabbix.log(4, 'vmware metrics=' + resp);         result = resp;          logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\         <soapenv:Header/>\         <soapenv:Body>\             <urn:Logout>\                 <urn:_this type="SessionManager">SessionManager</urn:_this>\             </urn:Logout>\         </soapenv:Body>\     </soapenv:Envelope>'          resp = req.post("{$VMWARE.URL}",logout);                  if (req.getStatus() != 200) {             throw 'Response code: '+req.getStatus();         }      } catch (error) {         Zabbix.log(4, 'vmware call failed : '+error);         result = {};     }      return result;   Once the item is configured, press *Test* button, then press *Get value*.   ![](../../../../assets/en/manual/appendix/items/perf_counter_item1.png){width=600}  Copy received XML to any XML formatter and find the desired metric.  An example of XML for one metric:       <PerfCounterInfo xsi:type="PerfCounterInfo">         <key>6</key>         <nameInfo>             <label>Usage in MHz</label>             <summary>CPU usage in megahertz during the interval</summary>             <key>usagemhz</key>         </nameInfo>         <groupInfo>             <label>CPU</label>             <summary>CPU</summary>             <key>cpu</key>         </groupInfo>         <unitInfo>             <label>MHz</label>             <summary>Megahertz</summary>             <key>megaHertz</key>         </unitInfo>         <rollupType>average</rollupType>         <statsType>rate</statsType>         <level>1</level>         <perDeviceLevel>3</perDeviceLevel>     </PerfCounterInfo>  Use XPath to extract the counter path from received XML. For the example above, the XPath will be:  |field |xPath | value | |--|--|--| |group | //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average |  Resulting performance counter path in this case is: `cpu/usagemhz[average]`
zh-cn	### 配置  1. 使用以下参数在主要的VMware主机（存在**eventlog[]**监控项的地方）上创建禁用的脚本监控项：  ![](../../../../assets/en/manual/appendix/items/perf_counter_item.png)  - *Name*: · VMware 指标 - *Type*: 脚本 - *Key*: vmware.metrics - *Type of information*: 文本 - *Script*: 复制并粘贴下面提供的[脚本](#script) - *Timeout*: 10 - *History storage period*: 不保留历史数据 - *Enabled*: 未标记    ### 脚本    · try {  · Zabbix.log(4, 'vmware metrics script');   · var result, resp,  · req = new HttpRequest();  · req.addHeader('Content-Type: application/xml');  · req.addHeader('SOAPAction: "urn:vim25/6.0"');   · login = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:Login>\  · <urn:_this type="SessionManager">SessionManager</urn:_this>\  · <urn:userName>{$VMWARE.USERNAME}</urn:userName>\  · <urn:password>{$VMWARE.PASSWORD}</urn:password>\  · </urn:Login>\  · </soapenv:Body>\  · </soapenv:Envelope>'  · resp = req.post("{$VMWARE.URL}", login);  · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }   · query = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:RetrieveProperties>\  · <urn:_this type="PropertyCollector">propertyCollector</urn:_this>\  · <urn:specSet>\  · <urn:propSet>\  · <urn:type>PerformanceManager</urn:type>\  · <urn:pathSet>perfCounter</urn:pathSet>\  · </urn:propSet>\  · <urn:objectSet>\  · <urn:obj type="PerformanceManager">PerfMgr</urn:obj>\  · </urn:objectSet>\  · </urn:specSet>\  · </urn:RetrieveProperties>\  · </soapenv:Body>\  · </soapenv:Envelope>'  · resp = req.post("{$VMWARE.URL}", query);  · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }  · Zabbix.log(4, 'vmware metrics=' + resp);  · result = resp;   · logout = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:vim25">\  · <soapenv:Header/>\  · <soapenv:Body>\  · <urn:Logout>\  · <urn:_this type="SessionManager">SessionManager</urn:_this>\  · </urn:Logout>\  · </soapenv:Body>\  · </soapenv:Envelope>'   · resp = req.post("{$VMWARE.URL}",logout); ·   · if (req.getStatus() != 200) {  · throw 'Response code: '+req.getStatus();  · }   · } catch (error) {  · Zabbix.log(4, 'vmware call failed : '+error);  · result = {};  · }    · 返回结果;   配置监控项后，点击 *Test* 按钮，然后点击 *Get value*。  ![](../../../../assets/en/manual/appendix/items/perf_counter_item1.png){width=600}  将收到的 XML 复制到任何 XML 格式化程序并找到所需的指标。  一个指标的 XML 示例：   · <PerfCounterInfo xsi:type="PerfCounterInfo">  · <key>6</key>  · <nameInfo>  · <label>Usage in MHz</label>  · <summary>CPU usage in megahertz during the interval</summary>  · <key>usagemhz</key>  · </nameInfo>  · <groupInfo>  · <label>CPU</label>  · <summary>CPU</summary>  · <key>cpu</key>  · </groupInfo>  · <unitInfo>  · <label>MHz</label>  · <summary>Megahertz</summary>  · <key>megaHertz</key>  · </unitInfo>  · <rollupType>average</rollupType>  · <statsType>rate</statsType>  · <level>1</level>  · <perDeviceLevel>3</perDeviceLevel>  · </PerfCounterInfo>   使用 XPath 从收到的 XML 中提取计数器路径。对于上面的示例，XPath 将是：  |字段 |xPath |值 | |--|--|--| |group | //groupInfo[../key=6]/key | cpu | |counter |//nameInfo[../key=6]/key |usagemhz | |rollup |//rollupType[../key=6] |average |  在这个例子中性能计数器路径是：`cpu/usagemhz[average]`

en-us	# configuration.export
zh-cn	# configuration.export

en-us	#### Configuration file  For details on configuring Zabbix agent see the configuration file options for [zabbix\_agentd](/manual/appendix/config/zabbix_agentd) or [Windows agent](/manual/appendix/config/zabbix_agentd_win).
zh-cn	#### 配置文件  有关配置 Zabbix agent 的详细信息，请查阅  [zabbix_agentd](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/config/zabbix_agentd)  或  [Windows agent](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/config/zabbix_agentd_win)  章节。

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_proxy) options for details on configuring zabbix\_proxy.
zh-cn	##### 配置文件  另请参考 [configuration file](/manual/appendix/config/zabbix_proxy) 配置zabbix\_proxy的详细信息。

en-us	##### Configuration file  See the [configuration file](/manual/appendix/config/zabbix_server) options for details on configuring zabbix\_server.
zh-cn	##### 配置文件  有关配置 Zabbix server 的详细信息，请查阅 [配置文件](/manual/appendix/config/zabbix_server) 章节。

en-us	#### Configuration  Global notifications can be enabled per user in the *Messaging* tab of [profile configuration](/manual/web_interface/user_profile).  ![profile\_c.png](../../../../assets/en/manual/web_interface/profile_c.png)  |Parameter|Description| |--|--------| |*Frontend messaging*|Mark the checkbox to enable global notifications.| |*Message timeout*|You can set for how long the message will be displayed. By default, messages will stay on screen for 60 seconds.<br>[Time suffixes](/manual/appendix/suffixes) are supported, e.g. 30s, 5m, 2h, 1d.| |*Play sound*|You can set how long the sound will be played.<br>**Once** - sound is played once and fully.<br>**10 seconds** - sound is repeated for 10 seconds.<br>**Message timeout** - sound is repeated while the message is visible.| |*Trigger severity*|You can set the trigger severities that global notifications and sounds will be activated for. You can also select the sounds appropriate for various severities.<br>If no severity is marked then no messages will be displayed at all.<br>Also, recovery messages will only be displayed for those severities that are marked. So if you mark *Recovery* and *Disaster*, global notifications will be displayed for the problems and the recoveries of disaster severity triggers.| |*Show suppressed problems*|Mark the checkbox to display notifications for problems which would otherwise be suppressed (not shown) because of host maintenance.|
zh-cn	#### 配置  可以在 [用户配置设置](/manual/web_interface/user_profile) 的 *消息* 选项卡中为每个用户启用全局通知。  ![profile\_c.png](../../../../assets/en/manual/web_interface/profile_c.png)  |参数|说明| |---------|---------| |*前端消息传递*|标记复选框以启用全局通知。| |*消息超时*|您可以设置消息显示的时长。默认情况下，消息将在屏幕上停留 60 秒。<br>支持[时间后缀](/manual/appendix/suffixes)，例如30s，5m，2h，1d。| |*播放声音*|您可以设置声音的播放时间。<br>**一次** - 声音播放一次并完全播放。<br>**10 秒** - 声音重复 10 秒。 <br>**消息超时** - 消息可见时重复声音。| |*触发严重性*|您可以设置将激活全局通知和声音的触发严重性。您还可以选择适合各种严重性的声音。<br>如果未标记严重性，则根本不会显示任何消息。<br>此外，仅针对已标记的严重性显示恢复消息。因此，如果您标记 *Recovery* 和 *Disaster*，将显示全局通知以显示问题和灾难严重性触发器的恢复。| |*显示抑制的问题*|标记复选框以显示由于主机维护而被抑制（未显示）的问题的通知。|

en-us	# configuration.import
zh-cn	# configuration.import

en-us	# configuration.importcompare
zh-cn	# configuration.importcompare

en-us	#### Configuration  ODBC configuration is done by editing **odbcinst.ini** and **odbc.ini** files. These configuration files can be found in */etc* folder. The file **odbcinst.ini** may be missing and in this case it is necessary to create it manually.  **odbcinst.ini**      [mysql]     Description = General ODBC for MySQL     Driver      = /usr/lib64/libmyodbc5.so     Setup       = /usr/lib64/libodbcmyS.so      FileUsage   = 1  Please consider the following examples of **odbc.ini** configuration parameters.  -   An example with a connection through an IP:  ```{=html} <!-- --> ```     [TEST_MYSQL]                                                          Description = MySQL database 1                                        Driver  = mysql                                                       Port = 3306                                                           Server = 127.0.0.1  -   An example with a connection through an IP and with the use of     credentials. A Zabbix database is used by default:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED]                            Description = MySQL database 2                      Driver  = mysql                                     User = root                                         Port = 3306                                         Password = zabbix                                Database = zabbix                                  Server = 127.0.0.1                               -   An example with a connection through a socket and with the use of     credentials. A Zabbix database is used by default:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED_SOCK]                       Description = MySQL database 3                      Driver  = mysql                                     User = root                                         Password = zabbix                                Socket = /var/run/mysqld/mysqld.sock                Database = zabbix  All other possible configuration parameter options can be found in [MySQL official documentation](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html) web page.
zh-cn	### 配置  通过编辑**odbcinstn.ini**和**odbcst.ini**文件来完成ODBC配置。这些配置文件可以在*/etc*文件夹下找到。可能缺少**odbcinstn .ini**文件，在这种情况下，需要手动创建它。  **odbcinst.ini**      [mysql]     Description = General ODBC for MySQL     Driver      = /usr/lib64/libmyodbc5.so     Setup       = /usr/lib64/libodbcmyS.so      FileUsage   = 1   请考虑以下 **odbc.ini** 配置示例参数。  - 通过 IP 连接的示例：  ```{=html} <!-- --> ```     [TEST_MYSQL]                                                          Description = MySQL database 1     Driver  = mysql      Port = 3306      Server = 127.0.0.1  - 通过 IP 连接并使用凭据，默认使用 Zabbix 数据库:  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED]                            Description = MySQL database 2                      Driver  = mysql                                     User = root                                         Port = 3306                                         Password = zabbix                                Database = zabbix                                  Server = 127.0.0.1    - 通过socket连接并使用凭据，默认使用 Zabbix 数据库：  ```{=html} <!-- --> ```     [TEST_MYSQL_FILLED_CRED_SOCK]                       Description = MySQL database 3                      Driver  = mysql                                     User = root                                         Password = zabbix                                Socket = /var/run/mysqld/mysqld.sock                Database = zabbix  其他配置和参数都可以参考[MySQL官方文档](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html)

en-us	#### Configuration  ODBC configuration is done by editing the **odbcinst.ini** and **odbc.ini** files. These configuration files can be found in */etc* folder. The file **odbcinst.ini** may be missing and in this case it is necessary to create it manually.  Please consider the following examples:  **odbcinst.ini**      $ vi /etc/odbcinst.ini     [FreeTDS]     Driver = /usr/lib64/libtdsodbc.so.0  **odbc.ini**      $ vi /etc/odbc.ini     [sql1]     Driver = FreeTDS     Server = <SQL server 1 IP>     PORT = 1433     TDS_Version = 8.0
zh-cn	#### 配置  通过编辑 **odbcinst.ini** 和 **odbc.ini** 文件来完成ODBC的配置。这些配置文件可以在 */etc* 文件夹中找到。**odbcinst.ini** 文件可能不存在，这时我们需要手动来创建它。  请考虑以下  **odbc.ini**  配置参数的示例：  **odbcinst.ini**      $ vi /etc/odbcinst.ini     [FreeTDS]     Driver = /usr/lib64/libtdsodbc.so.0  **odbc.ini**      $ vi /etc/odbc.ini     [sql1]     Driver = FreeTDS     Server = <SQL server 1 IP>     PORT = 1433     TDS_Version = 8.0

en-us	### Configuration  Once you have [installed](/manual/installation/install) and [configured](/manual/appendix/config/zabbix_proxy) a proxy, it is time to configure it in the Zabbix frontend.
zh-cn	### 配置  如果你 [安装](/manual/installation/install) 和[配置](/manual/appendix/config/zabbix_proxy) 一个proxy , 下一步就是Zabbix前端配置。

en-us	#### Configuration  Overall, the process of setting up the notification should feel familiar to those who have set up alerts in Zabbix before.
zh-cn	#### 配置  总的来说，以前在Zabbix中设置过警报的同学应该熟悉设置通知的过程。

en-us	 #### Configuration  Providing you have the HTTP master item configured, you need to create a [dependent item](/manual/config/items/itemtypes/dependent_items) that uses a Prometheus preprocessing step:  -   Enter general dependent item parameters in the configuration form -   Go to the Preprocessing tab -   Select a Prometheus preprocessing option (*Prometheus pattern* or     *Prometheus to JSON*)  ![](../../../../../assets/en/manual/config/items/itemtypes/prometheus_item.png)  The following parameters are specific to the *Prometheus pattern* preprocessing option:  |Parameter|Description|Examples| |--|------|------| |*Pattern*|To define the required data pattern you may use a query language that is similar to Prometheus query language (see [comparison table](#query-language-comparison)), e.g.:<br><metric name> - select by metric name<br>{\_\_name\_\_="<metric name>"} - select by metric name<br>{\_\_name\_\_=\~"<regex>"} - select by metric name matching a regular expression<br>{<label name>="<label value>",...} - select by label name<br>{<label name>=\~"<regex>",...} - select by label name matching a regular expression<br>{\_\_name\_\_=\~".\*"}==<value> - select by metric value<br>Or a combination of the above:<br><metric name>{<label1 name>="<label1 value>",<label2 name>=\~"<regex>",...}==<value><br><br>Label value can be any sequence of UTF-8 characters, but the backslash, double-quote and line feed characters have to be escaped as `\\`, `\"` and `\n` respectively; other characters shall not be escaped.|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Result processing*|Specify whether to return the value, the label or apply the appropriate function (if the pattern matches several lines and the result needs to be aggregated):<br>**value** - return metric value (error if multiple lines matched)<br>**label** - return value of the label specified in the *Label* field (error if multiple metrics are matched)<br>**sum** - return the sum of values<br>**min** - return the minimum value<br>**max** - return the maximum value<br>**avg** - return the average value<br>**count** - return the count of values<br>This field is only available for the *Prometheus pattern* option. |See also examples of using parameters below.| |*Output*|Define label name (optional). In this case the value corresponding to the label name is returned.<br>This field is only available for the *Prometheus pattern* option, if 'Label' is selected in the *Result processing* field.| |  **Examples of using parameters**  1. The most common use case is to return the **value**. To return  the value of `/var/db` from:  > `node_disk_usage_bytes{path="/var/cache"} 2.1766144e+09`<br> > `node_disk_usage_bytes{path="/var/db"} 20480`<br> > `node_disk_usage_bytes{path="/var/dpkg"} 8192`<br> > `node_disk_usage_bytes{path="/var/empty"} 4096`  use the following parameters:  * *Pattern* - `node_disk_usage_bytes{path="/var/db"}` * *Result processing* - select 'value'  2. You may also be interested in the **average** value of all  `node_disk_usage_bytes` parameters:  * *Pattern* - `node_disk_usage_bytes` * *Result processing* - select 'avg'  3. While Prometheus supports only numerical data, it is popular to use a  workaround that allows to return the relevant textual description as well.  This can be accomplished with a filter and specifying the label. So, to  return the value of the 'color' label from  > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="green"} 1`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="red"} 0`<br> > `elasticsearch_cluster_health_status{cluster="elasticsearch",color="yellow"} 0`  use the following parameters:  * *Pattern* - `elasticsearch_cluster_health_status {cluster="elasticsearch"} == 1` * *Result processing* - select 'label' * *Label* - specify 'color'  The filter (based on the numeric value '1') will match the appropriate row, while the label will  return the health status description (currently 'green'; but potentially also 'red' or 'yellow').
zh-cn	#### 配置  已经事先正确配置了 HTTP代理类型的主要监控项，你需要创建一个 [相关监控项](/manual/config/items/itemtypes/dependent_items) 来应用Prometheus 预处理步骤：  - 在配置表单中填入一般从属监控项的参数 - 前往预处理选项卡 - 选择一个 **Prometheus** 预处理选项（*Prometheus正则匹配* or *Prometheus转JSON*）  ![](../../../../../assets/en/manual/config/items/itemtypes/prometheus_item.png)  以下参数特定于 *Prometheus正则匹配* 预处理选项：  |参数|描述|示例| |---------|-----------|--------| |*Pattern*|要定义所需数据的正则匹配规则，可以使用与PromQL（Prometheus 查询语言）十分类似的检索语言 (详见 [对比表]](#query_language_comparison)), 举个例子：<br><metric name> - 指定指标名称<br>{\_\_name\_\_=\~"<regex>"} - 根据正则表达式，匹配指标名称<br>{<label name>="<label value>",...} - 指定标签名称<br>{<label name>=\~"<regex>",...} - 根据正则表达式，匹配标签名称<br>{\_\_name\_\_=\~".\*"}==<value> - 指定指标值<br>或者将以上的条件任意组合：<br><metric name>{<label1 name>="<label1 value>",<label2 name>=\~"<regex>",...}==<value><br><br>标签名称可以是任何UTF-8字符的序列，但对于反斜杠、双引号和换行符必须使用转义，就像 `\\`，`\"`， `\n`；其他字符不应被转义。|*wmi\_os\_physical\_memory\_free\_bytes*<br>*cpu\_usage\_system{cpu="cpu-total"}*<br>*cpu\_usage\_system{cpu=\~".\*"}*<br>*cpu\_usage\_system{cpu="cpu-total",host=\~".\*"}*<br>*wmi\_service\_state{name="dhcp"}==1*<br>*wmi\_os\_timezone{timezone=\~".\*"}==1*| |*Result processing*| 定义如何返回处理结果，提供了**值**，**标签** 或应用适当的函数（如正则匹配的到了多行结果，需要对这些结果进行简单聚合）:<br>**值** - 返回指标的值（当匹配到多行记录时，会引发错误）<br>**标签** - 在*标签*字段中指定的标签返回值（当匹配到多个指标时，会引发错误）<br>**总和** - 返回值的总和<br>**最小值** - 返回最小值<br>**max** - 返回最大值<br>**平均值** - 返回平均值<br>**计数** - 返回值的计数<br>此参数字段仅适用于**Prometheus正则匹配**预处理步骤。 | 实际用例见表后。 | |*Output*|定义标签名称（可选）。 在这种情况下，返回与标签名称对应的值。<br>如果在 *Result processing* 字段中选择了“Label”，则此字段仅适用于 *Prometheus pattern* 选项。| |

en-us	#### Configuration  Tags can be entered in a dedicated tab, for example, in trigger configuration:  ![](../../../assets/en/manual/config/tags_trigger.png)
zh-cn	#### 配置  可以在专用选项卡中输入标签，例如在触发器配置：  ![](../../../assets/en/manual/config/tags_trigger.png)

en-us	#### Configuration  The low-level discovery rule should be created as a [dependent item](/manual/config/items/itemtypes/dependent_items) to the HTTP master item that collects Prometheus data.
zh-cn	#### 配置  利用低级别自动发现规则创建一个 [依赖型监控项](/manual/config/items/itemtypes/dependent_items) ，附属于采集Prometheus数据的HTTP主监控项。

en-us	#### Configuration  To assign triggers as link indicators, do the following:  -   select a map element -   click on *Edit* in the *Links* section for the appropriate link -   click on *Add* in the *Link indicators* block and select one or more     triggers  ![](../../../../../assets/en/manual/config/visualization/map_triggers.png){width="600"}  All mandatory input fields are marked with a red asterisk.  Added triggers can be seen in the *Link indicators* list.  You can set the link type and color for each trigger directly from the list. When done, click on *Apply*, close the form and click on *Update* to save the map changes.
zh-cn	####  配置  要将触发器分配为链接指示器，请执行以下操作：  - 选择地图元素 - 单击 *链接* 部分中的 *编辑* 以获取相应的链接 - 点击*链接指标*块中的*添加*并选择一个或多个触发器  ![](../../../../../assets/en/manual/config/visualization/map_triggers.png){width="600"}  所有必填字段都标有红色星号。  在*链接指标*列表中可以看到添加的触发器。  你可以直接从列表中设置每个触发器的链接类型和颜色。完成后，点击 *应用*，关闭表格并点击 *更新*保存地图更改。

en-us	#### Configuration  To configure a CSV to JSON preprocessing step:  -   Go to the Preprocessing tab in     [item](/manual/config/items/preprocessing)/[discovery     rule](/manual/discovery/low_level_discovery#preprocessing)     configuration -   Click on *Add* -   Select the *CSV to JSON* option  ![](../../../../../assets/en/manual/appendix/csv_to_json_params.png){width="600"}  The first parameter allows to set a custom delimiter. Note that if the first line of CSV input starts with "Sep=" and is followed by a single UTF-8 character then that character will be used as the delimiter in case the first parameter is not set. If the first parameter is not set and a delimiter is not retrieved from the "Sep=" line, then a comma is used as a separator.  The second optional parameter allows to set a quotation symbol.  If the *With header row* checkbox is marked, the header line values will be interpreted as column names (see [Header processing](#csv_header_processing) for more information).  If the *Custom on fail* checkbox is marked, the item will not become unsupported in case of a failed preprocessing step. Additionally custom error handling options may be set: discard the value, set a specified value or set a specified error message.
zh-cn	#### 配置  配置CSV到JSON的预处理步骤:  -   转到预处理选项 [监控项](/manual/config/items/preprocessing)/[自动发现规则](/manual/discovery/low_level_discovery#预处理) 配置 -   点击 *添加* -   选择 *CSV to JSON* 选项  ![](../../../../../assets/en/manual/appendix/csv_to_json_params.png){width="600"}  第一个参数允许设置自定义分隔符。请注意，如果CSV输入的第一行以“Sep=”开头，后跟一个UTF-8字符，则在未设置第一个参数的情况下，该字符将用作分隔符。如果未设置第一个参数，且未从“Sep=”行检索到分隔符，则使用逗号作为分隔符。  第二个可选参数允许设置引号符号。  如果勾选 *With header row* ，标题行值将被解释为列名 (详见[标题预处理](#csv_header_processing) 了解更多信息)。  如果勾选 *Custom on fail* ，那么在预处理步骤失败的情况下，该监控项项将不会不受支持。另外，可以设置自定义错误处理选项:丢弃该值，设置指定值或设置指定的错误消息。

en-us	#### Configuration  To create an ad-hoc graph, do the following:  -   Go to *Monitoring* → *Latest data* -   Use filter to display items that you want -   Mark checkboxes of the items you want to graph -   Click on *Display stacked graph* or *Display graph* buttons  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graphs.png){width="600"}  Your graph is created instantly:  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graph.png){width="600"}  Note that to avoid displaying too many lines in the graph, only the average value for each item is displayed (min/max value lines are not displayed). Triggers and trigger information is not displayed in the graph.  In the created graph window you have the [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) available and the possibility to switch from the "normal" line graph to a stacked one (and back).  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_stacked.png){width="600"}
zh-cn	####  配置  要创建Ad-hoc图表，请执行以下操作：  - 转到*监控* → *最新数据* - 使用过滤器显示您想要的监控项 - 标记要绘制的监控项的复选框 - 点击*显示堆叠数据图*或*显示数据图*按钮  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graphs.png){width="600"}  您的图表会立即创建：  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_graph.png){width="600"}  请注意，为避免在图表中显示过多的线，只会显示每个监控项的平均值（不显示最小值/最大值行显示）。触发器和触发器信息不显示在图形。  在创建的图形窗口中，您可以使用[时间段选择器](/manual/config/visualization/graphs/simple#time_period_selector)，也可以从“正常”折线图切换到堆叠图（可来回切换）。  ![](../../../../../assets/en/manual/config/visualization/ad_hoc_stacked.png){width="600"}

en-us	#### Configuration  To ensure proper communication between all elements involved make sure server configuration file and frontend configuration file parameters are properly configured.
zh-cn	#### 配置 为确保所涉及的所有元素之间的正确通信，请确保服务器配置文件和前端配置文件参数正确。

en-us	#### Configuration  We assume that TimescaleDB extension has been already installed on the database server (see [installation instructions](https://docs.timescale.com/latest/getting-started/installation)).  TimescaleDB extension must also be enabled for the specific DB by executing:      echo "CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;" | sudo -u postgres psql zabbix  Running this command requires database administrator privileges.  ::: noteclassic If you use a database schema other than 'public' you need to add a SCHEMA clause to the command above. E.g.:\ `echo "CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;" | sudo -u postgres psql zabbix` :::  Then run the `timescaledb.sql` script located in database/postgresql. For new installations the script must be run after the regular PostgreSQL database has been created with initial schema/data (see [database creation](/manual/appendix/install/db_scripts)):      cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: noteimportant Please ignore warning messages informing that the best practices are not followed while running `timescaledb.sql` script on TimescaleDB version 2.9.0 and higher. Regardless of this warning, the configuration will be completed successfully. :::  The migration of existing history and trend data may take a lot of time. Zabbix server and frontend must be down for the period of migration.  The `timescaledb.sql` script sets the following housekeeping parameters:  -   Override item history period -   Override item trend period  In order to use partitioned housekeeping for history and trends, both these options must be enabled. It is also possible to enable override individually either for history only or trends only.  For PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher, the `timescaledb.sql` script sets two additional parameters:  -   Enable compression -   Compress records older than 7 days
zh-cn	#### 配置  我们假设数据库服务器上已经安装了 TimescaleDB 扩展（参见[安装说明](https://docs.timescale.com/latest/getting-started/installation)）。  还必须通过执行以下命令为特定数据库启用 TimescaleDB 扩展：      echo "CREATE EXTENSION IF NOT EXISTS timescaledb CASCADE;" | sudo -u postgres psql zabbix  运行此命令需要数据库管理员权限。  ::: noteclassic 如果您使用“public”以外的数据库模式，则需要在上面的命令中添加一个 SCHEMA 子句。 例如：\ `echo "CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;" | sudo -u postgres psql zabbix` :::  然后运行位于 database/postgresql 中的“timescaledb.sql”脚本。 对于新安装，必须在使用初始模式/数据创建常规 PostgreSQL 数据库后运行脚本（请参阅 [数据库创建](/manual/appendix/install/db_scripts)）：      cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: 注意重要 请忽略通知在 TimescaleDB 2.9.0 及更高版本上运行“timescaledb.sql”脚本时未遵循最佳实践的警告消息。 不管此警告如何，配置都将成功完成。 :::  现有历史和趋势数据的迁移可能需要很长时间。 Zabbix 服务器和前端在迁移期间必须关闭。  `timescaledb.sql` 脚本设置以下管理参数：  -  覆盖项目历史时期 -  覆盖项目趋势期  为了对历史和趋势使用分区管理，必须启用这两个选项。 也可以单独为仅历史或仅趋势启用覆盖。  对于 PostgreSQL 10.2 或更高版本和 TimescaleDB 1.5 或更高版本，`timescaledb.sql` 脚本设置了两个附加参数：  -  启用压缩 -  压缩超过 7 天的记录

en-us	##### Configure database for Zabbix proxy  Edit zabbix\_proxy.conf:      # vi /etc/zabbix/zabbix_proxy.conf     DBHost=localhost     DBName=zabbix     DBUser=zabbix     DBPassword=<password>  In DBName for Zabbix proxy use a separate database from Zabbix server.  In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL.  Use `DBHost=` with PostgreSQL. You might want to keep the default setting `DBHost=localhost` (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. See [SELinux configuration](/manual/installation/install_from_packages/rhel#selinux_configuration) for instructions.
zh-cn	##### 为 Zabbix 代理配置数据库  编辑 zabbix\_proxy.conf：   · # vi /etc/zabbix/zabbix_proxy.conf  · DBHost=localhost  · DBName=zabbix  · DBUser=zabbix  · DBPassword=<password>  在 Zabbix 代理的 DBName 中，使用与 Zabbix 服务器不同的数据库。  在 DBPassword 中使用 MySQL 的 Zabbix 数据库密码； PostgreSQL 的 PostgreSQL 用户密码。  在 PostgreSQL 中使用 `DBHost=`。 您可能希望保留默认值设置 `DBHost=localhost`（或 IP 地址），但这会使PostgreSQL 使用网络套接字连接到 Zabbix。 有关说明，请参阅 [SELinux 配置] (/manual/installation/install_from_packages/rhel#selinux_configuration)。

en-us	#### Configuring agent  Both generations of Zabbix agents run as a Windows service. For Zabbix agent 2, replace *agentd* with *agent2* in the instructions below.  You can run a single instance of Zabbix agent or multiple instances of the agent on a Microsoft Windows host. A single instance can use the default configuration file `C:\zabbix_agentd.conf` or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).  An example configuration file is available in Zabbix source archive as `conf/zabbix_agentd.win.conf`.  See the [configuration file](/manual/appendix/config/zabbix_agentd_win) options for details on configuring Zabbix Windows agent.
zh-cn	#### 配置 agent  两代Zabbix agent都是做为 Windows 服务运行的。对于 Zabbix agent 2，请在下面的说明中将 *agentd*  替换为 *agent2* 。  您可以在 Microsoft Windows 主机上运行 Zabbix agent的单个实例或多个实例。单个实例可以使用默认配置文件 `C:\zabbix_agentd.conf`或在命令行中指定的配置文件。在多个实例的情况下，每个代理实例都必须有自己的配置文件（其中一个实例可以使用默认配置文件）。  在Zabbix源码包中提供了一个示例配置文件，如下 `conf/zabbix_agentd.win.conf`.  有关配置 Zabbix Windows agent的详细信息的选项，另见 [配置文件](/manual/appendix/config/zabbix_agentd_win)。   ::: notewarning  ** 适用于 Windows 的 Zabbix  agent不支持非标准 Windows 配置，其 CPU 在 NUMA 节点之间不是统一分布的。 ** 如果逻辑 CPU 分布不均匀，则 CPU 性能指标可能不适用于某些 CPU。例如，如果有 72 个逻辑 CPU 和 2 个 NUMA 节点，则两个节点都必须有 36 个 CPU。 :::

en-us	#### Configuring and running Java gateway  By default, Java gateway listens on port 10052. If you plan on running Java gateway on a different port, you can specify that in settings.sh script. See the description of [Java gateway configuration file](/manual/appendix/config/zabbix_java) for how to specify this and other options.  ::: notewarning Port 10052 is not [IANA registered](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). :::  Once you are comfortable with the settings, you can start Java gateway by running the startup script:      $ ./startup.sh  Likewise, once you no longer need Java gateway, run the shutdown script to stop it:      $ ./shutdown.sh  Note that unlike server or proxy, Java gateway is lightweight and does not need a database.
zh-cn	#### 配置和运行Java网关  Java网关默认监听10052端口。如果你想运行Java网关在其他端口，你可以在settings.sh的脚本中指定其他端口号。详情可见[Java网关配置文件](/manual/appendix/config/zabbix_java)中描述的如何更改端口等其他信息。  ::: notewarning 10052端口不是由 [IANA 注册的](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt). :::  当配置好，你可以使用启动脚本来运行Java网关:      $ ./startup.sh  同样，如果你不再使用Java网关了，可以运行关闭脚本将其停止:      $ ./shutdown.sh  请注意，Java网关是轻量应用，不需要数据库，这一点与Server和Proxy不同。

en-us	#### Configuring authentication  The **Authentication** tab allows you to configure scenario authentication options. A green dot next to the tab name indicates that some type of HTTP authentication is enabled.  ![](../../assets/en/manual/config/scenario_d.png)  Authentication parameters:  |Parameter|Description| |--|--------| |*Authentication*|Authentication options.<br>**None** - no authentication used.<br>**Basic** - basic authentication is used.<br>**NTLM** - NTLM ([Windows NT LAN Manager)](http://en.wikipedia.org/wiki/NTLM) authentication is used.<br>**Kerberos** - Kerberos authentication is used. See also: [Configuring Kerberos with Zabbix](/manual/appendix/items/kerberos).<br>**Digest** - Digest authentication is used.<br>Selecting an authentication method will provide two additional fields for entering a user name and password.<br>User macros can be used in user and password fields.| |*SSL verify peer*|Mark the checkbox to verify the SSL certificate of the web server.<br>The server certificate will be automatically taken from system-wide certificate authority (CA) location. You can override the location of CA files using Zabbix server or proxy configuration parameter [SSLCALocation](/manual/appendix/config/zabbix_server).<br>This sets the [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL option.| |*SSL verify host*|Mark the checkbox to verify that the *Common Name* field or the *Subject Alternate Name* field of the web server certificate matches.<br>This sets the [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL option.| |*SSL certificate file*|Name of the SSL certificate file used for client authentication. The certificate file must be in PEM^1^ format. If the certificate file contains also the private key, leave the *SSL key file* field empty. If the key is encrypted, specify the password in *SSL key password* field. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLCertLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL option.| |*SSL key file*|Name of the SSL private key file used for client authentication. The private key file must be in PEM^1^ format. The directory containing this file is specified by Zabbix server or proxy configuration parameter [SSLKeyLocation](/manual/appendix/config/zabbix_server).<br>`HOST.*` macros and user macros can be used in this field.<br>This sets the [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL option.| |*SSL key password*|SSL private key file password.<br>User macros can be used in this field.<br>This sets the [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL option.|  ::: noteimportant  \[1\] Zabbix supports certificate and private key files in PEM format only. In case you have your certificate and private key data in PKCS \#12 format file (usually with extension \*.p12 or \*.pfx) you may generate the PEM file from it using the following commands:      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes  -out ssl-cert.key   :::  ::: noteclassic  Zabbix server picks up changes in certificates without a restart.  :::  ::: noteclassic  If you have client certificate and private key in a single file just specify it in a "SSL certificate file" field and leave "SSL key file" field empty. The certificate and key must still be in PEM format. Combining certificate and key is easy:      cat client.crt client.key > client.pem   :::
zh-cn	#### 配置认证  **认证** 选项卡允许配置场景身份认证选项。选项卡名称旁边的绿点表示启用了某种类型的 HTTP 身份验证。  ![](../../assets/en/manual/config/scenario_d.png)  认证参数：  |参数|描述| |---------|-----------| |*Authentication（认证）*|身份认证选项。<br>**None（无）** - 不使用身份认证。<br>**Basic（基本）** - 使用基本身份验证。<br>**NTLM** - 使用 NTLM（ [Windows NT LAN Manager](http://en.wikipedia.org/wiki/NTLM)） 身份认证。<br>**Kerberos** - 使用 Kerberos 身份验证。另请参阅：[Zabbix 配置 Kerberos 认证](/manual/appendix/items/kerberos).<br>**Digest** - 使用 Digest 身份认证。<br>选择身份认证将提供两个额外的字段用于输入用户名和密码。<br>用户宏可用于用户和密码字段。| |*SSL verify peer（SSL验证对端）*|勾选复选框以验证 Web 服务器的 SSL 证书。<br>服务器证书将自动从系统范围的证书颁发机构 (CA) 位置获取。您可以使用 Zabbix server 或 proxy 配置参数 [SSLCALocation](/manual/appendix/config/zabbix_server) 覆盖 CA 文件的位置。<br>这将设置 [CURLOPT\_SSL\_VERIFYPEER](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYPEER.html) cURL 选项。| |*SSL verify host（SSL验证主机）*|标记复选框以验证Web 服务器证书的 *Common Name* 字段或 *Subject Alternate Name* 字段是否匹配。<br>这将设置 [CURLOPT\_SSL\_VERIFYHOST](http://curl.haxx.se/libcurl/c/CURLOPT_SSL_VERIFYHOST.html) cURL 选项。| |*SSL certificate file（SSL证书文件）*|用于客户端身份验证的 SSL 证书文件的名称。证书文件必须为  PEM^1^ 格式。如果证书文件还包含私钥，请将 *SSL key file（SSL秘钥文件）* 字段留空。如果密钥已加密，请在 *SSL key password（SSL秘钥密码）*字段中指定密码。包含此文件的目录由  Zabbix server 或 proxy 配置参数 [SSLCertLocation](/manual/appendix/config/zabbix_server)指定。<br>支持`HOST.*` 宏和用户宏。<br>这将设置 [CURLOPT\_SSLCERT](http://curl.haxx.se/libcurl/c/CURLOPT_SSLCERT.html) cURL 选项。| |*SSL key file（SSL秘钥文件）*|用于客户端身份验证的 SSL 私钥文件的名称。私钥文件必须是 PEM^1^ 格式。包含此文件的目录由 Zabbix server 或 proxy 配置参数 [SSLKeyLocation](/manual/appendix/config/zabbix_server) 指定。<br>支持`HOST.*` 宏和用户宏。<br>这将设置 [CURLOPT\_SSLKEY](http://curl.haxx.se/libcurl/c/CURLOPT_SSLKEY.html) cURL 选项。| |*SSL key password（SSL秘钥密码）*|SSL 私钥文件密码。<br>支持用户宏。<br>这将设置 [CURLOPT\_KEYPASSWD](http://curl.haxx.se/libcurl/c/CURLOPT_KEYPASSWD.html) cURL 选项。|  ::: noteimportant  \[1\] Zabbix 仅支持 PEM 格式的证书和私钥文件。如果你有 PKCS \#12 格式文件（通常带有扩展名 \*.p12 或 \*.pfx）的证书和私钥数据，可以使用以下命令从中生成 PEM 文件：      openssl pkcs12 -in ssl-cert.p12 -clcerts -nokeys -out ssl-cert.pem     openssl pkcs12 -in ssl-cert.p12 -nocerts -nodes · -out ssl-cert.key  :::  ::: noteclassic  Zabbix server 无需重启即可获取证书中的更改。 :::  ::: noteclassic 如果你在单个文件中有客户端证书和私钥，只需在 "SSL certificate file（SSL 证书文件）" 字段中指定它，并将 "SSL key file（SSL秘钥文件）" 字段留空。证书和密钥必须仍为 PEM 格式。组合证书和密钥很容易：      cat client.crt client.key > client.pem   :::

en-us	#### Configuring certificate-based encryption for Zabbix proxy  1\. Prepare files with top-level CA certificates, proxy certificate (chain) and private key as described in [Configuring certificate on Zabbix server](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server). Edit parameters `TLSCAFile`, `TLSCertFile`, `TLSKeyFile` in proxy configuration accordingly.  2\. For active proxy edit `TLSConnect` parameter:      TLSConnect=cert  For passive proxy edit `TLSAccept` parameter:      TLSAccept=cert  3\. Now you have a minimal certificate-based proxy configuration. You may prefer to improve proxy security by setting `TLSServerCertIssuer` and `TLSServerCertSubject` parameters (see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject)).  4\. In final proxy configuration file TLS parameters may look like:      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix server,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_proxy.crt     TLSKeyFile=/home/zabbix/zabbix_proxy.key  5\. Configure encryption for this proxy in Zabbix frontend:  -   Go to: *Administration → Proxies* -   Select proxy and click on **Encryption** tab  In examples below Issuer and Subject fields are filled in - see [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) why and how to use these fields.  For active proxy  ![proxy\_active\_cert.png](../../../assets/en/manual/encryption/proxy_active_cert.png)  For passive proxy  ![proxy\_passive\_cert.png](../../../assets/en/manual/encryption/proxy_passive_cert.png)
zh-cn	 #### Zabbix proxy配置基于证书的加密  1\.使用顶级CA证书，proxy证书（链）和私钥准备文件，如在[Zabbix server上配置证书](/manual/encryption/using_certificates#configuring_certificate_on_zabbix_server)中所述。编辑参数`TLSCAFile`，`TLSCertFile`， `TLSKeyFile`在proxy配置相应。 编辑参数`TLSCAFile`，`TLSCertFile`， `TLSKeyFile`在proxy配置相应。  2\. 对于主动模式proxy 编辑`TLSConnect`参数：      TLSConnect=cert  对于被动模式proxy编辑`TLSAccept`参数：      TLSAccept=cert  3\. 现在你有一个基于证书的最小proxy配置。您可能希望通过设置`TLSServerCertIssuer`和`TLSServerCertSubject`参数来提高proxy安全性 (请参阅 [Restricting allowed certificate Issuer and Subject](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject))。  4\. 在最终的代理配置文件中，TLS参数可能看起来像:      TLSConnect=cert     TLSAccept=cert     TLSCAFile=/home/zabbix/zabbix_ca_file     TLSServerCertIssuer=CN=Signing CA,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSServerCertSubject=CN=Zabbix server,OU=Development group,O=Zabbix SIA,DC=zabbix,DC=com     TLSCertFile=/home/zabbix/zabbix_proxy.crt     TLSKeyFile=/home/zabbix/zabbix_proxy.key  5\.  在Zabbix前端配置此proxy的加密：  -   转到：_管理→agent代理程序(proxies)_ -   选择代理，然后单击**加密**选项卡  在下面的例子中，发行人和主题字段被填充-请参阅 [限制允许的证书颁发者和主题](/manual/encryption/using_certificates#restricting_allowed_certificate_issuer_and_subject) 为什么以及如何使用这些字段。  主动模式proxy  ![proxy\_active\_cert.png](../../../assets/en/manual/encryption/proxy_active_cert.png)  被动模式proxy  ![proxy\_passive\_cert.png](../../../assets/en/manual/encryption/proxy_passive_cert.png)

en-us	#### Configuring JMX interfaces and items in Zabbix frontend  With Java gateway running, server knowing where to find it and a Java application started with support for remote JMX monitoring, it is time to configure the interfaces and items in Zabbix GUI.
zh-cn	#### 在Zabbix web管理页面上配置JMX接口和监控项  Java网关在运行时，服务器会主动连接它，Java应用程序启用了远程JMX监视，现在可以在Zabbix GUI中配置接口和监控项了。

en-us	#### Configuring low-level discovery rules  See the [low-level discovery](/manual/discovery/low_level_discovery) section of the manual.
zh-cn	 #### 配置低级别自动发现规则  请参阅手册的[低级别自动发现](/manual/discovery/low_level_discovery)部分。

en-us	#### Configuring PSK for server - active proxy communication (example)  On the proxy, write the PSK value into a file, for example, `/home/zabbix/zabbix_proxy.psk`. The file must contain PSK in the first text string, for example:      e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9  Set access rights to PSK file - it must be readable only by Zabbix user.  Edit TLS parameters in proxy configuration file `zabbix_proxy.conf`, for example, set:      TLSConnect=psk     TLSPSKFile=/home/zabbix/zabbix_proxy.psk     TLSPSKIdentity=PSK 002  The proxy will connect to server using PSK. PSK identity will be "PSK 002".  (To minimize downtime see how to change connection type in [Connection encryption management](/manual/encryption#connection_encryption_management)).  Configure PSK for this proxy in Zabbix frontend. Go to *Administration→Proxies*, select the proxy, go to "Encryption" tab. In "Connections from proxy" mark `PSK`. Paste into "PSK identity" field "PSK 002" and "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" into "PSK" field. Click "Update".  Restart proxy. It will start using PSK-based encrypted connections to server. Check server and proxy logfiles for error messages.  For a passive proxy the procedure is very similar. The only difference - set `TLSAccept=psk` in proxy configuration file and set "Connections to proxy" in Zabbix frontend to `PSK`.
zh-cn	 #### 为服务器配置 PSK - 活动代理通信（示例）  在代理上，将 PSK 值写入文件，例如, `/home/zabbix/zabbix_proxy.psk`。该文件必须在第一个文本字符串中包含 PSK，例如：  ```   e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9 ``` 设置PSK文件的访问权限 - 它必须只能由Zabbix用户读取。   在代理配置文件 `zabbix_proxy.conf`中编辑TLS参数, 例如，设置: ```   TLSConnect=psk   TLSPSKFile=/home/zabbix/zabbix_proxy.psk   TLSPSKIdentity=PSK 002 ``` 代理将使用 PSK 连接到服务器。PSK 标识将是 "PSK 002"。  (为最大限度地减少停机时间，请参阅 [连接加密管理](/manual/encryption#connection_encryption_management))。  在 Zabbix 前端中为此代理配置 PSK。 转到*管理→代理*, 选择代理, 转到 "加密" 选项卡。 在"来自代理的连接" 中，标记`PSK`。将"PSK 002"粘贴到"PSK 标识"字段中，将"e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9" 粘贴到"PSK" 字段。 点击 "更新"。  重新启动代理。它将开始使用基于 PSK 的加密连接到服务器。检查服务器和代理日志文件中是否有错误消息。  对于被动代理，该过程非常相似。唯一的区别是 - 在代理配置文件中设置 `TLSAccept=psk`，并将Zabbix前端中的 "连接到 代理" 设置为 `PSK`。

en-us	#### Configuring tags  The **Tags** tab allows to define scenario-level [tags](/manual/config/tagging).  ![](../../assets/en/manual/config/scenario_c.png)  Tagging allows to filter web scenarios and web monitoring [items](/manual/web_monitoring/items).
zh-cn	#### 配置标签  **标签** 选项卡允许定义场景级别的 [标签](/manual/config/tagging)。  ![](../../assets/en/manual/config/scenario_c.png)  标签允许过滤 Web 场景和 Web [监控项](/manual/web_monitoring/items)。

en-us	### Connection set up  Zabbix supports two types of connect identifiers (connection methods):  -   Easy Connect -   Net Service Name  Connection configuration parameters for Zabbix server and Zabbix proxy can be set in the configuration files. Important parameters for the server and proxy are *DBHost*, *DBUser*, *DBName* and *DBPassword*. The same parameters are important for the frontend: *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*.  Zabbix uses the following connection string syntax:      {DBUser/DBPassword[@<connect_identifier>]}   <connect\_identifier> can be specified either in the form of "Net Service Name" or "Easy Connect".      @[[//]Host[:Port]/<service_name> | <net_service_name>]
zh-cn	### 连接设置  Zabbix支持两种类型的连接标识符（连接方法）：  -   Easy Connect -   Net Service Name  Zabbix server 和 Zabbix proxy的连接配置参数可以在配置文件中设置。server和proxy的重要参数是 *DBHost*, *DBUser*, *DBName* 和*DBPassword*。相同的参数对于前端很重要：  *$DB\["SERVER"\]*, *$DB\["PORT"\]*, *$DB\["DATABASE"\]*, *$DB\["USER"\]*, *$DB\["PASSWORD"\]*.  Zabbix 使用以下连接字符串语法：      {DBUser/DBPassword[@<connect_identifier>]}   <connect\_identifier> 可以以以下形式指定 "Net Service Name" 或 "Easy Connect".      @[[//]Host[:Port]/<service_name> | <net_service_name>]

en-us	# correlation.create
zh-cn	# 创建

en-us	# correlation.delete
zh-cn	# 删除

en-us	# correlation.get
zh-cn	# 获取

en-us	# > Correlation object  The following objects are directly related to the `correlation` API.
zh-cn	# > 关联对象  以下对象与`关联` API直接相关。

en-us	# Correlation  This class is designed to work with correlations.  Object references:\  -   [Correlation](/manual/api/reference/correlation/object#correlation)  Available methods:\  -   [correlation.create](/manual/api/reference/correlation/create) -     creating new correlations -   [correlation.delete](/manual/api/reference/correlation/delete) -     deleting correlations -   [correlation.get](/manual/api/reference/correlation/get) -     retrieving correlations -   [correlation.update](/manual/api/reference/correlation/update) -     updating correlations
zh-cn	 # 关联  此类用于关联。  对象引用：  -   [关联](/manual/api/reference/correlation/object#关联)  可用方法：  -   [correlation.create](/manual/api/reference/correlation/create) - 创建新关联 -   [correlation.delete](/manual/api/reference/correlation/delete) - 删除关联 -   [correlation.get](/manual/api/reference/correlation/get) - 获取关联 -   [correlation.update](/manual/api/reference/correlation/update) - 更新关联

en-us	# correlation.update
zh-cn	# 更新

en-us	##### Counting of threads in `proc.mem[]` and `proc.num[]` items  Linux kernel threads are counted by `proc.num[]` item but do not report memory in `proc.mem[]` item. For example:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     1      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory.  But what happens if there is a user process with the same name as a kernel thread ? Then it could look like this:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]     zabbix    9611  6133  0 17:58 pts/1    00:00:00 ./kthreadd      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     2      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     4157440  `proc.num[]` counted both the kernel thread and the user process. `proc.mem[]` reports memory for the user process only and counts the kernel thread memory as if it was 0. This is different from the case above when ZBX\_NOTSUPPORTED was reported.  Be careful when using `proc.mem[]` and `proc.num[]` items if the program name happens to match one of the thread.  Before putting parameters into `proc.mem[]` and `proc.num[]` items, you may want to test the parameters using `proc.num[]` item and `ps` command.
zh-cn	 ##### `proc.mem[]`  和`proc.num[]`  监控项中的线程计数  Linux 内核线程通过`proc.num[]`  监控项计数，但是  `proc.mem[]`  监控项并不报告内存。 例如:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     1      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     ZBX_NOTSUPPORTED: Cannot get amount of "VmSize" memory.  但是如果用户线程和内核线程名字相同会发生什么呢 ? 可能会是这样:      $ ps -ef | grep kthreadd     root         2     0  0 09:51 ?        00:00:00 [kthreadd]     zabbix    9611  6133  0 17:58 pts/1    00:00:00 ./kthreadd      $ zabbix_get -s localhost -k 'proc.num[kthreadd]'     2      $ zabbix_get -s localhost -k 'proc.mem[kthreadd]'     4157440   `proc.num[]`  计算内核线程和用户进程。  `proc.mem[]`  只计算用户进程内存，如果为0计算内核线程内存。这和上面报告 ZBX_NOTSUPPORTED 的例子不同。  如果程序名恰好匹配其中一个线程，请小心使用`proc.mem[]`  和`proc.num[]`  监控项 。  在给  `proc.mem[]`  和`proc.num[]`  监控项配置参数时, 你应该使用  `proc.num[]`  监控项 和  `ps`  命令测试该参数。

en-us	 Create another child service of Zabbix cluster with name "Zabbix server node 2".   Set the Problem tags as:   - Name: component - Operation: Equals - Value: HA node 2  Switch to the *Tags* tab and add a service tag: `Zabbix server:node 2`.  Save the new service. 
zh-cn	 创建另一个子服务 "Zabbix server node 2".   设置问题标签:   - 名称：组件 - 操作：等于 - 值：HA node 2  切换到*标签* 面板并添加服务标签：`Zabbix server:node 2`。  保存新建的服务。

en-us	##### Creating database  [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy.  Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
zh-cn	##### 创建数据库  [创建](/manual/appendix/install/db_scripts) Zabbix 代理的单独数据库。  Zabbix server 和 Zabbix proxy 不能使用同一个数据库。 如果它们安装在同一台主机上，则代理数据库必须具有不同的名称。

en-us	##### Creating database  [Create](/manual/appendix/install/db_scripts) a separate database for Zabbix proxy.  Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
zh-cn	##### 创建数据库  为 Zabbix proxy 单独[创建数据库](/manual/appendix/install/db_scripts) 。  Zabbix server 和 Zabbix proxy 不能使用同一个数据库。如果他们是安装在同一个主机中的，则 proxy 数据库需要不同的命名。

en-us	#### CRL expired or expires during server operation  [*OpenSSL*]{.underline}, in server log:  -   before expiration:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate revoked"  -   after expiration:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate expired"  The point here is that with valid CRL a revoked certificate is reported as "certificate revoked". When CRL expires the error message changes to "certificate expired" which is quite misleading.  [*GnuTLS*]{.underline}, in server log:  -   before and after expiration the same:  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\           invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked.
zh-cn	 #### CRL 已过期或者在服务器操作期间过期  [*OpenSSL*]{.underline}, 在服务器日志中会议如下显示：  -   到期前：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate revoked"  -   到期后：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\         SSL_connect() returned SSL_ERROR_SSL: file s3_clnt.c line 1253: error:14090086:\         SSL routines:ssl3_get_server_certificate:certificate verify failed:\         TLS write fatal alert "certificate expired"  这里需要注意的是，使用有效的 CRL，吊销的证书将报告为"证书已吊销"。当 CRL 过期时，错误消息将更改为"证书已过期"，这非常具有误导性。  [*GnuTLS*]{.underline}, 在服务器日志中会议如下显示：  -   到期前后显示相同：  ```{=html} <!-- --> ```     cannot connect to proxy "proxy-openssl-1.0.1e": TCP successful, cannot establish TLS to [[127.0.0.1]:20004]:\           invalid peer certificate: The certificate is NOT trusted. The certificate chain is revoked.

en-us	### Cryptography
zh-cn	### 密码学

en-us	#### Custom macros  The **LLD macros** tab allows to specify custom low-level discovery macros.  Custom macros are useful in cases when the returned JSON does not have the required macros already defined. So, for example:  -   The native `vfs.fs.discovery` key for filesystem discovery returns a     JSON with some pre-defined LLD macros such as {\#FSNAME},     {\#FSTYPE}. These macros can be used in item, trigger prototypes     (see subsequent sections of the page) directly; defining custom     macros is not needed; -   The `vfs.fs.get` agent item also returns a JSON with [filesystem     data](/manual/discovery/low_level_discovery/examples/mounted_filesystems),     but without any pre-defined LLD macros. In this case you may define     the macros yourself, and map them to the values in the JSON using     JSONPath:  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_c.png)  The extracted values can be used in discovered items, triggers, etc. Note that values will be extracted from the result of discovery and any preprocessing steps so far.  |Parameter|Description| |--|--------| |*LLD macro*|Name of the low-level discovery macro, using the following syntax: {\#MACRO}.| |*JSONPath*|Path that is used to extract LLD macro value from a LLD row, using JSONPath syntax.<br>For example, `$.foo` will extract "bar" and "baz" from this JSON: `[{"foo":"bar"}, {"foo":"baz"}]`<br>The values extracted from the returned JSON are used to replace the LLD macros in item, trigger, etc. prototype fields.<br>JSONPath can be specified using the dot notation or the bracket notation. Bracket notation should be used in case of any special characters and Unicode, like `$['unicode + special chars #1']['unicode + special chars #2']`.|
zh-cn	#### 自定义宏   **LLD 宏** 选项卡可以自定义底层自动发现的宏。  如果返回的JSON数据不包含所需的宏时，自定义宏就派上用场了。例如:  -   用于文件系统自动发现的内置的 `vfs.fs.discovery` 键返回JSON数据，其中包含一些预定义的LLD宏，比如 {\#FSNAME},     {\#FSTYPE}。这些宏可直接用于监控项和触发器原型，(参考本页后续小节); 自定义宏不是强制的; -    `vfs.fs.get` 键同样返回JSON数据，包含 [文件系统数据](/manual/discovery/low_level_discovery/examples/mounted_filesystems),     但不包括任何预定义的LLD宏。此例中你可以自定义宏, 并把自定义的宏映射到JSONPath返回的JSON数据上:  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_c.png)  提取的值可用于已发现的监控项、触发器等实体上。 注意，值会从自动发现的结果中提取出来，也会从任何到目前为止的预处理步骤的结果中提取出来。  |参数|描述| |---------|-----------| |*LLD宏*|底层自动发现宏的名称, 使用如下的语法格式: {\#MACRO}.| |*JSONPath*|用于提取LLD宏的取值的路径, 使用JSONPath语法格式.<br>比如, `$.foo` 会从下面的JSON数据中提取 "bar" 和 "baz": `[{"foo":"bar"}, {"foo":"baz"}]`<br>从JSON数据中提取的值用于替换监控项、触发器和其它实体的原型中配置的LLD宏。<br>可以使用点标记法或括号标记法来指定JSONPath。括号标记法应该用于任何使用特殊字符和编码的场景中, 像 `$['unicode + special chars #1']['unicode + special chars #2']`。|

en-us	# dashboard.create
zh-cn	# 创建

en-us	# dashboard.delete
zh-cn	# 删除

en-us	# dashboard.get
zh-cn	# 获取

en-us	# > Dashboard object  The following objects are directly related to the `dashboard` API.
zh-cn	# > 仪表盘对象  下列对象与`dashboard（仪表盘）` API 直接相关。

en-us	#### Dashboards  Manage dashboards and make scheduled reports based on them.  [Dashboard API](/manual/api/reference/dashboard) | [Template dashboard API](/manual/api/reference/templatedashboard) | [Report API](/manual/api/reference/report)
zh-cn	#### 仪表盘  管理仪表板并基于它们生成定时报表。  [Dashboard API](/manual/api/reference/dashboard) | [Template dashboard API](/manual/api/reference/templatedashboard) | [Report API](/manual/api/reference/report)

en-us	# Dashboard  This class is designed to work with dashboards.  Object references:\  -   [Dashboard](/manual/api/reference/dashboard/object#dashboard) -   [Dashboard     page](/manual/api/reference/dashboard/object#dashboard_page) -   [Dashboard     widget](/manual/api/reference/dashboard/object#dashboard_widget) -   [Dashboard widget     field](/manual/api/reference/dashboard/object#dashboard_widget_field) -   [Dashboard     user](/manual/api/reference/dashboard/object#dashboard_user) -   [Dashboard user     group](/manual/api/reference/dashboard/object#dashboard_user_group)  Available methods:\  -   [dashboard.create](/manual/api/reference/dashboard/create) -     creating new dashboards -   [dashboard.delete](/manual/api/reference/dashboard/delete) -     deleting dashboards -   [dashboard.get](/manual/api/reference/dashboard/get) - retrieving     dashboards -   [dashboard.update](/manual/api/reference/dashboard/update) -     updating dashboards
zh-cn	# 仪表盘  此类被设计用于仪表盘。  对象引用：  -   [仪表盘](/manual/api/reference/dashboard/object#仪表盘) -   [仪表盘页面](/manual/api/reference/dashboard/object#仪表盘页面) -   [仪表盘部件](/manual/api/reference/dashboard/object#仪表盘部件) -   [仪表盘部件字段](/manual/api/reference/dashboard/object#仪表盘部件字段) -   [仪表盘用户](/manual/api/reference/dashboard/object#仪表盘用户) -   [仪表盘用户组](/manual/api/reference/dashboard/object#仪表盘用户组)  可用方法：  -   [dashboard.create](/manual/api/reference/dashboard/create) - 创建新的仪表盘 -   [dashboard.delete](/manual/api/reference/dashboard/delete) - 删除仪表盘 -   [dashboard.get](/manual/api/reference/dashboard/get) - 获取仪表盘 -   [dashboard.update](/manual/api/reference/dashboard/update) - 更新仪表盘

en-us	# dashboard.update
zh-cn	# 更新

en-us	### Database creation  We assume that a *zabbix* database user with *password* password exists and has permissions to create database objects in ORCL service located on the *host* Oracle database server. Zabbix requires a Unicode database character set and a `UTF8` national character set. Check current settings:      sqlplus> select parameter,value from v$nls_parameters where parameter='NLS_CHARACTERSET' or parameter='NLS_NCHAR_CHARACTERSET';  Now prepare the database:      shell> cd /path/to/zabbix-sources/database/oracle     shell> sqlplus zabbix/password@oracle_host/ORCL     sqlplus> @schema.sql     # stop here if you are creating database for Zabbix proxy     sqlplus> @images.sql     sqlplus> @data.sql  ::: notetip Please set the initialization parameter CURSOR\_SHARING=FORCE for best performance. :::
zh-cn	 ### 数据库创建  假设有一个密码为 *password*的 *zabbix* 数据库用户，并且有权在 Oracle 数据库上的 ORCL 服务中创建数据库对象。Zabbix 需要一个 Unicode 数据库字符集和一个 `UTF8`字符集。检查当前的设置:      sqlplus> select parameter,value from v$nls_parameters where parameter='NLS_CHARACTERSET' or parameter='NLS_NCHAR_CHARACTERSET';   现在准备数据库:      shell> cd /path/to/zabbix-sources/database/oracle     shell> sqlplus zabbix/password@oracle_host/ORCL     sqlplus> @schema.sql     # stop here if you are creating database for Zabbix proxy     sqlplus> @images.sql     sqlplus> @data.sql  ::: notetip 请设置初始化参数以达到最佳的性能 CURSOR\_SHARING=FORCE :::

en-us	##### Database storage  All configuration information as well as the data gathered by Zabbix is stored in a database.
zh-cn	##### 数据存储  Zabbix 收集的所有配置信息以及数据都存储在数据库中。

en-us	#### Database TLS connection with MariaDB  Database TLS connection is not supported with the 'verify\_ca' option for the DBTLSConnect [parameter](/manual/appendix/config/zabbix_server) if MariaDB is used.
zh-cn	#### 与 MariaDB 的数据库 TLS 连接  如果使用 MariaDB 数据库，则 DBTLSConnect [参数](/manual/appendix/config/zabbix_server) 的 “verify\_ca” 选项不支持数据库 TLS 连接。

en-us	#### Data flow  In addition it is important to take a step back and have a look at the overall data flow within Zabbix. In order to create an item that gathers data you must first create a host. Moving to the other end of the Zabbix spectrum you must first have an item to create a trigger. You must have a trigger to create an action. Thus if you want to receive an alert that your CPU load is too high on *Server X* you must first create a host entry for *Server X* followed by an item for monitoring its CPU, then a trigger which activates if the CPU is too high, followed by an action which sends you an email. While that may seem like a lot of steps, with the use of templating it really isn't. However, due to this design it is possible to create a very flexible setup.
zh-cn	#### 数据流  此外，回顾一下 Zabbix 中的整体数据流也是很重要的。为了创建一个收集数据的监控项，必须首先创建一个主机。另一方面 Zabbix 必须首先拥有一个监控项来创建触发器。必须有触发器才能创建动作。因此，如果你想收到 *服务器 X* 上的 CPU 负载过高的警报，必须首先为 *服务器 X* 创建一个主机条目，然后创建一个用于监控其 CPU 的监控项，然后是一个触发器，如果 CPU 过高则触发动作，然后通过通过动作操作向您发送电子邮件。这可能看起来像很多步骤，其实使用模板并不需要。而且，由于这种设计，可以自定义创建非常灵活的设置。

en-us	# dcheck.get
zh-cn	 # 获取

en-us	##### Deny specific check  -   Blacklist a specific check with DenyKey parameter. Matching keys     will be disallowed. All non-matching keys will be allowed, except     system.run\[\] items.  For example:      # Deny secure data access     DenyKey=vfs.file.contents[/etc/passwd,*]  ::: noteimportant A blacklist may not be a good choice, because a new Zabbix version may have new keys that are not explicitly restricted by the existing configuration. This could cause a security flaw. :::
zh-cn	##### 拒绝特定检查  - 使用 DenyKey 参数将特定检查列入黑名单。匹配到的键值将被禁止。所有未匹配到的键值都将被允许，除了system.run\[\] 监控项。      例如：      # 拒绝安全数据访问     DenyKey=vfs.file.contents[/etc/passwd,*]  ::: noteimportant 黑名单可能不是一个好的选择，因为新的 Zabbix 版本中，可能存在没有在当前配置中明确限制的键值。这可能会导致安全缺陷。 :::

en-us	##### Deny specific command, allow others  -   Blacklist a specific command with DenyKey parameter. Whitelist all     other commands, with the AllowKey parameter.  ```{=html} <!-- --> ```     # Disallow specific command     DenyKey=system.run[ls -l /]           # Allow other scripts     AllowKey=system.run[*]
zh-cn	##### 拒绝特定命令，允许其他命令  - 使用 DenyKey 参数将特定命令列入黑名单。使用 AllowKey 参数将其他命令全部列入白名单。  ```{=html} <!-- --> ```     # 禁止特定命令     DenyKey=system.run[ls -l /]           # 允许其他脚本     AllowKey=system.run[*]

en-us	##### Dependent item prototype  Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `ipmi.get` item we created.  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_prototype.png)  Note the use of the {\#SENSOR\_ID} macro in the item prototype name and key:  -   *Name*: IPMI value for sensor {\#SENSOR\_ID} -   *Key*: ipmi\_sensor\[{\#SENSOR\_ID}\]  As type of information, *Numeric (unsigned)*.  In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter:      $.[?(@.id=='{#SENSOR_ID}')].value.first()  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_prototype_b.png)  When discovery starts, one item per each IPMI sensor will be created. This item will return the integer value of the given sensor.
zh-cn	##### 依赖型监控项原型  在此LLD规则中创建一个监控项原型，类型选择 "依赖型监控项".  此原型的主监控项选择之前创建的监控项 `ipmi.get`.  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_prototype.png)  注意 {\#SENSOR\_ID} 宏在监控项原型的名称和键中的使用方式:  -   *名称*: 传感器 {\#SENSOR\_ID} 的IPMI值 -   *键*: ipmi\_sensor\[{\#SENSOR\_ID}\]  信息类型选择 *Numeric (unsigned)*.  在监控项原型 "预处理" 选项卡中选择JSONPath并使用下面的JSONPath表达式作为参数:      $.[?(@.id=='{#SENSOR_ID}')].value.first()  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_prototype_b.png)  一旦自动发现开始执行，每个IPMI传感器会创建一个对应的监控项。 这个监控项会返回对应传感器的整数值.

en-us	##### Dependent item prototype  Create an item prototype with "Dependent item" type in this LLD rule. As master item for this prototype select the `vfs.fs.get` item we created.  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_prototype.png)  Note the use of custom macros in the item prototype name and key:  -   *Name*: Free disk space on {\#FSNAME}, type: {\#FSTYPE} -   *Key*: Free\[{\#FSNAME}\]  As type of information, use:  -   *Numeric (unsigned)* for metrics like 'free', 'total', 'used' -   *Numeric (float)* for metrics like 'pfree', 'pused' (percentage)  In the item prototype "Preprocessing" tab select JSONPath and use the following JSONPath expression as parameter:      $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_prototype_b.png)  When discovery starts, one item per each mountpoint will be created. This item will return the number of free bytes for the given mountpoint.
zh-cn	##### 依赖型监控项原型  在此LLD规则中创建一个监控项原型，类型选择 "依赖型监控项"。此原型的主监控项选择我们之前创建的 `vfs.fs.get` 监控项。  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_prototype.png)  注意，对于监控项原型的名称和键，其自定义宏的使用方式:  -   *名称*: {\#FSNAME}上的空闲磁盘空间, 类型: {\#FSTYPE} -   *键*: 空闲\[{\#FSNAME}\]  信息类型使用:  -   *数字 (无符号)* 用于像 'free', 'total', 'used' 这样的度量 -   *数字 (浮点数)* 用于像 'pfree', 'pused' (百分比) 这样的度量  在监控项原型 "Preprocessing" 选项卡中选择JSONPath并使用下面的 JSONPath表达式作为参数:      $.[?(@.fsname=='{#FSNAME}')].bytes.free.first()  ![](../../../../../assets/en/manual/discovery/low_level_discovery/fs_get_prototype_b.png)  一旦自动发现开始工作，每个挂载点会创建一个监控项。监控项会返回对应挂载点的空闲空间大小(字节)。

en-us	##### Dependent LLD rule  Create a low-level discovery rule as "Dependent item" type:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_lld.png)  As master item select the `ipmi.get` item we created.  In the "LLD macros" tab define a custom macro with the corresponding JSONPath:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_lld_b.png)
zh-cn	##### 依赖型LLD规则  创建一个低级别自动发现规则，类型选择 "依赖型监控项":  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_lld.png)  主监控项选择之前创建的 `ipmi.get` 监控项.  在 "LLD宏" 选项卡中用对应的JSONPath自定义一个宏:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/ipmi_get_lld_b.png)

en-us	### Description  `integer/array token.get(object parameters)`  The method allows to retrieve tokens according to the given parameters.  ::: noteclassic Only *Super admin* user type is allowed to view tokens for other users. :::
zh-cn	### 描述  `integer/array token.get(object parameters)`  此方法允许根据给定的参数获取令牌。  ::: noteclassic 只允许 *Super admin(超级管理员)* 用户可以查看其他用户的令牌。 :::

en-us	### Description  `object token.delete(array tokenids)`  This method allows to delete tokens.  ::: noteclassic Only *Super admin* user type is allowed to manage tokens for other users. :::
zh-cn	### 描述  `object token.delete(array tokenids)`  此方法允许删除令牌。  ::: noteclassic 只允许 *Super admin(超级管理员)* 用户可以管理其他用户的令牌。 :::

en-us	### Description  `object token.update(object/array tokens)`  This method allows to update existing tokens.  ::: noteclassic Only *Super admin* user type is allowed to manage tokens for other users. :::
zh-cn	### 描述  `object token.update(object/array tokens)`  此方法允许更新现有的令牌。  ::: noteclassic 只允许 *Super admin(超级管理员)* 用户可以管理其他用户的令牌。 :::

en-us	### Description  `string apiinfo.version(array)`  This method allows to retrieve the version of the Zabbix API.  ::: noteimportant This method is only available to unauthenticated users and must be called without the `auth` parameter in the JSON-RPC request. :::
zh-cn	### 描述  `string apiinfo.version(array)`  此方法允许检索 Zabbix API 的版本。  ::: noteimportant 此方法仅适用于未经身份验证的用户且必须在发送 JSON-RPC 请求中不加 `auth` 参数的情况下调用。 :::

en-us	### Description  `string/object user.login(object parameters)`  This method allows to log in to the API and generate an authentication token.  ::: notewarning When using this method, you also need to do [user.logout](/manual/api/reference/user/logout) to prevent the generation of a large number of open session records. :::  ::: noteimportant This method is only available to unauthenticated users and must be called without the `auth` parameter in the JSON-RPC request. :::
zh-cn	### 描述  `string/object user.login(object parameters)`  此方法用于登录到API并生成身份验证令牌.  ::: notewarning 使用此方法, 你同时需要使用 [注销](/manual/api/reference/user/logout) 方法, 防止产生大量未关闭的会话记录. :::  ::: noteimportant 此方法仅适用于未认证用户，同时在JSON-RPC请求中不能带有`auth`参数. :::

en-us	## DESCRIPTION  **zabbix\_agent2** is an application for monitoring parameters of various services.\ \ [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_agent2** 是一个用于监视各种服务参数的应用程序。\ \ [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_agentd** is a daemon for monitoring various server parameters. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_agentd** 是用于监视各种服务器参数的守护程序。 [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_get** is a command line utility for getting data from Zabbix agent. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_get** 是一个命令行实用程序，用于从zabbix agent获取数据。 [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_js** is a command line utility that can be used for embedded script testing. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_js** 是一个命令行实用程序，可用于嵌入式脚本测试。[ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_proxy** is a daemon that collects monitoring data from devices and sends it to Zabbix server. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_proxy** 是一个从设备收集监控数据并将其发送到Zabbix server的守护程序。[ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_sender** is a command line utility for sending monitoring data to Zabbix server or proxy. On the Zabbix server an item of type **Zabbix trapper** should be created with corresponding key. Note that incoming values will only be accepted from hosts specified in **Allowed hosts** field for this item. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_sender** 是一个命令行实用程序，用于向Zabbix server或者proxy发送监控数据。在Zabbix server上，应使用相应的密钥创建**Zabbix trapper**类型的项。请注意，传入值将仅接受从该项目的**Allowed hosts**字段中指定的主机。[]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_server** is the core daemon of Zabbix software. [ ]{#lbAE}
zh-cn	 ## 描述  **zabbix\_server** 是Zabbix软件的核心守护进程。 [ ]{#lbAE}

en-us	## DESCRIPTION  **zabbix\_web\_service** is an application for providing web services to Zabbix components. [ ]{#lbAE}
zh-cn	## 描述  **zabbix\_web\_service** 是一个为Zabbix组件提供web服务的应用程序。 [ ]{#lbAE}

en-us	#### Details about export  -   All supported elements are exported in one file. -   Host and template entities (items, triggers, graphs, discovery     rules) that are inherited from linked templates are not exported.     Any changes made to those entities on a host level (such as changed     item interval, modified regular expression or added prototypes to     the low-level discovery rule) will be lost when exporting; when     importing, all entities from linked templates are re-created as on     the original linked template. -   Entities created by low-level discovery and any entities depending     on them are not exported. For example, a trigger created for an     LLD-rule generated item will not be exported.
zh-cn	#### 详细的导出信息  -   所有支持的元素都导出到一个文件中。 -   从链接模板继承的主机和模板实体(项目、触发器、图形、发现规则)不会导出。 在宿主级别上对这些实体所做的任何更改 (如更改项目间隔、修改正则表达式或向低级别自动发现规则添加原型) 将在导出时丢失; 当导入时，所有来自链接模板的实体将被重新创建为原始链接模板上的实体。 -  由低级别自动发现创建的实体以及依赖于它们的任何实体都不会被导出。 例如，为lld规则生成的项创建的触发器将不会被导出。

en-us	#### - Details  To avoid calculations with huge numbers, we consider the timestamp of the first value in specified period plus 1 ns as a new zero-time (current epoch time is of order 10^9^, epoch squared is 10^18^, double precision is about 10^-16^). 1 ns is added to provide all positive time values for *logarithmic* and *power* fits which involve calculating log(t). Time shift does not affect *linear*, *polynomial*, *exponential* (apart from easier and more precise calculations) but changes the shape of *logarithmic* and *power* functions.
zh-cn	#### 3 细节  为避免计算量很大，我们将指定周期内第一个值的时间戳加上 1 ns视为新的零时间 (当前纪元时间为 10^9^, 纪元平方为 10^18^, 双精度约为10^-16^)。添加 1 ns以提供涉及计算log(t)的*对数* and *幂*_拟合的所有正时间值。时移不会影响 *线性*, *多项式*, *指数* (除了更简单和更精确的计算) 但会改变*对数* 和 *幂* 函数的形状。

en-us	# dhost.get
zh-cn	# dhost.get

en-us	### 'Diagnostic information' request object  The diagnostic information task request object has the following properties. Statistic request object for all types of properties is [described in detail below](/manual/api/reference/task/object#statistic_request_object).  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |historycache|object|History cache statistic request. Available on server and proxy.| |valuecache|object|Items cache statistic request. Available on server.| |preprocessing|object|Preprocessing manager statistic request. Available on server and proxy.| |alerting|object|Alert manager statistic request. Available on server.| |lld|object|LLD manager statistic request. Available on server.|
zh-cn	### “诊断信息”请求对象  诊断信息任务请求对象有以下这些属性。 所有类型属性的统计请求对象[详细描述如下](/manual/api/reference/task/object#statistic_request_object)。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |historycache|object|历史缓存统计请求。在服务器和代理上都可用。| |valuecache|object|监控项缓存统计请求。在服务器上可用。| |preprocessing|object|预处理管理器统计请求。在服务器和代理上都可用。| |alerting|object|告警管理器统计请求。在服务器上可用。| |lld|object|LLD管理器统计请求。在服务器上可用。|

en-us	### Discovered entities  The screenshots below illustrate how discovered items, triggers, and graphs look like in the host's configuration. Discovered entities are prefixed with an orange link to a discovery rule they come from.  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_items1.png)  Note that discovered entities will not be created in case there are already existing entities with the same uniqueness criteria, for example, an item with the same key or graph with the same name. An error message is displayed in this case in the frontend that the low-level discovery rule could not create certain entities. The discovery rule itself, however, will not turn unsupported because some entity could not be created and had to be skipped. The discovery rule will go on creating/updating other entities.  Items (similarly, triggers and graphs) created by a low-level discovery rule will be deleted automatically if a discovered entity (file system, interface, etc) stops being discovered (or does not pass the filter anymore). In this case the items, triggers and graphs will be deleted after the days defined in the *Keep lost resources period* field pass.  When discovered entities become 'Not discovered anymore', a lifetime indicator is displayed in the item list. Move your mouse pointer over it and a message will be displayed indicating how many days are left until the item is deleted.  ![](../../../assets/en/manual/discovery/low_level_discovery/not_discovered_message.png)  If entities were marked for deletion, but were not deleted at the expected time (disabled discovery rule or item host), they will be deleted the next time the discovery rule is processed.  Entities containing other entities, which are marked for deletion, will not update if changed on the discovery rule level. For example, LLD-based triggers will not update if they contain items that are marked for deletion.  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_triggers1.png)  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_graphs1.png)
zh-cn	### 发现的实体  下面的截图展示了主机配置中已发现的监控项、触发器和图表。发现的实体用橙色的链接作为前缀标记，橙色链接指向关联的自动发现规则。  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_items1.png)  注意，如果跟现有实体的设备唯一标识相同，则不会创建新发现的实体。比如，一个监控项的键的名称重复或图表的名称重复。此类错误会显示在前端页面上，表明低级别自动发现无法创建对应实体。然而自动发现规则本身无法变为不支持的(unsupported)状态，因为一些实体无法创建，且必须跳过。自动发现规则会继续创建/更新其它实体。  如果发现的实体(文件系统、接口等)不再被发现(或过滤器过滤不出来)，则由低级别自动发现创建的监控项(触发器、图表也类似)会自动删除。此场景中，监控项、触发器和图表会在若干时间后被删除，数据保存的时间定义在 *保存丢失资源周期* 输入框中。  当发现的实体变为 '不再被发现', 监控项列表中会显示一个涵盖整个生命周期的数据。移动鼠标到该数据上面，会显示离删除还剩多少天。   ![](../../../assets/en/manual/discovery/low_level_discovery/not_discovered_message.png)  如果实体标记为已删除，但过期未删除(由于禁用了发现规则或禁用了监控的主机)，则会在下次运行自动发现规则时删除这些实体。  包含其它实体的实体，且标记为已删除，如果在自动发现规则层面做了变更，则不会再更新。比如， 基于低级别自动发现的触发器不会再更新，即使它们包含标记为已删除的实体。  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_triggers1.png)  ![](../../../assets/en/manual/discovery/low_level_discovery/discovered_graphs1.png)

en-us	### Discovered host  ::: noteclassic Discovered host are created by the Zabbix server and cannot be modified via the API. :::  The discovered host object contains information about a host discovered by a network discovery rule. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dhostid|string|ID of the discovered host.| |druleid|string|ID of the discovery rule that detected the host.| |lastdown|timestamp|Time when the discovered host last went down.| |lastup|timestamp|Time when the discovered host last went up.| |status|integer|Whether the discovered host is up or down. A host is up if it has at least one active discovered service.<br><br>Possible values:<br>0 - host up;<br>1 - host down.|
zh-cn	### 发现主机  ::: noteclassic 发现的主机是由 Zabbix server 创建的，不能通过 API 进行修改。 :::  发现的主机对象包含一个被网络发现规则发现的主机的信息。其具有以下属性。  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |dhostid|string|主机的 ID。| |druleid|string|检测主机的发现规则的 ID。| |lastdown|timestamp|发现主机最后异常的时间。| |lastup|timestamp|发现主机最后正常的时间。| |status|integer|无论发现主机的规则是正常还是异常。如果一个主机至少还有一个活动的发现服务，那么它就是正常的。<br><br>可能的值:<br>0 - 主机正常;<br>1 - 主机异常。|

en-us	# > Discovered host object  The following objects are directly related to the `dhost` API.
zh-cn	# > 发现的主机对象  下列对象与 `dhost` API 直接相关。

en-us	# Discovered host  This class is designed to work with discovered hosts.  Object references:\  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host)  Available methods:\  -   [dhost.get](/manual/api/reference/dhost/get) - retrieve discovered     hosts
zh-cn	# 发现的主机  该类设计用于发现的主机。  对象引用:\  -   [发现的主机](/manual/api/reference/dhost/object#discovered_host)  可用方法:\  -   [dhost.get](/manual/api/reference/dhost/get) - 获取已发现的主机。

en-us	### Discovered service  ::: noteclassic Discovered services are created by the Zabbix server and cannot be modified via the API. :::  The discovered service object contains information about a service discovered by a network discovery rule on a host. It has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dserviceid|string|ID of the discovered service.| |dcheckid|string|ID of the discovery check used to detect the service.| |dhostid|string|ID of the discovered host running the service.| |dns|string|DNS of the host running the service.| |ip|string|IP address of the host running the service.| |lastdown|timestamp|Time when the discovered service last went down.| |lastup|timestamp|Time when the discovered service last went up.| |port|integer|Service port number.| |status|integer|Status of the service.<br><br>Possible values:<br>0 - service up;<br>1 - service down.| |value|string|Value returned by the service when performing a Zabbix agent, SNMPv1, SNMPv2 or SNMPv3 discovery check.|
zh-cn	 ### 被发现的服务  ::: noteclassic 被发现的服务由 Zabbix server 创建，不能通过 API 修改。 :::  被发现的服务对象包含一个关于被主机上网络发现规则发现的服务信息。具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |dserviceid|string|被发现服务的 ID。| |dcheckid|string|用于检测服务的发现检查的 ID。| |dhostid|string|运行服务的被发现主机的 ID。| |dns|string|运行服务的主机的 DNS。| |ip|string|运行服务的主机的 IP 地址。| |lastdown|timestamp|被发现的服务最后一次停止的时间。| |lastup|timestamp|被发现的服务最后一次启动的时间。| |port|integer|服务端口号。| |status|integer|服务状态。<br><br>可用值：<br>0 - 服务启动；<br>1 - 服务停止。| |value|string|当执行一个 Zabbix agent、SNMPv1、SNMPv2或SNMPv3 发现检查时，服务返回的值。|

en-us	# > Discovered service object  The following objects are directly related to the `dservice` API.
zh-cn	 # > 被发现的服务对象  以下对象与 `dservice` API 直接相关。

en-us	# Discovered service  This class is designed to work with discovered services.  Object references:\  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service)  Available methods:\  -   [dservice.get](/manual/api/reference/dservice/get) - retrieve     discovered services
zh-cn	 # 被发现的服务  此类用于被发现的服务。  对象引用：\  -   [Discovered service](/manual/api/reference/dservice/object#被发现的服务)  可用方法：\  -   [dservice.get](/manual/api/reference/dservice/get) - 获取被发现的服务

en-us	##### Discovering MBean attributes  Discovery item: `jmx.get[attributes,"com.example:type=*,*"]`  Response:  ``` {.json} [     {         "object": "com.example:type=*",         "domain": "com.example",         "properties": {             "type": "Simple"         }     },     {         "object": "com.zabbix:type=yes,domain=zabbix.com,data-source=/dev/rand,ключ=значение,obj=true",         "domain": "com.zabbix",         "properties": {             "type": "Hello",             "domain": "com.example",             "data-source": "/dev/rand",             "ключ": "значение",             "obj": true         }     } ] ```
zh-cn	##### MBean属性的自动发现  自动发现监控项: `jmx.get[attributes,"com.example:type=*,*"]`  返回数据:  ``` {.json} [     {         "object": "com.example:type=*",         "domain": "com.example",         "properties": {             "type": "Simple"         }     },     {         "object": "com.zabbix:type=yes,domain=zabbix.com,data-source=/dev/rand,ключ=значение,obj=true",         "domain": "com.zabbix",         "properties": {             "type": "Hello",             "domain": "com.example",             "data-source": "/dev/rand",             "ключ": "значение",             "obj": true         }     } ] ```

en-us	##### Discovering MBeans  Discovery item: `jmx.get[beans,"com.example:type=*,*"]`  Response:  ``` {.json} [     {         "object": "com.example:type=Hello,data-src=data-base,ключ=значение",         "domain": "com.example",         "properties": {             "data-src": "data-base",             "ключ": "значение",             "type": "Hello"         }     },     {         "object": "com.example:type=Atomic",         "domain": "com.example",         "properties": {             "type": "Atomic"         }     } ] ```
zh-cn	##### MBean的自动发现  自动发现的监控项: `jmx.get[beans,"com.example:type=*,*"]`  返回数据:  ``` {.json} [     {         "object": "com.example:type=Hello,data-src=data-base,ключ=значение",         "domain": "com.example",         "properties": {             "data-src": "data-base",             "ключ": "значение",             "type": "Hello"         }     },     {         "object": "com.example:type=Atomic",         "domain": "com.example",         "properties": {             "type": "Atomic"         }     } ] ```

en-us	#### Discovery actions  The following conditions can be used in discovery-based events:  |Condition type|Supported operators|Description| |--|--|------| |*Host IP*|equals<br>does not equal|Specify an IP address range or a range to exclude for a discovered host.<br>**equals** - host IP is in the range.<br>**does not equal** - host IP is not in the range.<br>It may have the following formats:<br>Single IP: 192.168.1.33<br>Range of IP addresses: 192.168.1-10.1-254<br>IP mask: 192.168.4.0/24<br>List: 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>Support for spaces in the list format is provided since Zabbix 3.0.0.| |*Service type*|equals<br>does not equal|Specify a service type of a discovered service or a service type to exclude.<br>**equals** - matches the discovered service.<br>**does not equal** - does not match the discovered service.<br>Available service types: SSH, LDAP, SMTP, FTP, HTTP, HTTPS *(available since Zabbix 2.2 version)*, POP, NNTP, IMAP, TCP, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping, telnet *(available since Zabbix 2.2 version)*.| |*Service port*|equals<br>does not equal|Specify a TCP port range of a discovered service or a range to exclude.<br>**equals** - service port is in the range.<br>**does not equal** - service port is not in the range.| |*Discovery rule*|equals<br>does not equal|Specify a discovery rule or a discovery rule to exclude.<br>**equals** - using this discovery rule.<br>**does not equal** - using any other discovery rule, except this one.| |*Discovery check*|equals<br>does not equal|Specify a discovery check or a discovery check to exclude.<br>**equals** - using this discovery check.<br>**does not equal** - using any other discovery check, except this one.| |*Discovery object*|equals|Specify the discovered object.<br>**equals** - equal to discovered object (a device or a service).| |*Discovery status*|equals|**Up** - matches 'Host Up' and 'Service Up' events.<br>**Down** - matches 'Host Down' and 'Service Down' events.<br>**Discovered** - matches 'Host Discovered' and 'Service Discovered' events.<br>**Lost** - matches 'Host Lost' and 'Service Lost' events.| |*Uptime/Downtime*|is greater than or equals<br>is less than or equals|Uptime for 'Host Up' and 'Service Up' events. Downtime for 'Host Down' and 'Service Down' events.<br>**is greater than or equals** - is more or equal to. Parameter is given in seconds.<br>**is less than or equals** - is less or equal to. Parameter is given in seconds.| |*Received value*|equals<br>does not equal<br>is greater than or equals<br>is less than or equals<br>contains<br>does not contain|Specify the value received from an agent (Zabbix, SNMP) check in a discovery rule. String comparison. If several Zabbix agent or SNMP checks are configured for a rule, received values for each of them are checked (each check generates a new event which is matched against all conditions).<br>**equals** - equal to the value.<br>**does not equal** - not equal to the value.<br>**is greater than or equals** - more or equal to the value.<br>**is less than or equals** - less or equal to the value.<br>**contains** - contains the substring. Parameter is given as a string.<br>**does not contain** - does not contain the substring. Parameter is given as a string.| |*Proxy*|equals<br>does not equal|Specify a proxy or a proxy to exclude.<br>**equals** - using this proxy.<br>**does not equal** - using any other proxy except this one.|  ::: noteclassic Service checks in a discovery rule, which result in discovery events, do not take place simultaneously. Therefore, if **multiple** values are configured for `Service type`, `Service port` or `Received value` conditions in the action, they will be compared to one discovery event at a time, but **not** to several events simultaneously. As a result, actions with multiple values for the same check types may not be executed correctly. :::
zh-cn	#### 发现操作  以下条件可用于基于发现的事件：  |条件类型|支持的运算符|说明| |--|--|------| |*Host IP*|等于<br>不等于|指定IP地址范围或要为已发现主机排除的范围。<br>**等于** - 主机IP在范围内。<br>** 不等于** - 主机IP不在范围内。<br>可能有以下格式：<br>单个 IP：192.168.1.33<br>IP地址范围：192.168.1-10.1-254<br >IP mask: 192.168.4.0/24<br>List: 192.168.1.1-254, 192.168.2.1-100, 192.168.2.200, 192.168.4.0/24<br>从Zabbix 3.0.0开始支持list格式的空格。| |*Service type*|等于<br>不等于|指定已发现服务的服务类型或要排除的服务类型。<br>**等于** - 匹配已发现服务。<br>**不等于** - 与发现的服务不匹配。<br>可用的服务类型：SSH、LDAP、SMTP、FTP、HTTP、HTTPS *（自 Zabbix 2.2 版本起可用）*、POP、NNTP、IMAP、TCP、Zabbix agent， SNMPv1 agent、SNMPv2 agent、SNMPv3 agent、ICMP ping、telnet *（自 Zabbix 2.2 版本起可用）*。| |*Service port*|等于<br>不等于|指定已发现服务的TCP端口范围或要排除的范围。<br>**等于** - 服务端口在范围内。<br>** 不等于** - 服务端口不在范围内。| |*Discovery rule*|等于<br>不等于|指定发现规则或要排除的发现规则。<br>**等于** - 使用此发现规则。<br>**不等于** - 使用除此之外的任何其他发现规则。| |*Discovery check*|等于<br>不等于|指定发现检查或要排除的发现检查。<br>**等于** - 使用此发现检查。<br>**不等于** - 使用除此之外的任何其他发现检查。 |*Discovery object*|等于|指定发现的对象。<br>**等于** - 等于发现的对象（设备或服务）。| |*Discovery status*|等于|**Up** - 匹配“Host Up”和“Service Up”事件<br>**Down** - 匹配“Host Down”和“Service Down”事件<br>** 发现** - 匹配“主机发现”和“服务发现”事件<br>**丢失** - 匹配“主机丢失”和“服务丢失”事件| |*Uptime/Downtime*|大于或等于<br>小于或等于|“主机启动”和“服务启动”事件的正常运行时间。 “主机停机”和“服务停机”事件的停机时间。<br>**大于或等于** - 大于或等于。 参数以秒为单位给出。<br>**小于或等于** - 小于或等于。 参数以秒为单位给出。| |*Received value*|等于<br>不等于<br>大于等于<br>小于等于<br>包含<br>不包含|指定从agent接收的值（Zabbix， SNMP) 检查发现规则。 字符串比较。 如果为规则配置了多个 Zabbix agent或 SNMP 检查，则会检查每个接收到的值（每个检查都会生成一个与所有条件匹配的新事件）。<br>**等于** - 等于值。 <br>**不等于** - 不等于该值。<br>**大于或等于** - 大于或等于该值。<br>**小于或等于** - 小于或等于该值。<br>**包含** - 包含子字符串。 参数以字符串形式给出。<br>**不包含** - 不包含子字符串。 参数以字符串形式给出。| |*Proxy*|等于<br>不等于|指定代理或要排除的代理。<br>**等于** - 使用此代理。<br>**不等于** - 使用除此之外的任何其他代理。|  ::: noteclassic 导致发现事件的发现规则中的服务检查不会同时发生。 因此，如果在操作中为“服务类型”、“服务端口”或“接收值”条件配置了**多个**值，它们将一次与一个发现事件进行比较，但**不会** 多个事件同时进行。 因此，可能无法正确执行具有相同检查类型的多个值的操作。 :::

en-us	# > Discovery check object  The following objects are directly related to the `dcheck` API.
zh-cn	 # > 发现检查对象  以下对象与 `dcheck` API 直接相关。

en-us	# Discovery check  This class is designed to work with discovery checks.  Object references:\  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)  Available methods:\  -   [dcheck.get](/manual/api/reference/dcheck/get) - retrieve discovery     checks
zh-cn	 # 发现检查  此类用于发现检查。  对象引用：\  -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)  可用方法：\  -   [dcheck.get](/manual/api/reference/dcheck/get) - 获取发现检查

en-us	#### Discovery events  Zabbix periodically scans the IP ranges defined in network discovery rules. Frequency of the check is configurable for each rule individually. Once a host or a service is discovered, a discovery event (or several events) are generated.  Zabbix generates the following events:  |Event|When generated| |--|--------| |Service Up|Every time Zabbix detects active service.| |Service Down|Every time Zabbix cannot detect service.| |Host Up|If at least one of the services is UP for the IP.| |Host Down|If all services are not responding.| |Service Discovered|If the service is back after downtime or discovered for the first time.| |Service Lost|If the service is lost after being up.| |Host Discovered|If host is back after downtime or discovered for the first time.| |Host Lost|If host is lost after being up.|
zh-cn	#### 自动发现事件  Zabbix定期扫描网络发现规则中定义的IP范围。每个规则可以单独配置检查频率。一旦发现主机或服务，就会生成发现事件（或多个事件）。  Zabbix生成以下事件：  |事件|何时生成| |-----|--------------| |服务启动|每当Zabbix检测到活跃的服务。| |服务停止|每当Zabbix不能检测到服务。| |主机启动|如果一个IP至少有一个服务UP的。| |主机宕机|如果所有服务都没有反应。| |发现服务|如果服务停止后恢复或第一次发现服务。| |服务丢失|如果服务启动后丢失。| |发现主机|如果主机宕机后恢复或第一次发现主机。| |主机丢失|如果主机启动后丢失。|

en-us	# discoveryrule.copy
zh-cn	# 复制

en-us	# discoveryrule.create
zh-cn	# 创建

en-us	# discoveryrule.delete
zh-cn	# 删除

en-us	# discoveryrule.get
zh-cn	# 获取

en-us	# > Discovery rule object  The following objects are directly related to the `drule` API.
zh-cn	 # > 发现规则对象  以下对象与 `drule` API 直接相关。

en-us	# Discovery rule  This class is designed to work with network discovery rules.  ::: notetip This API is meant to work with network discovery rules. For the low-level discovery rules see the [LLD rule API](discoveryrule). :::  Object references:\  -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)  Available methods:\  -   [drule.create](/manual/api/reference/drule/create) - create new     discovery rules -   [drule.delete](/manual/api/reference/drule/delete) - delete     discovery rules -   [drule.get](/manual/api/reference/drule/get) - retrieve discovery     rules -   [drule.update](/manual/api/reference/drule/update) - update     discovery rules
zh-cn	 # 发现规则  此类用于网络发现规则。  ::: notetip 此 API 旨在使用网络发现规则。有关低级发现规则，请查看  [LLD rule API](discoveryrule). :::  对象引用：\  -   [Discovery rule](/manual/api/reference/drule/object#发现规则)  可用方法：\  -   [drule.create](/manual/api/reference/drule/create) - 创建新的发现规则 -   [drule.delete](/manual/api/reference/drule/delete) - 删除发现规则 -   [drule.get](/manual/api/reference/drule/get) - 获取发现规则 -   [drule.update](/manual/api/reference/drule/update) - 更新发现规则

en-us	# discoveryrule.update
zh-cn	# 更新

en-us	#### Display
zh-cn	#### 展示

en-us	#### Displaying trigger status  With a trigger defined, you might be interested to see its status.  If the CPU load has exceeded the threshold level you defined in the trigger, the problem will be displayed in *Monitoring → Problems*.  ![](../../../assets/en/manual/quickstart/trigger_status0.png){width="600"}  The flashing in the status column indicates a recent change of trigger status, one that has taken place in the last 30 minutes.
zh-cn	#### 显示触发器状态  当一个触发器定义后，你可能想查看它的状态。  如果CPU负载超过了你在触发器中定义的阈值，这个问题将显示在*监测 → 问题*中。  ![](../../../assets/en/manual/quickstart/trigger_status0.png){width="600"}  状态栏中的闪烁表示最近触发状态的变化，即过去30分钟内发生的变化。