en-us	### Pre-requisites  Install MySQL database from the [official repository](https://dev.mysql.com/downloads/repo/yum/).  See [MySQL documentation](https://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en/) for details on how to use MySQL repo.  MySQL server is ready to accept secure connections using a self-signed certificate.  To see, which users are using an encrypted connection, run the following query (Performance Schema should be turned ON):      mysql> SELECT sbt.variable_value AS tls_version, t2.variable_value AS cipher, processlist_user AS user, processlist_host AS host              FROM performance_schema.status_by_thread  AS sbt             JOIN performance_schema.threads AS t ON t.thread_id = sbt.thread_id             JOIN performance_schema.status_by_thread AS t2 ON t2.thread_id = t.thread_id             WHERE sbt.variable_name = 'Ssl_version' and t2.variable_name = 'Ssl_cipher'             ORDER BY tls_version;
zh-cn	### 先决条件  安装MySQL请参照 [official repository](https://dev.mysql.com/downloads/repo/yum/).  有关如何使用 MySQL 存储库的详细信息 请参照[MySQL documentation](https://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en/)  MySQL服务器已准备好使用自签名证书接受安全连接.  若想查看哪些用户正在使用加密连接，请运行以下查询 (Performance Schema 选项应打开):      mysql> SELECT sbt.variable_value AS tls_version, t2.variable_value AS cipher, processlist_user AS user, processlist_host AS host              FROM performance_schema.status_by_thread  AS sbt             JOIN performance_schema.threads AS t ON t.thread_id = sbt.thread_id             JOIN performance_schema.status_by_thread AS t2 ON t2.thread_id = t.thread_id             WHERE sbt.variable_name = 'Ssl_version' and t2.variable_name = 'Ssl_cipher'             ORDER BY tls_version;

en-us	### Pre-requisites  Install the PostgreSQL database using the [official repository](https://www.postgresql.org/download/linux/redhat/).  PostgreSQL is not configured to accept TLS connections out-of-the-box. Please follow instructions from PostgreSQL documentation for [certificate preparation with postgresql.conf](https://www.postgresql.org/docs/13/ssl-tcp.html) and also for [user access control](https://www.postgresql.org/docs/13/auth-pg-hba-conf.html) through ph\_hba.conf.  By default, the PostgreSQL socket is binded to the localhost, for the network remote connections allow to listen on the real network interface.  PostgreSQL settings for all [modes](/manual/appendix/install/db_encrypt#terminology) can look like this:  **/var/lib/pgsql/13/data/postgresql.conf:**      ...     ssl = on     ssl_ca_file = 'root.crt'     ssl_cert_file = 'server.crt'     ssl_key_file = 'server.key'     ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL'     ssl_prefer_server_ciphers = on     ssl_min_protocol_version = 'TLSv1.3'     ...  For access control adjust */var/lib/pgsql/13/data/pg\_hba.conf*:      ...     ### require     hostssl all all 0.0.0.0/0 md5      ### verify CA     hostssl all all 0.0.0.0/0 md5 clientcert=verify-ca      ### verify full     hostssl all all 0.0.0.0/0 md5 clientcert=verify-full     ...
zh-cn	### 先决条件  安装 PostgreSQL 请参照[official repository](https://www.postgresql.org/download/linux/redhat/).  PostgreSQL未配置开箱即用的TLS连接。请按照 PostgreSQL 文档中的说明进行操作 [certificate preparation with postgresql.conf](https://www.postgresql.org/docs/13/ssl-tcp.html) 也适用于 [user access control](https://www.postgresql.org/docs/13/auth-pg-hba-conf.html) \ph_hba.conf.  默认情况下，PostgreSQL套接字绑定到本地主机，因为网络远程连接允许侦听真实的网络接口。  PostgreSQL 所有配置请参见 [modes](/manual/appendix/install/db_encrypt#terminology) 像这样:  **/var/lib/pgsql/13/data/postgresql.conf:**      ...     ssl = on     ssl_ca_file = 'root.crt'     ssl_cert_file = 'server.crt'     ssl_key_file = 'server.key'     ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL'     ssl_prefer_server_ciphers = on     ssl_min_protocol_version = 'TLSv1.3'     ...   */var/lib/pgsql/13/data/pg\_hba.conf* 配置文件用于访问控制的调整:      ...     ### require     hostssl all all 0.0.0.0/0 md5      ### verify CA     hostssl all all 0.0.0.0/0 md5 clientcert=verify-ca      ### verify full     hostssl all all 0.0.0.0/0 md5 clientcert=verify-full     ...

en-us	 ### Pre-requisites  Prior to configuring service monitoring, you need to have the hosts configured:  - *HA node 1* with at least one trigger and a tag (preferably set on a trigger level) `component:HA node 1` - *HA node 2* with at least one trigger and a tag (preferably set on a trigger level) `component:HA node 2`
zh-cn	 ### 先决条件  在配置服务监控前，需要先配置对应的主机:  - *HA node 1* 至少一个触发器，至少一个标签(最好是在触发器级别设置) `component:HA node 1` - *HA node 2* 至少一个触发器，至少一个标签(最好是在触发器级别设置) `component:HA node 2`

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

en-us	#### Problems  Retrieve problems according to the given parameters.  [Problem API](/manual/api/reference/problem)
zh-cn	#### 问题  根据给定的参数检索问题。  [Problem API](/manual/api/reference/problem)

en-us	 #### Problem tags  Problem tags are used to match problems and services. These tags are specified at the primary service configuration tab.   Only child services of the lowest hierarchy level may have problem tags defined and be directly correlated to problems. If problem tags match,  the service status will change to the same status as the problem has. In case of several problems, a service will have the status of the most severe one. Status of a  parent service is then calculated based on child services statuses according to Status calculation rules.   If several tags are specified, *AND* logic is used: a problem must have all tags  specified in the service configuration to be mapped to the service.   ![](../../../assets/en/manual/config/problem_tags.png){width=600}   :::noteclassic A problem in Zabbix inherits tags from the whole chain of templates, hosts, items, web scenarios, and triggers. Any of these tags can be used for matching problems to services. ::: 
zh-cn	#### 问题标签  问题标签用于匹配问题和服务。这些标签在主服务配置选项卡中指定。  只有最低层次级别的子服务可以定义问题标签并直接关联问题。如果问题标签匹配，服务状态将更改为与问题相同的状态。在多个问题的情况下，服务将具有最严重的状态。然后根据状态计算规则基于子服务状态计算父服务的状态。  如果指定了多个标签，则使用 *AND* 逻辑：问题必须将服务配置中指定的所有标签都映射到服务。  ![](../../../assets/en/manual/config/problem_tags.png){width=600}   :::noteclassic Zabbix 中的问题从模板、主机、项目、Web 场景和触发器的整个链中继承标签。这些标签中的任何一个都可用于匹配问题与服务。 ::: 

en-us	### Problem tag  The problem tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tag|string|Problem tag name.| |value|string|Problem tag value.|
zh-cn	### 问题标签  问题标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tag|string|问题标签名称。| |value|string|问题标签值。|

en-us	# Problem  This class is designed to work with problems.  Object references:\  -   [Problem](/manual/api/reference/problem/object#problem)  Available methods:\  -   [problem.get](/manual/api/reference/problem/get) - retrieving     problems
zh-cn	# 问题  此类设计用于管理问题。  对象引用：\  -   [问题](/manual/api/reference/problem/object#问题)  可用方法：\  -   [problem.get](/manual/api/reference/problem/get) - 获取问题

en-us	##### Problem with dots  So far so good. But what if an attribute name or a hash key contains dot symbol? Here is an example:      jmx[com.example:Type=Hello,all.fruits.apple.weight]  That's a problem. How to tell Zabbix that attribute name is "all.fruits", not just "all"? How to distinguish a dot that is part of the name from the dot that separates an attribute name and hash keys?  Before **2.0.4** Zabbix Java gateway was unable to handle such situations and users were left with UNSUPPORTED items. Since 2.0.4 this is possible, all you need to do is to escape the dots that are part of the name with a backslash:      jmx[com.example:Type=Hello,all\.fruits.apple.weight]  Same way, if your hash key contains a dot you escape it:      jmx[com.example:Type=Hello,all\.fruits.apple.total\.weight]
zh-cn	 ##### 关于点的问题  当属性名或哈希键包含点，下面就是个例子:      jmx[com.example:Type=Hello,all.fruits.apple.weight]  如何告诉Zabbix属性名是"all.fruits"，而不只是“all”呢？如何区分作为属性名称一部分的点与分隔属性名和哈希键的点呢？这是一个问题。  在 **2.0.4** 版本之前，Zabbix Java Gateway是无法处理此类情况的,在监控项里,用户只能留下UNSUPPORTED项了。 从2.0.4开始解决了此问题，你所需要做的就是用反斜杠来转义名字的一部分点：      jmx[com.example:Type=Hello,all\.fruits.apple.weight]  同样，如果哈希键包含一个点，你也可以转义它：      jmx[com.example:Type=Hello,all\.fruits.apple.total\.weight]

en-us	#### Process user  Zabbix agent on UNIX is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run agent as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run agent as 'root' if you modify the 'AllowRoot' parameter in the agent configuration file accordingly.
zh-cn	 #### 进程用户  Zabbix agent 在 UNIX 上允许使用非 root 用户运行。它将以任何非 root 用户的身份运行。因此，使用非 root 用户运行 agent 是没有任何问题的.  如果你试图以“root”身份运行它，它将会切换到一个已经“写死”的“zabbix”用户，该用户必须存在于您的系统上。如果您只想以“root”用户运行 agent，您必须在 agent 配置文件里修改‘AllowRoot‘参数。

en-us	##### Process user  Zabbix proxy is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run proxy as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly.
zh-cn	##### 进程用户  Zabbix proxy被设计为以非root用户的身份运行。它将以任何非root用户的身份运行。因此，您可以作为任何非root用户运行代理而没有任何问题。  如果您尝试以“root”身份运行它，它将切换到硬编码的“zabbix”用户，这必须在您的系统上。如果你相应地修改了代理配置文件中的AllowRoot参数，那么你只能以root身份运行proxy。

en-us	##### Process user  Zabbix server is designed to run as a non-root user. It will run as whatever non-root user it is started as. So you can run server as any non-root user without any issues.  If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be [present](/manual/installation/install) on your system. You can only run server as 'root' if you modify the 'AllowRoot' parameter in the server configuration file accordingly.  If Zabbix server and [agent](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.
zh-cn	##### 进程用户  Zabbix server 允许使用非 root 用户运行。它将以任何非 root 用户的身份运行。因此，使用非 root 用户运行 server 是没有任何问题的.  如果你试图以“root”身份运行它，它将会切换到一个已经“写死”的“zabbix”用户，您可以参考 [安装](/manual/installation/install) 章节。按此相应地修改 Zabbix server 配置文件中的“AllowRoot”参数，则可以只以“root”身份运行 Zabbix server。  如果 Zabbix server 和 [agent](agent) 均运行在同一台服务器上，建议您使用不同的用户运行 server 和 agent 。否则,，如果两者都以相同的用户运行，Agent 可以访问 Server 的配置文件, 任何 Zabbix 管理员级别的用户都可以很容易地检索到 Server 的信息。例如，数据库密码。

en-us	#### Prometheus to JSON  Data from Prometheus can be used for low-level discovery. In this case data in JSON format are needed and the *Prometheus to JSON* preprocessing option will return exactly that.  For more details, see [Discovery using Prometheus data](/manual/discovery/low_level_discovery/examples/prometheus).
zh-cn	#### Prometheus转JSON  来自Prometheus 的数据可以被低级别自动发现使用。要这样使用数据，必须要转化为JSON格式。Zabbix提供了*Prometheus转JSON*作为预处理步骤的选项，这可以直接按照格式要求返回数据。  详情参见[在低级别自动发现中，使用Prometheus数据](/manual/discovery/low_level_discovery/examples/prometheus)。

en-us	##### Prometheus to JSON  In the discovery rule, go to the Preprocessing tab and select the *Prometheus to JSON* preprocessing option. Data in JSON format are needed for discovery and the *Prometheus to JSON* preprocessing option will return exactly that, with the following attributes:  -   metric name -   metric value -   help (if present) -   type (if present) -   labels (if present) -   raw line  For example, querying `wmi_logical_disk_free_bytes`:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_prom_json.png)  from these Prometheus lines:      # HELP wmi_logical_disk_free_bytes Free space in bytes (LogicalDisk.PercentFreeSpace)     # TYPE wmi_logical_disk_free_bytes gauge     wmi_logical_disk_free_bytes{volume="C:"} 3.5180249088e+11     wmi_logical_disk_free_bytes{volume="D:"} 2.627731456e+09     wmi_logical_disk_free_bytes{volume="HarddiskVolume4"} 4.59276288e+08  will return:  ``` {.java} [     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "C:"          },         "value": "3.5180249088e+11",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"C:\"} 3.5180249088e+11"     },     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "D:"          },         "value": "2.627731456e+09",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"D:\"} 2.627731456e+09"     },     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "HarddiskVolume4"          },         "value": "4.59276288e+08",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"HarddiskVolume4\"} 4.59276288e+08"     } ] ```
zh-cn	##### Prometheus to JSON  在自动发现规则中, 找到预处理选项卡, 然后选择 *Prometheus to JSON* 这个预处理选项. 自动发现需要使用JSON格式的数据,  *Prometheus to JSON* 这个选项会返回所需的JSON格式, 并附带下列属性:  -   度量名称 -   度量值 -   帮助 (如果有) -   类型(如果有) -   标签(如果有) -   原始行  例如, 需要查询 `wmi_logical_disk_free_bytes`:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_prom_json.png)  从这些Prometheus的行中执行上述查询:      # HELP wmi_logical_disk_free_bytes Free space in bytes (LogicalDisk.PercentFreeSpace)     # TYPE wmi_logical_disk_free_bytes gauge     wmi_logical_disk_free_bytes{volume="C:"} 3.5180249088e+11     wmi_logical_disk_free_bytes{volume="D:"} 2.627731456e+09     wmi_logical_disk_free_bytes{volume="HarddiskVolume4"} 4.59276288e+08  会返回:  ``` {.java} [     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "C:"          },         "value": "3.5180249088e+11",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"C:\"} 3.5180249088e+11"     },     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "D:"          },         "value": "2.627731456e+09",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"D:\"} 2.627731456e+09"     },     {         "name": "wmi_logical_disk_free_bytes",         "help": "Free space in bytes (LogicalDisk.PercentFreeSpace)",         "type": "gauge",         "labels": {             "volume": "HarddiskVolume4"          },         "value": "4.59276288e+08",         "line_raw": "wmi_logical_disk_free_bytes{volume=\"HarddiskVolume4\"} 4.59276288e+08"     } ] ```

en-us	##### Protection against brute force attacks  In case of five consecutive failed login attempts, Zabbix interface will pause for 30 seconds in order to prevent brute force and dictionary attacks.  The IP address of a failed login attempt will be displayed after a successful login.
zh-cn	##### 防止暴力破解  为了防止暴力破解和词典攻击，如果发生连续五次尝试登录失败，Zabbix界面将暂停30秒。  在下次成功登录后，将会在界面上尝试登录失败的IP地址。

en-us	#### Proxies  In a [proxy](/manual/distributed_monitoring/proxies#configuration) configuration, user macros can be used in the following field:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Interface port (for passive proxy)|<|no|
zh-cn	#### 代理  在 [proxy](/manual/distributed_monitoring/proxies#configuration)配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |接口端口（用于被动代理）|<|不支持|

en-us	#### Proxies  Manage the proxies used in your distributed monitoring setup.  [Proxy API](/manual/api/reference/proxy)
zh-cn	#### Proxies  用于管理分布式监控设置中使用的 proxies。  [Proxy API](/manual/api/reference/proxy)

en-us	##### Proxy configuration  HA cluster nodes (servers) must be listed in the configuration of either  passive or active Zabbix proxy.  For a passive proxy, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_proxy) of the proxy,  separated by a **comma**.  ``` Server=zabbix-node-01,zabbix-node-02 ```  For an active proxy, the node names must be listed in the Server [parameter](/manual/appendix/config/zabbix_proxy) of the proxy,  separated by a **semicolon**. ``` Server=zabbix-node-01;zabbix-node-02 ```
zh-cn	##### 代理配置  HA 集群节点（服务器）必须列在被动或主动 Zabbix 代理的配置中。  对于被动代理，节点名称必须列在代理的服务器 [参数](/manual/appendix/config/zabbix_proxy) 中，以**逗号**分隔。  ``` Server=zabbix-node-01,zabbix-node-02 ```  对于主动代理，节点名称必须列在代理的服务器[参数](/manual/appendix/config/zabbix_proxy)中，以**分号**分隔。 ``` Server=zabbix-node-01;zabbix-node-02 ```

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

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

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

en-us	### Proxy installation  Once the required repository is added, you can install Zabbix proxy by running:      # dnf install zabbix-proxy-mysql zabbix-sql-scripts  Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL, or with 'sqlite3' to use SQLite3 (proxy only).  The package 'zabbix-sql-scripts' contains database schemas for all supported database management systems for both Zabbix server and Zabbix proxy and will be used for data import.
zh-cn	### 代理安装  添加所需的存储库后，您可以通过运行以下命令安装 Zabbix 代理：   · # dnf install zabbix-proxy-mysql zabbix-sql-scripts  将命令中的“mysql”替换为“pgsql”以使用 PostgreSQL，或替换为“sqlite3”以使用 SQLite3（仅限代理）。  “zabbix-sql-scripts”包包含 Zabbix 服务器和 Zabbix 代理的所有支持的数据库管理系统的数据库模式，并将用于数据导入。

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

en-us	#### Proxy startup with MySQL 8.0.0-8.0.17  zabbix\_proxy on MySQL versions 8.0.0-8.0.17 fails with the following "access denied" error:      [Z3001] connection to database 'zabbix' failed: [1227] Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation  That is due to MySQL 8.0.0 starting to enforce special permissions for setting session variables. However, in 8.0.18 this behavior was removed: [As of MySQL 8.0.18, setting the session value of this system variable is no longer a restricted operation.](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html)  The workaround is based on granting additional privileges to the `zabbix` user:  For MySQL versions 8.0.14 - 8.0.17:      grant SESSION_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost';  For MySQL versions 8.0.0 - 8.0.13:      grant SYSTEM_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost';
zh-cn	#### 使用 MySQL 8.0.0-8.0.17 启动 Proxy   zabbix\_proxy 在 8.0.0-8.0.17 版本的 MySQL 上启动失败并报错 "access denied" ：      [Z3001]  connection to database 'zabbix' failed: [1227] Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation  这是由于 MySQL 8.0.0 版本开始强制设置会话变量的特殊权限。然而，在 8.0.18 中删除了此行为： [从 MySQL 8.0.18 开始，不再限制设置系统会话变量的操作](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html)  解决方法是向`zabbix` 用户授予额外权限：  对于 MySQL 8.0.14 - 8.0.17:     grant SESSION_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost';  对于 MySQL 8.0.0 - 8.0.13:     grant SYSTEM_VARIABLES_ADMIN on *.* to 'zabbix'@'localhost';

en-us	# Proxy  This class is designed to work with proxies.  Object references:\  -   [Proxy](/manual/api/reference/proxy/object#proxy) -   [Proxy     interface](/manual/api/reference/proxy/object#proxy_interface)  Available methods:\  -   [proxy.create](/manual/api/reference/proxy/create) - create new     proxies -   [proxy.delete](/manual/api/reference/proxy/delete) - delete proxies -   [proxy.get](/manual/api/reference/proxy/get) - retrieve proxies -   [proxy.update](/manual/api/reference/proxy/update) - update proxies
zh-cn	# Proxy  此类被设计用来处理Proxy。  对象引用：\  -   [Proxy](/manual/api/reference/proxy/object#proxy) -   [Proxy interface](/manual/api/reference/proxy/object#proxy_interface)  可用方法：\  -   [proxy.create](/manual/api/reference/proxy/create) - 创建新proxy -   [proxy.delete](/manual/api/reference/proxy/delete) - 删除proxy -   [proxy.get](/manual/api/reference/proxy/get) - 获取proxy -   [proxy.update](/manual/api/reference/proxy/update) - 更新proxy

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

en-us	##### Proxy  [Zabbix proxy](/manual/concepts/proxy) can collect performance and availability data on behalf of Zabbix server. A proxy is an optional part of Zabbix deployment; however, it may be very beneficial to distribute the load of a single Zabbix server.
zh-cn	##### Proxy  [Zabbix proxy](/manual/concepts/proxy) 可以代替 Zabbix server 收集性能和可用性数据。proxy 是 Zabbix 部署的可选部分；但是对于分散单个 Zabbix server 的负载非常有用。

en-us	#### PSK contains an odd number of hex-digits  Proxy or agent does not start, message in the proxy or agent log:      invalid PSK in file "/home/zabbix/zabbix_proxy.psk"
zh-cn	 #### PSK 包含奇数个十六进制数字  Proxy 或者 agent 不能启动，proxy 或者 agent 日志中会有如下消息：      invalid PSK in file "/home/zabbix/zabbix_proxy.psk"

en-us	#### PSK identity string longer than 128 bytes is passed to GnuTLS  In TLS client side log:      gnutls_handshake() failed: -110 The TLS connection was non-properly terminated.  In TLS server side log.      gnutls_handshake() failed: -90 The SRP username supplied is illegal.
zh-cn	 #### 长度超过 128 个字节的 PSK 标识字符串将传递到 GnuTLS  在 TLS 客户端日志中会显示如下信息：      gnutls_handshake() failed: -110 The TLS connection was non-properly terminated.  在 TLS 服务器端日志中会显示如下信息：      gnutls_handshake() failed: -90 The SRP username supplied is illegal.

en-us	#### Query language comparison  The following table lists differences and similarities between PromQL and Zabbix Prometheus preprocessing query language.  |[PromQL instant vector selector](https://prometheus.io/docs/prometheus/latest/querying/basics/#instant-vector-selectors)|<|Zabbix Prometheus preprocessing| |----|----|----| |**Differences**|<|<| |Query target|Prometheus server|Plain text in Prometheus exposition format| |Returns|Instant vector|Metric or label value (Prometheus pattern)<br>Array of metrics for single value in JSON (Prometheus to JSON)| |Label matching operators|**=**, **!=**, **=\~**, **!\~**|**=**, **!=**, **=\~**, **!\~**| |Regular expression used in label or metric name matching|RE2|PCRE| |Comparison operators|See [list](https://prometheus.io/docs/prometheus/latest/querying/operators/#comparison-binary-operators)|Only **==** (equal) is supported for value filtering| |**Similarities**|<|<| |Selecting by metric name that equals string|<metric name> or {\_\_name\_\_="<metric name>"}|<metric name> or {\_\_name\_\_="<metric name>"}| |Selecting by metric name that matches regular expression|{\_\_name\_\_=\~"<regex>"}|{\_\_name\_\_=\~"<regex>"}| |Selecting by <label name> value that equals string|{<label name>="<label value>",...}|{<label name>="<label value>",...}| |Selecting by <label name> value that matches regular expression|{<label name>=\~"<regex>",...}|{<label name>=\~"<regex>",...}| |Selecting by value that equals string|{\_\_name\_\_=\~".\*"} == <value>|{\_\_name\_\_=\~".\*"} == <value>|
zh-cn	#### 查询语言对照表  下表列出了PromQL与Zabbix Prometheus 预处理查询语言之间的异同。  |<|[PromQL瞬时向量选择器](https://prometheus.io/docs/prometheus/latest/querying/basics/#instant-vector-selectors)|Zabbix Prometheus预处理| |----|----|----| |**不同点**|<|<| |查询目标|Prometheus服务器|Prometheus行协议中的纯文本| |返回值|瞬时向量|指标或标签的值（Prometheus正则匹配）<br>JSON格式的包含单个值的指标构成的数组（Prometheus转JSON）| |标签匹配操作符|**=**, **!=**, **=\~**, **!\~**|**=**, **!=**, **=\~**, **!\~**| |匹配标签或指标名称的正则表达式|RE2|PCRE| |比较操作符|详见[清单](https://prometheus.io/docs/prometheus/latest/querying/operators/#comparison-binary-operators)|只有 **==** (相等)用于支持值过滤| |**相似点**|<|<| |依据指标名相同的字符串筛选|<metric name> or {\_\_name\_\_="<metric name>"}|<metric name> or {\_\_name\_\_="<metric name>"}| |依据匹配正则表达式的指标名筛选|{\_\_name\_\_=\~"<regex>"}|{\_\_name\_\_=\~"<regex>"}| |依据相同字符串的标签名称值筛选|{<label name>="<label value>",...}|{<label name>="<label value>",...}| |依据匹配正则表达式的标签名称值筛选|{<label name>=\~"<regex>",...}|{<label name>=\~"<regex>",...}| |根据相同的字符串的值筛选|{\_\_name\_\_=\~".\*"} == <value>|{\_\_name\_\_=\~".\*"} == <value>|

en-us	#### Queue item  A special internal item **zabbix\[queue,<from>,<to>\]** can be used to monitor the health of the queue in Zabbix. It will return the number of items delayed by the set amount of time. For more information see [Internal items](/manual/config/items/itemtypes/internal).
zh-cn	#### 队列监控项  有一个特别的内部监控项**zabbix\[queue,<from>,<to>\]**可以用于监控ZABBIX中队列的健康状态。他会返回指定时间区间的监控项数目。有关更多信息请参阅[内部监控项](/zh/manual/config/items/itemtypes/internal)。\

en-us	##### Readable summary in maps  A hidden "aria-label" property is available allowing map information to be read with a screen reader. Both general map description and individual element description is available, in the following format:  -   for map description:     `<Map name>, <* of * items in problem state>, <* problems in total>.` -   for describing one element with one problem:     `<Element type>, Status <Element status>, <Element name>, <Problem description>.` -   for describing one element with multiple problems:     `<Element type>, Status <Element status>, <Element name>, <* problems>.` -   for describing one element without problems:     `<Element type>, Status <Element status>, <Element name>.`  For example, this description is available:      'Local network, 1 of 6 elements in problem state, 1 problem in total. Host, Status problem, My host, Free disk space is less than 20% on volume \/. Host group, Status ok, Virtual servers. Host, Status ok, Server 1. Host, Status ok, Server 2. Host, Status ok, Server 3. Host, Status ok, Server 4. '  for the following map:  ![](../../../../../assets/en/manual/web_interface/map_aria_label.png){width="600"}
zh-cn	##### 在拓扑图中读取摘要  一个隐藏的可用属性“气泡(aria-label)”，允许使用屏幕阅读器阅读拓扑图信息。 通用拓扑图描述和单个元素描述都可以用，格式如下：  - · 拓扑图描述：  · `<Map name>, <* of * items in problem state>, <* problems in total>.` - · 描述某个元素的某个问题：  · `<Element type>, Status <Element status>, <Element name>, <Problem description>.` - · 描述某个元素的多个问题：  · `<Element type>, Status <Element status>, <Element name>, <* problems>.` - · 描述某个没有问题的元素：  · `<Element type>, Status <Element status>, <Element name>.`  例如，可使用这个描述：   · 'Local network, 1 of 6 elements in problem state, 1 problem in total. Host, Status problem, My host, Free disk space is less than 20% on volume \/. Host group, Status ok, Virtual servers. Host, Status ok, Server 1. Host, Status ok, Server 2. Host, Status ok, Server 3. Host, Status ok, Server 4. '  以下拓扑图：  ![](../../../../../assets/en/manual/web_interface/map_aria_label.png){width="600"}

en-us	##### Recent change markers  Inward pointing red triangles around an element indicate a recent trigger status change - one that's happened within the last 30 minutes. These triangles are shown if the *Mark elements on trigger status change* check-box is marked in map [configuration](/manual/config/visualization/maps/map#creating_a_map).
zh-cn	##### 最近更改的标记  元素周围向内指向的红色三角形表示最近的触发状态变化 - 最近30分钟内触发状态发生更改。 如果在拓扑图[配置](/manual/config/visualization/maps/map#creating_a_map)中选择了“触发器状态上的标记组件改变”复选框，则会显示这些三角形。

en-us	#### Recent data vs longer periods  For very recent data a **single** line is drawn connecting each received value. The single line is drawn as long as there is at least one horizontal pixel available for one value.  For data that show a longer period **three lines** are drawn - a dark green one shows the average, while a light pink and a light green line shows the maximum and minimum values at that point in time. The space between the highs and the lows is filled with yellow background.  Working time (working days) is displayed in graphs as a white background, while non-working time is displayed in gray (with the *Original blue* default frontend theme).  ![](../../../../../assets/en/manual/config/graph_working_time.png){width="550"}  Working time is always displayed in simple graphs, whereas displaying it in [custom graphs](custom#configuring_custom_graphs) is a user preference.  Working time is not displayed if the graph shows more than 3 months.
zh-cn	#### 最近的数据与更长的时期  对于最近的数据，会绘制一条**单**线连接每个接收到的数据价值。只要至少有一条线，就画一条线水平像素可用于一个值。  对于显示较长周期的数据**绘制三条线** - 深色绿色表示平均值，而浅粉色和浅绿色线显示该时间点的最大值和最小值。空间高点和低点之间用黄色背景填充。  工作时间（工作日）在图表中显示为白色背景，而非工作时间以灰色显示（默认前端主题使用*原始蓝色*）。  ![](../../../../../assets/en/manual/config/graph_working_time.png){width="550"}  在简单的图表中工作时间总会显示，而在[自定义图表](custom#configuring_custom_graphs) 中可以按照用户偏好显示。  如果图表显示超过 3 个月，则不显示工作时间。

en-us	##### Referencing a network map  Network maps can be referenced by both `sysmapid` and `mapname` GET parameters. For example,      http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network  will open the map with that name (Local network).  If both `sysmapid` (map ID) and `mapname` (map name) are specified, `mapname` has higher priority.
zh-cn	##### 引用网络拓扑图  可以被  `sysmapid`  和  `mapname`  GET参数引用。例如，   · http://zabbix/zabbix/zabbix.php?action=map.view&mapname=Local%20network  将打开名称是本地网络的拓扑图。  如果同时指定了  `sysmapid`  （地图ID） 和  `mapname`  (地图名称) 时，  `mapname`  具有更高有优先级。

en-us	# regexp.create
zh-cn	# 正则表达式.创建

en-us	# regexp.delete
zh-cn	# 正则表达式.删除

en-us	# regexp.get
zh-cn	# 正则表达式.获取

en-us	# regexp.update
zh-cn	# 正则表达式.更新

en-us	# > Regular expression object  The following objects are directly related to the `regexp` API.
zh-cn	# > 目标：正则表达式  以下所列内容均与 `regexp（正则表达式）` API 直接关联。

en-us	#### - Regular expressions  This section allows creating custom regular expressions that can be used in several places in the frontend. See [Regular expressions](/manual/regular_expressions) section for details.
zh-cn	#### - 正则表达式  本节允许创建可在前端多个位置使用的自定义正则表达式。  有关详细信息，请参阅 [Regular expressions](/manual/regular_expressions) 部分。

en-us	# Regular expression  This class is designed to work with global regular expressions.  Object references:\  -   [Regular expression](/manual/api/reference/regexp/object)  Available methods:\  -   [regexp.create](/manual/api/reference/regexp/create) - creating new     regular expressions -   [regexp.delete](/manual/api/reference/regexp/delete) - deleting     regular expressions -   [regexp.get](/manual/api/reference/regexp/get) - retrieving regular     expressions -   [regexp.update](/manual/api/reference/regexp/update) - updating     regular expressions
zh-cn	# 正则表达式  本节内容用于使用户更全面的了解如何使用有关全局类正则表达式的API功能。  用户可直接参考：\  -   [正则表达式](zh/manual/api/reference/regexp/object)  可应用的功能方式包括：\  -   [regexp.create](zh/manual/api/reference/regexp/create) 创建新的正则表达式 -   [regexp.delete](zh/manual/api/reference/regexp/delete) - 删除目标正则表达式 -   [regexp.get](zh/manual/api/reference/regexp/get) - 检索正则表达式数据 -   [regexp.update](zh/manual/api/reference/regexp/update) - 更新正则表达式数据

en-us	#### Removing web server test page  It is recommended to remove the web server test page to avoid information exposure. By default, web server webroot contains a test page called index.html (Apache2 on Ubuntu is used as an example):  ![](../../../../assets/en/manual/installation/requirements/test_page.png)  The test page should be removed or should be made unavailable as part of the web server hardening process.
zh-cn	#### 删除web服务器测试页面  建议移除 web 服务器测试页面，以免信息泄露。 默认情况下，Web 服务器 webroot 包含一个名为 index.html 的测试页面（以 Ubuntu 上的 Apache2 为例）：  ![] (../../../../assets/en/manual/installation/requirements/test_page.png)  作为web服务器加固过程的一部分，测试页面应该被删除或设为不可用。

en-us	# report.create
zh-cn	# 报告.创建

en-us	# report.delete
zh-cn	# 报告.删除

en-us	# report.get
zh-cn	# 报告.获取

en-us	# > Report object  The following objects are directly related to the `report` API.
zh-cn	# > 目标：报告  接下来介绍有关`report（报告）` API 的相关内容。

en-us	 ### Report  The filter allows to select the report based on the SLA name as well as the  service name. It is also possible to limit the displayed period.  ![](../../../../../assets/en/manual/web_interface/sla_report.png){width="600"}  Each column (period) displays the SLI for that period. SLIs that are in breach of the set  SLO are highlighted in red.  20 periods are displayed in the report. A maximum of 100 periods can be displayed, if  both the *From* date and *To* date are specified. 
zh-cn	### 报告  可以根据SLA名称和服务名称筛选报告。也可以根据时间段来显示。  ![](../../../../../assets/en/manual/web_interface/sla_report.png){width="600"}  每列（周期）显示该期间的SLI。违反SLO的SLIs将以红色突出显示。  报表中显示20个周期。输入*From*日期和*To*日期，最多显示100个周期。

en-us	# Report  This class is designed to work with scheduled reports.  Object references:\  -   [Report](/manual/api/reference/report/object#report) -   [Users](/manual/api/reference/report/object#users) -   [User groups](/manual/api/reference/report/object#user_groups)  Available methods:\  -   [report.create](/manual/api/reference/report/create) - create new     scheduled reports -   [report.delete](/manual/api/reference/report/delete) - delete     scheduled reports -   [report.get](/manual/api/reference/report/get) - retrieve scheduled     reports -   [report.update](/manual/api/reference/report/update) - update     scheduled reports
zh-cn	# 报告  本章节介绍如何使用规划报告功能。 有关报告可参考的信息：\  -   [报告](zh/manual/api/reference/report/object#report) -   [用户](zh/manual/api/reference/report/object#users) -   [用户组](zh/manual/api/reference/report/object#user_groups)  用户可使用的功能：\  -   [report.create](zh/manual/api/reference/report/create) - 创建新的规划报告 -   [report.delete](/manual/api/reference/report/delete) - 删除已存在的规划报告 -   [report.get](/manual/api/reference/report/get) - 检索规划报告数据 -   [report.update](/manual/api/reference/report/update) - 更新规划报告数据

en-us	# report.update
zh-cn	# 报告.更新

en-us	### Required mode
zh-cn	### 所需模式

en-us	### Required mode
zh-cn	### 所需模式

en-us	##### Requirements  The following is required to set up encryption:  -   Developer-supported operating system with OpenSSL >=1.1.X or     alternative.  ::: noteclassic  It is recommended to avoid OS in the end-of-life status, especially in the case of new installations  :::  -   Database engine (RDBMS) installed and maintained from the official     repository provided by developer. Operating systems often shipped     with outdated  database software versions for which encryption     support is not implemented, for example RHEL 7 based systems and     PostgreSQL 9.2, MariaDB 5.5 without encryption support. 
zh-cn	##### 要求  设置加密需要以下内容:  -   需要具有 OpenSSL 1.1.X 及以上版本的操作系统或其他替代方案。  ::: noteclassic 不建议使用不再更新维护的操作系统，尤其是在新安装的情况下。 ::: 数据库引擎(RDBMS)的安装及维护由官方存储库的开发人员提供。操作系统通常自带的数据库版本较老，没有实现加密支持，例如基于RHEL 7 及 PostgreSQL 9.2、MariaDB 5.5 均没有加密支持。

en-us	### Reserved ID value "0"  Reserved ID value "0" can be used to filter elements and to remove referenced objects. For example, to remove a referenced proxy from a host, proxy\_hostid should be set to 0 ("proxy\_hostid": "0") or to filter hosts monitored by server option proxyids should be set to 0 ("proxyids": "0").
zh-cn	 ### 预留ID值“0”  预留ID值“0”，可以用来过滤元素和删除引用的对象。例如，从主机中删除一个引用的代理，proxy_hostid 应该设置为 0 ("proxy_hostid": "0")， 或者要过滤被zabbix server监控的主机，proxyids 选项应该被设置为 0 ("proxyids": "0")。

en-us	### Return values  `(array)` Returns an array of objects containing the ID of the generated token under the `tokenid` property and generated authorization string under `token` property.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |tokenid|string|ID of the token.| |token|string|The generated authorization string for this token.|
zh-cn	### 返回值  `(array)` 返回一个对象数组，其中包含 `tokenid` 属性下生成的令牌的 ID 和 `token` 属性下生成的授权字符串。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |tokenid|string|令牌ID。| |token|string|为此令牌生成的授权字符串。|

en-us	### Return values  `(boolean )` Returns boolean true as result on successful update.
zh-cn	### 返回值  `(boolean )` 成功更新后返回布尔值true。

en-us	### Return values  `(boolean)` Returns `true` if importing has been successful.
zh-cn	### 返回值  `(boolean)`如果导入成功将返回 `true` 

en-us	### Return values  `(boolean)` Returns `true` if the copying was successful.
zh-cn	### 返回值  `(boolean)` 如果复制成功，则返回 `true`。

en-us	### Return values  `(boolean)` Returns `true` if the user has been logged out successfully.
zh-cn	### 返回值  `(boolean)` 如果用户成功注销，返回 `true`.

en-us	### Return values  `(integer/array)` Returns an array of objects.
zh-cn	### 返回值  `(integer/array)` 返回一个对象的数组。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -  如果使用了 countOutput 参数，将返回获取对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回:  -   一组对象; -   如果使用了 `countOutput` 参数，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   对象数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回下列两种数值之一：  -   一组对象； -   在`countOutput`参数应用的情况下，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整数/数组)` 返回其中之一:  -   一组对象; -   如果使用了 `countOutput` 参数，则返回获取的对象数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(integer/array)`返回以下:  -   一组对象; -   如果`countOutput` 参数被使用，返回对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一:  -    一个对象数组 -   如果已经使用了`countOutput`参数，则统计对象的数量.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数,查询对象的数量.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回两者其中任一：  -   一组对象数组; -   如果已经使用了`countOutput`参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -   如果使用了 `countOutput` 参数，则返回检索到的对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整型/数组)` 返回其中之一： -   一个对象数组； -   如果使用`countOutput`参数，被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回数值  `(integer/array)`将返回以下两种数值中的任意一种：  -   一组有关对象的数组； -   若在使用`countOutput`参数的前提下，那么将会返回检索对象的总数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(整型/数组)` 返回其中之一： -   一组对象; -   如果用到`countOutput`参数，被检索到的对象数,。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回以下其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一组对象； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回其中一种结果：  -   一个对象数组； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回值是 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了`countOutput`参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回二者之一:  -   一个对象列表; -   查询结果数量, 如果使用了 `countOutput` 参数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，返回被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了`countOutput`参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  (integer/array) 返回其中之一：  -   对象数组；  -   如果使用了 countOutput 参数，则检索到对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中之一：  -   一组对象； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(整数/数组)` 返回其中之一:  -   一组对象; -   如果使用了 `countOutput` 参数,返回对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  返回 `(integer/array)` 其中之一：  -   一个对象的数组； -   如果使用了 `countOutput` 参数，则为检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	 ### 返回值  `(integer/array)` 返回以下其中一种结果：  -   一个数组对象； -   如果使用了参数`countOutput`，则返回检索到的对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整型/数组)` 返回其中之一：  -   一个对象数组； -   如果使用`countOutput`参数，返回被检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回:  -   一组对象; -  如果设置了`countOutput`参数,则返回获取到的对象数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回其中一个：  -   一个对象数组； -   如果使用了 countOutput 参数，将返回获取对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回结果二选一:  -   一个对象数组; -   如果使用 `countOutput` 参数，返回检索到的对象总数.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回下列两种之一：  -   一组对象； -   在`countOutput`参数应用的情况下，返回检索对象的数量。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回任一值:  - 对象数组； - 检索到的对象的计数，如果使用了 `countOutput` 参数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回:  -   一个对象数组; -   检索对象的计数, 如果, 如果 `countOutput` 参数被使用.

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值 `(integer/array)` 返回两者其一：  -   一个对象数组； -   如果使用了'countOutput'参数，则对检索对象进行计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(integer/array)` 返回以下任一选项：  -   对象数组； -   如果使用了 `countOutput` 参数，则检索对象的计数。

en-us	### Return values  `(integer/array)` Returns either:  -   an array of objects; -   the count of retrieved objects, if the `countOutput` parameter has     been used.
zh-cn	### 返回值  `(整数/数组)` 返回任一：  -   对象数组； -   如果已使用countOutput参数，则检索对象的计数。

en-us	### Return values  `(object)` Returns an object containing the IDs of the cleared items under the `itemids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含 `itemids` 属性（其中包含成功删除历史数据的监控项ID）的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created actions under the `actionids` property. The order of the returned IDs matches the order of the passed actions.
zh-cn	### 返回值  `(object)` 返回一个对象，其中 `actionids` 属性下包含已创建 动作 的 ID。 返回的 ID 的顺序与传递的 动作 顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created correlations under the `correlationids` property. The order of the returned IDs matches the order of the passed correlations.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含`correlationids` 属性下创建的关联的 ID。返回的 ID 的顺序与所传递的关联的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed dashboards.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 `dashboardids` 属性下创建的仪表盘的 ID。返回的 ID 的顺序与所传递的仪表盘的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created discovery rules under the `druleids` property. The order of the returned IDs matches the order of the passed discovery rules.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下创建的发现规则的ID。返回 ID 的顺序与传递的发现规则的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created global macros under the `globalmacroids` property. The order of the returned IDs matches the order of the passed global macros.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被创建全局宏的ID）的对象. 返回的主机宏ID顺序与传入的主机宏顺序相同.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graph prototypes under the `graphids` property. The order of the returned IDs matches the order of the passed graph prototypes.
zh-cn	 ### 返回值  `(object)`返回一个对象，包含在`graphids`属性下创建的图表原型的ID。返回的ID的顺序与传递的图表原型的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created graphs under the `graphids` property. The order of the returned IDs matches the order of the passed graphs.
zh-cn	### 返回值  `(object)`返回一个对象，包含在`graphids`属性下创建的图表的ID。返回的ID的顺序与传递的图表的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host groups under the `groupids` property. The order of the returned IDs matches the order of the passed host groups.
zh-cn	 ### 返回值  `(对象)` 在`groupids`属性下返回包含已创建主机组ID的对象.返回主机组ID的顺序与传入的主机组顺序一致.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`iterfaceids`属性中返回包含已创建主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)`  在`interfaceids`属性中返回已创建主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host interfaces under the `interfaceids` property. The order of the returned IDs matches the order of the passed host interfaces.
zh-cn	### 返回值  `(object)` 在 `interfaceids` 属性中返回已创建主机接口ID对象。 返回的ID顺序与传入的主机接口顺序保持一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host macros under the `hostmacroids` property. The order of the returned IDs matches the order of the passed host macros.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被创建主机宏的ID）的对象. 返回的主机宏ID顺序与传入的主机宏顺序相同.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created host prototypes under the `hostids` property. The order of the returned IDs matches the order of the passed host prototypes.
zh-cn	### 返回值  `(object)` 在`hostids`属性中返回包含创建主机原型的ID对象， 返回的ID顺序和传入的主机原型的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created hosts under the `hostids` property. The order of the returned IDs matches the order of the passed hosts.
zh-cn	 ### 返回值  `(对象)` 返回包含已创建主机ID的属性 `hostids` ，返回ID的顺序与传入主机的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created icon maps under the `iconmapids` property. The order of the returned IDs matches the order of the passed icon maps.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所创建图标映射的 ID。返回的多个 ID 的顺序与传参里多个图标映射的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created images under the `imageids` property. The order of the returned IDs matches the order of the passed images.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下创建的图像的 ID。返回 ID 的顺序与传递图像的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created item prototypes under the `itemids` property. The order of the returned IDs matches the order of the passed item prototypes.
zh-cn	### 返回值  返回一个对象`(object)` ，该对象包含在 `itemids` 属性下创建的监控项原型的 IDs。返回的 IDs 的顺序与传递的项目原型的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created items under the `itemids` property. The order of the returned IDs matches the order of the passed items.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `itemids` 属性下创建的监控项的 ID。返回 ID 的顺序与传递监控项的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created LLD rules under the `itemids` property. The order of the returned IDs matches the order of the passed LLD rules.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含在 `itemids` 属性下创建的 LLD 规则的 ID。返回 ID 的顺序与传递的 LLD 规则的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created maintenances under the `maintenanceids` property. The order of the returned IDs matches the order of the passed maintenances.
zh-cn	### 返回值   `(object)`在`maintenanceids`属性中返回一个包含所有已被创建的维护模式的对象的ID。返回的IDs的排序与传递的维护模式的IDs顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created maps under the `sysmapids` property. The order of the returned IDs matches the order of the passed maps.
zh-cn	### 返回值  `(对象)`返回一个对象，该对象包含在"sysmapid"属性下创建的拓扑图的id。返回id的顺序与传递的拓扑图的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created media types under the `mediatypeids` property. The order of the returned IDs matches the order of the passed media types.
zh-cn	### 返回值   `(object)`返回一个包含在"mediatypeids"属性下创建的媒介类型的IDs的对象，返回的顺序与传递的媒介类型的ID顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created regular expressions under the `regexpids` property.
zh-cn	### 返回值  根据`regexpids` 的特性`(object)`会反馈一个包含新创建的正则表达式ID的对象

en-us	### Return values  `(object)` Returns an object containing the IDs of the created roles under the `roleids` property. The order of the returned IDs matches the order of the passed roles.
zh-cn	### 返回值  根据`roleids`特性，`(object)` 会返回一个对象，包含创建的角色用户的ID号。返回的ID号顺序对应查询的角色用户次序。 

en-us	### Return values  `(object)` Returns an object containing the IDs of the created scheduled reports under the `reportids` property. The order of the returned IDs matches the order of the passed scheduled reports.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`会返回一个对象，包含已创建的规划报告ID。 返回的ID顺序与发送的规划报告顺序保持一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created scripts under the `scriptids` property. The order of the returned IDs matches the order of the passed scripts.
zh-cn	### 返回值  `(对象)` 返回一个`scriptids`属性包含被创建脚本ID的对象。返回的ID顺序与传入脚本的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created services under the `serviceids` property. The order of the returned IDs matches the order of the passed services.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids`属性包含被创建服务ID的对象。返回的ID顺序与传入服务的顺序一致。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created tasks under the `taskids` property. One task is created for each item and low-level discovery rule. The order of the returned IDs matches the order of the passed `itemids`.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`taskids` 属性下创建的任务的ID。为每个监控项和低级别自动发现规则创建一个任务。返回的ID的顺序与传递的`itemids`的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created template dashboards under the `dashboardids` property. The order of the returned IDs matches the order of the passed template dashboards.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids` 属性下创建的模板仪表盘的ID。返回ID的顺序与传递的模板仪表盘的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created templates under the `templateids` property. The order of the returned IDs matches the order of the passed templates.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下创建的模板的ID。返回ID的顺序与传递模板的顺序匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created tokens under the `tokenids` property. The order of the returned IDs matches the order of the passed tokens.
zh-cn	### 返回值  `(object)` 返回一个对象其中包含在 `tokenids` 属性下创建的令牌的 ID。返回的 ID 的顺序与传递的令牌的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created trigger prototypes under the `triggerids` property. The order of the returned IDs matches the order of the passed trigger prototypes.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含在`triggerids`属性中已创建触发器原型的ID，返回ID的顺序与传递触发器原型的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created triggers under the `triggerids` property. The order of the returned IDs matches the order of the passed triggers.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含在 `triggerids` 属性下创建的触发器 ID，返回 的ID 顺序与传递的触发器的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created user groups under the `usrgrpids` property. The order of the returned IDs matches the order of the passed user groups.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被创建用户组ID）的对象.  返回的ID的顺序与传递的用户组的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created users under the `userids` property. The order of the returned IDs matches the order of the passed users.
zh-cn	### 返回值  `(object)` 返回一个包含创建值的ID的对象映射 `userids` 属性. 返回的ID的顺序与传入的用户的顺序相匹配.

en-us	### Return values  `(object)` Returns an object containing the IDs of the created value maps the `valuemapids` property. The order of the returned IDs matches the order of the passed value maps.
zh-cn	### 返回值  `(object)` 返回一个包含已创建值映射的ID的对象，ID在`valuemapids` 属性下。返回的IDs的顺序和传递的值映射的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the created web scenarios under the `httptestids` property. The order of the returned IDs matches the order of the passed web scenarios.
zh-cn	 ### 返回值  `(object)` 返回一个包含已创建Web场景ID的对象，ID在`httptestids`属性下。返回的IDs的顺序和传递的Web场景的顺序相匹配。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted actions under the `actionids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象在 `actionids` 属性下包含要删除动作的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted correlations under the `correlationids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`correlationids`属性下删除的关联 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids`属性下删除的仪表盘 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted discovery rules under the `druleids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下已删除的发现规则的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted global macros under the `globalmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被删除全局宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graph prototypes under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个包含在`graphids`属性下被删除图表原型的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted graphs under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个对象，包含在`graphids`属性下删除的图表的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 在`groupids`属性中返回包含已删主机组ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已删除主机接口ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已删除主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host macros under the `hostmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被删除主机宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted host prototypes under the `hostids` property.
zh-cn	### 返回值 `(object)` 在`hostids`属性中返回已删除主机原型的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted hosts under the `hostids` property.
zh-cn	 ### 返回值  `(object)` 返回一个具有`hostids`属性（其中包含被删除主机的ID）的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted icon maps under the `iconmapids` property.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所删除的多个图标映射的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted images under the `imageids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下已删除图像的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted item prototypes under the `prototypeids` property.
zh-cn	### 返回值  `（object）`返回一个对象，该对象包含`prototypeids`属性下已删除监控项原型的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted items under the `itemids` property.
zh-cn	### 返回值  返回一个对象，该对象包含 `itemids` 属性下已删除项目的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted maintenance periods under the `maintenanceids` property.
zh-cn	### 返回值  `(object)`在`maintenanceids`属性下返回包含已被删除的维护周期的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted maps under the `sysmapids` property.
zh-cn	### 返回值  返回包含"sysmapid"属性下的已删除拓扑图的IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted media types under the `mediatypeids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `mediatypeids` 属性下已删除媒介类型的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted regular expressions under the `regexpids` property.
zh-cn	### 返回数值  根据`regexpids` 的特性`(object)`会反馈一个包含已删除正则表达式的ID对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted roles under the `roleids` property.
zh-cn	### 返回值  根据`roleids`特性，`(object)` 会返回一个对象，包含删除的角色用户的ID号。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted scheduled reports under the `reportids` property.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`返回一个包含已删除的规划报告ID的对象。 

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted scripts under the `scriptids` property.
zh-cn	### 返回值  `(对象)` 返回一个`scriptids`属性包含被删除脚本ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted services under the `serviceids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids` 属性包含被删除服务ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted template dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`dashboardids`属性下已删除模板仪表盘的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已删除模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted tokens under the `tokenids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `tokenids` 属性下已删除令牌的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted trigger prototypes under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象包含在`triggerids`属性中已删除触发器原型的ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted triggers under the `triggerids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含在 `triggerids` 属性下已删除触发器 ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted user groups under the `usrgrpids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被创建用户组ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被删除用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted value maps under the `valuemapids` property.
zh-cn	### 返回值  `(object)` 返回一个包含被删除的值映射ID的对象，ID在`valuemapids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the deleted web scenarios under the `httptestids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含被删除的Web场景的ID的对象，ID在`httptestids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the unblocked users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被解锁用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated actions under the `actionids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象在 `actionids` 属性下包含更新的动作的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated correlations under the `correlationids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 “correlationids” 属性下更新的关联的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated dashboards under the `dashboardids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `dashboardids`属性下更新的仪表盘 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated discovery rules under the `druleids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含“druleids”属性下更新的发现规则的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated events under the `eventids` property.
zh-cn	### 返回值  `(object)` 返回一个对象， 该对象包含 `eventids` 属性下更新的事件 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated global macros under the `globalmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `globalmacroids` 属性（其中包含被更新全局宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graph prototypes under the `graphids` property.
zh-cn	 ### 返回值  `(object)`返回一个包含`graphids'属性下更新的图表原型的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated graphs under the `graphids` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含 `graphids` 属性下的更新图表的ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值 `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host groups under the `groupids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `groupids` 属性下的已更新主机组的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host interfaces under the `interfaceids` property.
zh-cn	### 返回值  `(object)` 在`interfaceids`属性中返回已更新主机接口ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host macros under the `hostmacroids` property.
zh-cn	### 返回值  `(object)` 返回包含 `hostmacroids` 属性（其中包含被更新主机宏的ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated host prototypes under the `hostids` property.
zh-cn	### 返回值  `(object)` 在`hostids`属性中返回包含已更新主机原型ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated hosts under the `hostids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个对象，该对象包含 `hostids` 属性下更新的主机的id。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated icon maps under the `iconmapids` property.
zh-cn	### 返回值  `(object)` 返回一个如下对象：在 `iconmapids` 属性下包含所更新的多个图标映射的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated images under the `imageids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `imageids` 属性下更新的图像的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated item prototypes under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `itemids` 属性下更新的监控项原型的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated items under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含 `itemids` 属性下更新的监控项的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated LLD rules under the `itemids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `itemids` 属性下更新的 LLD 规则的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated maintenances under the `maintenanceids` property.
zh-cn	### 返回值   `(object)`在`maintenanceids`属性中返回一个包含已被更新的维护模式的IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated maps under the `sysmapids` property.
zh-cn	### 返回值  返回一个对象，该对象包含"sysmapid"属性下更新的映射的id.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated media types under the `mediatypeids` property.
zh-cn	### 返回值  `(object)` 返回包含`mediatypeids`属性下所更新IDs的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated regular expressions under the `regexpids` property.
zh-cn	### 返回值  根据`regexpids`的特性，`(object)` 会返回一个对象，其包含已升级的正则表达式ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated roles under the `roleids` property.
zh-cn	### 返回值  根据`roleids`的特性，`(object)`返回一个包含已更新职责用户ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated scheduled reports under the `reportids` property.
zh-cn	### 返回值  根据`reportids`的特性，`(object)`返回一个包含已更新定时报表ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated scripts under the `scriptids` property.
zh-cn	### 返回值 `(对象)` 返回一个`scriptids`属性包含被更新脚本ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated services under the `serviceids` property.
zh-cn	 ### 返回值  `(对象)` 返回一个`serviceids`属性包含了被更新服务ID的对象。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated template dashboards under the `dashboardids` property.
zh-cn	### 返回值 `(object)` 返回一个对象，该对象包含`dashboardids`属性下更新的模板仪表盘的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated templates under the `templateids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，该对象包含`templateids`属性下已更新模板的ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated tokens under the `tokenids` property.
zh-cn	### 返回值  `(object)` 返回一个对象，其中包含 `tokenids` 属性下已被更新的令牌的 ID。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated trigger prototypes under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，该对象是包含在`triggerids`属性中已更新触发器原型的ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated triggers under the `triggerids` property.
zh-cn	### 返回值  `(object)`返回一个对象，其中包含 triggerids 属性下已更新的触发器的 ID.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated user groups under the `usrgrpids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`usrgrpids`属性（其中包含被更新用户组ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated users under the `userids` property.
zh-cn	### 返回值  `(object)` 返回一个带有`userids`属性（其中包含被更新用户ID）的对象.

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated value maps under the `valuemapids` property.
zh-cn	 ### 返回值  `(object)` 返回一个对象，包含被更新的值映射的ID，ID在`valuemapids`属性下。

en-us	### Return values  `(object)` Returns an object containing the IDs of the updated web scenarios under the `httptestid` property.
zh-cn	 ### 返回值  `(object)` 返回一个包含被更新Web场景的ID的对象，ID在`httptestid`属性下。

en-us	### Return values  `(object)` Returns authentication object.
zh-cn	### 返回值  `(object)` 返回认证对象。

en-us	### Return values  `(object)` Returns autoregistration object.
zh-cn	### 返回值  `(object)` 返回自动注册对象

en-us	### Return values  `(object)` Returns housekeeping object.
zh-cn	### 返回值  `(object)` 返回管家对象

en-us	### Return values  `(object)` Returns settings object.
zh-cn	 ### 返回值  `(对象)`返回设置对象。

en-us	### Return values  `(object)` Returns the result of script execution.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |response|string|Whether the script was run successfully.<br><br>Possible value - `success`.| |value|string|Script output.| |debug|object|Contains a [debug object](/manual/api/reference/script/object#Debug) if a webhook script is executed. For other script types, it contains empty object.|
zh-cn	### 返回值  `(object)` 返回脚本执行的结果。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--|--|------| |response|string|脚本是否成功运行。<br><br>可能的值 - `success`或 `failed`。| |值|字符串|脚本输出。| |debug|object|如果执行 webhook 脚本，则包含 [调试对象](/manual/api/reference/script/object#Debug)。对于其他脚本类型，它包含空对象。|

en-us	### Return values  `(string)` Returns a serialized string containing the requested configuration data.
zh-cn	### 返回值  `(string)` 返回一个包含请求配置数据的序列化字符串

en-us	### Return values  `(string)` Returns the version of the Zabbix API.  ::: notetip Starting from Zabbix 2.0.4 the version of the API matches the version of Zabbix. :::
zh-cn	### 返回值  `(string)` 返回 Zabbix API 的版本。  ::: notetip 从 Zabbix 2.0.4 版本开始，API 的版本与 Zabbix 的版本相匹配。 :::

en-us	#### RHEL  Nginx is available only in EPEL:      # dnf -y install epel-release
zh-cn	#### RHEL  Nginx仅在EPEL中可用:     # dnf -y install epel-release

en-us	# role.create
zh-cn	# 角色.创建

en-us	# role.delete
zh-cn	# 角色.删除

en-us	# role.get
zh-cn	# 角色.获取

en-us	# > Role object  The following objects are directly related to the `role` API.
zh-cn	# > 角色 对象  以下内容将详细介绍有关 `角色` API的相关功能。

en-us	# Role  This class is designed to work with user roles.  Object references:\  -   [Role](/manual/api/reference/role/object#role) -   [Role rules](/manual/api/reference/role/object#role_rules) -   [UI element](/manual/api/reference/role/object#ui_element) -   [Service](/manual/api/reference/role/object#service) -   [Service tag](/manual/api/reference/role/object#service_tag) -   [Module](/manual/api/reference/role/object#module) -   [Action](/manual/api/reference/role/object#action)  Available methods:\  -   [role.create](/manual/api/reference/role/create) - create new user     roles -   [role.delete](/manual/api/reference/role/delete) - delete user roles -   [role.get](/manual/api/reference/role/get) - retrieve user roles -   [role.update](/manual/api/reference/role/update) - update user roles
zh-cn	# 角色  该章节介绍如何使用有关角色的功能。  参照资料：\  -   [角色](zh/manual/api/reference/role/object#role) -   [角色规则](zh/manual/api/reference/role/object#role_rules) -   [UI 元素](zh/manual/api/reference/role/object#ui_element) -   [业务](zh/manual/api/reference/role/object#service) -   [业务标签](zh/manual/api/reference/role/object#service_tag) -   [模块](zh/manual/api/reference/role/object#module) -   [动作](zh/manual/api/reference/role/object#action)  支持使用的功能包括：\  -   [role.create](zh/manual/api/reference/role/create) - 创建新的用户角色 -   [role.delete](zh/manual/api/reference/role/delete) - 删除用户角色 -   [role.get](zh/manual/api/reference/role/get) - 检索用户角色 -   [role.update](zh/manual/api/reference/role/update) - 升级用户角色

en-us	# role.update
zh-cn	# 角色.更新

en-us	#### Running proxy
zh-cn	#### 运行Proxy

en-us	#### Running server
zh-cn	#### 服务进程

en-us	#### Running Zabbix get  An example of running Zabbix get under UNIX to get the processor load value from the agent:      shell> cd bin     shell> ./zabbix_get -s 127.0.0.1 -p 10050 -k system.cpu.load[all,avg1]  Another example of running Zabbix get for capturing a string from a website:      shell> cd bin     shell> ./zabbix_get -s 192.168.1.1 -p 10050 -k "web.page.regexp[www.example.com,,,\"USA: ([a-zA-Z0-9.-]+)\",,\1]"  Note that the item key here contains a space so quotes are used to mark the item key to the shell. The quotes are not part of the item key; they will be trimmed by the shell and will not be passed to Zabbix agent.  Zabbix get accepts the following command line parameters:        -s --host <host name or IP>      Specify host name or IP address of a host.       -p --port <port number>          Specify port number of agent running on the host. Default is 10050.       -I --source-address <IP address> Specify source IP address.       -t --timeout <seconds>           Specify timeout. Valid range: 1-30 seconds (default: 30 seconds).       -k --key <item key>              Specify key of item to retrieve value of.       -h --help                        Give this help.       -V --version                     Display version number.  See also [Zabbix get manpage](/manpages/zabbix_get) for more information.  Zabbix get on Windows can be run similarly:      zabbix_get.exe [options]
zh-cn	#### 运行 Zabbix get  UNIX下运行Zabbix get从agent获取处理器负载值的例子：   · shell> cd bin  · shell> ./zabbix_get -s 127.0.0.1 -p 10050 -k system.cpu.load[all,avg1]  运行 Zabbix get 以从网站捕获字符串的另一个示例：   · shell> cd bin  · shell> ./zabbix_get -s 192.168.1.1 -p 10050 -k "web.page.regexp[www.example.com,,,\"USA: ([a-zA-Z0-9.-]+)\",,\1]"  请注意，此处的监控项键包含一个空格，因此引号用于将监控项键标记到 shell。 引号不是监控项键的一部分； 它们将被 shell 修剪，不会传递给 Zabbix agent。  Zabbix get 接受以下命令行参数：   · -s --host <host name or IP> · 指定主机的主机名或 IP 地址。  · -p --port <port number> · 指定在主机上运行的agent程序的端口号。 默认值为 10050。  · -I --source-address <IP address> 指定源 IP 地址。  · -t --timeout <seconds> · 指定超时。 有效范围：1-30 秒（默认值：30 秒）。  · -k --key <item key> · 指定监控项的键以检索其值。  · -h --help · 获取帮助信息。  · -V --version · 显示版本号。  另请参阅 [Zabbix get 帮助页](/manpages/zabbix_get) 了解更多信息。  Zabbix get on Windows 可以类似运行：   · zabbix_get.exe [options]

en-us	###      Runtime control options     **config\_cache\_reload**   Reload configuration cache. Ignored if cache is being currently loaded. Active Zabbix proxy will connect to the Zabbix server and request configuration data. Default configuration file (unless **-c** option is specified) will be used to find PID file and signal will be sent to process, listed in PID file.     **snmp\_cache\_reload**   Reload SNMP cache.     **housekeeper\_execute**   Execute the housekeeper. Ignored if housekeeper is being currently executed.     **diaginfo**\[=*section*\]   Log internal diagnostic information of the specified section. Section can be *historycache*, *preprocessing*. By default diagnostic information of all sections is logged.     **log\_level\_increase**\[=*target*\]   Increase log level, affects all processes if target is not specified.     **log\_level\_decrease**\[=*target*\]   Decrease log level, affects all processes if target is not specified.  [ ]{#lbAG}
zh-cn	 ###      运行时控制选项     **config\_cache\_reload**   重新加载配置缓存。如果当前正在加载缓存，则忽略。活动的Zabbix proxy将连接到Zabbix server并请求配置数据。默认配置文件（除非指定了**-c**选项）将用于查找PID文件，并将信号发送到进程，在PID文件中列出。     **snmp\_cache\_reload**   重新加载 SNMP 缓存。     **housekeeper\_execute**   执行housekeeper。如果当前housekeeper正在被执行则忽略。     **diaginfo**\[=*section*\]   记录指定部分的内部诊断信息。节可以是*historycache*，*preprocessing*。默认情况下，记录所有部分的诊断信息。     **log\_level\_increase**\[=*target*\]   提升日志级别，如果未指定目标，则会影响所有进程。     **log\_level\_decrease**\[=*target*\]   降低日志级别，如果未指定目标，则会影响所有进程。  [ ]{#lbAG}

en-us	#### Scenario
zh-cn	#### 场景

en-us	#### Scenario step items  As soon as a step is created, Zabbix automatically adds the following items for monitoring.  |Item|Description| |----|-----------| |*Download speed for step <Step> of scenario <Scenario>*|This item will collect information about the download speed (bytes per second) of the step.<br>Item key: web.test.in\[Scenario,Step,bps\]<br>Type: *Numeric(float)*| |*Response time for step <Step> of scenario <Scenario>*|This item will collect information about the response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred.<br>Item key: web.test.time\[Scenario,Step,resp\]<br>Type: *Numeric(float)*| |*Response code for step <Step> of scenario <Scenario>*|This item will collect response codes of the step.<br>Item key: web.test.rspcode\[Scenario,Step\]<br>Type: *Numeric(unsigned)*|  Actual scenario and step names will be used instead of "Scenario" and "Step" respectively.  ::: noteclassic Web monitoring items are added with a 30 day history and a 90 day trend retention period. :::  ::: noteclassic If scenario name starts with a doublequote or contains comma or square bracket, it will be properly quoted in item keys. In other cases no additional quoting will be performed. :::  These items can be used to create triggers and define notification conditions. For example, to create a "Zabbix GUI login is too slow" trigger, you can define a trigger expression:      last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3
zh-cn	#### 场景步骤监控项  一旦创建了一个步骤，Zabbix 就会自动添加以下监控项。  |监控项|描述| |----|-----------| |*Download speed for step <Step> of scenario <Scenario>*|该监控项收集有关该步骤的下载速度（每秒字节数）的信息。<br>监控项键值：web.test.in\[Scenario,Step,bps\]<br>类型：*Numeric(float)*| |*Response time for step <Step> of scenario <Scenario>*|该监控项收集有关步骤响应时间的信息（以秒为单位）。响应时间是从请求开始到所有信息传输完毕的时间。<br>监控项键值： web.test.time\[Scenario,Step,resp\]<br>类型： *Numeric(float)*| |*Response code for step <Step> of scenario <Scenario>*|该监控项收集步骤的响应代码。<br>监控项键值： web.test.rspcode\[Scenario,Step\]<br>类型： *Numeric(unsigned)*|  将分别使用实际场景和步骤名称代替 "Scenario" 和 "Step"。  ::: noteclassic Web 监控项添加了 30 天的历史记录和 90 天的趋势数据保留时长。 :::  ::: noteclassic 如果场景名称以双引号开头或包含逗号或方括号，它将在监控项键值中正确引用。在其他情况下，将不执行额外的引用。 :::  这些监控项可用于创建触发器和定义通知条件。例如，要创建一个 "Zabbix GUI login is too slow"的触发器，可以定义一个触发器表达式：      last(/zabbix/web.test.time[ZABBIX GUI,Login,resp])>3

en-us	#### Scheduling intervals  Scheduling intervals are used to check items at specific times. While flexible intervals are designed to redefine the default item update interval, the scheduling intervals are used to specify an independent checking schedule, which is executed in parallel.  A scheduling interval is defined as: `md<filter>wd<filter>h<filter>m<filter>s<filter>` where:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` is used to specify values for its prefix (days, hours, minutes, seconds) and is defined as: `[<from>[-<to>]][/<step>][,<filter>]` where:  -   `<from>` and `<to>` define the range of matching values (included).     If `<to>` is omitted then the filter matches a `<from> - <from>`     range. If `<from>` is also omitted then the filter matches all     possible values. -   `<step>` defines the skips of the number value through the range. By     default `<step>` has the value of 1, which means that all values of     the defined range are matched.  While the filter definitions are optional, at least one filter must be used. A filter must either have a range or the *<step>* value defined.  An empty filter matches either '0' if no lower-level filter is defined or all possible values otherwise. For example, if the hour filter is omitted then only '0' hour will match, provided minute and seconds filters are omitted too, otherwise an empty hour filter will match all hour values.  Valid `<from>` and `<to>` values for their respective filter prefix are:  |Prefix|Description|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  The `<from>` value must be less or equal to `<to>` value. The `<step>` value must be greater or equal to 1 and less or equal to `<to>` - `<from>`.  Single digit month days, hours, minutes and seconds values can be prefixed with 0. For example `md01-31` and `h/02` are valid intervals, but `md01-031` and `wd01-07` are not.  In Zabbix frontend, multiple scheduling intervals are entered in separate rows. In Zabbix API, they are concatenated into a single string with a semicolon `;` as a separator.  If a time is matched by several intervals it is executed only once. For example, `wd1h9;h9` will be executed only once on Monday at 9am.  Examples:  |Interval|Will be executed| |--------|----------------| |m0-59|every minute| |h9-17/2|every 2 hours starting with 9:00 (9:00, 11:00 ...)| |m0,30 or m/30|hourly at hh:00 and hh:30| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|every five minutes| |wd1-5h9|every Monday till Friday at 9:00| |wd1-5h9-18|every Monday till Friday at 9:00,10:00,...,18:00| |h9,10,11 or h9-11|every day at 9:00, 10:00 and 11:00| |md1h9m30|every 1st day of each month at 9:30| |md1wd1h9m30|every 1st day of each month at 9:30 if it is Monday| |h9m/30|every day at 9:00, 9:30| |h9m0-59/30|every day at 9:00, 9:30| |h9,10m/30|every day at 9:00, 9:30, 10:00, 10:30| |h9-10m30|every day at 9:30, 10:30| |h9m10-40/30|every day at 9:10, 9:40| |h9,10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9-10m10-40/30|every day at 9:10, 9:40, 10:10, 10:40| |h9m10-40|every day at 9:10, 9:11, 9:12, ... 9:40| |h9m10-40/1|every day at 9:10, 9:11, 9:12, ... 9:40| |h9-12,15|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0|every day at 9:00, 10:00, 11:00, 12:00, 15:00| |h9-12,15m0s30|every day at 9:00:30, 10:00:30, 11:00:30, 12:00:30, 15:00:30| |h9-12s30|every day at 9:00:30, 9:01:30, 9:02:30 ... 12:58:30, 12:59:30| |h9m/30;h10 (*API-specific syntax*)|every day at 9:00, 9:30, 10:00| |h9m/30<br>h10 (*add this as another row in frontend*)|every day at 9:00, 9:30, 10:00|
zh-cn	#### 调度  调度用于在特定时间检查监控项。虽然默认的自定义时间间隔是灵活，但是调度常用于指定独立执行的检查计划。  调度定义为: `md<filter>wd<filter>h<filter>m<filter>s<filter>` 其中:  -   **md** - month days -   **wd** - week days -   **h** - hours -   **m** - minutes -   **s** – seconds  `<filter>` 用于指定其前缀的值(日, 时, 分, 秒) 并被定义为:: `[<from>[-<to>]][/<step>][,<filter>]` 其中:  -   `<from>` 和`<to>` 定义匹配值的范围（包括）。     如果忽略 `<to>` 则过滤器匹配 `<from> - <from>`     范围。 如果 `<from>` 也被省略，则过滤器匹配所有可能的值。 -   `<step>` 通过该范围定义数字值的跳过。默认情况下，`<step>` 的值为1，这意味着所有定义范围的值都匹配。  <step> 通过该范围定义数字值的跳过。默认情况下， <step> 的值为1，这意味着所有定义范围的值都匹配。 虽然过滤器定义是可选的，但必须至少使用一个过滤器。过滤器必须有一个范围或定义的<step>值。  如果没有定义低级别过滤器，则一个空的filter既与“0”匹配，又匹配所有可能的值。例如，如果省略小时过滤器，仅当分钟和秒的过滤器也被省略则只有“0”小时将匹配，否则空的小时过滤器将匹配所有小时值。  过滤器前缀的有效 <from> 和 <to> 值分别为：  |前缀|描述|*<from>*|*<to>*| |------|-----------|--------------|------------| |md|Month days|1-31|1-31| |wd|Week days|1-7|1-7| |h|Hours|0-23|0-23| |m|Minutes|0-59|0-59| |s|Seconds|0-59|0-59|  <from> 值必须小于或等于 <to> 值。<step> 值必须大于或等于1且小于或等于 <to> - <from>。  单个数字月份、小时、分钟和秒值可以前缀为0。例如 md01-31 和 h/02 是有效间隔，但 md01-031 和 wd01-07 无效。  在Zabbix前端，多个调度间隔以单独的行输入。在Zabbix API中，它们连接成单个字符串，以分号 ; 作为分隔符。  如果同一个时间匹配了几个间隔，则只执行一次。例如， wd1h9;h9 将在星期一上午9点执行一次。  示例:  |间隔|描述| |--------|----------------| |m0-59|每分钟执行一次| |h9-17/2|从9:00开始每2小时执行一次（9:00，11:00 ...）| |m0,30 or m/30|在每小时的hh:00 和 hh:30执行| |m0,5,10,15,20,25,30,35,40,45,50,55 or m/5|每5分钟执行| |wd1-5h9|每周一至周五9:00| |wd1-5h9-18|每个星期一到星期五在9：00,10：00，...，18:00| |h9,10,11 or h9-11|每天上午9:00，10:00和11:00| |md1h9m30|每个月的第一天在9:30| |md1wd1h9m30|如果是星期一，每个月的第一天在9:30执行| |h9m/30|在9:00，9:30执行| |h9m0-59/30|在9:00，9:30执行| |h9,10m/30|在9:00，9:30，10:00，10:30执行| |h9-10m30|在9:30，10:30执行| |h9m10-40/30|在9:10，9:40执行| |h9,10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9-10m10-40/30|在9:10，9:40，10:10，10:40执行| |h9m10-40|在9:10，9:11，9:12，... 9:40执行| |h9m10-40/1|在9:10，9:11，9:12，... 9:40执行| |h9-12,15|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0|在9:00，10:00，11:00，12:00，15:00执行| |h9-12,15m0s30|在上午9时30分，上午10时30分，11时30分，12时30分，15时30分执行| |h9-12s30|在9:00:30，9:01:30，9:02:30 ... 12:58:30，12:59:30执行| |h9m/30;h10 (*API-指定语法*)|在9:00，9:30，10:00执行| |h9m/30<br>h10 (*在前端的另一行添加*)|在9:00，9:30，10:00执行|

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

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

en-us	# script.execute
zh-cn	# 执行

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

en-us	# script.getscriptsbyhosts
zh-cn	# 通过主机获取脚本

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

en-us	#### Scripts  Configure and execute scripts to help you with your daily tasks.  [Script API](/manual/api/reference/script)
zh-cn	#### 脚本  配置和执行脚本以帮助您完成日常任务。  [Script API](/manual/api/reference/script)

en-us	# Script  This class is designed to work with scripts.  Object references:\  -   [Script](/manual/api/reference/script/object#script) -   [Webhook     parameters](/manual/api/reference/script/object#webhook_parameters) -   [Debug](/manual/api/reference/script/object#debug) -   [Log entry](/manual/api/reference/script/object#log_entry)  Available methods:\  -   [script.create](/manual/api/reference/script/create) - create new     scripts -   [script.delete](/manual/api/reference/script/delete) - delete     scripts -   [script.execute](/manual/api/reference/script/execute) - run scripts -   [script.get](/manual/api/reference/script/get) - retrieve scripts -   [script.getscriptsbyhosts](/manual/api/reference/script/getscriptsbyhosts) -     retrieve scripts for hosts -   [script.update](/manual/api/reference/script/update) - update     scripts
zh-cn	 # 脚本  此类为使用脚本而设计。 参考对象:\  -   [脚本](/manual/api/reference/script/object#脚本) -   [Webhook参数](/manual/api/reference/script/object#Webhook_参数) -   [调试](/manual/api/reference/script/object#调试) -   [日志条目](/manual/api/reference/script/object#日志_条目)  可用方法:\  -   [script.create](/manual/api/reference/script/create) - 创建新脚本 -   [script.delete](/manual/api/reference/script/delete) - 删除脚本 -   [script.execute](/manual/api/reference/script/execute) - 运行脚本 -   [script.get](/manual/api/reference/script/get) - 检索脚本 -   [script.getscriptsbyhosts](/manual/api/reference/script/getscriptsbyhosts) -     通过主机检索脚本 -   [script.update](/manual/api/reference/script/update) - 更新脚本

en-us	#### Script timeout
zh-cn	#### 脚本超时

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

en-us	### See also  1.  [Additional details about memory calculation in different     OS](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size)
zh-cn	### 参见  1.[关于不同操作系统内存计算的详细信息](http://blog.zabbix.com/when-alexei-isnt-looking#vm.memory.size)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
zh-cn	### 参见  -   [动作过滤](object#动作过滤) -   [动作操作](object#动作操作)

en-us	### See also  -   [Action filter](object#action_filter) -   [Action operation](object#action_operation)
zh-cn	### 参见  -   [动作过滤](object#动作过滤) -   [动作操作](object#动作操作)

en-us	### See also  -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)
zh-cn	### 参见  -   [告警](/manual/api/reference/alert/object) -   [监控项](/manual/api/reference/item/object) -   [主机](/manual/api/reference/host/object) -   [自动发现规则](/manual/api/reference/discoveryrule/object#lld规则) -   [触发器](/manual/api/reference/trigger/object)

en-us	### See also  -   [Alert](/manual/api/reference/alert/object) -   [Item](/manual/api/reference/item/object) -   [Host](/manual/api/reference/host/object) -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule) -   [Trigger](/manual/api/reference/trigger/object)
zh-cn	### 参见  -   [告警](/manual/api/reference/alert/object) -   [监控项](/manual/api/reference/item/object) -   [主机](/manual/api/reference/host/object) -   [LLD规则](/manual/api/reference/discoveryrule/object#lld_rule) -   [触发器](/manual/api/reference/trigger/object)

en-us	### See also  -   [Audit log object](/manual/api/reference/auditlog/object)
zh-cn	### 参见  -   [审计日志对象](/manual/api/reference/auditlog/object)

en-us	### See also  -   [Authentication](/manual/api/reference/authentication)
zh-cn	### 参考  -   [认证](/manual/api/reference/authentication)

en-us	### See also  -   [Authentication](/manual/api/reference/authentication) -   [Media](/manual/api/reference/user/object#media) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)
zh-cn	### 参考  -   [认证](/manual/api/reference/authentication) -   [媒介](/manual/api/reference/user/object#media) -   [用户组](/manual/api/reference/usergroup/object#user_group) -   [角色](/manual/api/reference/role/object#role)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Correlation filter](object#correlation_filter) -   [Correlation operation](object#correlation_operation)
zh-cn	### 参见  -   [关联过滤](object#关联过滤) -   [关联操作](object#关联操作)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Dashboard page](object#dashboard_page) -   [Dashboard widget](object#dashboard_widget) -   [Dashboard widget field](object#dashboard_widget_field) -   [Dashboard user](object#dashboard_user) -   [Dashboard user group](object#dashboard_user_group)
zh-cn	### 参阅  -   [仪表盘页面](object#仪表盘页面) -   [仪表盘部件](object#仪表盘部件) -   [仪表盘部件字段](object#仪表盘部件字段) -   [仪表盘用户](object#仪表盘用户) -   [仪表盘用户组](object#仪表盘用户组)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovered host](/manual/api/reference/dhost/object#发现主机) -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovered     host](/manual/api/reference/dhost/object#discovered_host) -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check) -   [Host](/manual/api/reference/host/object#host)
zh-cn	 ### 参见  -   [Discovered     host](/manual/api/reference/dhost/object#发现主机) -   [Discovery     check](/manual/api/reference/dcheck/object#发现检查) -   [Host](/manual/api/reference/host/object#主机)

en-us	### See also  -   [Discovered     service](/manual/api/reference/dservice/object#discovered_service) -   [Discovery rule](/manual/api/reference/drule/object#discovery_rule)
zh-cn	### 参见  -   [发现服务](/manual/api/reference/dservice/object#discovered_service) -   [发现规则](/manual/api/reference/drule/object#discovery_rule)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovery     check](/manual/api/reference/dcheck/object#discovery_check)
zh-cn	 ### 参见  -   [Discovery check](/manual/api/reference/dcheck/object#发现检查)

en-us	### See also  -   [Discovery rule](/manual/api/reference/discoveryrule/object#discovery_rule) -   [Graph](/manual/api/reference/graph/object#graph) -   [Host](/manual/api/reference/host/object#host) -   [Host interface](/manual/api/reference/hostinterface/object#host_interface) -   [Trigger](/manual/api/reference/trigger/object#trigger)
zh-cn	### 另请参阅  -   [发现规则](/manual/api/reference/discoveryrule/object#discovery_rule) -   [图表](/manual/api/reference/graph/object#graph) -   [主机](/manual/api/reference/host/object#host) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface) -   [触发器](/manual/api/reference/trigger/object#trigger)

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8)  ------------------------------------------------------------------------  [ ]{#index}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8)  ------------------------------------------------------------------------  [ ]{#index}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}
zh-cn	## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAH}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAJ}
zh-cn	＃＃ 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(1), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8) [ ]{#lbAJ}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_get](zabbix_get)**(8), **[zabbix\_js](zabbix_js)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(8), **[zabbix\_server](zabbix_server)**(8) [ ]{#lbAI}

en-us	## SEE ALSO  Documentation <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAI}
zh-cn	 ## 另请参见  文档 <https://www.zabbix.com/manuals>  **[zabbix\_agentd](zabbix_agentd)**(8), **[zabbix\_proxy](zabbix_proxy)**(8), **[zabbix\_sender](zabbix_sender)**(1), **[zabbix\_server](zabbix_server)**(8), **[zabbix\_js](zabbix_js)**(1), **[zabbix\_agent2](zabbix_agent2)**(8), **[zabbix\_web\_service](zabbix_web_service)**(8) [ ]{#lbAI}

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
zh-cn	### 另见  -   [图表监控项](/manual/api/reference/graphitem/object#图表监控项)

en-us	### See also  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)
zh-cn	 ### 另见  -   [图表监控项](/manual/api/reference/graphitem/object#graph_item)

en-us	### See also  -   [Graph](/manual/api/reference/graph/object#graph)
zh-cn	 ### 另见  -   [图表](/manual/api/reference/graph/object#图表)

en-us	### See also  -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Host](/manual/api/reference/host/object#host) -   [Item prototype](/manual/api/reference/itemprototype/object#item_prototype) -   [LLD rule filter](object#lld_rule_filter) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [图形原型](/manual/api/reference/graphprototype/object#图形原型) - [主机](/manual/api/reference/host/object#主机) - [监控项原型](/manual/api/reference/itemprototype/object#监控项原型) - [LLD规则过滤](object#lld-规则过滤器) - [触发器原型](/manual/api/reference/triggerprototype/object#触发器原型)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [Host prototype tag](object#host_prototype_tag) -   [Custom interface](object#custom_interface) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参考  -   [Group link](object#group_link) -   [Group prototype](object#group_prototype) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [hostinterface.create](create) -   [host.massadd](/manual/api/reference/host/massadd) -   [Host](/manual/api/reference/host/object#host)
zh-cn	### 参考  -   [主机接口创建](create) -   [主机接口批量添加](/manual/api/reference/host/massadd) -   [主机](/manual/api/reference/host/object#host)

en-us	### See also  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)
zh-cn	### 参考  -   [hostinterface.delete](delete) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)
zh-cn	### 参考  -   [hostinterface.massadd](massadd) -   [host.massadd](/manual/api/reference/host/massadd)

en-us	### See also  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)
zh-cn	### 参考  -   [hostinterface.massremove](massremove) -   [host.massremove](/manual/api/reference/host/massremove)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Graph prototype](/manual/api/reference/graphprototype/object#graph_prototype) -   [Trigger prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)
zh-cn	### 参见  - [主机](/manual/api/reference/host/object#host) - [图形原型](/manual/api/reference/graphprototype/object#graph_prototype) - [触发器原型](/manual/api/reference/triggerprototype/object#trigger_prototype)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Time period](object#time_period)
zh-cn	### 参见  - [主机](/manual/api/reference/host/object#host) - [主机组](/manual/api/reference/hostgroup/object#host_group) - [时间段](object#time_period)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Item](/manual/api/reference/item/object#item)
zh-cn	### 参考  -   [主机](/manual/api/reference/host/object#host) -   [监控项](/manual/api/reference/item/object#item)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#主机) -   [媒介类型](/manual/api/reference/mediatype/object#媒介类型) -   [用户](/manual/api/reference/user/object#用户)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#host) -   [proxy接口](object#proxy_interface)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -   [主机](/manual/api/reference/host/object#主机) -   [代理接口](object#代理接口)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Proxy interface](object#proxy_interface)
zh-cn	### 参见  -  [主机](/manual/api/reference/host/object#host) -  [proxy接口](object#proxy_interface)

en-us	### See also  -   [Host](/manual/api/reference/host/object#host) -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Host](/manual/api/reference/host/object#主机) -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Host](/manual/api/reference/host/object#object_details) -   [Host group](/manual/api/reference/hostgroup/object#object_details)
zh-cn	### 另外参考 -   [主机](/manual/api/reference/host/object#对象_详情) -   [主机组](/manual/api/reference/hostgroup/object#对象_详情)

en-us	### See also  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)
zh-cn	### 参考  -   [host.update](/manual/api/reference/host/update) -   [host.massupdate](/manual/api/reference/host/massupdate)

en-us	### See also  -   [host.update](update) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#template) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	 ### 另请参阅  -   [主机更新](update) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#template) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [host.massadd](massadd) -   [host.massremove](massremove) -   [Host group](/manual/api/reference/hostgroup/object#host_group) -   [Template](/manual/api/reference/template/object#host_group) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 另请参阅  -   [主机更新](update) -   [主机批量创建](massadd) -   [主机批量删除](massremove) -   [主机组](/manual/api/reference/hostgroup/object#host_group) -   [模板](/manual/api/reference/template/object#host_group) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [host.update](update) -   [User     macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)
zh-cn	### 另请参阅  -   [主机更新](update) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro) -   [主机接口](/manual/api/reference/hostinterface/object#host_interface)

en-us	### See also  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	 ### 参见  -   [图标映射](object#icon_mapping)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	### 参阅  -   [图标映射关系（Icon mapping）](object#icon_mapping)

en-us	### See also  -   [Icon mapping](object#icon_mapping)
zh-cn	### 参阅  -   [图标映射关系（Icon mapping）](object#icon_mapping)

en-us	### See also  -   [LLD rule filter](object#lld_rule_filter) -   [LLD macro paths](object#lld_macro_path) -   [LLD rule preprocessing](object#lld_rule_preprocessing)
zh-cn	### 参见  -   [LLD规则过滤](object#lld-规则过滤器) -   [LLD宏路径](object#lld宏路径) -   [LLD规则预处理](object#lld-规则预处理)

en-us	### See also  -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shape](object#map_shapes) -   [Map line](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Map element](object#map_element) -   [Map link](object#map_link) -   [Map URL](object#map_url) -   [Map user](object#map_user) -   [Map user group](object#map_user_group) -   [Map shapes](object#map_shapes) -   [Map lines](object#map_lines)
zh-cn	### 查看相关  -   [拓扑图元素](object#map_element) -   [拓扑图关联](object#map_link) -   [拓扑图URL](object#map_url) -   [拓扑图用户](object#map_user) -   [拓扑图用户组](object#map_user_group) -   [拓扑图形状](object#map_shapes) -   [拓扑图线](object#map_lines)

en-us	### See also  -   [Media](/manual/api/reference/user/object#media) -   [Media type](/manual/api/reference/mediatype/object#media_type) -   [User group](/manual/api/reference/usergroup/object#user_group) -   [Role](/manual/api/reference/role/object#role)
zh-cn	### 参考  -   [媒介](/manual/api/reference/user/object#media) -   [媒介类型](/manual/api/reference/mediatype/object#media_type) -   [用户组](/manual/api/reference/usergroup/object#user_group) -   [角色](/manual/api/reference/role/object#role)

en-us	### See also  -   [Permission](object#permission)
zh-cn	### 参考  -   [权限](object#permission)

en-us	### See also  -   [Permission](object#permission)
zh-cn	### 参考  -   [权限](object#permission)

en-us	### See also  -   [Role rules](/manual/api/reference/role/object#role_rules) -   [User](/manual/api/reference/user/object#user)
zh-cn	### 另请参考  -   [角色规则](/manual/api/reference/role/object#role_rules) -   [用户](/manual/api/reference/user/object#user)

en-us	### See also  -   [Role rules](object#role_rules) -   [UI element](object#ui_element) -   [Module](object#module) -   [Action](object#action)
zh-cn	### 另见  -   [Role rules](object#role_rules) -   [UI element](object#ui_element) -   [Module](object#module) -   [Action](object#action)

en-us	### See also  -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Scenario step](object#scenario_step)
zh-cn	 ### 参见  -   [Scenario step](object#场景步骤)

en-us	### See also  -   [Task](/manual/api/reference/task/object) -   [Statistic result object](/manual/api/reference/task/object#statistic_result_object)
zh-cn	### 参阅  -   [任务](/manual/api/reference/task/object) -   [统计结果对象](/manual/api/reference/task/object#statistic_result_object)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘页面](object#template_dashboard_page) -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [Template dashboard page](object#template_dashboard_page) -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘页面](object#template_dashboard_page) -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [Template dashboard widget](object#template_dashboard_widget) -   [Template dashboard widget     field](object#template_dashboard_widget_field)
zh-cn	### 参阅  -   [模版仪表盘组件](object#template_dashboard_widget) -   [模版仪表盘组件字段](object#template_dashboard_widget_field)

en-us	### See also  -   [template.update](update) -   [User macro](/manual/api/reference/usermacro/object#hosttemplate_level_macro)
zh-cn	### 参阅  -   [更新模板](update) -   [用户宏](/manual/api/reference/usermacro/object#hosttemplate_level_macro)

en-us	### See also  -   [Time period](object#time_period)
zh-cn	### 另见  -   [Time period](object#time_period)

en-us	### See also  -   [Time period](object#time_period)
zh-cn	 ### 参见  - [时间段](object#time_period)

en-us	### See also  -   [user.login](login)
zh-cn	### 参考  -   [登录](login)

en-us	### See also  -   [user.logout](logout)
zh-cn	### 参考  -   [注销](logout)

en-us	### See also  -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参见  -   [用户](/manual/api/reference/user/object#用户)

en-us	### See also  -   [User](/manual/api/reference/user/object#user)
zh-cn	### 参考  -   [用户](/manual/api/reference/user/object#user)

en-us	### See also  -   [Users](/manual/api/reference/user/object#users) -   [User groups](/manual/api/reference/user/object#user_groups)
zh-cn	### 另请参考  -   [用户](zh/manual/api/reference/user/object#users) -   [用户组](zh/manual/api/reference/user/object#user_groups)

en-us	### See also  -   [Users](object#users) -   [User groups](object#user_groups)
zh-cn	### 另请参考  -   [用户](object#users) -   [用户组](object#user_groups)

en-us	### See also  -   [Users](object#users) -   [User groups](object#user_groups)
zh-cn	### 另请参考  -   [用户](object#users) -   [用户组](object#user_groups)

en-us	#### See also  -   [Zabbix blog article on SNMP     traps](https://blog.zabbix.com/snmp-traps-in-zabbix) -   [Configuring snmptrapd (official net-snmp documentation)](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd) -   [Configuring snmptrapd to receive SNMPv3 notifications (official net-snmp documentation)](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications)
zh-cn	#### 请参阅  - · [关于SNMP traps的Zabbix博客文章](https://blog.zabbix.com/snmp-traps-in-zabbix) - · [配置snmptrapd（net-snmp官方文档）](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd) - · [配置snmptrapd接收SNMPv3通知（net-snmp官方文档）](https://net-snmp.sourceforge.io/wiki/index.php/TUT:Configuring_snmptrapd_to_receive_SNMPv3_notifications)

en-us	#### Selecting a language  There are several ways to select a language in Zabbix web interface:  -   When installing web interface - in the frontend [installation     wizard](/manual/installation/frontend#welcome_screen). Selected     language will be set as system default. -   After the installation, system default language can be changed in     the *Administration→General→GUI* [menu     section](/manual/web_interface/frontend_sections/administration/general#gui). -   Language for a particular user can be changed in the [user     profile](/manual/web_interface/user_profile#user_profile).  If a locale for a language is not installed on the machine, this language will be greyed out in Zabbix language selector. A red icon is displayed next to the language selector if at least one locale is missing. Upon pressing on this icon the following message will be displayed: "You are not able to choose some of the languages, because locales for them are not installed on the web server."  ![locale\_warning.png](../../../../assets/en/manual/appendix/install/locale_warning.png){width="600"}
zh-cn	#### 选择语言  有几种方法可以在Zabbix Web界面中选择语言：  -   安装 Web 界面时 - 在前端 [installation wizard](/manual/installation/frontend#welcome_screen) 中。选择的语言将被设置为系统默认值。 -   安装完成后，系统默认语言可以在 *Administration→General→GUI* [menu section](/manual/web_interface/frontend_sections/administration/general#gui) 找到. -   特定用户的语言可以在 [user profile](/manual/web_interface/user_profile#user_profile)找到.  如果计算机上未安装某种语言的区域设置，则此语言将在 Zabbix 语言选择器中显示为灰色。如果没有一个可用的区域设置，则在语言选择器旁边显示一个红色图标。按下此图标后，将显示以下消息：“您无法选择某些语言，因为Web服务器上未安装它们。”  ![locale\_warning.png](../../../../assets/en/manual/appendix/install/locale_warning.png){width="600"}

en-us	#### Selecting elements  To select elements, select one and then hold down *Ctrl* to select the others.  You can also select multiple elements by dragging a rectangle in the editable area and selecting all elements in it.  Once you select more than one element, the element property form shifts to the mass-update mode so you can change attributes of selected elements in one go. To do so, mark the attribute using the checkbox and enter a new value for it. You may use macros here (for example, {HOST.NAME} for the element label).  ![](../../../../../assets/en/manual/config/visualization/map_update.png){width="600"}
zh-cn	#### 选择元素  要选择元素，请选择一个，然后按住 *Ctrl* 选择其他。  您还可以通过在可编辑区域并选择其中的所有元素。  一旦选择了多个元素，元素属性形式就会发生变化到批量更新模式，以便您可以更改选定的属性元素一气呵成。为此，请使用复选框标记属性，然后为其输入一个新值。您可以在此处使用宏（例如，{HOST.NAME} 用于元素标签）。  ![](../../../../../assets/en/manual/config/visualization/map_update.png){width="600"}

en-us	#### SELinux configuration Zabbix uses socket-based inter-process communication. On systems where SELinux is enabled, it may be required to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the SocketDir directory. Currently socket files are used by server (alerter, preprocessing, IPMI) and proxy (IPMI). Socket files are persistent, meaning they are present while the process is running.  Having SELinux status enabled in enforcing mode, you need to execute the following commands to enable communication between Zabbix frontend and server:  RHEL 7 and later:      # setsebool -P httpd_can_connect_zabbix on     If the database is accessible over network (including 'localhost' in case of PostgreSQL), you need to allow Zabbix frontend to connect to the database too:     # setsebool -P httpd_can_network_connect_db on  RHEL prior to 7:      # setsebool -P httpd_can_network_connect on     # setsebool -P zabbix_can_network on  After the frontend and SELinux configuration is done, restart the Apache web server:      # service httpd restart
zh-cn	#### SELinux 配置 Zabbix 使用基于套接字的进程间通信。 在启用 SELinux 的系统上，可能需要添加 SELinux 规则以允许 Zabbix 在 SocketDir 目录中创建/使用 UNIX 域套接字。 当前套接字文件由服务器（告警器、预处理、IPMI）和代理（IPMI）使用。 套接字文件是持久的，这意味着它们在进程运行时存在。  在强制模式下启用 SELinux 状态后，您需要执行以下命令以启用 Zabbix 前端和服务器之间的通信：  RHEL 7 及更高版本：    · # setsebool -P httpd_can_connect_zabbix on   · 如果可以通过网络访问数据库（包括 PostgreSQL 中的“localhost”），您也需要允许 Zabbix 前端连接到数据库：   · # setsebool -P httpd_can_network_connect_db on  7 之前的 RHEL：    · # setsebool -P httpd_can_network_connect on   · # setsebool -P zabbix_can_network on  前端和 SELinux 配置完成后，重启 Apache Web 服务器：   · # service httpd restart

en-us	##### Sending in data  In the simplest of cases, we may use [zabbix\_sender](/manual/concepts/sender) utility to send in some 'test value':      zabbix_sender -z <server IP address> -p 10051 -s "New host" -k trap -o "test value"  To send in the value we use these keys:  *-z* - to specify Zabbix server IP address  *-p* - to specify Zabbix server port number (10051 by default)  *-s* - to specify the host (make sure to use the 'technical' [host name](/manual/config/hosts/host#configuration) here, instead of the 'visible' name)  *-k* - to specify the key of the item we just defined  *-o* - to specify the actual value to send  ::: noteimportant Zabbix trapper process does not expand macros used in the item key in attempt to check corresponding item key existence for targeted host. :::
zh-cn	##### 数据发送  在最简单的情况下，我们可以使用 [zabbix\_sender](/manual/concepts/sender)程序来发送一些“测试值”：      zabbix_sender -z <server IP address> -p 10051 -s "New host" -k trap -o "test value"  我们使用下列这些关键字来指定发送值  *-z* - 指定Zabbix server的IP地址  *-p* - 指定Zabbix server的端口（默认为10051）  *-s* -指定主机（请确保在此使用“主机名称”的[主机名](/manual/config/hosts/host#configuration) ，而不是“可见的名称”名称）  *-k* - 指定我们之前定义的监控项的键值  *-o* - 指定要发送的实际值  ::: noteimportant  Zabbix trapper进程不会扩展监控项键值中使用的宏，以检查目标主机对应的监控项键值是否存在。 :::

en-us	##### Server configuration  By default, the Zabbix server is not configured to start any IPMI pollers, thus any added IPMI items won't work. To change this, open the Zabbix server configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) as root and look for the following line:      # StartIPMIPollers=0  Uncomment it and set poller count to, say, 3, so that it reads:      StartIPMIPollers=3  Save the file and restart zabbix\_server afterwards.
zh-cn	 ##### 服务器配置  默认情况下，Zabbix服务器未配置为启动任何IPMI轮询，因此任何添加的IPMI监控项将无法正常工作。要更改此选项，请以root身份打开Zabbix服务器配置文件([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) 并查找以下行:      # StartIPMIPollers=0  取消注释，并设置 IPMI Poller 计数为3，如下:      StartIPMIPollers=3  保存文件，然后重启 zabbix\_server 。

en-us	#### Server is configured to connect with PSK to agent but agent accepts only unencrypted connections  In server or proxy log (with *GnuTLS* 3.3.16)      Get value from agent failed: zbx_tls_connect(): gnutls_handshake() failed: \         -110 The TLS connection was non-properly terminated.  In server or proxy log (with *OpenSSL* 1.0.2c)      Get value from agent failed: TCP connection successful, cannot establish TLS to [[127.0.0.1]:10050]: \         Connection closed by peer. Check allowed connection types and access rights
zh-cn	#### Server配置为使用 PSK 连接到agent，但agent仅接受未加密的连接  在server或proxy日志中有如下显示 (对于 *GnuTLS* 3.3.16)      Get value from agent failed: zbx_tls_connect(): gnutls_handshake() failed: \         -110 The TLS connection was non-properly terminated.  在server或proxy日志中有如下显示 (对于 *OpenSSL* 1.0.2c)      Get value from agent failed: TCP connection successful, cannot establish TLS to [[127.0.0.1]:10050]: \         Connection closed by peer. Check allowed connection types and access rights

en-us	#### Server  To enable encryption with certificate and database host identity verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_full     DBTLSCAFile=/etc/ssl/pgsql/root.crt     DBTLSCertFile=/etc/ssl/pgsql/client.crt     DBTLSKeyFile=/etc/ssl/pgsql/client.key     ...
zh-cn	#### 服务端  要使用证书和数据库主机身份验证为Zabbix服务器和数据库之间的连接启用加密，请配置该文件 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_full     DBTLSCAFile=/etc/ssl/pgsql/root.crt     DBTLSCertFile=/etc/ssl/pgsql/client.crt     DBTLSKeyFile=/etc/ssl/pgsql/client.key     ...

en-us	#### Server  To enable encryption with certificate verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/mysql/ca.pem     ...
zh-cn	#### 服务端  要为Zabbix服务器和数据库之间的连接启用加密和证书验证，请配置 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/mysql/ca.pem     ...

en-us	#### Server  To enable encryption with certificate verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf:*      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/pgsql/root.crt     ...
zh-cn	#### 服务端  要为Zabbix服务端和数据库之间的连接启用加密和证书验证，请配置*/etc/zabbix/zabbix\_server.conf:*       ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_ca     DBTLSCAFile=/etc/ssl/pgsql/root.crt     ...

en-us	#### Server  To enable encryption with full verification for connections between Zabbix server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=verify_full     DBTLSCAFile=/etc/ssl/mysql/ca.pem     DBTLSCertFile=/etc/ssl/mysql/client-cert.pem     DBTLSKeyFile=/etc/ssl/mysql/client-key.pem     ...
zh-cn	#### 服务端  要为Zabbix服务端和数据库之间启用加密连接并进行完全验证，请配置 */etc/zabbix/zabbix\_server.conf*:   ...  DBHost=10.211.55.9  DBName=zabbix  DBUser=zbx_srv  DBPassword=<strong_password>  DBTLSConnect=verify_full  DBTLSCAFile=/etc/ssl/mysql/ca.pem  DBTLSCertFile=/etc/ssl/mysql/client-cert.pem  DBTLSKeyFile=/etc/ssl/mysql/client-key.pem  ...

en-us	#### Server  To enable transport-only encryption for connections between server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...
zh-cn	#### 服务端 请配置下面的参数来启用 Zabbix 前端和数据库之间的仅传输加密连接：      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...   

en-us	#### Server  To enable transport-only encryption for connections between server and the database, configure */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...
zh-cn	#### 服务端  要为服务端和数据库之间启用连接传输加密，请修改该文件 */etc/zabbix/zabbix\_server.conf*:      ...     DBHost=10.211.55.9     DBName=zabbix     DBUser=zbx_srv     DBPassword=<strong_password>     DBTLSConnect=required     ...     

en-us	##### Server  [Zabbix server](/manual/concepts/server) is the central component to which agents report availability and integrity information and statistics. The server is the central repository in which all configuration, statistical and operational data are stored.
zh-cn	##### Server  [Zabbix server](/manual/concepts/server) 是 agents 向其报告可用性和完整性信息和统计信息的中心组件。server 是存储所有配置、统计和操作数据的中央存储库。

en-us	# service.create
zh-cn	# 创建服务

en-us	# service.delete
zh-cn	 # service.delete

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

en-us	#### Service Level Agreement  Define Service Level Objectives (SLO), retrieve detailed Service Level Indicators (SLI) information about service performance.  [SLA API](/manual/api/reference/sla)
zh-cn	#### 服务水平协议  定义服务级别目标 （SLO），检索有关服务性能的详细服务级别指示器 （SLI） 信息。  [SLA API](/manual/api/reference/sla)

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

en-us	 ### Services  In older Zabbix versions, services had two types of dependencies: soft and hard. After an upgrade, all dependencies will become equal.   If a service "Child service" has been previously linked to "Parent service 1" via hard dependency and additionally "Parent service 2" via soft dependency, after an upgrade the "Child service" will have two parent services "Parent service 1" and "Parent service 2".  Trigger-based mapping between problems and services has been replaced by tag-based mapping. In Zabbix 6.0 and newer, service configuration form has a new parameter *Problem tags*, which allows specifying one or multiple tag name and value pairs for problem matching.  Triggers that have been linked to a service will get a new tag `ServiceLink` : `<trigger ID>:<trigger name>` (tag value will be truncated to 32 characters). Linked services will get `ServiceLink` [problem tag](/manual/it_services/service_tree#problem-tags) with the same value.
zh-cn	 ### 服务  在旧的 Zabbix 版本中，服务有两种类型的依赖：软依赖和硬依赖。 升级后，所有依赖项都将变得相同。  如果一个服务的“子服务”先前已通过硬依赖关系链接到“父级服务 1”并通过软依赖关系另外链接到“父级服务 2”，则升级后“子服务”将有两个父级服务“父级服务 1”和 "父级服务2"。  问题和服务之间基于触发器的映射已被基于标签的映射所取代。 在 Zabbix 6.0 及更新版本中，服务配置表单有一个新参数 *问题标签*，它允许指定一个或多个标签名称和值对用于问题匹配。 · 已链接到服务的触发器将获得一个新标签 `ServiceLink` ：`<trigger ID>:<trigger name>`（标签值将被截断为 32 个字符）。 链接服务将获得具有相同值的“ServiceLink”[问题标签](/manual/it_services/service_tree#problem-tags)。

en-us	#### Services  Manage services for service-level monitoring and retrieve detailed SLA information about any service.  [Service API](/manual/api/reference/service)
zh-cn	#### 服务  管理服务以进行服务级别监视，并检索有关任何服务的详细 SLA 信息。  [Service API](/manual/api/reference/service)

en-us	 ### Service tree  The next step is to build the service tree. In this example, the infrastructure is very basic and consists of three services: *Zabbix cluster* (parent) and two child services *Zabbix server node 1* and *Zabbix server node 2*.        Zabbix cluster     |     |- Zabbix server node 1     |- Zabbix server node 2  At the Services page, turn on *Edit* mode and press Create service:  ![](../../../assets/en/manual/config/service_mode.png){class="nozoom"}  In the service configuration window, enter name *Zabbix cluster* and mark the checkbox *Advanced configuration*.   ![](../../../assets/en/manual/config/service_cluster.png){width=600}  Configure additional rule:  ![](../../../assets/en/manual/config/service_add_rule.png){width=600}  Zabbix cluster will have two child services - one for each of the HA nodes. If both HA nodes have problems of at least *Warning* status,  parent service status should be set to *Disaster*. To achieve this, additional rule should be configured as:  - Set status to: Disaster - Condition: If at least `N` child services have `Status` status or above - N: 2 - Status: Warning  Switch to the *Tags* tab and add a tag `Zabbix:server`. This tag will be used later for service actions and SLA reports.  ![](../../../assets/en/manual/config/service_cluster1.png){width=600}  Save the new service. 
zh-cn	 ### 服务树  下一步是建立服务树。在此示例中，只包含基础的设置以及三个服务： *Zabbix cluster* (父) 和两个子服务 *Zabbix server node 1* 和*Zabbix server node 2*.        Zabbix cluster     |     |- Zabbix server node 1     |- Zabbix server node 2  在服务页面，打开 *编辑* 模式并点击创建服务：  ![](../../../assets/en/manual/config/service_mode.png){class="nozoom"}  在服务配置窗口中，输入名称*Zabbix cluster* 并选取检查框*高级配置*。  ![](../../../assets/en/manual/config/service_cluster.png){width=600}  配置额外规则：  ![](../../../assets/en/manual/config/service_add_rule.png){width=600}  Zabbix集群需要两个子服务 - 用于各自的HA节点。如果两个HA节点均产生至少为*警告* 级别的告警信息，父服务的状态将设置为*灾难*。要实现上述需求，需要配置如下的额外规则：  - 设置状态为：灾难 - 条件：如果至少 `N` 个子服务有`状态` 状态或以上 - N: 2 - 状态: 警告  切换到*标签* 界面并添加标签 `Zabbix:server`。此标签后续会用于服务动作和SLA报告。  ![](../../../assets/en/manual/config/service_cluster1.png){width=600}  保存新建的服务。

en-us	# service.update
zh-cn	 # service.update

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

en-us	# > Settings object  The following objects are directly related to the `settings` API.
zh-cn	 # > 设置对象  以下对象都是与`settings` 直接相关的API。

en-us	# Settings  This class is designed to work with common administration settings.  Object references:\  -   [Settings](/manual/api/reference/settings/object#settings)  Available methods:\  -   [settings.get](/manual/api/reference/settings/get) - retrieve     settings -   [settings.update](/manual/api/reference/settings/update) - update     settings
zh-cn	 # 设置  此类为进行常用管理设置而设计。  参考对象:\  -   [设置](/manual/api/reference/settings/object#设置)  可用办法\  -   [settings.get](/manual/api/reference/settings/get) - 检索设置 -   [settings.update](/manual/api/reference/settings/update) - 更新设置

en-us	# settings.update
zh-cn	 # settings.update

en-us	#### Setup wizard on SUSE with NGINX and php-fpm  Frontend setup wizard cannot save configuration file on SUSE with NGINX + php-fpm. This is caused by a setting in /usr/lib/systemd/system/php-fpm.service unit, which prevents Zabbix from writing to /etc. (introduced in [PHP 7.4](https://bugs.php.net/bug.php?id=72510)).  There are two workaround options available:  -   Set the     [ProtectSystem](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectSystem=)     option to 'true' instead of 'full' in the php-fpm systemd unit. -   Manually save /etc/zabbix/web/zabbix.conf.php file.
zh-cn	#### 使用 NGINX 和 php-fpm 在 SUSE 上设置向导  在 SUSE 上使用 NGINX + php-fpm，前端设置向导将无法保存配置文件。这是由 /usr/lib/systemd/system/php-fpm.service 单元中的设置引起的，该设置阻止 Zabbix 写入 /etc。 (在 [PHP 7.4 中引入](https://bugs.php.net/bug.php?id=72510)).。  有两种解决方法可供选择：  -   在 php-fpm systemd 单元中将 [ProtectSystem](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectSystem=) 选项设置为 'true' 而不是 'full'。 -   手动保存 /etc/zabbix/web/zabbix.conf.php 文件。

en-us	 ### SLA  In this example, expected Zabbix cluster performance is 100% excluding semi-annual one hour maintenance period.     First, you need to add a new service level agreement.   Go to the *Services->SLA* menu section and press Create SLA. Enter name *Zabbix cluster performance* and set the SLO to 100%.   The service Zabbix cluster has a service tag `Zabbix:server`. To use this SLA for measuring performance of Zabbix cluster, in the *Service tags* parameter, specify:  - Name: Zabbix - Operation: Equals - Value: server  ![](../../../assets/en/manual/config/service_sla.png){width=600}  In a real-life setup, you can also update desired reporting period, time zone and start date or change the schedule from 24/7 to custom. For this example, the default settings are sufficient.   Switch to the *Excluded downtimes* tab and add downtimes for scheduled maintenance periods to exclude these periods from SLA calculation. In the Excluded downtimes section press the Add link, enter downtime name, planned start time and duration.  ![](../../../assets/en/manual/config/service_sla1.png){width=600}  Press Add to save the new SLA.  Switch to the SLA reports section to view the SLA report for Zabbix cluster.    ![](../../../assets/en/manual/config/service_sla2.png){width=600}  The SLA info can also be checked in the *Services* section.   ![](../../../assets/en/manual/config/service_sla3.png){width=600}
zh-cn	 ### SLA  在此示例中，预期的Zabbix集群性能是100%，排除了每半年一次的一小时维护时间。  首先需要添加一个服务级别协议。  转到 *服务->SLA* 菜单点击创建SLA。输入名称 *Zabbix集群性能* 并 设置SLO为100%。  Zabbix集群有 `Zabbix:server`标签。要使用该SLA来测量Zabbix集群的性能，需要在*服务标签*的参数中指定：  - 名称：Zabbix - 操作：Equals - 值：server  ![](../../../assets/en/manual/config/service_sla.png){width=600}  在实际设置中，还可以更新所需的报告周期、时区和开始日期，或把时间表从24/7改为自定义。就这个例子来说，默认设置就够了。  切换到*例外停机时间* 面板并添加用于例行维护的停机时间，这样SLA就不会将这些时间段计算在内了。在例外停机时间面板总点击添加(Add)链接，输入停机时间名称、计划开始时间和持续时长。  ![](../../../assets/en/manual/config/service_sla1.png){width=600}  点击添加(Add)来保存新建的SLA。  切换到SLA报告界面查看关于Zabbix集群的SLA报告。  ![](../../../assets/en/manual/config/service_sla2.png){width=600}  还可以在*服务* 界面下查看SLA信息。  ![](../../../assets/en/manual/config/service_sla3.png){width=600}

en-us	### SLAs  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  A list of the configured SLAs is displayed. *Note* that only the SLAs  related to services accessible to the user will be displayed (as read-only,  unless *Manage SLA* is enabled for the user role).   Displayed data:  |Parameter|Description| |--|--------| |*Name*|The SLA name is displayed.<br>The name is a link to [SLA configuration](/manual/it_services/sla#configuration). | |*SLO*|The service level objective (SLO) is displayed. | |*Effective date*|The date of starting SLA calculation is displayed. | |*Reporting period*|The period used in the SLA report is displayed - *daily*, *weekly*, *monthly*, *quarterly*, or *annually*. | |*Time zone*|The SLA time zone is displayed. | |*Schedule*|The SLA schedule is displayed - 24x7 or custom. | |*SLA report*|Click on the link to see the SLA report for this SLA. | |*Status*|The SLA status is displayed - enabled or disabled. |
zh-cn	### SLAs  ![](../../../../../assets/en/manual/web_interface/sla_list.png){width="600"}  显示已配置SLA的列表。 *注意*只有与用户可访问的服务相关的SLA才会显示（只读，除非为用户角色启用了*管理SLA*）。   显示的数据：  |参数|描述| |---------|-----------| |*Name*|显示SLA名称。<br>该名称链接到[SLA配置](/manual/it_services/sla#configuration)。| |*SLO*|显示服务级别目标（SLO）。| |*Effective date*|显示开始SLA计算的日期。| |*Reporting period*|显示SLA报告中使用的期间 - *每天*，*每周*，*每月*，*每季*，或者*每年*。| |*Time zone*|显示SLA时区。| |*Schedule*|显示SLA计划 - 全天候或定制。| |*SLA report*|点击链接查看此SLA的SLA报告。| |*Status*|显示SLA状态 - 可用或者禁用。|

en-us	#### Slideshow  It is possible to activate a slideshow in the dashboard:  -   `/zabbix.php?action=dashboard.view&slideshow=1` - activate slideshow
zh-cn	#### 幻灯片模式  可以在仪表板中激活幻灯片模式：  -   `/zabbix.php?action=dashboard.view&slideshow=1` - 激活幻灯片模式

en-us	#### Solaris  See values supported for 'memtype' parameter on Solaris in the table.  |Supported value|Description|Source in psinfo structure|Tries to be compatible with| |--|------|--|--| |vsize ^[1](proc_mem_notes#footnotes)^|Size of process image|pr\_size|ps -o vsz| |pmem|Percentage of real memory|pr\_pctmem|ps -o pmem| |rss|Resident set size<br>It may be underestimated - see rss description in "man ps".|pr\_rssize|ps -o rss|
zh-cn	#### Solaris  请参见表中的Solaris上的“memtype”参数所支持的值。  |支持值|描述|psinfo 结构中的源代码|兼容| |---------------|-----------|--------------------------|---------------------------| |vsize ^[1](proc_mem_notes#footnotes)^|过程映像的大小|pr\_size|ps -o vsz| |pmem|实际内存百分比|pr\_pctmem|ps -o pmem| |rss|驻留集大小<br>可能被低估了 - 请参阅“man ps”中的 rss 描述。|pr\_rssize|ps -o rss|

en-us	### Source  CAction::create() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::create() 。

en-us	### Source  CAction::delete() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::delete()。

en-us	### Source  CAction::get() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::get()。

en-us	### Source  CAction::update() in *ui/include/classes/api/services/CAction.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAction.php* 中的 CAction::update()。

en-us	### Source  CAlert::get() in *ui/include/classes/api/services/CAlert.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAlert.php* 中的 CAlert::get()。

en-us	### Source  CAPIInfo::version() in *ui/include/classes/api/services/CAPIInfo.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAPIInfo.php* 中的 CAPIInfo::version()。

en-us	### Source  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.
zh-cn	### 来源  CAuditLog::get() in *ui/include/classes/api/services/CAuditLog.php*.

en-us	### Source  CAutoregistration::get() in *ui/include/classes/api/services/CAutoregistration.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAutoregistration.php* 中的 CAutoregistration::get()。

en-us	### Source  CAutoregistration::update() in *ui/include/classes/api/services/CAutoregistration.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CAutoregistration.php* 中的 CAutoregistration::update()。

en-us	### Source  CCorrelation::create() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::create()。

en-us	### Source  CCorrelation::delete() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::delete()。

en-us	### Source  CCorrelation::get() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::get()。

en-us	### Source  CCorrelation::update() in *ui/include/classes/api/services/CCorrelation.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CCorrelation.php* 中的 CCorrelation::update()。

en-us	### Source  CDashboard::create() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::create()。

en-us	### Source  CDashboard::delete() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::delete() 。

en-us	### Source  CDashboard::get() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::get() 。

en-us	### Source  CDashboard::update() in *ui/include/classes/api/services/CDashboard.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDashboard.php* 中的 CDashboard::update() 。

en-us	### Source  CDCheck::get() in *ui/include/classes/api/services/CDCheck.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDCheck.php* 中的 CDCheck::get()。

en-us	### Source  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.
zh-cn	### 源代码  CDHost::get() in *ui/include/classes/api/services/CDHost.php*.

en-us	### Source  CDiscoveryRule::create() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::create()。

en-us	### Source  CDiscoveryRule::delete() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::delete()。

en-us	### Source  CDiscoveryRule::get() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::get()。

en-us	### Source  CDiscoveryRule::update() in *ui/include/classes/api/services/CDiscoveryRule.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CDiscoveryRule.php* 中的 CDiscoveryRule::update()。

en-us	### Source  CDRule::create() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::create()。

en-us	### Source  CDRule::delete() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::delete()。

en-us	### Source  CDRule::get() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::get()。

en-us	### Source  CDRule::update() in *ui/include/classes/api/services/CDRule.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDRule.php* 中的 CDRule::update()。

en-us	### Source  CDService::get() in *ui/include/classes/api/services/CDService.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CDService.php* 中的 CDService::get()。

en-us	### Source  CEvent::acknowledge() in *ui/include/classes/api/services/CEvent.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CEvent.php* 中的 CEvent::acknowledge() 。

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CEvent.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CEvent.php* 中的 CEvent::get() 。

en-us	### Source  CEvent::get() in *ui/include/classes/api/services/CProblem.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CProblem.php* 中的 CEvent::get()。

en-us	### Source  CGraph::create() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CGraph.php*中的CGraph::create()。

en-us	### Source  CGraph::delete() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::delete()。

en-us	### Source  CGraph::get() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::get()。

en-us	### Source  CGraphItem::get() in *ui/include/classes/api/services/CGraphItem.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphItem.php* 中的 CGraphItem::get()。

en-us	### Source  CGraphPrototype::create() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::create()。

en-us	### Source  CGraphPrototype::delete() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::delete()。

en-us	### Source  CGraphPrototype::get() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::get()。

en-us	### Source  CGraphPrototype::update() in *ui/include/classes/api/services/CGraphPrototype.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraphPrototype.php* 的 CGraphPrototype::update()。

en-us	### Source  CGraph::update() in *ui/include/classes/api/services/CGraph.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CGraph.php* 中的 CGraph::update()。

en-us	### Source  CHaNode::get() in *ui/include/classes/api/services/CHaNode.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHaNode.php* 的 CHaNode::get()。

en-us	### Source  CHistory::clear() in *ui/include/classes/api/services/CHistory.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHistory.php* 的 CHistory::clear()。

en-us	### Source  CHistory::get() in *ui/include/classes/api/services/CHistory.php*.
zh-cn	 ### 来源  *ui/include/classes/api/services/CHistory.php* 的 CHistory::get()。

en-us	### Source  CHost::create() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::create() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::delete() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::delete() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::get() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::get() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::create() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::delete() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::delete() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::get() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massAdd() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massRemove() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::massUpdate() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.
zh-cn	### 源代码  CHostGroup::update() in *ui/include/classes/api/services/CHostGroup.php*.

en-us	### Source  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::create() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::delete() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::get() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::massAdd() in *ui/include/classes/api/services/CHostInterface.php*.

en-us	### Source  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::massRemove() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源 CHostInterface::replaceHostInterfaces() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*.
zh-cn	### 来源  CHostInterface::update() in *ui/include/classes/api/services/CHostInterface.php*。

en-us	### Source  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massAdd() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massRemove() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::massUpdate() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::create() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::delete() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::get() in *ui/include/classes/api/services/CHostPrototype.php*。

en-us	### Source  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.
zh-cn	### 来源  CHostPrototype::update() in *ui/include/classes/api/services/CHostPrototype.php*.

en-us	### Source  CHost::update() in *ui/include/classes/api/services/CHost.php*.
zh-cn	### 源代码  CHost::update() in *ui/include/classes/api/services/CHost.php*.

en-us	### Source  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.
zh-cn	### 来源  CHousekeeping ::get() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.
zh-cn	### 来源  CHousekeeping::update() in *ui/include/classes/api/services/CHousekeeping.php*.

en-us	### Source  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::create() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::delete() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::get() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.
zh-cn	 ### 来源  CHttpTest::update() in *ui/include/classes/api/services/CHttpTest.php*.

en-us	### Source  CIconMap::create() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::create() 。

en-us	### Source  CIconMap::delete() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::delete()。

en-us	### Source  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	 ### 来源  CIconMap::get() in *ui/include/classes/api/services/CIconMap.php*.

en-us	### Source  CIconMap::update() in *ui/include/classes/api/services/CIconMap.php*.
zh-cn	### 来源  来自 *ui/include/classes/api/services/CIconMap.php* 的 CIconMap::update()。

en-us	### Source  CImage::create() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::create()

en-us	### Source  CImage::delete() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::delete()

en-us	### Source  CImage::get() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::get()

en-us	### Source  CImage::update() in *ui/include/classes/api/services/CImage.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CImage.php* - CImage::update()

en-us	### Source  CItem::create() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::create()

en-us	### Source  CItem::delete() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::delete()

en-us	### Source  CItem::get() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::get()

en-us	### Source  CItemPrototype::create() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::create() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::delete() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::get() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::get() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItemPrototype::update() in *ui/include/classes/api/services/CItemPrototype.php*.
zh-cn	### 来源  CItemPrototype::update() in *ui/include/classes/api/services/CItemPrototype.php*.

en-us	### Source  CItem::update() in *ui/include/classes/api/services/CItem.php*.
zh-cn	### 源码  *ui/include/classes/api/services/CItem.php* - CItem::update()

en-us	### Source  CMaintenance::create() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::create() in *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::delete() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::delete() in *frontends/php/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::get() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::get() 在 *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMaintenance::update() in *ui/include/classes/api/services/CMaintenance.php*.
zh-cn	### 来源  CMaintenance::update() in *ui/include/classes/api/services/CMaintenance.php*.

en-us	### Source  CMap::create() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源   CMap::create() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::delete() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::delete() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::get() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::get() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMap::update() in *ui/include/classes/api/services/CMap.php*.
zh-cn	### 来源  CMap::update() in *ui/include/classes/api/services/CMap.php*.

en-us	### Source  CMediaType::create() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::create()。

en-us	### Source  CMediaType::delete() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::delete()。

en-us	### Source  CMediaType::get() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源   *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::get()。

en-us	### Source  CMediaType::update() in *ui/include/classes/api/services/CMediaType.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CMediaType.php* 中的 CMediaType::update()。

en-us	### Source  CProxy::create() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CProxy.php* 中的 CProxy::create()。

en-us	### Source  CProxy::delete() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源   *ui/include/classes/api/services/CProxy.php* 中的 CProxy::delete()。

en-us	### Source  CProxy::get() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  CProxy::get() in *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CProxy::update() in *ui/include/classes/api/services/CProxy.php*.
zh-cn	### 来源  CProxy::update() in *ui/include/classes/api/services/CProxy.php*.

en-us	### Source  CRegexp::create() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::create() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::delete() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::delete() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::get() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::get() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CRegexp::update() in *ui/include/classes/api/services/CRegexp.php*.
zh-cn	### 参考来源  CRegexp::update() in *ui/include/classes/api/services/CRegexp.php*.

en-us	### Source  CReport::create() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::create() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::delete() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::delete() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::get() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::get() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CReport::update() in *ui/include/classes/api/services/CReport.php*.
zh-cn	### 参考来源  CReport::update() in *ui/include/classes/api/services/CReport.php*.

en-us	### Source  CRole::create() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 来源  CRole::create() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::delete() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::delete() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::get() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::get() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CRole::update() in *ui/include/classes/api/services/CRole.php*.
zh-cn	### 参考来源  CRole::update() in *ui/include/classes/api/services/CRole.php*.

en-us	### Source  CScript::create() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码  CScript::create() 在 *ui/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::delete() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码  CScript::delete() 在*frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::execute() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::execute() 在*ui/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::get() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::get() 在*frontends/php/include/classes/api/services/CScript.php*.

en-us	### Source  CScript::getScriptsByHosts() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::getScriptsByHosts()  在*frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CScript::update() in *ui/include/classes/api/services/CScript.php*.
zh-cn	### 源代码 CScript::update() 在 *frontends/php/include/classes/api/services/CScript.php*。

en-us	### Source  CService::create() in *ui/include/classes/api/services/CService.php*.
zh-cn	### 来源 CService::create() 在 *frontends/php/include/classes/api/services/CService.php*。

en-us	### Source  CService::delete() in *ui/include/classes/api/services/CService.php*.
zh-cn	 ### 来源  CService::delete() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CService::get() in *ui/include/classes/api/services/CService.php*.
zh-cn	### 来源  CService::get() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CService::update() in *ui/include/classes/api/services/CService.php*.
zh-cn	 ### 来源  CService::update() 在*ui/include/classes/api/services/CService.php*。

en-us	### Source  CSettings::get() in *ui/include/classes/api/services/CSettings.php*.
zh-cn	 ### 来源  CSettings::get()见*ui/include/classes/api/services/CSettings.php*。

en-us	### Source  CSettings::update() in *ui/include/classes/api/services/CSettings.php*.
zh-cn	 ### 来源  CSettings::update() 在*ui/include/classes/api/services/CSettings.php*。

en-us	### Source  CSla::getSli() in *ui/include/classes/api/services/CSla.php*
zh-cn	### 来源  *ui/include/classes/api/services/CSla.php* 中的 CSla::getSli()

en-us	### Source  CTask::create() in *ui/include/classes/api/services/CTask.php*.
zh-cn	### 来源  CTask::create() in *ui/include/classes/api/services/CTask.php*.

en-us	### Source  CTask::get() in *ui/include/classes/api/services/CTask.php*.
zh-cn	### 来源  CTask::get() in *ui/include/classes/api/services/CTask.php*.

en-us	### Source  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 来源  CTemplate::create() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplateDashboard::create() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::create() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::delete() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::delete() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::get() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::get() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplateDashboard::update() in *ui/include/classes/api/services/CTemplateDashboard.php*.
zh-cn	### 源码  CTemplateDashboard::update() in *ui/include/classes/api/services/CTemplateDashboard.php*.

en-us	### Source  CTemplate::delete() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 来源  CTemplate::delete() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::get() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::get() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massAdd() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massAdd() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massRemove() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massRemove() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::massUpdate() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码  CTemplate::massUpdate() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CTemplate::update() in *ui/include/classes/api/services/CTemplate.php*.
zh-cn	### 源码 CTemplate::update() in *ui/include/classes/api/services/CTemplate.php*.

en-us	### Source  CToken::create() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::create()。

en-us	### Source  CToken::delete() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::delete()。

en-us	### Source  CToken::generate() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::generate()。

en-us	### Source  CToken::get() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::get()。

en-us	### Source  CToken::update() in *ui/include/classes/api/services/CToken.php*.
zh-cn	### 来源  *ui/include/classes/api/services/CToken.php* 中的 CToken::update()。

en-us	### Source  CTrend::get() in *ui/include/classes/api/services/CTrend.php*.
zh-cn	### 源码  CTrend::get() in *ui/include/classes/api/services/CTrend.php*.

en-us	### Source  CTrigger::create() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::create() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::delete() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::delete() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTrigger::get() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::get() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CTriggerPrototype::create() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::create() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTriggerPrototype::delete() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::delete() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTriggerPrototype::update() in *ui/include/classes/api/services/CTriggerPrototype.php*.
zh-cn	### 源码  CTriggerPrototype::update() in *ui/include/classes/api/services/CTriggerPrototype.php*.

en-us	### Source  CTrigger::update() in *ui/include/classes/api/services/CTrigger.php*.
zh-cn	### 源码  CTrigger::update() in *ui/include/classes/api/services/CTrigger.php*.

en-us	### Source  CUser::create() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::create() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::delete() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::delete() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::get() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源<br>CUser::get() in ui/include/classes/api/services/CUser.php.

en-us	### Source  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::create() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::delete() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::delete() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::get() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::get() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUserGroup::update() in *ui/include/classes/api/services/CUserGroup.php*.
zh-cn	### 来源  CUserGroup::update() in *ui/include/classes/api/services/CUserGroup.php*.

en-us	### Source  CUser::login() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::login() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::login() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::login() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUserMacro::createGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::createGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::create() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::create() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::deleteGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::deleteGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::delete() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::delete() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::get() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::get() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::updateGlobal() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::updateGlobal() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUserMacro::update() in *ui/include/classes/api/services/CUserMacro.php*.
zh-cn	### 来源  CUserMacro::update() in *ui/include/classes/api/services/CUserMacro.php*.

en-us	### Source  CUser::unblock() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::unblock() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CUser::update() in *ui/include/classes/api/services/CUser.php*.
zh-cn	### 来源  CUser::update() in *ui/include/classes/api/services/CUser.php*.

en-us	### Source  CValueMap::create() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::create() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::delete() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::delete() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::get() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	 ### 来源  CValueMap::get() in *ui/include/classes/api/services/CValueMap.php*.

en-us	### Source  CValueMap::update() in *ui/include/classes/api/services/CValueMap.php*.
zh-cn	### 来源  CValueMap::update() in *ui/include/classes/api/services/CValueMap.php*.

en-us	##### Specify server  Make sure you have the Zabbix server identified in the agent [configuration file](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf      ServerActive=10.0.0.1  Unless you specifically define a *Hostname* in zabbix\_agentd.conf, the system hostname of agent location will be used by server for naming the host. The system hostname in Linux can be obtained by running the 'hostname' command.  If *Hostname* is defined in Zabbix agent configuration as a comma-delimited list of hosts, hosts will be created for all listed hostnames.  Restart the agent after making any changes to the configuration file.
zh-cn	##### 定义Zabbix server  确保在 [配置文件](/manual/appendix/config/zabbix_agentd) - zabbix\_agentd.conf中定义了Zabbix server。      ServerActive=10.0.0.1  如果不在zabbix\_agentd.conf中定义 *主机名称(Hostname)*，则Zabbix会使用agent所在系统的主机名称给主机命名。Linux系统的主机名称可以通过运行命令 'hostname' 来获取。  如果定义的 *主机名称(Hostname)* 是以逗号分隔的多台主机，那么其中定义的所有主机均会被创建。  agent配置变更需要重启agent生效。

en-us	#### SQLite  Using SQLite is supported for **Zabbix proxy** only!  The database will be automatically created if it does not exist.  Return to the [installation section](/manual/installation/install).
zh-cn	#### SQLite  仅 **Zabbix proxy** 支持使用 SQLite！  如果数据库不存在，将自动创建该数据库。  返回[安装部分](/manual/installation/install)。

en-us	#### Starting agent  To start the agent service, you can use Control Panel or do it from command line.  To start a single instance of Zabbix agent with the default configuration file:       zabbix_agentd.exe --start  To start a single instance of Zabbix agent with another configuration file:       zabbix_agentd.exe --config <your_configuration_file> --start  To start one of multiple instances of Zabbix agent:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --start --multiple-agents
zh-cn	#### Starting agent 要启动agent服务，可以使用"控制面板"或从命令行执行此操作  使用默认配置文件启动单个实例的 Zabbix agent:       zabbix_agentd.exe --start  指定配置文件启动单个实例的 Zabbix agent:       zabbix_agentd.exe --config <your_configuration_file> --start  启动多个Zabbix agent实例的其中一个，请执行以下操作：       zabbix_agentd.exe --config <configuration_file_for_this_instance> --start --multiple-agents

en-us	##### Starting Zabbix proxy process  To start a Zabbix proxy process and make it start at system boot:      # service zabbix-proxy start     # systemctl enable zabbix-proxy
zh-cn	##### 启动Zabbix代理进程  要启动 Zabbix 代理进程并使其在系统启动时启动：   · # service zabbix-proxy start  · # systemctl enable zabbix-proxy

en-us	##### Starting Zabbix proxy process  To start a Zabbix proxy process and make it start at system boot:      # systemctl restart zabbix-proxy     # systemctl enable zabbix-proxy
zh-cn	##### 启动 Zabbix proxy 进程  要启动Zabbix proxy 进程并使其在系统启动时启动，请执行以下操作:      # systemctl restart zabbix-proxy     # systemctl enable zabbix-proxy

en-us	##### Starting Zabbix server as cluster node  Two parameters are required  in the server [configuration](/manual/appendix/config/zabbix_server)  to start a Zabbix server as cluster node:  -    **HANodeName** parameter must be specified for each Zabbix server  that will be an HA cluster node.   This is a unique node identifier (e.g. `zabbix-node-01`) that the server will be referred to in agent  and proxy configurations. If you do not specify HANodeName, then the server will be  started in standalone mode.  -    **NodeAddress** parameter must be specified for each node.   The NodeAddress parameter (address:port) will be used by Zabbix frontend to connect  to the active server node. NodeAddress must match the IP or FQDN name of the respective Zabbix server.  Restart all Zabbix servers after making changes to the configuration files. They will  now be started as cluster nodes. The new status of the servers can be seen in  *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)*  and also by running:  ``` zabbix_server -R ha_status ```  This runtime command will log the current HA cluster status into the Zabbix server log (and to stdout):  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}
zh-cn	##### 作为集群节点启动Zabbix server  在server[配置](/manual/appendix/config/zabbix_server)中需要两个参数来启动Zabbix server作为集群节点:  -    **HANodeName** 集群中每个zabbix server节点名称必须要有且唯一。  这是将在agent和proxy配置中引用server的名称 (例如： `zabbix-node-01`)。如果您没有指定HANodeName，那么服务器将以standalone模式启动。  -    **NodeAddress** 参数必须为每个节点指定。  NodeAddress参数(address:port)将被Zabbix前端用来连接到主server节点。NodeAddress必须匹配相应Zabbix server的IP或FQDN名称。  在对配置文件进行更改后，重新启动所有Zabbix server。-   它们现在将作为集群节点启动。-   server的新状态可以在 *报表* → *[系统信息](/manual/web_interface/frontend_sections/reports/status_of_zabbix#status_of_ha_cluster_nodes)* 查看 ，也可以用以下命令查看:  ``` zabbix_server -R ha_status ```  此运行时命令会将当前 HA 集群状态记录到 Zabbix 服务器日志中（并输出到标准输出）：  ![](../../../../assets/en/manual/config/runtime_ha_status.png){width="600"}

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_agentd binary and execute:      shell> zabbix_agentd
zh-cn	##### 手动启动  如果以上操作均无效，您可能需要手动启动，找到 Zabbix agent 二进制文件的路径并且执行：     shell> zabbix_agentd

en-us	##### Start up manually  If the above does not work you have to start it manually. Find the path to the zabbix\_proxy binary and execute:      shell> zabbix_proxy  You can use the following command line parameters with Zabbix proxy:      -c --config <file>              path to the configuration file     -f --foreground                 run Zabbix proxy in foreground     -R --runtime-control <option>   perform administrative functions     -h --help                       give this help     -V --version                    display version number  Examples of running Zabbix proxy with command line parameters:      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf     shell> zabbix_proxy --help     shell> zabbix_proxy -V
zh-cn	##### 手动启动  如果上述方法无效，则必须手动启动。找到路 到zabbix\_proxy二进制文件并执行：      shell> zabbix_proxy  您可以将以下命令行参数用于Zabbix proxy:      -c --config <file>              配置文件的路径     -f --foreground                 运行Zabbix proxy在前台     -R --runtime-control <option>   启动管理员后台功能     -h --help                       帮助     -V --version                    显示版本信息    使用命令行参数运行Zabbix proxy的示例：      shell> zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf     shell> zabbix_proxy --help     shell> zabbix_proxy -V

en-us	##### Start-up scripts  The scripts are used to automatically start/stop Zabbix processes during system's start-up/shutdown. The scripts are located under directory misc/init.d.
zh-cn	##### 启动脚本  这些脚本用于在系统启动和关闭期间自动启动和停止 Zabbix 进程。 此脚本位于 misc/init.d 目录下。

en-us	##### Step 1  Defining a network discovery rule for our IP range.  ![](../../../../assets/en/manual/discovery/network_discovery/discovery.png)  Zabbix will try to discover hosts in the IP range of 192.168.1.1-192.168.1.254 by connecting to Zabbix agents and getting the value from the **system.uname** key. The value received from the agent can be used to name the hosts and also to apply different actions for different operating systems. For example, link Windows servers to the template *Windows*, Linux servers to the template *Linux*.  The rule will be executed every 10 minutes.  When this rule is added, Zabbix will automatically start the discovery and generation of the discovery-based events for further processing.
zh-cn	##### 第一步  给IP地址范围定义网络发现规则。  ![](../../../../assets/en/manual/discovery/network_discovery/discovery.png)  主机的发现机制是通过尝试连接主机上的Zabbix agent并获取 **system.uname** 这个键来实现的。从Zabbix agent获取到的值可以用于给主机命名以及为不同操作系统执行不同的动作。比如链接Windows服务器到 *Windows* 模板，链接Linux服务器到 *Linux* 模板。  规则每十分钟执行一次。   添加规则后，发现会自动执行，同时会产生相关事件。

en-us	##### Step 1  Install Kerberos package.  For Debian/Ubuntu:      apt install krb5-user  For RHEL:      dnf install krb5-workstation
zh-cn	##### 第1步  安装 Kerberos 包。  对于 Debian/Ubuntu：     apt install krb5-user  对于 RHEL：     dnf install krb5-workstation

en-us	##### Step 1  To define your own theme you'll need to create a CSS file and save it in the `assets/styles/` folder (for example, *custom-theme.css*). You can either copy the files from a different theme and create your theme based on it or start from scratch.
zh-cn	##### 步骤1  要定义您自己的主题，您需要创建一个 CSS 文件并将其保存在 `assets/styles/` 文件夹中（例如，*custom-theme.css*）。您可以从不同的主题复制文件并基于它创建主题，也可以从头开始。

en-us	##### Step 1  Write a script or command line to retrieve required parameter.  For example, we may write the following command in order to get total number of queries executed by a MySQL server:      mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  When executed, the command returns total number of SQL queries.
zh-cn	##### 第一步  写一个脚本或命令行以检测所需的参数。\  举个例子，我们编辑了下面的命令以获取 MySQL Server 执行的查询总数：      mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  这个命令执行后，将恢复返回 SQL 查询的总数。

en-us	##### Step 2  Add the command to zabbix\_agentd.conf:      UserParameter=mysql.questions,mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  **mysql.questions** is a unique identifier. It can be any valid key identifier, for example, *queries*.  Test this parameter by using Zabbix agent with "-t" flag (if running under root, however, note that the agent may have different permissions when launched as a daemon):      zabbix_agentd -t mysql.questions
zh-cn	##### 第二步  添加命令到 zabbix\_agentd.conf:      UserParameter=mysql.questions,mysqladmin -uroot status | cut -f4 -d":" | cut -f1 -d"S"  **mysql.questions** 作为key需要是唯一标识符。可以是任何有效的字符，比如*queries*。  通过使用带有 ‘-t’ 标识的 zabbix\_agentd命令测试此用户自定义参数的执行。（如果是以root用户运行，请注意agent与作为守护进程执行时的权限差异）：      zabbix_agentd -t mysql.questions

en-us	##### Step 2  Add your theme to the list of themes returned by the APP::getThemes() method. You can do this by overriding the ZBase::getThemes() method in the APP class. This can be done by adding the following code before the closing brace in *include/classes/core/APP.php*:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme')           ]);       }  ::: noteimportant Note that the name you specify within the first pair of quotes must match the name of the theme file without extension. :::  To add multiple themes, just list them under the first theme, for example:        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme'),               'anothertheme' => _('Another theme'),               'onemoretheme' => _('One more theme')           ]);       }  Note that every theme except the last one must have a trailing comma.  ::: notetip To change graph colors, the entry must be added in the *graph\_theme* database table. :::
zh-cn	##### 步骤2  将您的主题添加到 APP::getThemes() 方法返回的主题列表中。您可以通过覆盖 APP 类中的 ZBase::getThemes() 方法来做到这一点。这可以通过在 *include/classes/core/APP.php* 的右大括号之前添加以下代码来完成：        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme')           ]);       }  ::: noteimportant 请注意，您在第一对引号中指定的名称必须与不带扩展名的主题文件的名称匹配。 :::  要添加多个主题，只需将它们列在第一个主题下即可，例如：        public static function getThemes() {           return array_merge(parent::getThemes(), [               'custom-theme' => _('Custom theme'),               'anothertheme' => _('Another theme'),               'onemoretheme' => _('One more theme')           ]);       }  请注意，除了最后一个主题之外的每个主题都必须有一个尾随逗号。  ::: notetip 要更改图形颜色，必须在 *graph\_theme* 数据库表中添加条目。 :::

en-us	##### Step 2  Configure Kerberos configuration file (see MIT documentation for details)  ``` {.java} cat /etc/krb5.conf  [libdefaults]     default_realm = EXAMPLE.COM # The following krb5.conf variables are only for MIT Kerberos.     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```
zh-cn	##### 第2步  设置Kerberos配置文件 (看MIT详细文档)  ``` {.java} cat /etc/krb5.conf  [libdefaults]     default_realm = EXAMPLE.COM # The following krb5.conf variables are only for MIT Kerberos.     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```

en-us	##### Step 2  Define steps for the scenario.  Click on *Add* button in the *Steps* tab to add individual steps.  *Web scenario step 1*  We start by checking that the first page responds correctly, returns with HTTP response code 200 and contains text "Zabbix SIA".  ![](../../../assets/en/manual/web_monitoring/scen_step1.png){width="600"}  When done configuring the step, click on *Add*.  *Web scenario step 2*  We continue by logging in to the Zabbix frontend, and we do so by reusing the macros (variables) we defined on the scenario level - {user} and {password}.  ![](../../../assets/en/manual/web_monitoring/scen_step2.png){width="600"}  ::: noteimportant Note that Zabbix frontend uses JavaScript redirect when logging in, thus first we must log in, and only in further steps we may check for logged-in features. Additionally, the login step must use full URL to **index.php** file. :::  Take note also of how we are getting the content of the `{sid}` variable (session ID) using a variable syntax with regular expression: `regex:name="csrf-token" content="([0-9a-z]{16})"`. This variable will be required in step 4.  *Web scenario step 3*  Being logged in, we should now verify the fact. To do so, we check for a string that is only visible when logged in - for example, **Administration**.  ![](../../../assets/en/manual/web_monitoring/scen_step3.png){width="600"}  *Web scenario step 4*  Now that we have verified that frontend is accessible and we can log in and retrieve logged-in content, we should also log out - otherwise Zabbix database will become polluted with lots and lots of open session records.  ![](../../../assets/en/manual/web_monitoring/scen_step4.png){width="600"}  *Web scenario step 5*  We can also check that we have logged out by looking for the **Username** string.  ![](../../../assets/en/manual/web_monitoring/scen_step5.png){width="600"}  *Complete configuration of steps*  A complete configuration of web scenario steps should look like this:  ![](../../../assets/en/manual/web_monitoring/scenario_steps.png){width="600"}
zh-cn	##### 第2步  定义场景的步骤。  单击  *Steps（步骤）* 中的 *Add（添加）* 按钮以添加各个步骤。   *Web scenario step 1（Web 场景步骤 1）*  我们首先检查第一页是否正确响应，返回 HTTP 响应代码 200 并包含文本 "Zabbix SIA"。  ![](../../../assets/en/manual/web_monitoring/scen_step1.png){width="600"}  完成配置步骤后，单击 *Add（添加）*。  *Web scenario step 2（Web 场景步骤 2）*  我们继续登录 Zabbix 前端，并通过重用我们在场景级别定义的宏（变量） - {user} 和 {password}。  ![](../../../assets/en/manual/web_monitoring/scen_step2.png){width="600"}  ::: noteimportant 注意 Zabbix 前端在登录时使用 JavaScript 重定向，因此首先我们必须登录，并且只有在进一步的步骤中，我们才能检查已登录的功能。此外，登录步骤必须使用 **index.php** 文件的完整 URL。 :::  注意我们是如何使用正则表达式的变量语法 'regex:name="csrf-token" content="([0-9a-z]{16})" '获取 ' {sid} ' 变量 (会话ID) 的内容的。这个变量在步骤4中是必需的。  *Web 场景步骤 3*  登录后，我们应该验证。为此，我们检查仅在登录时可见的字符串，例如**Administration**。  ![](../../../assets/en/manual/web_monitoring/scen_step3.png){width="600"}  *Web 场景步骤 4*  已经验证了前端是可访问的并且可以登录并检索登录的内容，之后应该注销 - 否则 Zabbix 数据库将被大量打开的会话记录污染。  ![](../../../assets/en/manual/web_monitoring/scen_step4.png){width="600"}  *Web 场景步骤 5*  可以通过查找 **Username（用户名）** 字符串来确认是否已注销。  ![](../../../assets/en/manual/web_monitoring/scen_step5.png){width="600"}  *步骤的完整配置*  一个完整的 Web 场景步骤的配置如下所示：  ![](../../../assets/en/manual/web_monitoring/scenario_steps.png){width="600"}

en-us	##### Step 2  Defining a discovery [action](/manual/config/notifications/action) for adding the discovered Linux servers to the respective group/template.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action.png)  The action will be activated if:  -   the "Zabbix agent" service is "up" -   the value of system.uname (the Zabbix agent key we used in rule     definition) contains "Linux" -   Uptime is 1 hour (3600 seconds) or more  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_b.png)  The action will execute the following operations:  -   add the discovered host to the "Linux servers" group (and also add     host if it wasn't added previously) -   link host to the *Linux* template. Zabbix will automatically start     monitoring the host using items and triggers from the "Linux"     template.
zh-cn	##### 第二步  定义一个网络发现 [动作](/manual/config/notifications/action) ，用于 添加发现的Linux服务器到对应的组并链接到对应模板。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action.png)  同时满足下列条件才会使动作生效:  -   "Zabbix agent" 服务是已启动(up)状态的 -   system.uname(规则里定义的Zabbix agent的键)的值包含 "Linux"  -   运行时长(uptime)大于1小时(3600秒)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_b.png)  动作会执行下列操作:  -   添加发现的主机到 "Linux服务器" 组(如果之前主机不存在，则同时创建主机) -   链接主机到 *Linux* 模板。主机会自动纳入监控，监控使用 "Linux" 模板中的监控项和触发器

en-us	##### Step 3  Activate the new theme.  In Zabbix frontend, you may either set this theme to be the default one or change your theme in the user profile.  Enjoy the new look and feel!
zh-cn	##### 步骤 3  激活新主题。  在 Zabbix 前端，您可以将此主题设置为默认主题，也可以在用户配置文件中更改您的主题。  享受新的外观和感觉！

en-us	##### Step 3  Create a Kerberos ticket for user *zabbix*. Run the following command as user *zabbix*:      kinit zabbix  ::: noteimportant It is important to run the above command as user *zabbix*. If you run it as *root* the authentication will not work. :::
zh-cn	 ##### 第3步  创建*zabbix*用户的Kerberos ticket。使用*zabbix*执行命令：      kinit zabbix  ::: noteimportant 要使用*zabbix*用户执行以上命令。如果使用 root 用户将不会通过认证。 :::

en-us	##### Step 3  Defining a discovery action for adding the discovered Windows servers to the respective group/template.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win_b.png)
zh-cn	##### 第三步  定义网络发现动作，添加发现的Windows服务器到对应组并链接到对应模板。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_win_b.png)

en-us	##### Step 3  Reload user parameters from the configuration file by running:      zabbix_agentd -R userparameter_reload  You may also restart the agent instead of the runtime control command.  Test the parameter by using [zabbix\_get](/manual/concepts/get) utility.
zh-cn	##### 第三步  通过如下方式重新加载用户自定义参数:      zabbix_agentd -R userparameter_reload  除了执行命令行，也可以重启agent来实现。  使用 [zabbix\_get](/manual/concepts/get) 程序测试该用户自定义参数。

en-us	##### Step 3  Save the finished web monitoring scenario.  The scenario will be added to a host. To view web scenario information go to *Monitoring → Hosts*, locate the host in the list and click on the Web hyperlink in the last column.  ![](../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  Click on the scenario name to see more detailed statistics:  ![](../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}
zh-cn	##### 步骤 3  保存完成的 Web 监控场景。  该场景将被添加到主机。要查看 Web 场景信息，请转到 *Monitoring（监控中） → Hosts（主机）*，在列表中找到主机，然后单击最后一列中的 Web 超链接。  ![](../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  点击场景名称可查看更详细的统计信息：  ![](../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}

en-us	##### Step 4  Add new item with Key=mysql.questions to the monitored host. Type of the item must be either Zabbix Agent or Zabbix Agent (active).  Be aware that type of returned values must be set correctly on Zabbix server. Otherwise Zabbix won't accept them.
zh-cn	##### 第四步  在被监控主机中添加使用key值为 ‘mysql.questions’的新监控项。监控项类型必须使用 Zabbix Agent 或 Zabbix Agent（Active）。\  注意在 Zabbix Server上。必须设置正确的返回值类型，否则Zabbix无法处理。\

en-us	##### Step 4  Create a web scenario or HTTP agent item with Kerberos authentication type.  Optionally can be tested with the following curl command:      curl -v --negotiate -u : http://example.com  Note that for lengthy web monitoring it is necessary to take care of renewing the Kerberos ticket. Default time of ticket expiration is 10h.
zh-cn	 ##### 第4步  创建具有Kerberos身份验证类型的web方案或HTTP代理监控项。  可以选择使用以下curl命令进行测试：      curl -v --negotiate -u : http://example.com  请注意，对于冗长的web监视，有必要更新Kerberos ticket。Kerberos ticket到期时间默认为10小时。

en-us	##### Step 4  Defining a discovery action for removing lost servers.  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove_b.png)  A server will be removed if "Zabbix agent" service is 'down' for more than 24 hours (86400 seconds).
zh-cn	##### 第四步  定义网络发现动作，删除丢失的(lost)主机。  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove.png)  ![](../../../../assets/en/manual/discovery/network_discovery/discov_action_remove_b.png)  如果 "Zabbix agent" 服务停止(down)时间超过24小时(86400秒)，则会删除对应主机。

en-us	#### Steps
zh-cn	#### 步骤

en-us	#### Stopping agent  To stop the agent service, you can use Control Panel or do it from command line.  To stop a single instance of Zabbix agent started with the default configuration file:       zabbix_agentd.exe --stop  To stop a single instance of Zabbix agent started with another configuration file:       zabbix_agentd.exe --config <your_configuration_file> --stop  To stop one of multiple instances of Zabbix agent:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --stop --multiple-agents
zh-cn	#### 停止 agent  要停止agent服务，可以使用"控制面板"或从命令行执行此操作.  使用默认配置文件停止单个实例的 Zabbix agent:       zabbix_agentd.exe --stop       指定配置文件停止单个实例的 Zabbix agent:       zabbix_agentd.exe --config <your_configuration_file> --stop  停止多个Zabbix agent实例的其中一个，请执行以下操作:       zabbix_agentd.exe --config <configuration_file_for_this_instance> --stop --multiple-agents

en-us	#### Storing history data in multiple date-based indices  This section describes additional steps required to work with pipelines and ingest nodes.  To begin with, you must create templates for indices.  The following example shows a request for creating uint template:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/uint_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "uint*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "type": "long"          }       }    } }' ```  To create other templates, user should change the URL (last part is the name of template), change `"index_patterns"` field to match index name and to set valid mapping, which can be taken from `database/elasticsearch/elasticsearch.map`.  For example, the following command can be used to create a template for text index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/text_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "text*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "fields": {                "analyzed": {                   "index": true,                   "type": "text",                   "analyzer": "standard"                }             },             "index": false,             "type": "text"          }       }    } }' ```  This is required to allow Elasticsearch to set valid mapping for indices created automatically. Then it is required to create the pipeline definition. Pipeline is some sort of preprocessing of data before putting data in indices. The following command can be used to create pipeline for uint index:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_ingest/pipeline/uint-pipeline \  -H 'content-type:application/json' \  -d '{    "description": "daily uint index naming",    "processors": [       {          "date_index_name": {             "field": "clock",             "date_formats": [                "UNIX"             ],             "index_name_prefix": "uint-",             "date_rounding": "d"          }       }    ] }' ```  User can change the rounding parameter ("date\_rounding") to set a specific index rotation period. To create other pipelines, user should change the URL (last part is the name of pipeline) and change "index\_name\_prefix" field to match index name.  See also [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/master/date-index-name-processor.html).  Additionally, storing history data in multiple date-based indices should also be enabled in the new parameter in Zabbix server configuration:      ### Option: HistoryStorageDateIndex     # Enable preprocessing of history values in history storage to store values in different indices based on date.     # 0 - disable     # 1 - enable     #     # Mandatory: no     # Default:     # HistoryStorageDateIndex=0
zh-cn	#### 将历史数据存储在多个基于日期的索引中  本节介绍使用管道和引入节点所需的其他步骤。 首先，必须为索引创建模板。 以下示例为创建 uint 模板的请求：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/uint_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "uint*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "type": "long"          }       }    } }' ``` 要创建其他模板，用户应更改URL（最后一部分是模板的名称），更改`"index_patterns"`字段以匹配索引名称并设置有效的映射，这可以在`database/elasticsearch/elasticsearch.map`获取。 以下命令可用于为文本索引创建模板，例如：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_template/text_template \  -H 'content-type:application/json' \  -d '{    "index_patterns": [       "text*"    ],    "settings": {       "index": {          "number_of_replicas": 1,          "number_of_shards": 5       }    },    "mappings": {       "properties": {          "itemid": {             "type": "long"          },          "clock": {             "format": "epoch_second",             "type": "date"          },          "value": {             "fields": {                "analyzed": {                   "index": true,                   "type": "text",                   "analyzer": "standard"                }             },             "index": false,             "type": "text"          }       }    } }' ``` 这是允许 Elasticsearch 为自动创建的索引设置有效的映射所必需做的。然后需要创建pipeline定义。pipeline是在将数据放入索引之前对数据的某种预处理。以下命令可用于为 uint 索引创建pipeline：  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/_ingest/pipeline/uint-pipeline \  -H 'content-type:application/json' \  -d '{    "description": "daily uint index naming",    "processors": [       {          "date_index_name": {             "field": "clock",             "date_formats": [                "UNIX"             ],             "index_name_prefix": "uint-",             "date_rounding": "d"          }       }    ] }' ``` 用户可以更改参数("date\_rounding")以设置特定的索引轮换周期。要创建其他pipelines，用户应更改 URL（最后一部分是pipelines的名称）并更改"index\_name\_prefix"字段以匹配索引名称 另见 [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/master/date-index-name-processor.html). 此外，在Zabbix服务器新的配置参数中，还应启用将历史数据存储在多个基于日期的索引中：      ### Option: HistoryStorageDateIndex     # Enable preprocessing of history values in history storage to store values in different indices based on date.     # 0 - disable     # 1 - enable     #     # Mandatory: no     # Default:     # HistoryStorageDateIndex=0

en-us	### String history  The string history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|string|Received value.|
zh-cn	 ### 字符串型历史数据  字符串型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |clock|timestamp|收到值的时间。| |itemid|string|相关监控项的 ID。| |ns|integer|收到值时的纳秒数。| |value|string|收到的值。|

en-us	#### Structure  The content of this manual is divided into sections and subsections to provide easy access to particular subjects of interest.  When you navigate to respective sections, make sure that you expand section folders to reveal full content of what is included in subsections and individual pages.  Cross-linking between pages of related content is provided as much as possible to make sure that relevant information is not missed by the users.
zh-cn	#### 结构  本手册的内容分为多个部分和小节，以便您轻松访问感兴趣的特定主题。  当您导航到各个部分时，请确保展开部分文件夹以显示子文件和各个页面中包含的全部内容。  手册尽可能提供相关内容页面之间的交叉链接，以确保用户不会错过相关信息。

en-us	 #### Structure  The header consists of four fields. All numbers in the header are formatted as little-endian.  |Field|Size|Size<br>(large packet)|Description| |--|-|-|------| |`<PROTOCOL>`|4|4|`"ZBXD"` or `5A 42 58 44`| |`<FLAGS>`|1|1|Protocol flags:<br>`0x01` - Zabbix communications protocol<br>`0x02` - compression<br>`0x04` - large packet| |`<DATALEN>`|4|8|Data length.| |`<RESERVED>`|4|8|When compression is used (`0x02` flag) - the length of uncompressed data<br>When compression is not used - `00 00 00 00`|
zh-cn	#### 结构  标头由四个字段组成。 标头中的所有数字都采用小端格式。  |字段|大小|大小<br>（大包）|描述| |---|---|---|------| |`<PROTOCOL>`|4|4|`"ZBXD"` 或 `5A 42 58 44`| |`<FLAGS>`|1|1|协议标志：<br>`0x01` - Zabbix 通信协议<br>`0x02` - 压缩<br>`0x04` - 大数据包| |`<DATALEN>`|4|8|数据长度。| |`<RESERVED>`|4|8|使用压缩时（`0x02` 标志）- 未压缩数据的长度<br>不使用压缩时- `00 00 00 00`|

en-us	##### Substring extraction in trigger tags  Substring extraction is supported for populating the tag name or tag value, using a macro [function](/manual/config/macros/macro_functions) - applying a regular expression to the value obtained by the {ITEM.VALUE}, {ITEM.LASTVALUE} macro or a low-level discovery macro. For example:      {{ITEM.VALUE}.regsub(pattern, output)}     {{ITEM.VALUE}.iregsub(pattern, output)}      {{#LLDMACRO}.regsub(pattern, output)}     {{#LLDMACRO}.iregsub(pattern, output)}  Tag name and value will be cut to 255 characters if their length exceeds 255 characters after macro resolution.  See also: Using macro functions in [low-level discovery macros](/manual/config/macros/lld_macros#using_macro_functions) for event tagging.
zh-cn	##### 触发器标签中提取子字符串  支持提取子字符串以填充标签名称或标签值，使用宏 [function](/manual/config/macros/macro_functions) -将正则表达式应用于 {ITEM.VALUE}，{ITEM.LASTVALUE} 宏或低级发现宏所获得的值。例如：      {{ITEM.VALUE}.regsub（pattern，output）}     {{ITEM.VALUE}.iregsub（pattern，output）}      {{#LLDMACRO}.regsub（pattern，output）}     {{#LLDMACRO}.iregsub（pattern，output）}  如果标签名和标签值的宏被解析后长度超过255 个字符，标记名和值将被切割为255个字符。  另请参阅：在 [低级发现宏](/manual/config/macros/lld_macros#using_macro_functions)使用宏函数来实现事件标记。

en-us	##### Supported checks  The table below describes in-built items that are supported in IPMI agent checks.  |Item key|<|<|<| |--|--|------|------| |▲|Description|Return value|Comments| |ipmi.get|<|<|<| |<|IPMI-sensor related information.|JSON object|This item can be used for the [discovery of IPMI sensors](/manual/discovery/low_level_discovery/examples/ipmi_sensors#overview).<br>Supported since Zabbix 5.0.0.|
zh-cn	##### 支持的检查  下表描述了 IPMI 代理检查中支持的内置监控项。  |监控项键|<|<|<| |--|--|------|------| |▲|描述|返回值|注释| |ipmi.get|<|<|<| |<|IPMI 传感器相关信息。|JSON 对象|此监控项可用于 [IPMI 传感器的发现](/manual/discovery/low_level_discovery/examples/ipmi_sensors#overview)。<br>从 Zabbix 5.0.0 开始支持 .|

en-us	#### Supported macros  The discovery will return all instances of the specified object in the {\#INSTANCE} macro, which may be used in the prototypes of perf\_count and perf\_count\_en items.  ``` {.java} [     {"{#INSTANCE}":"0"},     {"{#INSTANCE}":"1"},     {"{#INSTANCE}":"_Total"} ] ```  For example, if the item key used in the discovery rule is:      perf_instance.discovery[Processor]  you may create an item prototype:      perf_counter["\Processor({#INSTANCE})\% Processor Time"]  Notes:  -   If the specified object is not found or does not support variable     instances then the discovery item will become NOTSUPPORTED. -   If the specified object supports variable instances, but currently     does not have any instances, then an empty JSON array will be     returned. -   In case of duplicate instances they will be skipped.
zh-cn	#### 支持的宏  自动发现会返回 {\#INSTANCE} 宏的所有对象实例 , 可用于perf\_count 和 perf\_count\_en监控项原型中。  ``` {.java} [     {"{#INSTANCE}":"0"},     {"{#INSTANCE}":"1"},     {"{#INSTANCE}":"_Total"} ] ```  例如, 假设自动发现规则中使用的监控项的键是：      perf_instance.discovery[Processor]  则可以创建这样的监控项原型：      perf_counter["\Processor({#INSTANCE})\% Processor Time"]  注意：  -   如果指定的对象找不到或者不支持可变实例，则自动发现监控项会变成NOTSUPPORTED状态。 -   如果指定的对象支持可变实例，但当前不存在任何实例，则会返回一个空的JSON数组。 -   重复的实例会被忽略。

en-us	##### Supported macros  The following macros are supported for use in the discovery rule [filter](/manual/discovery/low_level_discovery#discovery_rule_filter) and prototypes of items, triggers and graphs:  |Macro|Description| |-----|-----------| |Discovery of MBean attributes|<| |{\#JMXVALUE}|Attribute value.| |{\#JMXTYPE}|Attribute type.| |{\#JMXOBJ}|Object name.| |{\#JMXDESC}|Object name including attribute name.| |{\#JMXATTR}|Attribute name.| |Discovery of MBeans|<| |{\#JMXDOMAIN}|MBean domain. (*Zabbix reserved name*)| |{\#JMXOBJ}|Object name. (*Zabbix reserved name*)| |{\#JMX<key property>}|MBean properties (like {\#JMXTYPE}, {\#JMXNAME}) (see [Limitations](#limitations) below).|
zh-cn	##### 支持的宏  支持在自动发现规则的[过滤器](/manual/discovery/low_level_discovery#discovery_rule_filter)和监控项、触发器、图形的原型中使用下面的宏：  |宏|描述| |-----|-----------| |MBean属性的自动发现|<| |{\#JMXVALUE}|属性的值。| |{\#JMXTYPE}|属性的类型。| |{\#JMXOBJ}|对象名称。| |{\#JMXDESC}|包含属性名称的对象名称。| |{\#JMXATTR}|属性名称。| |MBean的自动发现|<| |{\#JMXDOMAIN}|MBean的域。 (*Zabbix的保留名称*)| |{\#JMXOBJ}|对象名称。 (*Zabbix的保留名称*)| |{\#JMX<key property>}|MBean属性 (类似 {\#JMXTYPE}, {\#JMXNAME}) (参考下面的[限制](#限制))。|

en-us	### Supported macros  The following macros are supported for use in the discovery rule [filter](/manual/discovery/low_level_discovery#discovery_rule_filter) and prototypes of items, triggers and graphs:  |Macro|Description| |-----|-----------| |{\#UNIT.NAME}|Primary unit name.| |{\#UNIT.DESCRIPTION}|Human readable description.| |{\#UNIT.LOADSTATE}|Load state (i.e. whether the unit file has been loaded successfully)| |{\#UNIT.ACTIVESTATE}|Active state (i.e. whether the unit is currently started or not)| |{\#UNIT.SUBSTATE}|Sub state (a more fine-grained version of the active state that is specific to the unit type, which the active state is not)| |{\#UNIT.FOLLOWED}|Unit that is being followed in its state by this unit, if there is any; otherwise an empty string.| |{\#UNIT.PATH}|Unit object path.| |{\#UNIT.JOBID}|Numeric job ID if there is a job queued for the job unit; 0 otherwise.| |{\#UNIT.JOBTYPE}|Job type.| |{\#UNIT.JOBPATH}|Job object path.| |{\#UNIT.UNITFILESTATE}|The install state of the unit file.|
zh-cn	#### 支持的宏  在自动发现规则的 [过滤器](/manual/discovery/low_level_discovery#discovery_rule_filter) 和监控项、触发器、图形的原型配置中支持的宏如下所示:  |宏|描述| |-----|-----------| |{\#UNIT.NAME}|主单元名称。| |{\#UNIT.DESCRIPTION}|通俗易懂的描述。| |{\#UNIT.LOADSTATE}|加载状态 (比如单元文件是否成功加载)| |{\#UNIT.ACTIVESTATE}|激活状态 (比如单元是否已启动)| |{\#UNIT.SUBSTATE}|子状态 (激活状态的另一个更加细致的版本，根据单元类型不同而不同, 而激活状态更加通用)| |{\#UNIT.FOLLOWED}|此单元所跟踪的单元的状态; 如果没有则显示空字符串。| |{\#UNIT.PATH}|单元对象路径。| |{\#UNIT.JOBID}|如果在任务单元中有排队的任务，则显示任务ID的数字; 否则为0。| |{\#UNIT.JOBTYPE}|任务类型。| |{\#UNIT.JOBPATH}|任务对象路径。| |{\#UNIT.UNITFILESTATE}|单元文件的安装状态。|

en-us	#### Supported macros  This discovery key returns two macros - {\#CPU.NUMBER} and {\#CPU.STATUS} identifying the CPU order number and status respectively. Note that a clear distinction cannot be made between actual, physical processors, cores and hyperthreads. {\#CPU.STATUS} on Linux, UNIX and BSD systems returns the status of the processor, which can be either "online" or "offline". On Windows systems, this same macro may represent a third value - "unknown" - which indicates that a processor has been detected, but no information has been collected for it yet.  CPU discovery relies on the agent's collector process to remain consistent with the data provided by the collector and save resources on obtaining the data. This has the effect of this item key not working with the test (-t) command line flag of the agent binary, which will return a NOT\_SUPPORTED status and an accompanying message indicating that the collector process has not been started.  Item prototypes that can be created based on CPU discovery include, for example:  -   `system.cpu.util[{#CPU.NUMBER},<type>,<mode>]` -   `system.hw.cpu[{#CPU.NUMBER},<info>]`  For detailed item key description, see [Zabbix agent item keys](/manual/config/items/itemtypes/zabbix_agent#supported_item_keys).
zh-cn	#### 支持的宏  这个键使用两个宏 - {\#CPU.NUMBER} 用于识别CPU序号， {\#CPU.STATUS} 用于识别CPU状态。 注意，没有办法清楚地区分出来实际的物理处理器、核心与超线程这三者。Linux、UNIX和BSD系统上的 {\#CPU.STATUS} 返回处理器的状态，状态可以是 "在线" 或者 "离线"。在Windows操作系统上，同样的宏可能会返回第三个取值 - "未知" - 表示已检测到处理器，但还未收集到相关信息。  为了保持与收集器提供的数据一致，CPU自动发现功能依赖agent的收集器进程，通过此方式还能在获取数据方面节省资源，但是这会导致此监控项的键不支持二进制agent的测试(-t)命令行参数，并且会返回一个NOT\_SUPPORTED状态，并附带信息，表明收集器进程未启动。  可基于CPU自动发现来创建监控项原型，比如:  -   `system.cpu.util[{#CPU.NUMBER},<type>,<mode>]` -   `system.hw.cpu[{#CPU.NUMBER},<info>]`  关于监控项的键的详细信息, 参考 [Zabbix agent 监控项的键](/manual/config/items/itemtypes/zabbix_agent#supported_item_keys)。

en-us	#### Supported macros  This discovery key returns two macros - {\#DEVNAME} and {\#DEVTYPE} identifying the block device name and type respectively, e.g.:  ``` {.java} [     {        "{#DEVNAME}":"loop1",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"dm-0",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda1",       "{#DEVTYPE}":"partition"    } ] ```  Block device discovery allows to use `vfs.dev.read[]` and `vfs.dev.write[]` items to create item prototypes using the {\#DEVNAME} macro, for example:  -   "vfs.dev.read\[{\#DEVNAME},sps\]" -   "vfs.dev.write\[{\#DEVNAME},sps\]"  {\#DEVTYPE} is intended for device filtering.
zh-cn	#### 支持的宏  此监控项返回两个宏 - {\#DEVNAME} 和 {\#DEVTYPE} 分别用于识别块设备名称和块设备类型, 例如:  ``` {.java} [     {        "{#DEVNAME}":"loop1",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"dm-0",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda",       "{#DEVTYPE}":"disk"    },    {        "{#DEVNAME}":"sda1",       "{#DEVTYPE}":"partition"    } ] ```  块设备的自动发现允许使用 `vfs.dev.read[]` 和 `vfs.dev.write[]` 监控项和 {\#DEVNAME} 宏来创建监控项原型, 例如:  -   "vfs.dev.read\[{\#DEVNAME},sps\]" -   "vfs.dev.write\[{\#DEVNAME},sps\]"  {\#DEVTYPE} 用于设备过滤。

en-us	#### Supported macros  You may use the {\#IFNAME} macro in the discovery rule [filter](/manual/discovery/low_level_discovery#filter) and prototypes of items, triggers and graphs.  Examples of item prototypes that you might wish to create based on "net.if.discovery":  -   "net.if.in\[{\#IFNAME},bytes\]", -   "net.if.out\[{\#IFNAME},bytes\]".  Note that on Windows {\#IFGUID} is also returned.
zh-cn	#### 支持的宏  可在自动发现规则的 [过滤器](/manual/discovery/low_level_discovery#filter) 和监控项、触发器、图表的原型中用使用{\#IFNAME} 宏。  下面是基于 "net.if.discovery" 键创建的监控项原型:  -   "net.if.in\[{\#IFNAME},bytes\]", -   "net.if.out\[{\#IFNAME},bytes\]".  注意，在Windows操作系统上也可使用 {\#IFGUID} 宏获取返回值。

en-us	#### Supported platforms  Due to the security requirements and mission-critical nature of server operation, UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance and resilience. Zabbix operates on market leading versions.  Zabbix server is tested on the following platforms:  -   Linux -   Solaris -   AIX -   HP-UX -   Mac OS X -   FreeBSD -   OpenBSD -   NetBSD -   SCO Open Server -   Tru64/OSF1  ::: noteclassic Zabbix may work on other Unix-like operating systems as well. :::
zh-cn	#### 支持的平台  由于服务器操作的安全性要求和任务关键性，UNIX是唯一能够始终如一地提供必要性能、容错和弹性的操作系统。Zabbix以市场主流的操作系统版本运行。  经测试，Zabbix 可以运行在下列平台：  -   Linux -   Solaris -   AIX -   HP-UX -   Mac OS X -   FreeBSD -   OpenBSD -   NetBSD -   SCO Open Server -   Tru64/OSF1  ::: noteclassic Zabbix 可以运行在其他类 Unix 操作系统上。 :::

en-us	#### Supported segments  |Segment|Description| |--|--------| |`<name>`|Match object property by name.| |`*`|Match all object properties.| |`['<name>']`|Match object property by name.| |`['<name>', '<name>', ...]`|Match object property by any of the listed names.| |`[<index>]`|Match array element by the index.| |`[<number>, <number>, ...]`|Match array element by any of the listed indexes.| |`[*]`|Match all object properties or array elements.| |`[<start>:<end>]`|Match array elements by the defined range:<br>**<start>** - the first index to match (including). If not specified matches all array elements from the beginning. If negative specifies starting offset from the end of array.<br>**<end>** - the last index to match (excluding). If not specified matches all array elements to the end. If negative specifies starting offset from the end of array.| |`[?(<expression>)]`|Match objects/array elements by applying a filter expression.|  To find a matching segment ignoring its ancestry (detached segment) it must be prefixed with '..' , for example `$..name` or `$..['name']` return values of all 'name' properties.  Matched element names can be extracted by adding a `~` suffix to the JSONPath. It returns the name of the matched object or an index in string format of the matched array item. The output format follows the same rules as other JSONPath queries - definite path results are returned 'as is' and indefinite path results are returned in array. However there is not much point of extracting the name of an element matching a definite path - it's already known.
zh-cn	#### 支持的段  |段|描述| |-------|-----------| |`<name>`|按名称匹配对象属性。| |`*`|匹配所有对象属性。| |`['<name>']`|按名称匹配对象属性。| |`['<name>', '<name>', ...]`|通过任何列出的名称匹配对象属性。| |`[<index>]`|按索引匹配数组元素。| |`[<number>, <number>, ...]`|通过任何列出的索引匹配数组元素。| |`[*]`|匹配所有对象属性或数组元素。| |`[<start>:<end>]`|按定义的范围匹配数组元素：<br>**<start>** - 要匹配的第一个索引（包括）。 如果未指定，则匹配从头开始的所有数组元素。 如果为负数，则指定从数组末尾开始的偏移量。<br>**<end>** - 要匹配的最后一个索引（不包括）。 如果未指定，则匹配所有数组元素到最后。 如果为负数，则指定从数组末尾开始的偏移量。| |`[?(<表达式>)]`|通过应用过滤表达式匹配对象/数组元素。|  要查找忽略其根节点的匹配段（单独的段），它必须以 '..' 为前缀，例如 `$..name` 或 `$..['name']` 返回所有 'name' 属性的值。  可以通过在 JSONPath 中添加 `~` 后缀来提取匹配的元素名称。 它返回匹配对象的名称或匹配数组项的字符串格式的索引。 输出格式遵循与其他 JSONPath 查询相同的规则 - 确定路径结果按“原样”返回，不确定路径结果以数组形式返回。 但是，提取与明确路径匹配的元素的名称并没有多大意义——它是已知的。

en-us	##### Switching from AES128 to AES256  Zabbix uses AES128 as the built-in default for data. Let's assume you are using certificates and want to switch to AES256, on OpenSSL 1.1.1.  This can be achieved by adding the respective parameters in `zabbix_server.conf`:        TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/server.crt       TLSKeyFile=/home/zabbix/server.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384       TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256       TLSCipherPSK=kECDHEPSK+AES256:-SHA1       TLSCipherAll13=TLS_AES_256_GCM_SHA384       TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384  ::: noteimportant Although only certificate-related ciphersuites will be used, `TLSCipherPSK*` parameters are defined as well to avoid their default values which include less secure ciphers for wider interoperability. PSK ciphersuites cannot be completely disabled on server/proxy. :::  And in `zabbix_agentd.conf`:        TLSConnect=cert       TLSAccept=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384
zh-cn	##### 从AES128 到 AES256转换  Zabbix使用AES128作为数据的内置默认值。让我们假设您正在使用证书，并希望切换到OpenSSL 1.1.1上的AES256。 这可以通过添加相应的参数来实现 `zabbix_server.conf`:        TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/server.crt       TLSKeyFile=/home/zabbix/server.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384       TLSCipherPSK13=TLS_CHACHA20_POLY1305_SHA256       TLSCipherPSK=kECDHEPSK+AES256:-SHA1       TLSCipherAll13=TLS_AES_256_GCM_SHA384       TLSCipherAll=EECDH+aRSA+AES256:-SHA1:-SHA384  ::: noteimportant 虽然只使用与证书相关的密码套件，但' TLSCipherPSK* '参数也被定义得很好，以避免它们的默认值包括较不安全的密码，以实现更广泛的互操作性。 不能在server/proxy上完全禁用PSK密码套件。 :::  并且在 `zabbix_agentd.conf`:        TLSConnect=cert       TLSAccept=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSCipherCert13=TLS_AES_256_GCM_SHA384       TLSCipherCert=EECDH+aRSA+AES256:-SHA1:-SHA384

en-us	##### Switching interface back to available  When the unreachability period is over, the interface is polled again, decreasing priority for item that turned the interface into unreachable state. If the unreachable interface reappears, the monitoring returns to normal automatically:      resuming Zabbix agent checks on host "New host": connection restored  ::: noteclassic Once interface becomes available, the host does not poll all its items immediately for two reasons:  -   It might overload the host. -   The interface restore time is not always matching planned item     polling schedule time.  So, after the interface becomes available, items are not polled immediately, but they are getting rescheduled to their next polling round. :::
zh-cn	 ##### 将主机接口状态切换回可用  当不可达期结束时，再次轮询接口， 降低使主机接口状态无法访问的监控项的优先级 状态。如果不可达接口再次出现，则监控自动恢复正常：      resuming Zabbix agent checks on host "New host": connection restored  ::: noteclassic 一旦接口可用，主机不会立即轮询所有监控项有两个原因：  -   它可能会使主机过载。 -   主机接口恢复时间并不总是与监控项计划轮询时间匹配。  因此，在主机接口可用后，监控项不会立即被轮询，但他们将被重新安排到下一次轮询。 :::

en-us	#### Switching to raw values  A dropdown on the upper right allows to switch from the simple graph to the *Values/500 latest values* listings. This can be useful for viewing the numeric values making up the graph.  The values represented here are raw, i.e. no units or postprocessing of values is used. Value mapping, however, is applied.
zh-cn	#### 切换到原始值  右上角的下拉菜单允许从简单图形切换到*值/500 个最新值* 列表。这对于查看组成图形的数值很有用。  这里表示的是原始值，即没有单位或使用处理后的值。但是，会显示应用了值映射。

en-us	## SYNOPSIS  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_agent2** \[**-c** *config-file*\]\ **zabbix\_agent2** \[**-c** *config-file*\] **-p**\ **zabbix\_agent2** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agent2** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agent2 -h**\ **zabbix\_agent2 -V**\ \ [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_agentd** \[**-c** *config-file*\]\ **zabbix\_agentd** \[**-c** *config-file*\] **-p**\ **zabbix\_agentd** \[**-c** *config-file*\] **-t** *item-key*\ **zabbix\_agentd** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_agentd -h**\ **zabbix\_agentd -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}
zh-cn	 ## 概要   **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-agent-cert-issuer** *cert-issuer*\] \[**--tls-agent-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -s** *host-name-or-IP* \[**-p** *port-number*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *item-key*\ **zabbix\_get -h**\ **zabbix\_get -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_js -s** *script-file* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_js -s** *script-file* **-p** *input-param* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -s** *script-file* **-i** *input-file* \[**-l** *log-level*\] \[**-t** *timeout*\]\ **zabbix\_js -h**\ **zabbix\_js -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_proxy** \[**-c** *config-file*\]\ **zabbix\_proxy** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_proxy -h**\ **zabbix\_proxy -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **cert** **--tls-ca-file** *CA-file* \[**--tls-crl-file** *CRL-file*\] \[**--tls-server-cert-issuer** *cert-issuer*\] \[**--tls-server-cert-subject** *cert-subject*\] **--tls-cert-file** *cert-file* **--tls-key-file** *key-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] **-s** *host* **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-z** *server* \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] **-k** *key* **-o** *value*\ **zabbix\_sender** \[**-v**\] **-c** *config-file* \[**-z** *server*\] \[**-p** *port*\] \[**-I** *IP-address*\] \[**-t** *timeout*\] \[**-s** *host*\] **--tls-connect** **psk** **--tls-psk-identity** *PSK-identity* **--tls-psk-file** *PSK-file* \[**--tls-cipher13** *cipher-string*\] \[**--tls-cipher** *cipher-string*\] \[**-T**\] \[**-N**\] \[**-r**\] **-i** *input-file*\ **zabbix\_sender -h**\ **zabbix\_sender -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}
zh-cn	 ## 概要  **zabbix\_server** \[**-c** *config-file*\]\ **zabbix\_server** \[**-c** *config-file*\] **-R** *runtime-option*\ **zabbix\_server -h**\ **zabbix\_server -V** [ ]{#lbAD}

en-us	## SYNOPSIS  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}
zh-cn	## 概要  **zabbix\_web\_service** \[**-c** *config-file*\]\ **zabbix\_web\_service -h**\ **zabbix\_web\_service -V** [ ]{#lbAD}

en-us	#### Syntax  To retrieve aggregates, you may:  -   list several items for aggregation:  ``` aggregate_function(function(/host/key,parameter),function(/host2/key2,parameter),...) ```  Note that `function` here must be a history/trend function.  -   use the **foreach** function, as the only parameter, and its item filter to select the required items:  ``` aggregate_function(foreach_function(/host/key?[group="host group"],timeperiod)) ```  Aggregate function is one of the supported [aggregate functions](/manual/appendix/functions/aggregate#aggregate-functions-1): avg, max, min, sum, etc.  A **foreach** function (e.g. *avg_foreach*, *count_foreach*, etc.) returns one aggregate value for each selected item. Items are selected by using the item filter (`/host/key?[group="host group"]`), from item history.  If some of the items have no data for the requested period, they are ignored in the calculation. If no items have  data, the function will return an error.  For more details, see [foreach functions](/manual/appendix/functions/aggregate/foreach).  ::: noteclassic If the aggregate results in a float value it will be trimmed to an integer if the aggregated item type of information is *Numeric (unsigned)*. :::  An aggregate calculation may become unsupported if:  -   none of the referenced items is found (which may happen if the item     key is incorrect, none of the items exists or all included groups     are incorrect) -   no data to calculate a function
zh-cn	 -   项目历史:  ``` aggregate_function(function(/host/item,parameter),function(/host2/item2,parameter),...) ``` -  一个 foreach 函数作为唯一参数:  ``` aggregate_function(foreach_function(/*/key?[group="host group"],timeperiod)) ```         where:     -   `聚合函数`是支持的聚合函数之一: avg，max，min，sum，等等.     -    函数是受支持的 foreach 函数之一: avg _ foreach、 count _ foreach 等  Foreach 函数使用项筛选器处理多个项的历史记录，并返回一个值数组——每个项一个值。  注意: 如果聚合项类型的信息是 Numeric (无符号) ，则聚合结果生成的浮点值将被裁剪为整数。. 如果出现以下情况，则可能不支持聚合计算: -   没有找到任何引用的项(如果项目键不正确、项目不存在或所有包含的组都不正确，则可能发生这种情况) -   没有数据来计算函数

en-us	#### Tags  -   Performance – device family MIBs provide a way to monitor CPU and     memory items; -   Fault - device family MIBs provide a way to monitor at least one     temperature sensor; -   Inventory – device family MIBs provide a way to collect at least the     device serial number and model name; -   Certified – all three main categories above are covered.
zh-cn	 #### 标签  -   Performance – 设备系列MIB提供了一种监控CPU和内存监控项的方法; -   Fault - 设备系列MIB提供监控至少一个温度传感器的方法; -   Inventory – 设备系列MIB提供了至少收集设备序列号和型号名称的方法; -   Certified – 涵盖上述所有三个主要类别。

en-us	# task.create
zh-cn	# task.create

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

en-us	#### Tasks  Interact with Zabbix server task manager, creating tasks and retrieving response.  [Task API](/manual/api/reference/task)
zh-cn	#### 任务  与Zabbix Server task manager 交互，创建任务并检索响应。  [Task API](/manual/api/reference/task)

en-us	# template.create
zh-cn	# template.create

en-us	# templatedashboard.create
zh-cn	# 创建模板仪表盘

en-us	# templatedashboard.delete
zh-cn	# 删除模板仪表盘

en-us	# templatedashboard.get
zh-cn	# 检索模板仪表盘

en-us	# > Template dashboard object  The following objects are directly related to the `templatedashboard` API.
zh-cn	# > 模版仪表盘对象  以下对象与 `templatedashboard` API 直接相关。

en-us	##### Template dashboard tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |dashboards| |\-| | |Root element for template dashboards.| | |uuid|x|`string`| |Unique identifier for this dashboard.| | |name|x|`string`| |Template dashboard name.| | |display period|\-|`integer`| |Display period of dashboard pages.| | |auto\_start|\-|`string`|0 - no<br>1 - yes|Slideshow auto start.| |pages| |\-| | |Root element for template dashboard pages.| | |name|\-|`string`| |Page name.| | |display period|\-|`integer`| |Page display period.| | |sortorder|\-|`integer`| |Page sorting order.| |widgets| |\-| | |Root element for template dashboard widgets.| | |type|x|`string`| |Widget type.| | |name|\-|`string`| |Widget name.| | |x|\-|`integer`|0-23|Horizontal position from the left side of the template dashboard.| | |y|\-|`integer`|0-62|Vertical position from the top of the template dashboard.| | |width|\-|`integer`|1-24|Widget width.| | |height|\-|`integer`|2-32|Widget height.| | |hide\_header|\-|`string`|0 - no<br>1 - yes|Hide widget header.| |fields| |\-| | |Root element for the template dashboard widget fields.| | |type|x|`string`|0 - INTEGER<br>1 - STRING<br>3 - HOST<br>4 - ITEM<br>5 - ITEM\_PROTOTYPE<br>6 - GRAPH<br>7 - GRAPH\_PROTOTYPE|Widget field type.| | |name|x|`string`| |Widget field name.| | |value|x|mixed| |Widget field value, depending on the field type.|
zh-cn	##### 模板仪表盘标签  |元素|元素属性|是否必须|类型|使用范围^**[1](#footnotes)**^|描述| |-------|----------------|--------|----|--------------------------|-----------| |dashboards|<|\-|<|<|模板仪表板的根元素。| |<|uuid|x|`string`|<|此仪表板的唯一标识符。| |<|name|x|`string`|<|模板仪表盘的名字。| |<|display period|\-|`integer`|<|仪表盘页面的显示周期。| |<|auto\_start|\-|`string`|0 - no<br>1 - yes|幻灯片自动开始。| |pages|<|\-|<|<|模板仪表板页面的根元素。| |<|name|\-|`string`|<|页面名称。| |<|display period|\-|`integer`|<|页面显示。| |<|sortorder|\-|`integer`|<|页面排序顺序。| |widgets|<|\-|<|<|模板仪表板小部件的根元素。| |<|type|x|`string`|<|小部件类型。| |<|name|\-|`string`|<|小部件名称。| |<|x|\-|`integer`|0-23|模板仪表板左侧的水平位置。| |<|y|\-|`integer`|0-62|从模板仪表板顶部开始的垂直位置。| |<|width|\-|`integer`|1-24|小部件宽度。| |<|height|\-|`integer`|2-32|小部件的高度。| |<|hide\_header|\-|`string`|0 - no<br>1 - yes|隐藏小部件标题。| |fields|<|\-|<|<|模板仪表板小部件字段的根元素。| |<|type|x|`string`|0 - INTEGER<br>1 - STRING<br>3 - HOST<br>4 - ITEM<br>5 - ITEM\_PROTOTYPE<br>6 - GRAPH<br>7 - GRAPH\_PROTOTYPE|小部件字段类型。| |<|name|x|`string`|<|小部件字段名。| |<|value|x|mixed|<|小部件字段值，取决于字段类型。|

en-us	# Template dashboard  This class is designed to work with template dashboards.  Object references:\  -   [Template dashboard](/manual/api/reference/templatedashboard/object) -   [Template dashboard     page](/manual/api/reference/templatedashboard/object#template_dashboard_page) -   [Template dashboard     widget](/manual/api/reference/templatedashboard/object#template_dashboard_widget) -   [Template dashboard widget     field](/manual/api/reference/templatedashboard/object#template_dashboard_widget_field)  Available methods:\  -   [templatedashboard.create](/manual/api/reference/templatedashboard/create) -     creating new template dashboards -   [templatedashboard.delete](/manual/api/reference/templatedashboard/delete) -     deleting template dashboards -   [templatedashboard.get](/manual/api/reference/templatedashboard/get) -     retrieving template dashboards -   [templatedashboard.update](/manual/api/reference/templatedashboard/update) -     updating template dashboards
zh-cn	# 模版仪表盘  此类设计用于使用模板仪表盘。  对象引用:\  -   [模版仪表盘](/manual/api/reference/templatedashboard/object) -   [模版仪表盘页面](/manual/api/reference/templatedashboard/object#template_dashboard_page) -   [模版仪表盘组件](/manual/api/reference/templatedashboard/object#template_dashboard_widget) -   [模版仪表盘组件字段](/manual/api/reference/templatedashboard/object#template_dashboard_widget_field)  可用方法:\  -   [templatedashboard.create](/manual/api/reference/templatedashboard/create) -     创建一个新的模版仪表盘 -   [templatedashboard.delete](/manual/api/reference/templatedashboard/delete) -     删除模版仪表盘 -   [templatedashboard.get](/manual/api/reference/templatedashboard/get) -     检索模版仪表盘 -   [templatedashboard.update](/manual/api/reference/templatedashboard/update) -     更新模版仪表盘

en-us	# templatedashboard.update
zh-cn	# 更新模板仪表盘

en-us	# template.delete
zh-cn	# template.delete

en-us	# template.get
zh-cn	# 检索模板

en-us	##### Template graph tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |uuid|x|`string`| |Unique identifier for this graph.| | |name|x|`string`| |Graph name.| | |width|\-|`integer`|20-65535 (default: 900)|Graph width, in pixels. Used for preview and for pie/exploded graphs.| | |height|\-|`integer`|20-65535 (default: 200)|Graph height, in pixels. Used for preview and for pie/exploded graphs.| | |yaxismin|\-|`double`|Default: 0|Value of Y axis minimum.<br><br>Used if 'ymin\_type\_1' is FIXED.| | |yaxismax|\-|`double`|Default: 0|Value of Y axis maximum.<br><br>Used if 'ymax\_type\_1' is FIXED.| | |show\_work\_period|\-|`string`|0 - NO<br>1 - YES (default)|Highlight non-working hours.<br><br>Used by normal and stacked graphs.| | |show\_triggers|\-|`string`|0 - NO<br>1 - YES (default)|Display simple trigger values as a line.<br><br>Used by normal and stacked graphs.| | |type|\-|`string`|0 - NORMAL (default)<br>1 - STACKED<br>2 - PIE<br>3 - EXPLODED|Graph type.| | |show\_legend|\-|`string`|0 - NO<br>1 - YES (default)|Display graph legend.| | |show\_3d|\-|`string`|0 - NO (default)<br>1 - YES|Enable 3D style.<br><br>Used by pie and exploded pie graphs.| | |percent\_left|\-|`double`|Default:0|Show the percentile line for left axis.<br><br>Used only for normal graphs.| | |percent\_right|\-|`double`|Default:0|Show the percentile line for right axis.<br><br>Used only for normal graphs.| | |ymin\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Minimum value of Y axis.<br><br>Used by normal and stacked graphs.| | |ymax\_type\_1|\-|`string`|0 - CALCULATED (default)<br>1 - FIXED<br>2 - ITEM|Maximum value of Y axis.<br><br>Used by normal and stacked graphs.| |ymin\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymin\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |ymax\_item\_1| |\-| | |Individual item details.<br><br>Required if 'ymax\_type\_1' is ITEM.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.| |graph\_items| |x| | |Root element for graph items.| | |sortorder|\-|`integer`| |Draw order. The smaller value is drawn first. Can be used to draw lines or regions behind (or in front of) another.| | |drawtype|\-|`string`|0 - SINGLE\_LINE (default)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_LINE|Draw style of the graph item.<br><br>Used only by normal graphs.| | |color|\-|`string`| |Element color (6 symbols, hex).| | |yaxisside|\-|`string`|0 - LEFT (default)<br>1 - RIGHT|Side of the graph where the graph item's Y scale will be drawn.<br><br>Used by normal and stacked graphs.| | |calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG (default)<br>4 - MAX<br>7 - ALL (minimum, average and maximum; used only by simple graphs)<br>9 - LAST (used only by pie and exploded pie graphs)|Data to draw if more than one value exists for an item.| | |type|\-|`string`|0 - SIMPLE (default)<br>2 - GRAPH\_SUM (value of the item represents the whole pie; used only by pie and exploded pie graphs)|Graph item type.| |item| |x| | |Individual item.| | |host|x|`string`| |Item host.| | |key|x|`string`| |Item key.|
zh-cn	##### 模板图形标签  |元素|元素属性|是否必须|类型|适用范围^**[1](#footnotes)**^|描述| |-------|----------------|--------|----|--------------------------|-----------| |graphs|<|\-|<|<|图形的根元素。| |<|uuid|x|`string`|<|此图形的唯一标识符。| |<|name|x|`string`|<|图形的名称。| |<|width|\-|`integer`|20-65535 (默认: 900)|图形宽度，以像素为单位。 用于预览和饼图/分解图。| |<|height|\-|`integer`|20-65535 (默认: 200)|图形高度，以像素为单位。 用于预览和饼图/分解图。| |<|yaxismin|\-|`double`|默认: 0|Y轴最小值。 <br><br>当'ymin\_type\_1'为固定值时使用。| |<|yaxismax|\-|`double`|默认: 0|Y轴最大值。 <br><br>当'ymax\_type\_1'为固定值时使用。| |<|show\_work\_period|\-|`string`|0 - NO<br>1 - YES(默认)|突出显示非工作时间。 <br><br>用于普通图和堆叠图。| |<|show\_triggers|\-|`string`|0 - NO<br>1 - YES(默认)|将简单的触发值显示为一行。 <br><br>用于普通图和堆叠图。| |<|type|\-|`string`|0 - NORMAL(默认)<br>1 - STACKED<br>2 - PIE<br>3 - expanded |图类型。| |<|show\_legend|\-|`string`|0 - NO<br>1 - YES(默认)|显示图形图例。| |<|show\_3d|\-|`string`|0 - NO(默认)<br>1 - YES|启用3D样式。 <br><br>用于饼图和分解饼图。| |<|percent\_left|\-|`double`|默认:0|显示左轴的百分位线。 <br><br>仅用于普通图形。| |<|percent\_right|\-|`double`|默认:0|显示右轴的百分位线。 <br><br>仅用于普通图形。| |<|ymin\_type\_1|\-|`string`|0 - calculate(默认值)<br>1 - FIXED<br>2 - ITEM| Y轴的最小值。 <br><br>用于普通图和堆叠图。| |<|ymax\_type\_1|\-|`string`|0 - calculate(默认值)<br>1 - FIXED<br>2 - ITEM| Y轴的最大值。 <br><br>用于普通图和堆叠图。| |ymin\_item\_1|<|\-|<|<|个别监控项的细节。 <br><br>当'ymin\_type\_1'为ITEM时需要。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。| |ymax\_item\_1|<|\-|<|<|个别监控项的细节。 <br><br>当'ymax\_type\_1'为ITEM时需要。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。| |graph\_items|<|x|<|<|图形项的根元素。| |<|sortorder|\-|`integer`|<|画出顺序。 先画出较小的值。 可用于在另一个线或区域后面(或前面)画线或区域。| |<|drawtype|\-|`string`|0 - SINGLE\_LINE(默认)<br>1 - FILLED\_REGION<br>2 - BOLD\_LINE<br>3 - dot \_LINE<br>4 -虚线\_LINE<br>5 -渐变\_LINE|图形项的绘制风格。 <br><br>仅用于普通图形。| |<|color|\-|`string`|<|元素颜色(6个符号，十六进制)。| |<|yaxisside|\-|`string`|0 - LEFT(默认)<br>1 - RIGHT|图形项的Y比例将被绘制的部分。 <br><br>用于普通图和堆叠图。| |<|calc\_fnc|\-|`string`|1 - MIN<br>2 - AVG(默认值)<br>4 - MAX<br>7 - ALL(最小值，平均值和最大值; <br>9 - LAST(仅用于饼图和分解饼图)|表示一个监控项存在多个值的数据。| |<|type|\-|`string`|0 - SIMPLE(默认)<br>2 - GRAPH\_SUM(监控项值代表整个饼图; 仅用于饼图和分解饼图)|图形监控项类型。| |item|<|x|<|<|单独监控项。| |<|host|x|`string`|<|监控项主机。| |<|key|x|`string`|<|监控项键值。|

en-us	# template.massadd
zh-cn	# 批量添加模板

en-us	# template.massremove
zh-cn	# 批量删除模板

en-us	# template.massupdate
zh-cn	# 批量更新模板

en-us	# > Template object  The following objects are directly related to the `template` API.
zh-cn	# > 模版对象  以下对象都是与`template` 直接相关的API。

en-us	#### Templates  In a [template](/manual/config/templates/template) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### 模板  在 [模板](/manual/config/templates/template) 配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |*标签*^[2](supported_by_location_user#footnotes)^|<|<| | |标签名称|支持| |^|标签值|支持|

en-us	#### Templates  Templates are available for [remote monitoring](/manual/appendix/items/remote_stats) of Zabbix server or proxy internal metrics from an external instance:  -   Remote Zabbix server -   Remote Zabbix proxy  Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring.
zh-cn	#### 模版  Zabbix server和Zabbix proxy  [远程监控](/manual/appendix/items/remote_stats) 模板:  -   Template App Remote Zabbix server -   Template App Remote Zabbix proxy  请注意，为了使用模板远程监视多个外部实例，每个外部实例监视都需要一个单独的主机。

en-us	# Template  This class is designed to work with templates.  Object references:  -   [Template](/manual/api/reference/template/object#template)  Available methods:  -   [template.create](/manual/api/reference/template/create) - creating new templates -   [template.delete](/manual/api/reference/template/delete) - deleting templates -   [template.get](/manual/api/reference/template/get) - retrieving templates -   [template.massadd](/manual/api/reference/template/massadd) - adding related objects to templates -   [template.massremove](/manual/api/reference/template/massremove) - removing related objects from templates -   [template.massupdate](/manual/api/reference/template/massupdate) - replacing or removing related objects from templates -   [template.update](/manual/api/reference/template/update) - updating templates
zh-cn	# 模版  这个类是为使用模板而设计的。  对象引用:  -   [模版](/manual/api/reference/template/object#template)  可用方法:  -   [template.create](/manual/api/reference/template/create) - 创建一个新模版 -   [template.delete](/manual/api/reference/template/delete) - 删除模版 -   [template.get](/manual/api/reference/template/get) - 检索模版 -   [template.massadd](/manual/api/reference/template/massadd) - 向模板添加相关对象 -   [template.massremove](/manual/api/reference/template/massremove) - 从模板中删除相关对象 -   [template.massupdate](/manual/api/reference/template/massupdate) - 从模板中替换或删除相关对象 -   [template.update](/manual/api/reference/template/update) - 更新模版

en-us	# template.update
zh-cn	# 更新模板

en-us	##### Terminology  Setting this option enforces to use TLS connection to database from Zabbix server/proxy and frontend to database:  -   required - connect using TLS as transport mode without identity     checks; -   verify\_ca - connect using TLS and verify certificate; -   verify\_full - connect using TLS, verify certificate and verify that     database identity (CN) specified by DBHost matches its certificate;
zh-cn	##### 术语  通过设置此选项强制Zabbix Server/proxy/前端使用TLS连接数据库:  - required - 使用无需身份检查的TLS作为数据传输的连接; - verify\_ca - 使用TLS连接并验证证书; - verify\_full - 使用TLS连接，验证证书及DBHost指定的数据库身份(CN)匹配的证书;