en-us	#### Display  In *Monitoring → Maps* the respective color will be displayed on the link if the trigger goes into a problem state.  ![](../../../../../assets/en/manual/config/visualization/map_problem.png)  ::: noteclassic If multiple triggers go into a problem state, the problem with the highest severity will determine the link style and color. If multiple triggers with the same severity are assigned to the same map link, the one with the lowest ID takes precedence. Note also that:\ \ 1. *Minimum trigger severity* and *Show suppressed problem* settings from map configuration affect which problems are taken into account.\ 2. In the case of triggers with multiple problems (multiple problem generation), each problem may have a severity that differs from trigger severity (changed manually), may have different tags (due to macros), and may be suppressed. :::
zh-cn	#### 展示  在 *监控→ 地图* 中，在触发器进入问题状态时相应的颜色的链接将显示。  ![](../../../../../assets/en/manual/config/visualization/map_problem.png)  ::: noteclassic 如果多个触发器进入问题状态，则问题具有最高严重性的将确定链接样式和颜色。如果具有相同严重性的多个触发器分配给同一个映射链接，ID 最低的优先。另请注意：\ \ 1. *最低严重性触发*和*显示抑制问题*设置从地图配置影响考虑哪些问题。\ 2. 在触发器有多个问题的情况下（发生了多个问题），每个问题的严重性可能与触发器不同严重性（手动更改），可能有不同的标签（由于宏），并且可能被压制。 :::

en-us	#### Display  The following screen will be displayed when trying to access the Zabbix frontend while in maintenance mode. The screen is refreshed every 30 seconds in order to return to a normal state without user intervention when the maintenance is over.  ![](../../../assets/en/manual/web_interface/frontend_maintenance.png)  IP addresses defined in ZBX\_GUI\_ACCESS\_IP\_RANGE will be able to access the frontend as always.
zh-cn	#### 显示  在维护模式下尝试访问 Zabbix 前端时，将显示以下屏幕。屏幕每 30 秒刷新一次，以便在维护结束时无需用户干预即可返回正常状态。  ![](../../../assets/en/manual/web_interface/frontend_maintenance.png)  ZBX\_GUI\_ACCESS\_IP\_RANGE 中定义的 IP 地址将能够像往常一样访问前端。

en-us	##### Display  This is the result in *Monitoring → Latest data*:  ![](../../../../../assets/en/manual/config/items/itemtypes/trapped_data.png){width="600"}  Note that if a single numeric value is sent in, the data graph will show a horizontal line to the left and to the right of the time point of the value.
zh-cn	##### 展示  这是 *监控 → 最新数据 * 中的结果：  ![](../../../../../assets/en/manual/config/items/itemtypes/trapped_data.png){width="600"}  请注意，如果传入一个数值，数据图将在该值的时间点的左边和右边显示一条水平线。

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

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

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

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

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

en-us	#### Easy Connect  Easy Connect uses the following parameters to connect to the database:  -   *Host* - the host name or IP address of the database server computer     (DBHost parameter in the configuration file). -   *Port* - the listening port on the database server (DBPort parameter     in the configuration file; if not set the default 1521 port will be     used). -   <service\_name> - the service name of the database you want to     access (DBName parameter in the configuration file).  **Example:**  Database parameters set in the server or proxy configuration file (zabbix\_server.conf and zabbix\_proxy.conf):      DBHost=localhost     DBPort=1521     DBUser=myusername     DBName=ORCL     DBPassword=mypassword  Connection string used by Zabbix to establish connection:      DBUser/DBPassword@DBHost:DBPort/DBName  During Zabbix frontend installation, set the corresponding parameters in the *Configure DB connection* step of the setup wizard:  -   Database host: localhost -   Database port: 1521 -   Database name: ORCL -   User: myusername -   Password: mypassword  ![](../../../../assets/en/manual/appendix/install/oracle_easy_connect.png){width="600"}  Alternatively, these parameters can be set in the frontend configuration file (zabbix.conf.php):      $DB["TYPE"]                     = 'ORACLE';     $DB["SERVER"]                   = 'localhost';     $DB["PORT"]             = '1521';     $DB["DATABASE"]                 = 'ORCL';     $DB["USER"]                     = 'myusername';     $DB["PASSWORD"]                 = 'mypassword';
zh-cn	#### Easy Connect  Easy Connect 使用以下参数连接到数据库：  -   *Host* - 数据库服务器的主机名或 IP 地址（配置文件中的 DBHost 参数）。 -   *Port* - 数据库服务器上的监听端口（配置文件中的 DBPort 参数;如果未设置，将使用默认的 1521 端口） -   <service\_name> - 要访问数据库的服务名称（配置文件中的 DBName 参数）。  **例:** 在server 或 proxy 配置文件中设置的数据库参数 (zabbix\_server.conf and zabbix\_proxy.conf):      DBHost=localhost     DBPort=1521     DBUser=myusername     DBName=ORCL     DBPassword=mypassword  Zabbix 用于建立连接的字符串:      DBUser/DBPassword@DBHost:DBPort/DBName  在 Zabbix 前端安装过程中，在安装向导的*Configure DB connection*步骤中设置相应的参数：  -   Database host: localhost -   Database port: 1521 -   Database name: ORCL -   User: myusername -   Password: mypassword  ![](../../../../assets/en/manual/appendix/install/oracle_easy_connect.png){width="600"}  或者，可以在前端配置文件 (zabbix.conf.php) 中设置这些参数:      $DB["TYPE"]                     = 'ORACLE';     $DB["SERVER"]                   = 'localhost';     $DB["PORT"]             = '1521';     $DB["DATABASE"]                 = 'ORCL';     $DB["USER"]                     = 'myusername';     $DB["PASSWORD"]                 = 'mypassword';

en-us	#### Element tags  Element tag values are explained in the table below.
zh-cn	#### 元素标签  下表解释了元素标签值。

en-us	#### Element tags  Element tag values are explained in the table below.
zh-cn	#### 元素标签  下表解释了元素标记值。

en-us	### Enabling high availability
zh-cn	### 启用高可用集群

en-us	##### Encryption  The **Encryption** tab allows you to require [encrypted](/manual/encryption) connections with the host.  |Parameter|Description| |--|--------| |*Connections to host*|How Zabbix server or proxy connects to Zabbix agent on a host: no encryption (default), using PSK (pre-shared key) or certificate.| |*Connections from host*|Select what type of connections are allowed from the host (i.e. from Zabbix agent and Zabbix sender). Several connection types can be selected at the same time (useful for testing and switching to other connection type). Default is "No encryption".| |*Issuer*|Allowed issuer of certificate. Certificate is first validated with CA (certificate authority). If it is valid, signed by the CA, then the *Issuer* field can be used to further restrict allowed CA. This field is intended to be used if your Zabbix installation uses certificates from multiple CAs. If this field is empty then any CA is accepted.| |*Subject*|Allowed subject of certificate. Certificate is first validated with CA. If it is valid, signed by the CA, then the *Subject* field can be used to allow only one value of *Subject* string. If this field is empty then any valid certificate signed by the configured CA is accepted.| |*PSK identity*|Pre-shared key identity string.<br>Do not put sensitive information in the PSK identity, it is transmitted unencrypted over the network to inform a receiver which PSK to use.| |*PSK*|Pre-shared key (hex-string). Maximum length: 512 hex-digits (256-byte PSK) if Zabbix uses GnuTLS or OpenSSL library, 64 hex-digits (32-byte PSK) if Zabbix uses mbed TLS (PolarSSL) library. Example: 1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952|
zh-cn	##### 加密   **加密** 选项卡允许建立与主机的 [加密](/manual/encryption) 连接。  |选项|描述| |---------|-----------| |*连接到主机*|Zabbix server 或 proxy 如何与 Zabbix agent 连接：不加密（默认），使用 PSK（预共享密钥）或证书。| |*从主机连接*|选择允许来自主机的连接类型（即来自 Zabbix agent 和 Zabbix sender）。可以同时选择多种连接类型（用于测试和切换到其他连接类型）。默认为“不加密”。| |*发行者*|许可的证书颁发者。证书首先通过 CA （证书颁发机构）进行验证。如果它是由 CA 签名的有效证书，则 *Issuer* 字段可用于进一步限制允许的 CA。如果 Zabbix 安装使用来自多个 CA 的证书，则使用此字段。如果此字段为空，则接受任何 CA。| |*主体*|允许的证书主体。证书首先通过 CA （证书颁发机构）进行验证。如果它是由 CA 签名的有效证书，则 *主体* 字段只能用于允许 *主体* 字符串的一个值。如果此字段为空，则接受配置的 CA 签名的任何有效证书。| |*共享密钥身份*|预共享密钥标识字符串。<br>不要将敏感信息放在此处，它会在网络上以未加密方式传输，以通知接收者使用哪个 PSK。| |*共享密钥（PSK）*|预共享密钥（十六进制字符串）。最大长度：如果 Zabbix 使用 GnuTLS 或 OpenSSL 库，则为 512 个十六进制数字（256 字节 PSK），如果 Zabbix 使用 mbed TLS（PolarSSL）库，则为 64 个十六进制数字（32 字节 PSK）。示例：1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952。|

en-us	#### Error messages  ODBC error messages are structured into fields to provide detailed information. For example:      Cannot execute ODBC query: [SQL_ERROR]:[42601][7][ERROR: syntax error at or near ";"; Error while executing the query]     └───────────┬───────────┘  └────┬────┘ └──┬──┘└┬┘└─────────────────────────────┬─────────────────────────────────────┘                 │                   │         │    └─ Native error code            └─ Native error message                 │                   │         └─ SQLState                 └─ Zabbix message   └─ ODBC return code  Note that the error message length is limited to 2048 bytes, so the message can be truncated. If there is more than one ODBC diagnostic record Zabbix tries to concatenate them (separated with `|`) as far as the length limit allows.
zh-cn	#### 错误信息  ODBC错误消息被构造成字段,以提供详细信息.例如：      Cannot execute ODBC query: [SQL_ERROR]:[42601][7][ERROR: syntax error at or near ";"; Error while executing the query]     └───────────┬───────────┘  └────┬────┘ └──┬──┘└┬┘└─────────────────────────────┬─────────────────────────────────────┘                 │                   │         │    └─ Native error code            └─ Native error message                 │                   │         └─ SQLState                 └─ Zabbix message   └─ ODBC return code  请注意，错误消息长度限制为2048字节，因此信息可以被截断。如果有多个ODBC诊断记录，只要长度允许，Zabbix将尝试把它们连接起来（用`|`分隔）。

en-us	#### Escalation examples
zh-cn	#### 升级示例

en-us	#### Evaluation period  An evaluation period is used in functions referencing the item history. It allows to specify the interval we are interested in. It can be specified as time period (30s, 10m, 1h) or as a value range (\#5 - for five latest values).  The evaluation period is measured up to "now" - where "now" is the latest recalculation time of the trigger (see [Calculation time](#calculation_time) above); "now" is not the "now" time of the server.  The evaluation period specifies either:  -   To consider all values between "now-time period" and "now" (or, with     time shift, between "now-time shift-time period" and     "now-time\_shift") -   To consider no more than the num count of values from the past, up     to "now"     -   If there are 0 available values for the time period or num count         specified - then the trigger or calculated item that uses this         function becomes unsupported  Note that:  -   If only a single function (referencing data history) is used in the     trigger, "now" is always the latest received value. For example, if     the last value was received an hour ago, the evaluation period will     be regarded as up to the latest value an hour ago. -   A new trigger is calculated as soon as the first value is received     (history functions); it will be calculated within 30 seconds for     time-based functions. Thus the trigger will be calculated even     though perhaps the set evaluation period (for example, one hour) has     not yet passed since the trigger was created. The trigger will also     be calculated after the first value, even though the evaluation     range was set, for example, to ten latest values.
zh-cn	#### 评估周期  在引用监控项历史的函数中使用评估周期。 它允许指定我们感兴趣的间隔。它可以是 指定为时间段 (30s, 10m, 1h) 或值范围 (#5 - for 五个最近值）。  评估周期测量到“now(现在)” - 其中“now(现在)”是 触发器的最新重新计算时间（参见[Calculation time](#calculation_time) 上面）； “now(现在)”不是现在的“now(现在)”服务器时间。  评估周期指定：  - 考虑“now-time period（现在时间周期）”和“now(现在)”之间的所有值（或者，与 时间偏移量，在“now-time shift-time period(现在时间偏移点时间区间)”和 “now-time\_shift(现在\偏移量)”） - 考虑不超过过去的值的数量，向上 到“now(现在)”    - 如果时间周期或计数有 0 个可用值 指定 - 然后是使用它的触发器或计算项 功能变得不受支持.  注意：  - 如果在触发器中只使用一个函数(引用监控数据历史)，那么“now（现在）”总是最新收到的值。例如，如果最后一个值是在一小时前收到的，那么评估期将被视为一小时前的最新值。 - 当第一个监控值被接收时，一个新的触发器被计算出来(history functions 历史函数);基于时间的函数将在30秒内计算。因此，即使设置的评估周期(例如 一个小时)自触发器创建以来还没有过去，也将计算触发器。触发器也将在第一个值之后计算，即使计算范围被设置为10个最新的值。

en-us	# event.acknowledge
zh-cn	# 确认

en-us	#### Event correlation  Create custom event correlation rules.  [Correlation API](/manual/api/reference/correlation)
zh-cn	#### 事件关联性  创建自定义事件相关规则。  [Correlation API](/manual/api/reference/correlation)

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

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

en-us	#### Events  Retrieve events generated by triggers, network discovery and other Zabbix systems for more flexible situation management or third-party tool integration.  [Event API](/manual/api/reference/event)
zh-cn	#### 事件  检索由触发器、网络发现和其他 Zabbix 系统生成的事件，以实现更灵活的情况管理或第三方工具集成。  [Event API](/manual/api/reference/event)

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

en-us	# Event  This class is designed to work with events.  Object references:\  -   [Event](/manual/api/reference/event/object#host)  Available methods:\  -   [event.get](/manual/api/reference/event/get) - retrieving events -   [event.acknowledge](/manual/api/reference/event/acknowledge) -     acknowledging events
zh-cn	# 事件  此类用于处理事件。  对象引用：\  -   [事件](/manual/api/reference/event/object#主机)  可用方法：\  -   [event.get](/manual/api/reference/event/get) - 获取事件 -   [event.acknowledge](/manual/api/reference/event/acknowledge) -     确认事件

en-us	### Example
zh-cn	### 示例

en-us	##### Example 1  General example:  |Parameter|Description| |--|--------| |**OID**|1.2.3.45.6.7.8.0 (or .1.2.3.45.6.7.8.0)| |**Key**|<Unique string to be used as reference to triggers><br>For example, "my\_param".|  Note that OID can be given in either numeric or string form. However, in some cases, string OID must be converted to numeric representation. Utility snmpget may be used for this purpose:      shell> snmpget -On localhost public enterprises.ucdavis.memory.memTotalSwap.0
zh-cn	##### 示例 1  通用示例：  |参数 |描述 | |---------------------|-| |**OID**|1.2.3.45.6.7.8.0 (or .1.2.3.45.6.7.8.0)| |**键值**|用作触发器引用的唯一字符串><br>例如, "my\_param".|  请注意，OID 可以以数字或字符串形式给出。但是，在某些情况下，必须将字符串 OID 转换为数字表示。实用程序 snmpget 可用于此目的：     shell> snmpget -On localhost public enterprises.ucdavis.memory.memTotalSwap.0

en-us	##### Example 1  Send simple GET requests to retrieve data from services such as Elasticsearch:  -   Create a GET item with URL: `localhost:9200/?pretty` -   Notice the response:  ```{=html} <!-- --> ```     {       "name" : "YQ2VAY-",       "cluster_name" : "elasticsearch",       "cluster_uuid" : "kH4CYqh5QfqgeTsjh2F9zg",       "version" : {         "number" : "6.1.3",         "build_hash" : "af51318",         "build_date" : "2018-01-26T18:22:55.523Z",         "build_snapshot" : false,         "lucene_version" : "7.1.0",         "minimum_wire_compatibility_version" : "5.6.0",         "minimum_index_compatibility_version" : "5.0.0"       },       "tagline" : "You know, for search"     }  -   Now extract the version number using a JSONPath preprocessing step:     `$.version.number`
zh-cn	 ##### 示例 1  发送一个简单GET请求，以从其他服务获取数据。案例为Elasticsearch：  -   创建一个从URL `localhost:9200/?pretty` GET 的监控项 -   注意获得的相应内容：  ```{=html} <!-- --> ```     {       "name" : "YQ2VAY-",       "cluster_name" : "elasticsearch",       "cluster_uuid" : "kH4CYqh5QfqgeTsjh2F9zg",       "version" : {         "number" : "6.1.3",         "build_hash" : "af51318",         "build_date" : "2018-01-26T18:22:55.523Z",         "build_snapshot" : false,         "lucene_version" : "7.1.0",         "minimum_wire_compatibility_version" : "5.6.0",         "minimum_index_compatibility_version" : "5.0.0"       },       "tagline" : "You know, for search"     }  -  现在可以使用JSONPath 预处理步骤获取版本号信息： `$.version.number` 

en-us	##### Example 1  Something very simple:      UserParameter=ping[*],echo $1  We may define unlimited number of items for monitoring all having format ping\[something\].  -   ping\[0\] - will always return '0' -   ping\[aaa\] - will always return 'aaa'
zh-cn	##### 示例1   先来一个简单的：\      UserParameter=ping[*],echo $1  我们可以定义无数个监控项来监控所有形如ping\[something\]格式的东西。\  -   ping\[0\] - 将总是返回 ‘ 0 ’ -   ping\[aaa\] - 将总是返回 ‘aaa’

en-us	##### Example 1  Temperature in server room is too high.  Problem expression:      last(/server/temp)>20  Recovery expression:      last(/server/temp)<=15
zh-cn	##### 示例 1   机房温度过高。  问题表达式:      last(/server/temp)>20  恢复表达式：      last(/server/temp)<=15

en-us	##### Example 1  The processor load is too high on Zabbix server.      last(/Zabbix server/system.cpu.load[all,avg1])>5  By using the function 'last()', we are referencing the most recent value. `/Zabbix server/system.cpu.load[all,avg1]` gives a short name of the monitored parameter. It specifies that the host is 'Zabbix server' and the key being monitored is 'system.cpu.load\[all,avg1\]'. Finally, `>5` means that the trigger is in the PROBLEM state whenever the most recent processor load measurement from Zabbix server is greater than 5.
zh-cn	##### 示例 1 Zabbix server上的处理器负载太高。      last(/Zabbix server/system.cpu.load[all,avg1])>5  '/Zabbix server/system.cpu.load[all,avg1]' 给出了被监控参数的简短名称。它指定了服务器是“Zabbix server”，监控项的键值是“system.cpu.load[all,avg1]”。通过使用函数“last()”获取最新的值。最后，“>5”意味着当Zabbix server最新获取的处理器负载值大于5时触发器就会处于异常状态。

en-us	##### Example 1  To create a "Web scenario failed" trigger, you can define a trigger expression:      last(/host/web.test.fail[Scenario])<>0  Make sure to replace 'Scenario' with the real name of your scenario.
zh-cn	##### 示例 1  要创建 "Web scenario failed（Web 场景失败）"触发器，您可以定义触发器表达式：      last(/host/web.test.fail[Scenario])<>0  确保将 'Scenario' 替换为场景的真实名称。

en-us	##### Example 1  Total disk space of host group 'MySQL Servers'.      sum(last_foreach(/*/vfs.fs.size[/,total]?[group="MySQL Servers"]))
zh-cn	##### 示例 1  主机组“  MySQL Servers”的总磁盘空间      sum(last_foreach(/*/vfs.fs.size[/,total]?[group="MySQL Servers"]))

en-us	##### Example 1  Use of host-level macro in the "Status of SSH daemon" item key:  `net.tcp.service[ssh,,{$SSH_PORT}]`  This item can be assigned to multiple hosts, providing that the value of **{$SSH\_PORT}** is defined on those hosts.
zh-cn	##### 示例 1  在“SSH daemon 状态”项键中使用主机级宏：`net.tcp.service[ssh,,{$SSH_PORT}]`  此项可以分配给多个主机，前提是**{$SSH\_PORT}** 在这些主机上定义。

en-us	##### Example 1  Use of the following expression in low-level discovery to discover databases except a database with a specific name:      ^TESTDATABASE$  ![regexp\_expr\_2.png](../../assets/en/manual/regular_expressions/regexp_expr_2.png)  Chosen *Expression type*: "Result is FALSE". Doesn't match name, containing string "*TESTDATABASE*".
zh-cn	##### 示例1  在低级别自动发现中使用下列表达式发现具有特定名称的数据库以外的数据库：      ^TESTDATABASE$  ![regexp\_expr\_2.png](../../assets/en/manual/regular_expressions/regexp_expr_2.png)  选择的 *Expression type（表达式类型）*：“Result is FALSE（结果为假）”。 与名称不匹配，包含字符串 "*TESTDATABASE*"。

en-us	##### Example 1  Using host metadata to distinguish between Linux and Windows hosts.  Say you would like the hosts to be autoregistered by the Zabbix server. You have active Zabbix agents (see "Configuration" section above) on your network. There are Windows hosts and Linux hosts on your network and you have "Linux by Zabbix agent" and "Windows by Zabbix agent" templates available in your Zabbix frontend. So at host registration, you would like the appropriate Linux/Windows template to be applied to the host being registered. By default, only the hostname is sent to the server at autoregistration, which might not be enough. In order to make sure the proper template is applied to the host you should use host metadata.
zh-cn	##### 例1  使用主机元数据区分Linux和Windows主机。  假设你想让主机自动注册到Zabbix server。 网络中有配置了active agent(参阅上述"配置"章节)的Windows和Linux主机，并且Zabbix页面中有"Linux by Zabbix agent"和"Windows by Zabbix agent"这两个可用模板。 于是你想在注册过程中将Linux/Windows模板自动应用到对应主机。在自动注册过程中，默认只有主机名称会发送给Zabbix server，可是这些信息并不够。要想确保合适的模板应用到对应主机上，需要使用主机元数据。

en-us	##### Example 2  Calculating a 10-minute average of the number of values processed by Zabbix.  Use of function **avg**:      avg(/Zabbix Server/zabbix[wcache,values],10m)  Note that extensive use of calculated items with long time periods may affect performance of Zabbix server.
zh-cn	##### 示例 2  计算 Zabbix 处理的值的 10 分钟平均值。  使用函数 **avg**:      avg(/Zabbix Server/zabbix[wcache,values],10m)  请注意，可计算监控项选取长时间段的数据会影响 Zabbix 服务器的性能。

en-us	##### Example 2  Free disk space is too low.  Problem expression: it is less than 10GB for last 5 minutes      max(/server/vfs.fs.size[/,free],5m)<10G  Recovery expression: it is more than 40GB for last 10 minutes      min(/server/vfs.fs.size[/,free],10m)>40G
zh-cn	##### 示例 2   磁盘剩余空间过低。  问题表达式: 最后 5 分钟小于 10GB      max(/server/vfs.fs.size[/,free],5m)<10G  恢复表达式：最近10分钟超过40GB      min(/server/vfs.fs.size[/,free],10m)>40G

en-us	##### Example 2  Let's add more sense!      UserParameter=mysql.ping[*],mysqladmin -u$1 -p$2 ping | grep -c alive  This parameter can be used for monitoring availability of MySQL database. We can pass user name and password:      mysql.ping[zabbix,our_password]
zh-cn	##### 示例2  让我们更进一步！\      UserParameter=mysql.ping[*],mysqladmin -u$1 -p$2 ping | grep -c alive  这个用户自定义参数可以用来监控 MySQL 数据库的可用性状态。我们可以传入用户名和密码：      mysql.ping[zabbix,our_password]

en-us	##### Example 2  Message:      Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])}  When you receive the message, the message will be replaced by something like:      Processor load is: 1.45
zh-cn	##### 示例 2  消息：      Processor load is: {?last(/zabbix.zabbix.com/system.cpu.load[,avg1])}  当收到消息时，将被替换为类似如下内容：      Processor load is: 1.45

en-us	##### Example 2  Monitoring of uptime:  |Parameter|Description| |--|--------| |**OID**|MIB::sysUpTime.0| |**Key**|router.uptime| |**Value type**|Float| |**Units**|uptime| |**Preprocessing step: Custom multiplier**|0.01|
zh-cn	##### 示例 2  监控正常运行时间：  |参数|说明| |---------|------------| |**OID**|MIB::sysUpTime.0| |**Key**|router.uptime| |**Value type**|浮点数| |**Units**|uptime| |**Multiplier**|0.01| |**Preprocessing step: Custom multiplier**|0.01|

en-us	##### Example 2  Send simple POST requests to retrieve data from services such as Elasticsearch:  -   Create a POST item with URL:     `http://localhost:9200/str/values/_search?scroll=10s` -   Configure the following POST body to obtain the processor load (1     min average per core)  ```{=html} <!-- --> ```     {         "query": {             "bool": {                 "must": [{                     "match": {                         "itemid": 28275                     }                 }],                 "filter": [{                     "range": {                         "clock": {                             "gt": 1517565836,                             "lte": 1517566137                         }                     }                 }]             }         }     }  -   Received:  ```{=html} <!-- --> ```     {         "_scroll_id": "DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAAkFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAJRZZUTJWQVktVFNacU5nRHhlcEI0QUxRAAAAAAAAACYWWVEyVkFZLVRTWnFOZ0R4ZXBCNEFMUQAAAAAAAAAnFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAKBZZUTJWQVktVFNacU5nRHhlcEI0QUxR",         "took": 18,         "timed_out": false,         "_shards": {             "total": 5,             "successful": 5,             "skipped": 0,             "failed": 0         },         "hits": {             "total": 1,             "max_score": 1.0,             "hits": [{                 "_index": "dbl",                 "_type": "values",                 "_id": "dqX9VWEBV6sEKSMyk6sw",                 "_score": 1.0,                 "_source": {                     "itemid": 28275,                     "value": "0.138750",                     "clock": 1517566136,                     "ns": 25388713,                     "ttl": 604800                 }             }]         }     }  -   Now use a JSONPath preprocessing step to get the item value:     `$.hits.hits[0]._source.value`
zh-cn	 ##### 示例 2  发送一个简单POST请求，从其他服务抓取数据。以Elasticsearch为例：  -   创建一个POST监控项使用此URL:    `http://localhost:9200/str/values/_search?scroll=10s` -   配置以下的POST请求体获取处理器负载（1分钟平均值/核心）  ```{=html} <!-- --> ```     {         "query": {             "bool": {                 "must": [{                     "match": {                         "itemid": 28275                     }                 }],                 "filter": [{                     "range": {                         "clock": {                             "gt": 1517565836,                             "lte": 1517566137                         }                     }                 }]             }         }     }  -   得到响应:  ```{=html} <!-- --> ```     {         "_scroll_id": "DnF1ZXJ5VGhlbkZldGNoBQAAAAAAAAAkFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAJRZZUTJWQVktVFNacU5nRHhlcEI0QUxRAAAAAAAAACYWWVEyVkFZLVRTWnFOZ0R4ZXBCNEFMUQAAAAAAAAAnFllRMlZBWS1UU1pxTmdEeGVwQjRBTFEAAAAAAAAAKBZZUTJWQVktVFNacU5nRHhlcEI0QUxR",         "took": 18,         "timed_out": false,         "_shards": {             "total": 5,             "successful": 5,             "skipped": 0,             "failed": 0         },         "hits": {             "total": 1,             "max_score": 1.0,             "hits": [{                 "_index": "dbl",                 "_type": "values",                 "_id": "dqX9VWEBV6sEKSMyk6sw",                 "_score": 1.0,                 "_source": {                     "itemid": 28275,                     "value": "0.138750",                     "clock": 1517566136,                     "ns": 25388713,                     "ttl": 604800                 }             }]         }     }  -   现在可以使用JSONPath 预处理步骤获取监控项的值： `$.hits.hits[0]._source.value`  

en-us	##### Example 2  Sum of latest values of all items matching net.if.in\[\*\] on the host.      sum(last_foreach(/host/net.if.in[*]))
zh-cn	##### 示例 2  主机上与 net.if.in[*]匹配的所有项的最新值之和。      sum(last_foreach(/host/net.if.in[*]))

en-us	##### Example 2  To create a "Web scenario failed" trigger with a useful problem description in the trigger name, you can define a trigger with name:      Web scenario "Scenario" failed: {ITEM.VALUE}  and trigger expression:      length(last(/host/web.test.error[Scenario]))>0 and last(/host/web.test.fail[Scenario])>0  Make sure to replace 'Scenario' with the real name of your scenario.
zh-cn	##### 示例 2  要在触发器名称中创建一个带有有用问题描述的"Web scenario failed（ Web 场景失败）"触发器，您可以使用名称定义触发器：      Web scenario "Scenario" failed: {ITEM.VALUE}  和触发表达式：      length(last(/host/web.test.error[Scenario]))>0 and last(/host/web.test.fail[Scenario])>0  确保将 'Scenario' 替换为场景的真实名称。

en-us	##### Example 2  Use of host-level macro in the "CPU load is too high" trigger:  `last(/ca_001/system.cpu.load[,avg1])>{$MAX_CPULOAD}`  Such a trigger would be created on the template, not edited in individual hosts.  ::: notetip If you want to use the amount of values as the function parameter (for example, **max(/host/key,\#3)**), include hash mark in the macro definition like this: SOME\_PERIOD => \#3 :::
zh-cn	##### 示例 2  在“CPU负载太高”触发器中使用主机级宏：`last(/ca_001/system.cpu.load[,avg1])>{$MAX_CPULOAD}`  这样的触发器将在模板上创建，而不是在个别主机。  ::: notetip 如果要使用值的数量作为函数参数（例如，**max(/host/key,\#3)**），在宏定义中包含如下哈希标记： SOME\_PERIOD => \#3 :::

en-us	##### Example 2  www.example.com is overloaded.      last(/www.example.com/system.cpu.load[all,avg1])>5 or min(/www.example.com/system.cpu.load[all,avg1],10m)>2   The expression is true when either the current processor load is more than 5 or the processor load was more than 2 during last 10 minutes.
zh-cn	##### 示例 2  www.example.com 已超载。      last(/www.example.com/system.cpu.load[all,avg1])>5 or min(/www.example.com/system.cpu.load[all,avg1],10m)>2   当前处理器负载超过5或过去10分钟内CPU负载都超过2。

en-us	##### Example 3  Average processor load of host group 'MySQL Servers'.      avg(last_foreach(/*/system.cpu.load[,avg1]?[group="MySQL Servers"]))
zh-cn	##### 示例 3  主机组“MySQL Servers”的平均处理器负载。      avg(last_foreach(/*/system.cpu.load[,avg1]?[group="MySQL Servers"]))

en-us	##### Example 3  How many lines matching a regular expression in a file?      UserParameter=wc[*],grep -c "$2" $1  This parameter can be used to calculate number of lines in a file.      wc[/etc/passwd,root]     wc[/etc/services,zabbix]
zh-cn	##### 示例3  一个文件中有多少行匹配正则表达式？      UserParameter=wc[*],grep -c "$2" $1  这个用户自定义参数能用来计算一个文件中有多少行匹配相应的表达式。就像下面一样：      wc[/etc/passwd,root]     wc[/etc/services,zabbix]

en-us	##### Example 3  Message:      Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})}     MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)}     MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)}  When you receive the message, the message will be replaced by something like:      Latest value: 1.45     MAX for 15 minutes: 2.33     MIN for 15 minutes: 1.01
zh-cn	##### 示例 3  消息：      Latest value: {?last(/{HOST.HOST}/{ITEM.KEY})}     MAX for 15 minutes: {?max(/{HOST.HOST}/{ITEM.KEY},15m)}     MIN for 15 minutes: {?min(/{HOST.HOST}/{ITEM.KEY},15m)}  当收到消息时，将被替换为类似如下内容：      Latest value: 1.45     MAX for 15 minutes: 2.33     MIN for 15 minutes: 1.01

en-us	##### Example 3  To create a "Web application is slow" trigger, you can define a trigger expression:      last(/host/web.test.in[Scenario,,bps])<10000  Make sure to replace 'Scenario' with the real name of your scenario.
zh-cn	##### 示例 3  要创建 "Web application is slow（Web 应用程序慢）" 的触发器，可以定义以下触发器表达式：      last(/host/web.test.in[Scenario,,bps])<10000  确保将 'Scenario' 替换为场景的真实名称。

en-us	##### Example 3  Use of two macros in the "CPU load is too high" trigger:  `min(/ca_001/system.cpu.load[,avg1],{$CPULOAD_PERIOD})>{$MAX_CPULOAD}`  Note that a macro can be used as a parameter of trigger function, in this example function **min()**.
zh-cn	##### 示例 3  在“CPU负载太高”触发器中使用两个宏：`min(/ca_001/system.cpu.load[,avg1],{$CPULOAD_PERIOD})>{$MAX_CPULOAD}`  注意宏可以作为触发函数的参数，在这个示例函数**min()**。

en-us	##### Example 4  5-minute average of the number of queries per second for host group 'MySQL Servers'.      avg(avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m))
zh-cn	##### 示例 4  主机组“MySQL Servers”每秒平均查询次数5分钟平均值。      avg(avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m))

en-us	##### Example 4  A more complex scenario. After multiple messages to MySQL administrators and escalation to the manager, Zabbix will try to restart the MySQL database. It will happen if the problem exists for 2:30 hours and it hasn't been acknowledged.  If the problem still exists, after another 30 minutes Zabbix will send a message to all guest users.  If this does not help, after another hour Zabbix will reboot server with the MySQL database (second remote command) using IPMI commands.  ![](../../../../../assets/en/manual/config/escalations_d.png){width="600"}
zh-cn	##### 例4  更复杂的情况。在向MySQL管理员发送多条消息并升级到manager后，Zabbix将尝试重新启动MySQL数据库。如果问题存在2:30小时，但尚未确认，则会发生这种情况。  如果问题仍然存在，30分钟后，Zabbix将向所有来宾用户发送消息。  如果这没有帮助，再过一个小时，Zabbix将使用IPMI命令使用MySQL数据库（第二个远程命令）重新启动服务器。  ![](../../../../../assets/en/manual/config/escalations_d.png){width=“600”}

en-us	##### Example 4  Someone is downloading a large file from the Internet.  Use of function min:      min(/www.example.com/net.if.in[eth0,bytes],5m)>100K  The expression is true when number of received bytes on eth0 is more than 100 KB within last 5 minutes.
zh-cn	##### 示例 4  服务器网卡从 Internet 下载一个大文件。  min 函数的使用：      min(/www.example.com/net.if.in[eth0,bytes],5m)>100K  在过去5分钟内，eth0上接收字节数大于100kb时，表达式为true。

en-us	##### Example 4  Synchronize the agent unavailability condition with the item update interval:  -   define {$INTERVAL} macro and use it in the item update interval; -   use {$INTERVAL} as parameter of the agent unavailability trigger:  `nodata(/ca_001/agent.ping,{$INTERVAL})=1`
zh-cn	##### 示例 4  将代理不可用条件与项目更新同步间隔：  - 定义 {$INTERVAL} 宏并在项目更新间隔中使用它； - 使用 {$INTERVAL} 作为代理不可用触发器的参数：  `nodata(/ca_001/agent.ping,{$INTERVAL})=1`

en-us	##### Example 5  Average CPU load on all hosts in multiple host groups that have the specific tags.      avg(last_foreach(/*/system.cpu.load?[(group="Servers A" or group="Servers B" or group="Servers C") and (tag="Service:" or tag="Importance:High")]))
zh-cn	##### 示例 5  具有特定标记的多个主机组中所有主机的平均 CPU 负载。      avg(last_foreach(/*/system.cpu.load?[(group="Servers A" or group="Servers B" or group="Servers C") and (tag="Service:" or tag="Importance:High")]))

en-us	##### Example 5  Both nodes of clustered SMTP server are down.  Note use of two different hosts in one expression:      last(/smtp1.example.com/net.tcp.service[smtp])=0 and last(/smtp2.example.com/net.tcp.service[smtp])=0  The expression is true when both SMTP servers are down on both smtp1.example.com and smtp2.example.com.
zh-cn	##### 示例 5   SMTP服务群集的两个节点都停止。  注意在一个表达式中使用两个不同的主机:      last(/smtp1.example.com/net.tcp.service[smtp])=0 and last(/smtp2.example.com/net.tcp.service[smtp])=0  当两个SMTP服务器（smtp1.example.com 和 smtp2.example.com）的smtp服务关闭时为真。

en-us	##### Example 5  Connecting to Nginx status page and getting its metrics in bulk.  -   Configure Nginx following the [official     guide](https://nginx.ru/en/docs/http/ngx_http_stub_status_module.html).  ```{=html} <!-- --> ``` -   Configure a master item for bulk data collection:  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_a.png)  Sample Nginx stub status output:      Active connections: 1 Active connections:     server accepts handled requests      52 52 52      Reading: 0 Writing: 1 Waiting: 0  The next task is to configure dependent items that extract data.  -   Configure a sample dependent item for requests per second:  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_b.png)  -   Sample dependent item value preprocessing with regular expression     `server accepts handled requests\s+([0-9]+) ([0-9]+) ([0-9]+)`:  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_c.png){width="600"}  -   Check the complete result from stub module in *Latest data*:  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_d.png){width="600"}
zh-cn	 ##### 示例 5  链接Nginx状态页面，批量获取它的指标。  -   根据 [官方指南](https://nginx.ru/en/docs/http/ngx_http_stub_status_module.html)配置NGINX。  ```{=html} <!-- --> ``` -  配置一个主要监控项批量收集数据:   ![](../../../../../assets/en/manual/config/items/itemtypes/example5_a.png)  简单的Nginx状态也输出如下：      Active connections: 1 Active connections:     server accepts handled requests      52 52 52      Reading: 0 Writing: 1 Waiting: 0  下一个任务是任务是配置从属监控项提取数据。  -   配置简单从属监控项名以采集每秒请求数数据：  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_b.png)  -   这个简单从属监控项，需要配置正则表达式预处理步骤     `server accepts handled requests\s+([0-9]+) ([0-9]+) ([0-9]+)`:  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_c.png){width="600"}  -   对所有数据都配置好了从属监控项后，在 *最新数据* 中，可以查看到来自stub模块的完整结果  ![](../../../../../assets/en/manual/config/items/itemtypes/example5_d.png){width="600"}

en-us	##### Example 6  Calculation used on the latest item value sums of a whole host group.      sum(last_foreach(/*/net.if.out[eth0,bytes]?[group="video"])) / sum(last_foreach(/*/nginx_stat.sh[active]?[group="video"])) 
zh-cn	##### 示例 6  用于计算整个主机组的监控项最新值总和。      sum(last_foreach(/*/net.if.out[eth0,bytes]?[group="video"])) / sum(last_foreach(/*/nginx_stat.sh[active]?[group="video"])) 

en-us	##### Example 6  Receiving details of both the problem event and recovery event in a [recovery](/manual/config/notifications/action/recovery_operations) message:  Message:      Problem:      Event ID: {EVENT.ID}     Event value: {EVENT.VALUE}      Event status: {EVENT.STATUS}      Event time: {EVENT.TIME}     Event date: {EVENT.DATE}     Event age: {EVENT.AGE}     Event acknowledgment: {EVENT.ACK.STATUS}      Event update history: {EVENT.UPDATE.HISTORY}      Recovery:       Event ID: {EVENT.RECOVERY.ID}     Event value: {EVENT.RECOVERY.VALUE}      Event status: {EVENT.RECOVERY.STATUS}      Event time: {EVENT.RECOVERY.TIME}     Event date: {EVENT.RECOVERY.DATE}     Operational data: {EVENT.OPDATA}  When you receive the message, the macros will be replaced by something like:      Problem:      Event ID: 21874     Event value: 1      Event status: PROBLEM      Event time: 13:04:30     Event date: 2018.01.02     Event age: 5m     Event acknowledgment: Yes      Event update history: 2018.01.02 13:05:51 "John Smith (Admin)"     Actions: acknowledged.      Recovery:       Event ID: 21896     Event value: 0      Event status: OK      Event time: 13:10:07     Event date: 2018.01.02     Operational data: Current value is 0.83  ::: noteimportant Separate notification macros for the original problem event and recovery event are supported since Zabbix 2.2.0. :::
zh-cn	##### 示例 6  在同一个[恢复](/manual/config/notifications/action/recovery_operations)消息中接收故障事件和恢复事件的详情：  消息：      Problem:      Event ID: {EVENT.ID}     Event value: {EVENT.VALUE}      Event status: {EVENT.STATUS}      Event time: {EVENT.TIME}     Event date: {EVENT.DATE}     Event age: {EVENT.AGE}     Event acknowledgment: {EVENT.ACK.STATUS}      Event update history: {EVENT.UPDATE.HISTORY}      Recovery:       Event ID: {EVENT.RECOVERY.ID}     Event value: {EVENT.RECOVERY.VALUE}      Event status: {EVENT.RECOVERY.STATUS}      Event time: {EVENT.RECOVERY.TIME}     Event date: {EVENT.RECOVERY.DATE}     Operational data: {EVENT.OPDATA}  当收到消息时，宏将被替换为类似如下内容：       Problem:      Event ID: 21874     Event value: 1      Event status: PROBLEM      Event time: 13:04:30     Event date: 2018.01.02     Event age: 5m     Event acknowledgment: Yes      Event update history: 2018.01.02 13:05:51 "John Smith (Admin)"     Actions: acknowledged.      Recovery:       Event ID: 21896     Event value: 0      Event status: OK      Event time: 13:10:07     Event date: 2018.01.02     Operational data: Current value is 0.83  ::: noteimportant 自 Zabbix 2.2.0开始支持原始故障事件和恢复事件单独的通知宏。 :::

en-us	##### Example 6  Use host prototype macro to configure items for discovered hosts:  -   on a host prototype define user macro {$SNMPVALUE} with     {\#SNMPVALUE} [low-level     discovery](/manual/config/macros/lld_macros) macro as a value:  ![](../../../../assets/en/manual/config/macros/usermacro_example6.png)  -   assign *Generic SNMPv2* template to the host prototype; -   use {$SNMPVALUE} in the *SNMP OID* field of *Generic SNMPv2*     template items.
zh-cn	##### 示例 6  使用主机原型宏为发现的主机配置项目：  - 在主机原型上定义用户宏 {$SNMPVALUE}和{\#SNMPVALUE} [低级发现](/manual/config/macros/lld_macros) 宏作为值：  ![](../../../../assets/en/manual/config/macros/usermacro_example6.png)  - 将 *Generic SNMPv2* 模板分配给主机原型； - 在 *Generic SNMPv2* 的 *SNMP OID* 字段中使用 {$SNMPVALUE} 模板项。

en-us	##### Example 6  Zabbix agent needs to be upgraded.  Use of function find():      find(/example.example.com/agent.version,,"like","beta8")=1  The expression is true if Zabbix agent has version beta8.
zh-cn	##### 示例 6  Zabbix 代理需要升级。 函数 find() 的使用：      find(/example.example.com/agent.version,,"like","beta8")=1  如果 Zabbix 代理的版本为 beta8，则表达式为真。

en-us	##### Example 7  Server is unreachable.      count(/example.example.com/icmpping,30m,,"0")>5  The expression is true if host "example.example.com" is unreachable more than 5 times in the last 30 minutes.
zh-cn	##### 示例 7  服务器无法访问。      count(/example.example.com/icmpping,30m,,"0")>5  如果主机“example.example.com” 在过去 30 分钟内超过 5 次无法访问，则表达式为真。

en-us	##### Example 7  The total number of unsupported items in host group 'Zabbix servers'.      sum(last_foreach(/*/zabbix[host,,items_unsupported]?[group="Zabbix servers"]))
zh-cn	##### 示例 7  主机组“Zabbix servers”中不支持的监控项总数。       sum(last_foreach(/*/zabbix[host,,items_unsupported]?[group="Zabbix servers"]))

en-us	##### Example 8  No heartbeats within last 3 minutes.  Use of function nodata():      nodata(/example.example.com/tick,3m)=1  To make use of this trigger, 'tick' must be defined as a Zabbix [trapper](/manual/config/items/itemtypes/trapper) item. The host should periodically send data for this item using zabbix\_sender. If no data is received within 180 seconds, the trigger value becomes PROBLEM.  *Note* that 'nodata' can be used for any item type.
zh-cn	##### 示例 8  最近 3 分钟内没有心跳。 函数 nodata() 的使用：      nodata(/example.example.com/tick,3m)=1  要使用这个触发器，'tick'必须定义成一个[trapper陷阱器](/manual/config/items/itemtypes/trapper)监控项。主机应该使用zabbix_sender定期发送这个监控项的数据。如果在180秒内没有接收到数据，则触发值变为异常状态。  *注释* ‘nodata’可以在任何类型的监控项中使用。

en-us	##### Example configuration for Apache      # ..     ProxyPass "/" http://host/zabbix/     ProxyPassReverse "/" http://host/zabbix/     ProxyPassReverseCookiePath /zabbix /     ProxyPassReverseCookieDomain host zabbix.example.com     # ..
zh-cn	#####  Apache 的示例配置      # ..     ProxyPass "/" http://host/zabbix/     ProxyPassReverse "/" http://host/zabbix/     ProxyPassReverseCookiePath /zabbix /     ProxyPassReverseCookieDomain host zabbix.example.com     # ..

en-us	##### Example configuration for nginx      # ..     location / {     # ..     proxy_cookie_path /zabbix /;     proxy_pass http://192.168.0.94/zabbix/;     # ..
zh-cn	 #####  nginx 的示例配置      # ..     location / {     # ..     proxy_cookie_path /zabbix /;     proxy_pass http://192.168.0.94/zabbix/;     # ..

en-us	 *Example:*  Problem *Web camera 3 is down* has tags `type:video surveillance`, `floor:1st` and `name:webcam 3` and status *Warning*  The service **Web camera 3** has the only problem tag specified: `name:webcam 3`       ![](../../../assets/en/manual/config/services_example_tags.png){width=600}     Service status will change from *OK* to *Warning* when this problem is detected.   If the service **Web camera 3** had problem tags `name:webcam 3` and `floor:2nd`, its status would not be changed, when the problem is detected, because the conditions are only partially met. 
zh-cn	*示例：*  问题 *Web camera 3 is down* 有标签 `type:video surveillance`， `floor:1st` 和 `name:webcam 3` ，状态为 *Warning*  服务 **Web camera 3** 具有指定的唯一问题标签： `name:webcam 3`       ![](../../../assets/en/manual/config/services_example_tags.png){width=600}     检测到此问题时，服务状态将从 *OK* 变为 *Warning*。  如果服务 **Web camera 3** 有问题标签 `name:webcam 3` 和 `floor:2nd`，则在检测到问题时不会更改其状态，因为仅部分条件满足。

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 例如

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 参考示例

en-us	### Examples
zh-cn	 ### Examples例如

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	### 示例

en-us	### Examples
zh-cn	 ### 示例

en-us	### Examples
zh-cn	### 案例

en-us	### Examples
zh-cn	### 示例

en-us	#### Examples
zh-cn	#### 示例

en-us	#### Examples
zh-cn	#### 示例

en-us	#### Examples
zh-cn	#### 示例

en-us	#### - Examples and dealing with errors  To get a warning when you are about to run out of free disk space on your host, you may use a trigger expression like this:      timeleft(/host/vfs.fs.size[/,free],1h,0)}<1h  However, error code -1 may come into play and put your trigger in a problem state. Generally it's good because you get a warning that your predictions don't work correctly and you should look at them more thoroughly to find out why. But sometimes it's bad because -1 can simply mean that there was no data about the host free disk space obtained in the last hour. If you are getting too many false positive alerts, consider using more complicated trigger expression [^5]:      timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1  The situation is a bit more difficult with **forecast**. First of all, -1 may or may not put the trigger in a problem state depending on whether you have expression like `forecast(/host/item,(...))<...` or like `forecast(/host/item,(...))>...`  Furthermore, -1 may be a valid forecast if it's normal for the item value to be negative. But probability of this situation in the real world situation is negligible (see [how](/manual/config/triggers/expression) the operator **=** works). So add `... or forecast(/host/item,(...))=-1` or `... and forecast(/host/item,(...))<>-1` if you want or don't want to treat -1 as a problem respectively.  [^1]: For example, a simple trigger like     `timeleft(/host/item,1h,X) < 1h` may go into problem state when the     item value approaches X and then suddenly recover once value X is     reached. If the problem is item value being below X, use:     `last(/host/item) < X or timeleft(/host/item,1h,X) < 1h` If the     problem is item value being above X use:     `last(/host/item) > X or timeleft(/host/item,1h,X) < 1h`  [^2]: Polynomial degree can be from 1 to 6, *polynomial1* is equivalent     to *linear*. However, use higher degree polynomials [with     caution](https://en.wikipedia.org/wiki/Runge's_phenomenon). If the     evaluation period contains less points than needed to determine     polynomial coefficients, polynomial degree will be lowered (e.g.,     *polynomial5* is requested, but there are only 4 points, therefore     *polynomial3* will be fitted).  [^3]: For example, fitting *exponential* or *power* functions involves     calculating log() of item values. If data contains zeros or negative     numbers, you will get an error since log() is defined for positive     values only.  [^4]: For *linear*, *exponential*, *logarithmic* and *power* fits all     necessary calculations can be written explicitly. For *polynomial*     only *value* can be calculated without any additional steps.     Calculating *avg* involves computing polynomial antiderivative     (analytically). Computing *max*, *min* and *delta* involves     computing polynomial derivative (analytically) and finding its roots     (numerically). Solving f(t) = 0 involves finding polynomial roots     (numerically).  [^5]: But in this case -1 can cause your trigger to recover from the     problem state. To be fully protected use:     `timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and ({TRIGGER.VALUE}=0 and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1 or {TRIGGER.VALUE}=1)`
zh-cn	#### 5 示例和错误处理  要在主机上的可用磁盘空间即将用完时收到警告，可以使用如下触发器表达式：      timeleft(/host/vfs.fs.size[/,free],1h,0)}<1h  但是，错误代码 -1 可能会发挥作用并使你的触发器处于问题状态。一般来说，你会收到警告说明你的预测无法正常工作，你应该更彻底地查看它们以找出原因。但有时它很糟糕，因为 -1 可能只是意味着没有关于在过去一小时内获得的主机可用磁盘空间的数据。如果您收到太多误报警报，请考虑使用更复杂的触发器表达式 [^5]：      timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1   **forecast**情况有点困难。 首先，-1 可能会或可能不会将触发器置于问题状态，具体取决于您是否有表达式 像`forecast(/host/item,(...))<...`或像 `forecast(/host/item,(...))>...`  此外，如果监控项值为负是正常的，则 -1 可能是有效的预测。但是在现实世界中这种情况的概率可以忽略不计 (看看operator **=**[如何](/manual/config/triggers/expression)工作)。因此，如果您想要或不想分别将 -1 视为问题，可以添加 `... 或 forecast(/host/item,(...))=-1`或`... and forecast(/host/item,(...))<>-1`  [^1]: 例如，一个简单的触发器 `timeleft(/host/item,1h,X) < 1h` 可能会在监控项值接近 X 时进入问题状态，然后在达到值 X 时突然恢复。如果异常时监控项值低于X，请使用：`last(/host/item) < X or timeleft(/host/item,1h,X) < 1h`如果异常时监控项值高于X，请使用： `last(/host/item) > X or timeleft(/host/item,1h,X) < 1h`  [^2]: 多项式次数可以是 1 到 6, *多项式1*等价于*线性*。但是 [请谨慎](https://en.wikipedia.org/wiki/Runge's_phenomenon)使用高次多项式。如果评估周期包含的点数少于确定多项式系数所需的点数，则会降低多项式次数(例如 要求*多项式5*, 但只有4个点，因此将拟合*多项式3* )。  [^3]: 例如，拟合 *指数* 或 *幂* 函数涉及计算监控项值的log() 。如果数据包含零或负数，你将收到错误，因为 log() 仅针对正值定义。  [^4]: 对于*线性*, *指数*, *对数* 和 *幂* 拟合，所有必要的计算都可以明确写出来。对于*多项式*无需任何额外步骤即可计算仅*值* 。计算 *平均* 涉及计算多项式反导数（分析）。计算*最大*, *最小* 和 *增量*涉及计算多项式导数 (解析) 并找到它的根 (数值). 求解 f(t) = 0 涉及找到多项式根（数值）。  [^5]: 但在这种情况下，-1 可能会导致您的触发器从问题状态中恢复。要完全保护使用 ：`timeleft(/host/vfs.fs.size[/,free],1h,0)<1h and ({TRIGGER.VALUE}=0 and timeleft(/host/vfs.fs.size[/,free],1h,0)<>-1 or {TRIGGER.VALUE}=1)`

en-us	#### Examples  Here are some code snippets showing how to add Zabbix protocol header to the data you want to send in order  to obtain the packet you should send to Zabbix so that it is interpreted correctly. These code snippets  assume that the data is not larger than 1GB, thus the large packet format is not used.  ##### Python    ```python packet = b"ZBXD\1" + struct.pack("<II", len(data), 0) + data ```  or  ```python def zbx_create_header(plain_data_size, compressed_data_size=None):     protocol = b"ZBXD"     flags = 0x01     if compressed_data_size is None:         datalen = plain_data_size         reserved = 0     else:         flags |= 0x02         datalen = compressed_data_size         reserved = plain_data_size     return protocol + struct.pack("<BII", flags, datalen, reserved)  packet = zbx_create_header(len(data)) + data ```  ##### Perl  ```perl my $packet = "ZBXD\1" . pack("(II)<", length($data), 0) . $data; ```  or  ```perl sub zbx_create_header($;$) {     my $plain_data_size = shift;     my $compressed_data_size = shift;      my $protocol = "ZBXD";     my $flags = 0x01;     my $datalen;     my $reserved;      if (!defined($compressed_data_size))     {         $datalen = $plain_data_size;         $reserved = 0;     }     else     {         $flags |= 0x02;         $datalen = $compressed_data_size;         $reserved = $plain_data_size;     }      return $protocol . chr($flags) . pack("(II)<", $datalen, $reserved); }  my $packet = zbx_create_header(length($data)) . $data; ```  ##### PHP  ```php $packet = "ZBXD\1" . pack("VV", strlen($data), 0) . $data; ```  or  ```php function zbx_create_header($plain_data_size, $compressed_data_size = null) {     $protocol = "ZBXD";     $flags = 0x01;     if (is_null($compressed_data_size))     {         $datalen = $plain_data_size;         $reserved = 0;     }     else     {         $flags |= 0x02;         $datalen = $compressed_data_size;         $reserved = $plain_data_size;     }     return $protocol . chr($flags) . pack("VV", $datalen, $reserved); }  $packet = zbx_create_header(strlen($data)) . $data; ```  ##### Bash    ```bash datalen=$(printf "%08x" ${#data}) datalen="\\x${datalen:6:2}\\x${datalen:4:2}\\x${datalen:2:2}\\x${datalen:0:2}" printf "ZBXD\1${datalen}\0\0\0\0%s" "$data" ```
zh-cn	#### 例子  以下是一些代码片段，展示了如何将 Zabbix 协议标头添加到您要发送的数据中，以便获得您应该发送到 Zabbix 的数据包，从而正确解释它。 这些代码片段假定数据不大于 1GB，因此不使用大数据包格式。  ##### Python  ```python packet = b"ZBXD\1" + struct.pack("<II", len(data), 0) + data ```  or  ```python def zbx_create_header(plain_data_size, compressed_data_size=None):  · protocol = b"ZBXD"  · flags = 0x01  · if compressed_data_size is None:  · datalen = plain_data_size  · reserved = 0  · else:  · flags |= 0x02  · datalen = compressed_data_size  · reserved = plain_data_size  · return protocol + struct.pack("<BII", flags, datalen, reserved)  packet = zbx_create_header(len(data)) + data ```  ##### Perl  ```perl my $packet = "ZBXD\1" . pack("(II)<", length($data), 0) . $data; ```  or  ```perl sub zbx_create_header($;$) {  · my $plain_data_size = shift;  · my $compressed_data_size = shift;   · my $protocol = "ZBXD";  · my $flags = 0x01;  · my $datalen;  · my $reserved;   · if (!defined($compressed_data_size))  · {  · $datalen = $plain_data_size;  · $reserved = 0;  · }  · else  · {  · $flags |= 0x02;  · $datalen = $compressed_data_size;  · $reserved = $plain_data_size;  · }   · return $protocol . chr($flags) . pack("(II)<", $datalen, $reserved); }  my $packet = zbx_create_header(length($data)) . $data; ```  ##### PHP  ```php $packet = "ZBXD\1" . pack("VV", strlen($data), 0) . $data; ```  or  ```php function zbx_create_header($plain_data_size, $compressed_data_size = null) {  · $protocol = "ZBXD";  · $flags = 0x01;  · if (is_null($compressed_data_size))  · {  · $datalen = $plain_data_size;  · $reserved = 0;  · }  · else  · {  · $flags |= 0x02;  · $datalen = $compressed_data_size;  · $reserved = $plain_data_size;  · }  · return $protocol . chr($flags) . pack("VV", $datalen, $reserved); }  $packet = zbx_create_header(strlen($data)) . $data; ```  ##### Bash  ```bash datalen=$(printf "%08x" ${#data}) datalen="\\x${datalen:6:2}\\x${datalen:4:2}\\x${datalen:2:2}\\x${datalen:0:2}" printf "ZBXD\1${datalen}\0\0\0\0%s" "$data" ```

en-us	 ##### Examples of correct/incorrect syntax  Expressions (including function calls) cannot be used as history, trend, or foreach [function](/manual/appendix/functions) parameters. However, those functions themselves can be used in other (non-historical) function parameters.  |Expression|Example| |-|---------| |Valid|`avg(last(/host/key1),last(/host/key2)*10,last(/host/key1)*100)`<br>`max(avg(avg_foreach(/*/system.cpu.load?[group="Servers A"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers B"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers C"],5m)))`| |Invalid|`sum(/host/key,10+2)`<br>`sum(/host/key, avg(10,2))`<br>`sum(/host/key,last(/host/key2))`|  Note that in an expression like:      sum(sum_foreach(//resptime[*],5m))/sum(count_foreach(//resptime[*],5m))  it cannot be guaranteed that both parts of the equation will always have the same set of values.  While one part of the expression is evaluated, a new value for the requested period may arrive and  then the other part of the expression will have a different set of values.
zh-cn	 ##### 正确/错误的语法示例  表达式（包括函数调用）不能用作历史、趋势或循环 [函数](/manual/appendix/functions) 参数。 但是，这些函数本身可以在其他（非历史）函数参数中使用。  |表达式|示例| |-|---------| |有效的|`avg(last(/host/key1),last(/host/key2)*10,last(/host/key1)*100)`<br>`max(avg(avg_foreach(/*/system.cpu.load?[group="Servers A"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers B"],5m)),avg(avg_foreach(/*/system.cpu.load?[group="Servers C"],5m)))`| |无效的|`sum(/host/key,10+2)`<br>`sum(/host/key, avg(10,2))`<br>`sum(/host/key,last(/host/key2))`|  请注意，在如下表达式中：   · sum(sum_foreach(//resptime[*],5m))/sum(count_foreach(//resptime[*],5m))  不能保证等式的两个部分始终具有相同的一组值。在计算表达式的一部分时，可能会收到请求期间的新值，然后表达式的另一部分将具有一组不同的值。

en-us	##### Examples of simple user parameters  A simple command:      UserParameter=ping,echo 1  The agent will always return '1' for an item with 'ping' key.  A more complex example:      UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive  The agent will return '1', if MySQL server is alive, '0' - otherwise.
zh-cn	##### 用户自定义参数用例  一个简单的命令：      UserParameter=ping,echo 1  agent 将始终为使用“ping”为key的监控项返回“1”。  一个复杂一些的例子：      UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive  如果Mysql服务器是活动状态，agent将返回“1”，否则会返回“0”。

en-us	#### Examples of triggers
zh-cn	#### 触发器示例

en-us	##### Examples  Problem:      {"clock":1519304285,"ns":123456789,"value":1,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"eventid":42, "hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}  Recovery:      {"clock":1519304345,"ns":987654321,"value":0,"eventid":43,"p_eventid":42}  Problem (multiple problem event generation):      {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}      {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}  Recovery:      {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":43}      {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":42}
zh-cn	##### 例  问题:      {"clock":1519304285,"ns":123456789,"value":1,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"eventid":42, "hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}  恢复:      {"clock":1519304345,"ns":987654321,"value":0,"eventid":43,"p_eventid":42}  问题（多个问题事件生成）：      {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}      {"clock":1519304286,"ns":123456789,"value":1,"eventid":43,"name":"Either Zabbix agent is unreachable on Host B or pollers are too busy on Zabbix Server","severity":3,"hosts":[{"host":"Host B", "name":"Host B visible"},{"host":"Zabbix Server","name":"Zabbix Server visible"}],"groups":["Group X","Group Y","Group Z","Zabbix servers"],"tags":[{"tag":"availability","value":""},{"tag":"data center","value":"Riga"}]}  恢复:      {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":43}      {"clock":1519304346,"ns":987654321,"value":0,"eventid":44,"p_eventid":42}

en-us	#### Examples  Working hours. Monday - Friday from 9:00 till 18:00:      1-5,09:00-18:00  Working hours plus weekend. Monday - Friday from 9:00 till 18:00 and Saturday, Sunday from 10:00 till 16:00:      1-5,09:00-18:00;6-7,10:00-16:00
zh-cn	 #### 示例  工作时间。周一至周五 9:00 到18:00：      1-5,09:00-18:00  工作时间加上周末。周一至周五9:00 到18:00 和周六、周日10:00 到 16:00：      1-5,09:00-18:00;6-7,10:00-16:00

en-us	## EXAMPLES  **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH}
zh-cn	 ## 示例  **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]"**\ **zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-agent-cert-issuer "CN=Signing CA,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-agent-cert-subject "CN=server1,OU=IT operations,O=Example Corp,DC=example,DC=com" --tls-cert-file /home/zabbix/zabbix\_get.crt --tls-key-file /home/zabbix/zabbix\_get.key\ zabbix\_get -s 127.0.0.1 -p 10050 -k "system.cpu.load\[all,avg1\]" --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk** [ ]{#lbAH}

en-us	## EXAMPLES  **zabbix\_js -s script-file.js -p example** [ ]{#lbAG}
zh-cn	 ## 示例  **zabbix\_js -s script-file.js -p example** [ ]{#lbAG}

en-us	## EXAMPLES  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\     Send **342.45** as the value for **mysql.queries** item of monitored host. Use monitored host and Zabbix server defined in agent configuration file.  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\     Send **342.45** as the value for **mysql.queries** item of **Monitored Host** host using Zabbix server defined in agent configuration file.  \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt**     \ Send values from file **data\_values.txt** to Zabbix server with IP **192.168.1.113**. Host names and keys are defined in the file.  \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\     Send a timestamped value from the commandline to Zabbix server, specified in the agent configuration file. Dash in the input data indicates that hostname also should be used from the same configuration file.  \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\     Send empty value of an item to the Zabbix server with IP address **192.168.1.113** on port **10000** from the commandline. Empty values must be indicated by empty double quotes.  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\     Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with certificate.  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\     Send **342.45** as the value for **mysql.queries** item in **Monitored Host** host to server with IP **192.168.1.113** using TLS with pre-shared key (PSK).  [ ]{#lbAI}
zh-cn	  ## 示例  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -k mysql.queries -o 342.45**\    发送 **342.45** 作为受监视主机的 **mysql.queries** 项的值。使用代理配置文件中定义的受监视主机和 Zabbix 服务器。  **zabbix\_sender -c /etc/zabbix/zabbix\_agentd.conf -s "Monitored Host" -k mysql.queries -o 342.45**\    使用代理配置文件中定义的 Zabbix 服务器发送 **342.45** 作为在前端注册的 **受监视主机** 主机的 **mysql.queries** 项的值。  \ **zabbix\_sender -z 192.168.1.113 -i data\_values.txt**   \ 将值从文件 **data\_values.txt** 发送到 IP 为 **192.168.1.113** 的 Zabbix 服务器。主机名和密钥在文件中定义。   \ **echo "- hw.serial.number 1287872261 SQ4321ASDF" | zabbix\_sender -c /usr/local/etc/zabbix\_agentd.conf -T -i -**\    将带时间戳的值从命令行发送到agent配置文件中指定的 Zabbix 服务器。输入数据中的短划线表示主机名也应从同一使用的配置文件中读取。  \ **echo '"Zabbix server" trapper.item ""' | zabbix\_sender -z 192.168.1.113 -p 10000 -i -**\   从命令行将项目的空值发送到端口 **10000** 上的 IP 地址为 **192.168.1.113** 的 Zabbix 服务器。空值必须由空双引号表示。  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect cert --tls-ca-file /home/zabbix/zabbix\_ca\_file --tls-cert-file /home/zabbix/zabbix\_agentd.crt --tls-key-file /home/zabbix/zabbix\_agentd.key**\     使用带有证书的 TLS 将 **342.45** 作为 **mysql.queries** 项的值发送到 IP 为 192.168.1.113** 的 IP 主机的服务器。  **zabbix\_sender -z 192.168.1.113 -s "Monitored Host" -k mysql.queries -o 342.45 --tls-connect psk --tls-psk-identity "PSK ID Zabbix agentd" --tls-psk-file /home/zabbix/zabbix\_agentd.psk**\  使用带有预共享密钥 （PSK） 的 TLS 将 **342.45** 作为 **mysql.queries** 项的值发送到 IP 为 IP 为 **192.168.1.113** 的服务器。  [ ]{#lbAI}

en-us	##### Example with an inline regex modifier  Use of the following regular expression including an inline modifier (?i) to match the characters "error":      (?i)error  ![regexp\_expr\_3a.png](../../assets/en/manual/regular_expressions/regexp_expr_3a.png)  Chosen *Expression type*: "Result is TRUE". Characters "error" are matched.
zh-cn	##### 使用内联正则表达式修饰符的示例  使用以下正则表达式，包括一个内联修饰符 (?i) 来匹配字符 "error"：      (?i)error  ![regexp\_expr\_3a.png](../../assets/en/manual/regular_expressions/regexp_expr_3a.png)  选择的 *Expression type（表达式类型）*："Result is TRUE（结果为真）"。字符 "error" 被匹配。

en-us	## EXIT STATUS  The exit status is 0 if the values were sent and all of them were successfully processed by server. If data was sent, but processing of at least one of the values failed, the exit status is 2. If data sending failed, the exit status is 1.  [ ]{#lbAH}
zh-cn	 ## 退出状态  如果值已发送且服务器已成功处理所有值，则退出状态为0。如果发送了数据，但至少一个值的处理失败，则退出状态为2。如果数据发送失败，退出状态为1。  [ ]{#lbAH}

en-us	#### Export and import  Export and import Zabbix configuration data for configuration backups, migration or large-scale configuration updates.  [Configuration API](/manual/api/reference/configuration)
zh-cn	#### 导入和导出  导出和导入Zabbix配置数据，用于配置备份，迁移或大规模配置更新。  [Configuration API](/manual/api/reference/configuration)

en-us	##### Export format  Data can be exported using the Zabbix web frontend or [Zabbix API](/manual/api/reference/configuration). Supported export formats are YAML, XML and JSON.
zh-cn	 ##### 输出格式  数据可以使用Zabbix web前端或 [Zabbix API](/manual/api/reference/configuration)。 支持的导出格式是YAML, XML和JSON。

en-us	#### Exposed metrics  The stats items gather the statistics in bulk and return a JSON, which is the basis for dependent items to get their data from. The following [internal metrics](/manual/config/items/itemtypes/internal) are returned by either of the two items:  -   `zabbix[boottime]` -   `zabbix[hosts]` -   `zabbix[items]` -   `zabbix[items_unsupported]` -   `zabbix[preprocessing_queue]` (server only) -   `zabbix[process,<type>,<mode>,<state>]` (only process type based     statistics) -   `zabbix[rcache,<cache>,<mode>]` -   `zabbix[requiredperformance]` -   `zabbix[triggers]` (server only) -   `zabbix[uptime]` -   `zabbix[vcache,buffer,<mode>]` (server only) -   `zabbix[vcache,cache,<parameter>]` -   `zabbix[version]` -   `zabbix[vmware,buffer,<mode>]` -   `zabbix[wcache,<cache>,<mode>]` ('trends' cache type server only)
zh-cn	 #### 内部指标  状态监控项收集统计信息后返回一个JSON，这是其他依赖监控项从中获取数据的基础。以下[内部指标](/manual/config/items/itemtypes/internal) 的用法：  -   `zabbix[boottime]` -   `zabbix[hosts]` -   `zabbix[items]` -   `zabbix[items_unsupported]` -   `zabbix[preprocessing_queue]` (server only) -   `zabbix[process,<type>,<mode>,<state>]` (only process type based     statistics) -   `zabbix[rcache,<cache>,<mode>]` -   `zabbix[requiredperformance]` -   `zabbix[triggers]` (server only) -   `zabbix[uptime]` -   `zabbix[vcache,buffer,<mode>]` (server only) -   `zabbix[vcache,cache,<parameter>]` -   `zabbix[version]` -   `zabbix[vmware,buffer,<mode>]` -   `zabbix[wcache,<cache>,<mode>]` ('trends' cache type server only)

en-us	#### Extended monitoring  Sometimes it is necessary to log received HTML page content. This is especially useful if some web scenario step fails. Debug level 5 (trace) serves that purpose. This level can be set in [server](/manual/appendix/config/zabbix_server) and [proxy](/manual/appendix/config/zabbix_proxy) configuration files or using a runtime control option (`-R log_level_increase="http poller,N"`, where N is the process number). The following examples demonstrate how extended monitoring can be started provided debug level 4 is already set:      Increase log level of all http pollers:     shell> zabbix_server -R log_level_increase="http poller"      Increase log level of second http poller:     shell> zabbix_server -R log_level_increase="http poller,2"  If extended web monitoring is not required it can be stopped using the `-R log_level_decrease` option.
zh-cn	#### 扩展监控  记录收到的 HTML 页面内容是有必要的，尤其是当某些 Web 场景步骤失败 。调试级别 5（跟踪）用于此目的。此级别可以在 [server](/manual/appendix/config/zabbix_server) 和 [proxy](/manual/appendix/config/zabbix_proxy) 配置文件中设置，也可以使用运行时控制选项 （`-R log_level_increase="http poller,N"`，其中 N 是进程号）。以下示例演示了如何在已设置调试级别 4 的情况下启动扩展监控：      Increase log level of all http pollers:     shell> zabbix_server -R log_level_increase="http poller"      Increase log level of second http poller:     shell> zabbix_server -R log_level_increase="http poller,2"  如果不需要扩展 Web 监控，可以使用`-R log_level_decrease` 选项。

en-us	## FILES  */usr/local/etc/zabbix\_agent2.conf*   Default location of Zabbix agent 2 configuration file (if not modified during compile time).  [ ]{#lbAH}
zh-cn	 ## 文件  */usr/local/etc/zabbix\_agent2.conf*   Zabbix agent 2 配置文件的默认位置（如果在编译时未修改的话）。  [ ]{#lbAH}

en-us	## FILES  */usr/local/etc/zabbix\_agentd.conf*   Default location of Zabbix agent configuration file (if not modified during compile time).  [ ]{#lbAI}
zh-cn	 ## 文件  */usr/local/etc/zabbix\_agentd.conf*   Zabbix agent 配置文件的默认位置（如果在编译时未修改的话）。  [ ]{#lbAI}

en-us	## FILES  */usr/local/etc/zabbix\_proxy.conf*   Default location of Zabbix proxy configuration file (if not modified during compile time).  [ ]{#lbAI}
zh-cn	 ## 文件  */usr/local/etc/zabbix\_proxy.conf*   Zabbix proxy 配置文件的默认位置（如果在编译时未修改的话）。  [ ]{#lbAI}

en-us	## FILES  */usr/local/etc/zabbix\_server.conf*   Default location of Zabbix server configuration file (if not modified during compile time).  [ ]{#lbAI}
zh-cn	 ## 文件  */usr/local/etc/zabbix\_server.conf*   Zabbix proxy 配置文件的默认位置（如果在编译时未修改的话）。  [ ]{#lbAI}

en-us	## FILES  */usr/local/etc/zabbix\_web\_service.conf*   Default location of Zabbix web service configuration file (if not modified during compile time).  [ ]{#lbAG}
zh-cn	## 文件  */usr/local/etc/zabbix\_web\_service.conf*   Zabbix proxy 配置文件的默认位置（如果在编译时未修改的话）。  [ ]{#lbAG}

en-us	##### Filter buttons  |   |   | |--|--------| |![filter\_apply.png](../../../../../assets/en/manual/web_interface/filter_apply.png)|Apply specified filtering criteria (without saving).| |![filter\_reset.png](../../../../../assets/en/manual/web_interface/filter_reset.png)|Reset current filter and return to saved parameters of the current tab. On the main tab, this will clear the filter.| |![filter\_save\_as.png](../../../../../assets/en/manual/web_interface/filter_save_as.png)|Save current filter parameters in a new tab. Only available on the main tab.| |![filter\_update.png](../../../../../assets/en/manual/web_interface/filter_update.png)|Replace tab parameters with currently specified parameters. Not available on the main tab.|
zh-cn	##### 过滤器按钮  | · | · | |---|---| |![filter\_apply.png](../../../../../assets/en/manual/web_interface/filter_apply.png)|应用指定的过滤器条件（不保存）。| |![filter\_reset.png](../../../../../assets/en/manual/web_interface/filter_reset.png)|重置当前过滤器并返回当前选项卡的已保存参数。在主选项卡上，这将清除过滤器。| |![filter\_save\_as.png](../../../../../assets/en/manual/web_interface/filter_save_as.png)|在新选项卡中保存当前的过滤器参数。只在主选项卡上可用。| |![filter\_update.png](../../../../../assets/en/manual/web_interface/filter_update.png)|将选项卡参数替换为当前指定的参数。在主选项卡上不可用。|

en-us	#### Filter expression  The filter expression is an arithmetical expression in infix notation.  Supported operands:  |Operand|Description|Example| |--|------|------| |`"<text>"`<br>`'<text>'`|Text constant.|'value: \\'1\\''<br>"value: '1'"| |`<number>`|Numeric constant supporting scientific notation.|123| |`<jsonpath starting with $>`|Value referred to by the JSONPath from the input document root node; only definite paths are supported.|$.object.name| |`<jsonpath starting with @>`|Value referred to by the JSONPath from the current object/element; only definite paths are supported.|@.name|  Supported operators:  |Operator|Type|Description|Result| |--|--------|----|----| |`-`|binary|Subtraction.|Number.| |`+`|binary|Addition.|Number.| |`/`|binary|Division.|Number.| |`*`|binary|Multiplication.|Number.| |`==`|binary|Is equal to.|Boolean (1 or 0).| |`!=`|binary|Is not equal to.|Boolean (1 or 0).| |`<`|binary|Is less than.|Boolean (1 or 0).| |`<=`|binary|Is less than or equal to.|Boolean (1 or 0).| |`>`|binary|Is greater than.|Boolean (1 or 0).| |`>=`|binary|Is greater than or equal to.|Boolean (1 or 0).| |`=~`|binary|Matches regular expression.|Boolean (1 or 0).| |`!`|unary|Boolean not.|Boolean (1 or 0).| |`||`|binary|Boolean or.|Boolean (1 or 0).| |`&&`|binary|Boolean and.|Boolean (1 or 0).|
zh-cn	#### 过滤表达式  过滤表达式是固定符号的一种表达式。  支持的操作：  |操作|描述|示例| |-------|-----------|-------| |`"<text>"`<br>`'<text>'`|文本常量。|'value: \\'1\\''<br>"value: '1'"| |`<number>`|支持科学计数法的数值常数。|123| |`<以$开头的jsonpath>`|来自输入文档根节点的JSONPath引用的值； 只支持明确的路径。|$.object.name| |`<以@开头的jsonpath>`|当前对象/元素的JSONPath引用的值； 只支持明确的路径。|@.name|   支持的操作：  |操作|类型|描述|结果| |--------|----|-----------|------| |`-`|二进制|减法|数字| |`+`|二进制|加法|数字| |`/`|二进制|除法|数字| |`*`|二进制|乘法|数字| |`==`|二进制|等于|布尔值（1 或 0）| |`!=`|二进制|不等于|布尔值（1 或 0）| |`<`|二进制|小于|布尔值（1 或 0）| |`<=`|二进制|小于或等于|布尔值（1 或 0）| |`>`|二进制|大于|布尔值（1 或 0）| |`>=`|二进制|大于或等于|布尔值（1 或 0）| |`=~`|二进制|匹配正则表达式|布尔值（1 或 0）| |`!`|一元|非布尔值|布尔值（1 或 0）| |`\|\|`|二进制|布尔值或|布尔值（1 或 0。| |`&&`|二进制|布尔值和|布尔值（1 或 0）|

en-us	#### Flexible user parameters  Flexible user parameters accept parameters with the key. This way a flexible user parameter can be the basis for creating several items.  Flexible user parameters have the following syntax:      UserParameter=key[*],command  |Parameter|Description| |--|--------| |**Key**|Unique item key. The \[\*\] defines that this key accepts parameters within the brackets.<br>Parameters are given when configuring the item.| |**Command**|Command to be executed to evaluate value of the key.<br>*For flexible user parameters only*:<br>You may use positional references $1…$9 in the command to refer to the respective parameter in the item key.<br>Zabbix parses the parameters enclosed in \[ \] of the item key and substitutes $1,...,$9 in the command accordingly.<br>$0 will be substituted by the original command (prior to expansion of $0,...,$9) to be run.<br>Positional references are interpreted regardless of whether they are enclosed between double (") or single (') quotes.<br>To use positional references unaltered, specify a double dollar sign - for example, awk '{print $$2}'. In this case `$$2` will actually turn into `$2` when executing the command.|  ::: noteimportant Positional references with the $ sign are searched for and replaced by Zabbix agent only for flexible user parameters. For simple user parameters, such reference processing is skipped and, therefore, any $ sign quoting is not necessary. :::  ::: noteimportant Certain symbols are not allowed in user parameters by default. See [UnsafeUserParameters](/manual/appendix/config/zabbix_agentd) documentation for a full list. :::
zh-cn	#### 灵活的用户自定义参数  灵活的用户自定义参数可以从key中接受参数。这是一种使用一个用户自定义参数创建多个监控项的方式。\  灵活的用户自定义参数的语法如下：      UserParameter=key[*],command  |参数   |描述| |-------------------|---------------| |**Key**|唯一的监控项key。 \[\*\] 用于定义该key接受括号内的参数。<br>参数需在配置监控项时给出| |**Command**|命令在执行时，引用key中指定的值<br>*只对灵活的用户参数有效*:<br>你可以在命令中使用位置引用$1 … $9来引用监控项Key中的相应参数。<br>Zabbix解析监控项Key的\[\]中包含的参数，并相应地替换$1，…，$9。<br>$0会替换为完整的原始命令（在对$0，…，$9执行替换之前的命令）运行。<br>不管位置参数（$0,…,$9)是用双引号( " )还是单引号( ' )括起来，都会解析位置引用。<br>要使用位置引用解析，请指定双美元符号（$） - 例如， '' awk '{print $$2}' '' 。 在这种情况下，执行命令时， `$$2` 实际上会变成 `$2` 。|  ::: noteimportant 仅对灵活的用户自定义参数进行带有$符号的搜索，并由Zabbix agent解析替换。对于简单的用户自定义参数，这种引用会被跳过，因此不需要任何$符号引用。 :::  ::: noteimportant 默认情况下，用户自定义参数中不允许使用某些特殊符号。有关完整列表，请参阅[不安全的用户参数](/zh/manual/appendix/config/zabbix_agentd)文档。 :::

en-us	#### Flipping frontend locales  It has been observed that frontend locales may flip without apparent logic, i. e. some pages (or parts of pages) are displayed in one language while other pages (or parts of pages) in a different language. Typically the problem may appear when there are several users, some of whom use one locale, while others use another.  A known workaround to this is to disable multithreading in PHP and Apache.  The problem is related to how setting the locale works [in PHP](https://www.php.net/manual/en/function.setlocale): locale information is maintained per process, not per thread. So in a multi-thread environment, when there are several projects run by same Apache process, it is possible that the locale gets changed in another thread and that changes how data can be processed in the Zabbix thread.  For more information, please see related problem reports:  -   [ZBX-10911](https://support.zabbix.com/browse/ZBX-10911) (Problem     with flipping frontend locales) -   [ZBX-16297](https://support.zabbix.com/browse/ZBX-16297) (Problem     with number processing in graphs using the `bcdiv` function of BC     Math functions)
zh-cn	#### 前端区域信息错乱  已经观察到，前端当地区域值可能会在没有明显逻辑的情况下错乱，例如：某些页面（或部分页面）以一种语言显示，其他页面（或部分页面）显示另一种语言。常出现在一些用户使用一个语言环境，而其他用户使用另一个语言环境的情况。  已知的解决方法是在 PHP 和 Apache 中禁用多线程。 问题与如何 [在 PHP 中] (https://www.php.net/manualen/function.setlocale) 设置语言环境有关：语言环境信息是按进程维护的，而不是按线程维护的。因此，在多线程环境中，当有多个监控项由同一个 Apache 进程运行时，可能会在另一个线程中更改语言环境，从而改变 Zabbix 线程中处理数据的方式。  更多信息，详见相关问题报告: -   [ZBX-10911](https://support.zabbix.com/browse/ZBX-10911) (Problem with flipping frontend locales) -   [ZBX-16297](https://support.zabbix.com/browse/ZBX-16297) (Problem  with number processing in graphs using the `bcdiv` function of BC Math functions)

en-us	### Float history  The float 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|float|Received value.|
zh-cn	 ### 浮点型历史数据  浮点型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |clock|timestamp|收到该数值的时间。| |itemid|string|相关监控项的 ID。| |ns|integer|收到数值时的纳秒数。| |value|float|收到的数值。|

en-us	##### Footnotes  ^**1**^ Default value.
zh-cn	##### 注释批注  ^**1**^ 默认值

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "EMAIL") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
zh-cn	 ##### 附注  ^**1**^ 对于字符串值，只有字符串将被导出(例如“EMAIL”)，而不使用该表中使用的编号。 该表中的范围值(对应于API值)的编号仅用于排序。

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "ZABBIX\_ACTIVE") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
zh-cn	 ##### 附注  ^**1**^ 对于字符串值，只有字符串将被导出(例如"ZABBIX\_ACTIVE")，而不使用该表中使用的编号。 该表中的范围值(对应于API值)的编号仅用于排序。

en-us	##### Footnotes  ^**1**^ For string values, only the string will be exported (e.g. "ZABBIX\_ACTIVE") without the numbering used in this table. The numbers for range values (corresponding to the API values) in this table is used for ordering only.
zh-cn	##### 附注  ^**1**^ 对于字符串值，只有字符串将被导出(例如"ZABBIX\_ACTIVE")，而不使用该表中使用的编号。该表中的范围值(对应于API值)的编号仅用于排序。

en-us	##### Footnotes  ^**1**^ In the fields marked with ^[1](lld_macros#footnotes)^ a single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.
zh-cn	##### 脚注  ^**1**^ 在标有 ^[1](lld_macros#footnotes)^ 的字段中，单个宏必须填充整个字段。一个或多个字段中的多个宏不支持与文本混合。

en-us	#### Form buttons  Buttons at the bottom of the form allow to perform several operations.  |   |   | |--|--------| |![](../../../assets/en/manual/config/button_add.png)|Add a discovery rule. This button is only available for new discovery rules.| |![](../../../assets/en/manual/config/button_update.png)|Update the properties of a discovery rule. This button is only available for existing discovery rules.| |![](../../../assets/en/manual/config/button_clone.png)|Create another discovery rule based on the properties of the current discovery rule.| |![](../../../assets/en/manual/config/button_check_now.png)|Perform discovery based on the discovery rule immediately. The discovery rule must already exist. See [more details](/manual/config/items/check_now).<br>*Note* that when performing discovery immediately, configuration cache is not updated, thus the result will not reflect very recent changes to discovery rule configuration.| |![](../../../assets/en/manual/config/button_delete.png)|Delete the discovery rule.| |![](../../../assets/en/manual/config/button_cancel.png)|Cancel the editing of discovery rule properties.|
zh-cn	#### 表格按钮  表格底部按钮允许执行一些操作。  | · | · | |---|---| |![](../../../assets/en/manual/config/button_add.png)|添加自动发现规则。此按钮只能用于新的自动发现规则。| |![](../../../assets/en/manual/config/button_update.png)|更新自动发现规则的属性。此按钮只能用于现有的自动发现规则。| |![](../../../assets/en/manual/config/button_clone.png)|基于当前自动发现规则的属性，创建另一个自动发现规则。| |![](../../../assets/en/manual/config/button_check_now.png)|立即运行自动发现规则。该自动发现规则必须已存在。 参考 [更多信息](/manual/config/items/check_now).<br>*注意* 当立即执行自动发现时, 配置缓存并没有更新, 所以自动发现的结果可能不会显示最近的变更。| |![](../../../assets/en/manual/config/button_delete.png)|删除自动发现规则。| |![](../../../assets/en/manual/config/button_cancel.png)|取消对自动发现规则的编辑。|

en-us	##### Form buttons  Buttons at the bottom of the form allow to perform several operations.  |   |   | |--|--------| |![](../../../assets/en/manual/config/button_add.png)|Add a report. This button is only available for new reports.| |![](../../../assets/en/manual/config/button_update.png)|Update the properties of a report.| |![](../../../assets/en/manual/config/button_clone.png)|Create another report based on the properties of the current report.| |![](../../../assets/en/manual/config/button_test.png)|Test if report configuration is correct by sending a report to the current user.| |![](../../../assets/en/manual/config/button_delete.png)|Delete the report.| |![](../../../assets/en/manual/config/button_cancel.png)|Cancel the editing of report properties.|
zh-cn	##### 表单按钮  表单底部的按钮允许执行多项操作。  | | | |---|---| |![](../../../assets/en/manual/config/button_add.png)|添加报告。 此按钮仅适用于新报告。| |![](../../../assets/en/manual/config/button_update.png)|更新报告的属性。| |![](../../../assets/en/manual/config/button_clone.png)|根据当前报告的属性创建另一个报告。| |![](../../../assets/en/manual/config/button_test.png)|通过向当前用户发送报告来测试报告配置是否正确。| |![](../../../assets/en/manual/config/button_delete.png)|删除报告。| |![](../../../assets/en/manual/config/button_cancel.png)|取消编辑报表属性。|

en-us	#### FreeBSD  See values supported for 'memtype' parameter on FreeBSD in the table.  |Supported value|Description|Source in kinfo\_proc structure|Tries to be compatible with| |--|------|--|--| |vsize|Virtual memory size|kp\_eproc.e\_vm.vm\_map.size or ki\_size|ps -o vsz| |pmem|Percentage of real memory|calculated from rss|ps -o pmem| |rss|Resident set size|kp\_eproc.e\_vm.vm\_rssize or ki\_rssize|ps -o rss| |size ^[1](proc_mem_notes#footnotes)^|Size of process (code + data + stack)|tsize + dsize + ssize| | |tsize|Text (code) size|kp\_eproc.e\_vm.vm\_tsize or ki\_tsize|ps -o tsiz| |dsize|Data size|kp\_eproc.e\_vm.vm\_dsize or ki\_dsize|ps -o dsiz| |ssize|Stack size|kp\_eproc.e\_vm.vm\_ssize or ki\_ssize|ps -o ssiz|
zh-cn	#### FreeBSD  请参见表中FreeBSD上的“memtype”参数支持的值。  |支持的参数值|描述|proentry64 结构中的源代码|兼容| |---------------|-----------|-------------------------------|---------------------------| |vsize|虚拟内存大小|kp\_eproc.e\_vm.vm\_map.size or ki\_size|ps -o vsz| |pmem|实际内存的百分比|calculated from rss|ps -o pmem| |rss|驻留内存大小|kp\_eproc.e\_vm.vm\_rssize or ki\_rssize|ps -o rss| |size ^[1](proc_mem_notes#footnotes)^|进程大小 (代码 + 数据 + 堆栈)|tsize + dsize + ssize|<| |tsize|文本(代码)的大小|kp\_eproc.e\_vm.vm\_tsize or ki\_tsize|ps -o tsiz| |dsize|数据大小|kp\_eproc.e\_vm.vm\_dsize or ki\_dsize|ps -o dsiz| |ssize|堆栈大小|kp\_eproc.e\_vm.vm\_ssize or ki\_ssize|ps -o ssiz|

en-us	##### Frontend configuration  A Zabbix proxy does not have a frontend; it communicates with Zabbix server only.
zh-cn	##### 前端配置  Zabbix 代理没有前端； 它只与 Zabbix 服务器通信。

en-us	##### Frontend configuration  A Zabbix proxy does not have a frontend; it communicates with Zabbix server only.
zh-cn	##### 前端配置  Zabbix proxy 没有前端；它只与 Zabbix server 通信。

en-us	#### Frontend  To enable encryption with certificate and database host identity verification for connections between Zabbix frontend and the database:  -   Check *Database TLS encryption* and *Verify database certificate* -   Specify path to *Database TLS key file* -   Specify path to *Database TLS CA file* -   Specify path to *Database TLS certificate file* -   Check *Database host verification*  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_verify_full2.png){width="600"}  Alternatively, this can be set in */etc/zabbix/web/zabbix.conf.php:*      $DB['ENCRYPTION'] = true;     $DB['KEY_FILE'] = '';     $DB['CERT_FILE'] = '';     $DB['CA_FILE'] = '/etc/ssl/pgsql/root.crt';     $DB['VERIFY_HOST'] = true;     $DB['CIPHER_LIST'] = '';     ...
zh-cn	#### 前端  要使用证书和数据库主机身份验证为 Zabbix 前端和数据库之间的连接启用加密，请执行以下操作:  -   勾选*Database TLS encryption* 和*Verify database certificate* -   指定 *Database TLS key file* 路径 -   指定  *Database TLS CA file* 路径  -   指定  *Database TLS certificate file* 路径 -   勾选 *Database host verification*  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_verify_full2.png){width="600"}  或者，可以在这里配置 */etc/zabbix/web/zabbix.conf.php:*      $DB['ENCRYPTION'] = true;     $DB['KEY_FILE'] = '';     $DB['CERT_FILE'] = '';     $DB['CA_FILE'] = '/etc/ssl/pgsql/root.crt';     $DB['VERIFY_HOST'] = true;     $DB['CIPHER_LIST'] = '';     ...

en-us	#### Frontend  To enable encryption with certificate verification for connections between Zabbix frontend and the database:  -   Check *Database TLS encryption* and *Verify database certificate* -   Specify path to Database TLS CA file  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_verify_ca.png){width="600"}  Alternatively, this can be set in */etc/zabbix/web/zabbix.conf.php*:      ...     $DB['ENCRYPTION'] = true;     $DB['KEY_FILE'] = '';     $DB['CERT_FILE'] = '';     $DB['CA_FILE'] = '/etc/ssl/mysql/ca.pem';     $DB['VERIFY_HOST'] = false;     $DB['CIPHER_LIST'] = '';     ...  Troubleshoot user using command-line tool to check if connection is possible for required user:      $ mysql -u zbx_web -p -h 10.211.55.9 --ssl-mode=REQUIRED --ssl-ca=/var/lib/mysql/ca.pem
zh-cn	使用证书验证为 Zabbix 前端和数据库之间的连接启用加密:  -   勾选*Database TLS encryption* 和 *Verify database certificate* -   指定数据库 TLS CA 文件的路径  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_verify_ca.png){width="600"}  或者，可以在 */etc/zabbix/web/zabbix.conf.php* 配置:      ...     $DB['ENCRYPTION'] = true;     $DB['KEY_FILE'] = '';     $DB['CERT_FILE'] = '';     $DB['CA_FILE'] = '/etc/ssl/mysql/ca.pem';     $DB['VERIFY_HOST'] = false;     $DB['CIPHER_LIST'] = '';     ...  使用命令行工具对用户进行故障排除，以检查所需用户是否可以连接:      $ mysql -u zbx_web -p -h 10.211.55.9 --ssl-mode=REQUIRED --ssl-ca=/var/lib/mysql/ca.pem

en-us	#### Frontend  To enable transport-only encryption for connections between Zabbix frontend and the database:  -   Check *Database TLS encryption* -   Leave *Verify database certificate* unchecked  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_transport2.png){width="600"}
zh-cn	#### 前端  请执行以下操作来启用 Zabbix 前端和数据库之间的仅传输加密连接：  -   勾选 *Database TLS encryption* -   取消勾选 *Verify database certificate*   ![](../../../../../assets/en/manual/appendix/install/encrypt_db_transport2.png){width="600"}

en-us	#### Frontend  To enable transport-only encryption for connections between Zabbix frontend and the database:  -   Check *Database TLS encryption* -   Leave *Verify database certificate* unchecked  ![](../../../../../assets/en/manual/appendix/install/encrypt_db_transport.png){width="600"}
zh-cn	#### 前端  要为 Zabbix 前端和数据库之间的连接建立传输加密，请执行以下操作：  -   勾选 *Database TLS encryption* -   取消勾选 *Verify database certificate*   ![](../../../../../assets/en/manual/appendix/install/encrypt_db_transport.png){width="600"}

en-us	##### Frontend to the database  A secure connection to the database can be configured during frontend installation:  -   Mark the *Database TLS encryption* checkbox in the [Configure DB     connection](/manual/installation/frontend#configure_db_connection)     step to enable transport encryption. -   Mark the *Verify database certificate* checkbox that appears when     *TLS encryption* field is checked to enable encryption with     certificates.  ::: noteclassic  For MySQL, the *Database TLS encryption* checkbox is disabled, if *Database host* is set to localhost, because connection that uses a socket file (on Unix) or shared memory (on Windows) cannot be encrypted.\ For PostgreSQL, the *TLS encryption* checkbox is disabled, if the value of the *Database host* field begins with a slash or the field is empty.  :::  The following parameters become available in the TLS encryption in certificates mode (if both checkboxes are marked):  |Parameter|Description| |--|--------| |*Database TLS CA file*|Specify the full path to a valid TLS certificate authority (CA) file.| |*Database TLS key file*|Specify the full path to a valid TLS key file.| |*Database TLS certificate file*|Specify the full path to a valid TLS certificate file.| |*Database host verification*|Mark this checkbox to activate host verification.<br>Disabled for MYSQL, because PHP MySQL library does not allow to skip the peer certificate validation step.| |*Database TLS cipher list*|Specify a custom list of valid ciphers. The format of the cipher list must conform to the OpenSSL standard.<br>Available for MySQL only.|  ::: noteimportant TLS parameters must point to valid files. If they point to non-existent or invalid files, it will lead to the authorization error.\ If certificate files are writable, the frontend generates a warning in the [System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix) report that "TLS certificate files must be read-only." (displayed only if the PHP user is the owner of the certificate).\ \ Certificates protected by passwords are not supported.  :::
zh-cn	##### 前端连接数据库  在前端安装的过程中可以配置使用数据库的安全连接:  - · 在[配置数据库连接](/manual/installation/frontend#configure_db_connection)步骤中勾选*Database TLS encryption*复选框以启用传输加密。 - · 选中*TLS 加密*字段时出现的*验证数据库证书*复选框，以启用证书加密。  ::: noteclassic 对于MySQL，如果*Database host*设置为localhost， *Database TLS encryption* 复选框是禁用的，因为连接使用 socket 文件 (Unix) 或共享内存(Windows) 是不能加密的。 对于 PostgreSQL，如果 *Database host* 字段的值以斜线开头或字段为空，则 *TLS encryption* 复选框被禁用。 :::  以下参数在证书模式 TLS 加密时可用 (如果两个复选框都勾选):  |参数|描述| |---------|-----------| |*Database TLS CA file*|指定有效的TLS证书颁发机构(CA)文件的完整路径| |*Database TLS key file*|指定有效的TLS密钥文件的完整路径| |*Database TLS certificate file*|指定有效TLS证书文件的完整路径| |*Database host verification*|标记此复选框以激活主机验证.<br>对MYSQL禁用，因为PHP MYSQL库不允许跳过对端证书验证步骤。| |*Database TLS cipher list*|指定有效密码的自定义列表。密码列表的格式必须符合OpenSSL标准。<br>仅对MySQL可用。|  ::: noteimportant TLS参数必须指向有效的文件。如果指向的文件不存在或无效，则会导致授权错误.\ 如果证书文件权限是可写的，前端会在 [系统信息](/manual/web_interface/frontend_sections/reports/status_of_zabbix) 报告中生成警告“TLS 证书文件必须是只读的。” （仅当 PHP 用户是证书的所有者时才显示）。 不支持受密码保护的证书。  :::

en-us	#### Function parameters  Function parameters allow to specify:  -   host and item key (functions referencing the host item history only) -   function-specific parameters -   other expressions (not available for functions referencing the host     item history, see [other expressions](#other_expressions) for     examples)  The host and item key can be specified as `/host/key`. The referenced item must be in a supported state (except for **nodata()** function, which is calculated for unsupported items as well).  While other trigger expressions as function parameters are limited to non-history functions in triggers, this limitation does not apply in [calculated items](/manual/config/items/itemtypes/calculated).
zh-cn	 #### 函数参数  函数参数允许选项：  - 主机和监控项（仅引用主机项目历史的功能） - 功能特定的参数 - 其他表达式（不适用于引用主机的函数 监控项，历史数据，请参阅 [other expressions（其他表达式）](#other_expressions) 例子）  主机和监控项键可以指定为`/host/key`。被引用的监控项必须处于支持的状态（**nodata()无数据** 函数除外， 这也是为不受支持的监控项计算的）。  而作为函数参数的其他触发器表达式仅限于 触发器中的非历史函数，此限制不适用于 [calculated items（计算监控项）](/manual/config/items/itemtypes/calculated)。

en-us	#### Functions  Functions allow to calculate the collected values (average, minimum, maximum, sum), find strings, reference current time and other factors.  A complete list of [supported functions](/manual/appendix/functions) is available.  Typically functions return numeric values for comparison. When returning strings, comparison is possible with the **=** and **<>** operators (see [example](#example_14)).
zh-cn	 #### 函数  函数允许计算收集的值（average 平均值、minimum 最小值、maximum 最大值、sum 总和）、查找字符串、参考当前时间和其他因素。  [支持的函数](/manual/appendix/functions)可用的完整列表。  通常，函数会返回数值以进行比较。返回字符串时，可以使用 **=** 和 **<>** 运算符进行比较（参见[示例](#example_14)）。

en-us	#### Functions  Functions can be used at the end of JSONPath. Multiple functions can be chained if the preceding function returns value that is accepted by the following function.  Supported functions:  |Function|Description|Input|Output| |--|--------|----|----| |`avg`|Average value of numbers in input array.|Array of numbers.|Number.| |`min`|Minimum value of numbers in input array.|Array of numbers.|Number.| |`max`|Maximum value of numbers in input array.|Array of numbers.|Number.| |`sum`|Sum of numbers in input array.|Array of numbers.|Number.| |`length`|Number of elements in input array.|Array.|Number.| |`first`|The first array element.|Array.|A JSON construct (object, array, value) depending on input array contents.|  Quoted numeric values are accepted by the JSONPath aggregate functions. It means that the values are converted from string type to numeric if aggregation is required.  Incompatible input will cause the function to generate error.
zh-cn	#### 函数  函数可以用在 JSONPath 的末尾。 如果前面的函数返回后面函数接受的值，则可以链接多个函数。  支持的函数：  |函数|描述|输入|输出| |--------|-----------|-----|------| |`avg`|输入数组中数字的平均值。|数字数组。|数字。| |`min`|输入数组中数字的最小值。|数字数组。|数字。| |`max`|输入数组中数字的最大值。|数字数组。|数字。| |`sum`|输入数组中数字的总和。|数字数组。|数字。| |`length`|输入数组中的元素数量。|数组。|数字。| |`first`|第一个数组元素。|数组。|取决于输入数组内容的 JSON 构造（对象、数组、值）。|  JSONPath 聚合函数接受带引号的数值。 这意味着如果需要聚合，则将值从字符串类型转换为数字。  不兼容的输入会导致函数产生错误。

en-us	#### Function syntax  Foreach functions support two common parameters: `item filter` (see details below) and `time period`:      foreach_function(item filter,time period)  For example:   `avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)`  will return the five-minute average of each 'mysql.qps' item in the MySQL server group.  Note that some functions support additional [parameters](#additional_parameters).
zh-cn	#### 参数  Foreach 函数支持两个常用参数 - 监控项过滤器和时间段：      foreach_function(item filter,time period)  例如：      avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)  一些函数支持附加参数。

en-us	#### General recommendations  -   Start with understanding which component acts as a TLS client and     which one acts as a TLS server in problem case.\     Zabbix server, proxies and agents, depending on interaction between     them, all can work as TLS servers and clients.\     For example, Zabbix server connecting to agent for a passive check,     acts as a TLS client. The agent is in role of TLS server.\     Zabbix agent, requesting a list of active checks from proxy, acts as     a TLS client. The proxy is in role of TLS server.\     `zabbix_get` and `zabbix_sender` utilities always act as TLS     clients. -   Zabbix uses mutual authentication.\     Each side verifies its peer and may refuse connection.\     For example, Zabbix server connecting to agent can close connection     immediately if agent's certificate is invalid. And vice versa -     Zabbix agent accepting a connection from server can close connection     if server is not trusted by agent. -   Examine logfiles in both sides - in TLS client and TLS server.\     The side which refuses connection may log a precise reason why it     was refused. Other side often reports rather general error (e.g.     "Connection closed by peer", "connection was non-properly     terminated"). -   Sometimes misconfigured encryption results in confusing error     messages in no way pointing to real cause.\     In subsections below we try to provide a (far from exhaustive)     collection of messages and possible causes which could help in     troubleshooting.\     Please note that different crypto toolkits (OpenSSL, GnuTLS) often     produce different error messages in same problem situations.\     Sometimes error messages depend even on particular combination of     crypto toolkits on both sides.
zh-cn	 #### 一般建议  - 首先了解哪些组件充当 TLS 客户端，哪个组件在出现问题时充当 TLS 服务器。     Zabbix server、proxies和agents，取决于它们之间的交互，都可以用作 TLS 服务器和客户端。     例如，Zabbix server充当TLS客户端连接到agent进行被动检查。Agent充当 TLS 服务器的角色。\     Zabbix agent充当 TLS 客户端从proxy请求活动检查列表。Proxy充当 TLS 服务器的角色。\     "zabbix_get"和"zabbix_sender"应用程序始终充当 TLS 客户端。 - Zabbix 使用相互身份验证。\     每一方都会验证其对等方，并可能拒绝连接。\     例如，如果agent的证书无效，连接到agent的 Zabbix server可以立即关闭连接。反之亦然 - 如果server不受agent信任，则接受来自server的连接的Zabbix agent也可以关闭连接。 - 检查两端的日志文件 - 在 TLS 客户端和 TLS 服务器中。     拒绝连接的一方可以记录被拒绝的确切原因。另一方经常报告相当一般的错误（例如，"对等方关闭的连接"，"连接未正确终止"）。 - 有时，错误配置的加密会导致令人困惑的错误消息，而无法指向真正的原因。     在下面的小节中，我们尝试提供（仍有未尽之处）消息和可能原因的集合，以帮助进行故障排除。     请注意，不同的加密工具包（OpenSSL，GnuTLS）在相同的问题情况下通常会产生不同的错误消息。     有时，错误消息甚至取决于双方加密工具包的特定组合。

en-us	##### Generating from history/trends  Graphs can be drawn based on either item [history or trends](/manual/config/items/history_and_trends).  For the users who have frontend [debug mode](/manual/web_interface/debug_mode) activated, a gray, vertical caption is displayed at the bottom right of a graph indicating where the data come from.  Several factors influence whether history of trends is used:  -   longevity of item history. For example, item history can be kept for     14 days. In that case, any data older than the fourteen days will be     coming from trends.  ```{=html} <!-- --> ``` -   data congestion in the graph. If the amount of seconds to display in     a horizontal graph pixel exceeds 3600/16, trend data are displayed     (even if item history is still available for the same period).  ```{=html} <!-- --> ``` -   if trends are disabled, item history is used for graph building - if     available for that period. This is supported starting with Zabbix     2.2.1 (before, disabled trends would mean an empty graph for the     period even if item history was available).
zh-cn	##### 从历史/趋势生成  可以根据监控项[历史或趋势](/manual/config/items/history_and_trends)生成图表。  对于前端[调试模式](/manual/web_interface/debug_mode) 已激活的用户，在图表的右下角显示一个灰色的垂直标题，指示数据来源。  影响趋势历史使用的几个因素：  - 监控项历史的寿命。例如，项目历史可以保留14 天。在这种情况下，任何超过十四天的数据都将不被保存。  ```{=html} <!-- --> ``` - 图表中的数据拥塞。如果要显示的秒数水平图形像素超过 3600/16，显示趋势数据（即使监控项历史在同一时期仍然可用）。  ```{=html} <!-- --> ``` - 如果趋势被禁用，监控项历史将用于图表构建（如果可用于该时期）。从 Zabbix 2.2.1开始支持此功能（之前，禁用趋势意味着期间的图表是空的，即使监控项历史可用）。

en-us	#### Generating PSK  For example, a 256-bit (32 bytes) PSK can be generated using the following commands:  -   with *OpenSSL*:  ```{=html} <!-- --> ```       $ openssl rand -hex 32       af8ced32dfe8714e548694e2d29e1a14ba6fa13f216cb35c19d0feb1084b0429  -   with *GnuTLS*:  ```{=html} <!-- --> ```       $ psktool -u psk_identity -p database.psk -s 32       Generating a random key for user 'psk_identity'       Key stored to database.psk              $ cat database.psk        psk_identity:9b8eafedfaae00cece62e85d5f4792c7d9c9bcc851b23216a1d300311cc4f7cb  Note that "psktool" above generates a database file with a PSK identity and its associated PSK. Zabbix expects just a PSK in the PSK file, so the identity string and colon (':') should be removed from the file.
zh-cn	   #### 生成 PSK  例如，可以使用以下命令生成 256 位 （32 字节）PSK:  -  对于*OpenSSL*: ```{=html}   <!-- --> ```       $ openssl rand -hex 32       af8ced32dfe8714e548694e2d29e1a14ba6fa13f216cb35c19d0feb1084b0429   -  对于 *GnuTLS*: ```{=html}   <!-- -->    $ psktool -u psk_identity -p database.psk -s 32   为用户 'psk_identity'生成随机密钥   密钥存储到 database.psk      $ cat database.psk    psk_identity:9b8eafedfaae00cece62e85d5f4792c7d9c9bcc851b23216a1d300311cc4f7cb ``` 请注意，上面的"psktool"会生成一个具有 PSK 标识及其关联 PSK 的数据库文件。 Zabbix 期望 PSK 文件中只有一个 PSK，因此应从文件中删除标识字符串和冒号 （':'）。

en-us	#### Getting Java gateway  You can install Java gateway either from the sources or packages downloaded from [Zabbix website](http://www.zabbix.com/download.php).  Using the links below you can access information how to get and run Zabbix Java gateway, how to configure Zabbix server (or Zabbix proxy) to use Zabbix Java gateway for JMX monitoring, and how to configure Zabbix items in Zabbix frontend that correspond to particular JMX counters.  |Installation from|Instructions|Instructions| |-----------------|------------|------------| |*Sources*|[Installation](/manual/installation/install#installing_java_gateway)|[Setup](/manual/concepts/java/from_sources)| |*RHEL packages*|[Installation](/manual/installation/install_from_packages/rhel#java_gateway_installation)|[Setup](/manual/concepts/java/from_rhel)| |*Debian/Ubuntu packages*|[Installation](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)|[Setup](/manual/concepts/java/from_debian_ubuntu)|
zh-cn	#### 获取java网关  您可以从源代码或从下载的包中安装Java网关 [Zabbix website](http://www.zabbix.com/download.php).  使用下面的链接，您可以访问以下信息：如何获取和运行Zabbix java网关，如何配置Zabbix server（或Zabbix proxy）以使用Zabbix Java 网关进行JMX监控，以及如何在Zabbix前端配置对应于特定JMX计数器的Zabbix监控项。  |安装途径|安装说明|配置步骤说明| |-----------------|------------|------------| |*Sources*|[安装](/manual/installation/install#installing_java_gateway)|[配置](/manual/concepts/java/from_sources)| |*RHEL packages*|[安装](/manual/installation/install_from_packages/rhel#java_gateway_installation)|[配置](/manual/concepts/java/from_rhel)| |*Debian/Ubuntu packages*|[安装](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)|[配置](/manual/concepts/java/from_debian_ubuntu)|

en-us	#### Getting Zabbix source code  There are several ways of getting Zabbix source code:  -   You can [download](https://www.zabbix.com/download_sources) the     released stable versions from the official Zabbix website -   You can [download](https://www.zabbix.com/developers) nightly builds     from the official Zabbix website developer page -   You can get the latest development version from the Git source code     repository system:     -   The primary location of the full repository is at         <https://git.zabbix.com/scm/zbx/zabbix.git>     -   Master and supported releases are also mirrored to Github at         <https://github.com/zabbix/zabbix>  A Git client must be installed to clone the repository. The official commandline Git client package is commonly called **git** in distributions. To install, for example, on Debian/Ubuntu, run:      sudo apt-get update     sudo apt-get install git  To grab all Zabbix source, change to the directory you want to place the code in and execute:      git clone https://git.zabbix.com/scm/zbx/zabbix.git
zh-cn	#### 获取Zabbix源码  如何获取Zabbix源码有如下几种方式：   -   可从 Zabbix 官方网站获取发布的稳定版本 [下载](https://www.zabbix.com/download_sources)     -   可从 Zabbix官方开发网站页面获取源架构 [下载](https://www.zabbix.com/developers)  -   可以从 Git 源代码中获取最新的开发版本存储系统：        -   完整存储Zabbix源码的主要位置是         <https://git.zabbix.com/scm/zbx/zabbix.git>        -   主版本和支持版本也镜像到 Github，网址为         <https://github.com/zabbix/zabbix>  必须安装 Git 客户端才能克隆存储源。 官方命令行 Git 客户端包在发布版本中通常称为 **git**。 示例：在 Debian/Ubuntu 上安装，请运行如下命令：      sudo apt-get update     sudo apt-get install git  若需获取所有 Zabbix 源代码，请更改相应文件来替换源码并执行如下命令：      git clone https://git.zabbix.com/scm/zbx/zabbix.git

en-us	##### Global messages displayed  As the messages arrive, they are displayed in a floating section on the right hand side. This section can be repositioned freely by dragging the section header.  ![global\_messages.png](../../../../assets/en/manual/web_interface/global_messages.png)  For this section, several controls are available:  -   ![](../../../../assets/en/manual/about/message_button_snooze.png)     **Snooze** button silences the currently active alarm sound; -   ![](../../../../assets/en/manual/about/message_button_mute.png)     **Mute/Unmute** button switches between playing and not playing the     alarm sounds at all.
zh-cn	##### 显示全局消息  当消息到达时，它们会显示在右侧的浮动部分中。 该部分可以通过拖动部分标题自由重新定位。  ![global\_messages.png](../../../../assets/en/manual/web_interface/global_messages.png)  对于本节，有几个控件可用：  - · ![](../../../../assets/en/manual/about/message_button_snooze.png) **延后警报** 按钮使当前活动的警报声音静音； - · ![](../../../../assets/en/manual/about/message_button_mute.png) **静音/取消静音**按钮在播放和不播放警报声之间切换。

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

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

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

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

en-us	# > Graph item object  The following objects are directly related to the `graphitem` API.
zh-cn	 # > 图表监控项对象  以下对象与 `图表监控项` API直接相关。

en-us	# Graph item  This class is designed to work with graph items.  Object references:\  -   [Graph item](/manual/api/reference/graphitem/object#graph_item)  Available methods:\  -   [graphitem.get](/manual/api/reference/graphitem/get) - retrieving     graph items
zh-cn	# 图表监控项  这个类别旨在为主机使用。  对象引用：\  -   [图表监控项](/manual/api/reference/graphitem/object#图表监控项)  可用方法：\  -   [graphitem.get](/manual/api/reference/graphitem/get) - 获取图表监控项

en-us	# > Graph object  The following objects are directly related to the `graph` API.
zh-cn	 # > 图表对象  以下这些对象与 `graph` API 直接相关。

en-us	##### Graph preview  In the *Preview* tab, a preview of the graph is displayed so you can immediately see what you are creating.  ![](../../../../../assets/en/manual/config/visualization/graph_preview.png){width="600"}  Note that the preview will not show any data for template items.  ![](../../../../../assets/en/manual/config/visualization/graph_preview2.png){width="600"}  In this example, pay attention to the dashed bold line displaying the trigger level and the trigger information displayed in the legend.  ::: noteclassic No more than 3 trigger lines can be displayed. If there are more triggers then the triggers with lower severity are prioritized for display.\ \ If graph height is set as less than 120 pixels, no trigger will be displayed in the legend. :::
zh-cn	##### 图表预览  在 *预览* 选项卡中，将显示图形的预览，以便您可以立即查看您正在创建的内容。  ![](../../../../../assets/en/manual/config/visualization/graph_preview.png){width="600"}  请注意，预览不会显示模板项的任何数据。  ![](../../../../../assets/en/manual/config/visualization/graph_preview2.png){width="600"}  在此示例中，请注意显示触发级别的粗虚线和图例中显示的触发信息。  ::: noteclassic 最多可显示 3 条触发线。如果有更多的触发器，然后具有较低严重性的触发器被优先用于展示。\ \ 如果图形高度设置为小于 120 像素，则不会触发显示在图例中。 :::

en-us	# graphprototype.create
zh-cn	# 创建图表原型

en-us	# graphprototype.delete
zh-cn	# 删除图表原型

en-us	# graphprototype.get
zh-cn	# 查询图表原型

en-us	# > Graph prototype object  The following objects are directly related to the `graphprototype` API.
zh-cn	# > 图表原型对象  以下对象与 `图表原型` API直接相关。

en-us	# Graph prototype  This class is designed to work with graph prototypes.  Object references:\  -   [Graph     prototype](/manual/api/reference/graphprototype/object#graph_prototype)  Available methods:\  -   [graphprototype.create](/manual/api/reference/graphprototype/create) -     creating new graph prototypes -   [graphprototype.delete](/manual/api/reference/graphprototype/delete) -     deleting graph prototypes -   [graphprototype.get](/manual/api/reference/graphprototype/get) -     retrieving graph prototypes -   [graphprototype.update](/manual/api/reference/graphprototype/update) -     updating graph prototypes
zh-cn	 # 图表原型  这个类旨在为图表原型使用。  对象引用:\  -   [图表原型](/manual/api/reference/graphprototype/object#graph_prototype)  可用的方法:\  -   [graphprototype.create](/manual/api/reference/graphprototype/create) - 创建图表原型 -   [graphprototype.delete](/manual/api/reference/graphprototype/delete) - 删除图表原型 -   [graphprototype.get](/manual/api/reference/graphprototype/get) - 检索图表原型 -   [graphprototype.update](/manual/api/reference/graphprototype/update) - 升级图表原型

en-us	# graphprototype.update
zh-cn	# 更新图表原型

en-us	#### Graphs  Edit graphs or separate graph items for better presentation of the gathered data.  [Graph API](/manual/api/reference/graph) | [Graph item API](/manual/api/reference/graphitem)
zh-cn	#### 图形  编辑图形或单独的图形项，以便更好地呈现收集的数据。  [Graph API](/manual/api/reference/graph) | [Graph item API](/manual/api/reference/graphitem)

en-us	##### Graphs  With the item working for a while, it might be time to see something visual. [Simple graphs](/manual/config/visualization/graphs/simple) are available for any monitored numeric item without any additional configuration. These graphs are generated on runtime.  To view the graph, go to *Monitoring → Latest data* and click on the 'Graph' link next to the item.  ![](../../../assets/en/manual/quickstart/simple_graph.png){width="600"}
zh-cn	##### 图表  当监控项运行了一段时间后，可以查看可视化图表。 [简单图表](/manual/config/visualization/graphs/simple) 适用于任何信息类型为数值型的监控项，且不需要额外的配置。这些图表会在运行时生成。  前往*Monitoring → Latest data*，然后点击监控项后的”图表“'链接来查看。  ![](../../../assets/en/manual/quickstart/simple_graph.png){width="600"}

en-us	# Graph  This class is designed to work with graphs.  Object references:\  -   [Graph](/manual/api/reference/graph/object#graph)  Available methods:\  -   [graph.create](/manual/api/reference/graph/create) - creating new     graphs -   [graph.delete](/manual/api/reference/graph/delete) - deleting graphs -   [graph.get](/manual/api/reference/graph/get) - retrieving graphs -   [graph.update](/manual/api/reference/graph/update) - updating graphs
zh-cn	# 图表  这个类旨在为监控项使用。  对象参考：\  -   [图表](/manual/api/reference/graph/object#graph)  可用方法：\  -   [graph.create](/manual/api/reference/graph/create) - 创建图表 -   [graph.delete](/manual/api/reference/graph/delete) - 删除图表 -   [graph.get](/manual/api/reference/graph/get) - 获取图表 -   [graph.update](/manual/api/reference/graph/update) - 更新图表

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

en-us	# hanode.get
zh-cn	# HA 节点获取

en-us	#### Hardware
zh-cn	#### 硬件

en-us	#### Header processing  The CSV file header line can be processed in two different ways:  -   If the *With header row* checkbox is marked - header line values are     interpreted as column names. In this case the column names must be     unique and the data row should not contain more columns than the     header row; -   If the *With header row* checkbox is not marked - the header line is     interpreted as data. Column names are generated automatically     (1,2,3,4...)  CSV file example:      Nr,Item name,Key,Qty     1,active agent item,agent.hostname,33     "2","passive agent item","agent.version","44"     3,"active,passive agent items",agent.ping,55  ::: noteclassic A quotation character within a quoted field in the input must be escaped by preceding it with another quotation character. :::  **Processing header line**  JSON output when a header line is expected:  ``` {.json} [    {       "Nr":"1",       "Item name":"active agent item",       "Key":"agent.hostname",       "Qty":"33"    },    {       "Nr":"2",       "Item name":"passive agent item",       "Key":"agent.version",       "Qty":"44"    },    {       "Nr":"3",       "Item name":"active,passive agent items",       "Key":"agent.ping",       "Qty":"55"    } ] ```  **No header line processing**  JSON output when a header line is not expected:  ``` {.json} [    {       "1":"Nr",       "2":"Item name",       "3":"Key"       "4":"Qty"    },    {       "1":"1",       "2":"active agent item",       "3":"agent.hostname"       "4":"33"    },    {       "1":"2",       "2":"passive agent item",       "3":"agent.version"       "4":"44"    },    {       "1":"3",       "2":"active,passive agent items",       "3":"agent.ping"       "4":"55"    } ] ```
zh-cn	#### 标题预处理  CSV文件标题行可以用两种不同的方式处理:  -   如果勾选*With header row*  - 标题行值被解释为列名。在这种情况下，列名必须是唯一的，数据行不应该包含比标题行更多的列； -   如果勾选 *With header row*  - 标题行解释为数据。自动生成列名(1,2,3,4…)  CSV 文件示例:      Nr,Item name,Key,Qty     1,active agent item,agent.hostname,33     "2","passive agent item","agent.version","44"     3,"active,passive agent items",agent.ping,55  ::: noteclassic 输入中的引号字段中的引号字符必须在其前面加上另一个引号字符进行转义。 :::  **有标题行预处理**  有标题行预处理时期望JSON的输出:  ``` {.json} [    {       "Nr":"1",       "Item name":"active agent item",       "Key":"agent.hostname",       "Qty":"33"    },    {       "Nr":"2",       "Item name":"passive agent item",       "Key":"agent.version",       "Qty":"44"    },    {       "Nr":"3",       "Item name":"active,passive agent items",       "Key":"agent.ping",       "Qty":"55"    } ] ```  **无标题行预处理**  无标题行预处理时期望JSON的输出:  ``` {.json} [    {       "1":"Nr",       "2":"Item name",       "3":"Key"       "4":"Qty"    },    {       "1":"1",       "2":"active agent item",       "3":"agent.hostname"       "4":"33"    },    {       "1":"2",       "2":"passive agent item",       "3":"agent.version"       "4":"44"    },    {       "1":"3",       "2":"active,passive agent items",       "3":"agent.ping"       "4":"55"    } ] ```

en-us	#### High availability cluster  Retrieve a list of server nodes and their status.  [High availability cluster API](/manual/api/reference/hanode)
zh-cn	#### 高可用集群  检索服务器节点及其状态的列表。  [High availability cluster API](/manual/api/reference/hanode)

en-us	# > High availability node object  The following object is related to operating a High availability cluster of Zabbix servers.
zh-cn	 # > 高可用节点对象  以下对象与操作Zabbix servers 的高可用集群有关。

en-us	# High availability node  This class is designed to work with server nodes that are part of a High availability cluster, or a standalone server instance.  Object references:\  -   [High availability node](/manual/api/reference/hanode/object#hanode)  Available methods:\  -   [hanode.get](/manual/api/reference/hanode/get) - retrieving nodes
zh-cn	 # 高可用节点  该类被设计用来与作为高可用性集群一部分的服务器节点或独立的服务器实例一起工作。  对象引用:\  -   [高可用节点](/manual/api/reference/hanode/object#hanode)  可用的方法:\  -   [hanode.get](/manual/api/reference/hanode/get) - 检索节点

en-us	# history.clear
zh-cn	# 删除历史数据

en-us	# history.get
zh-cn	 # 查询历史数据

en-us	# > History object  The following objects are directly related to the `history` API.  ::: noteclassic History objects differ depending on the item's type of information. They are created by the Zabbix server and cannot be modified via the API. :::
zh-cn	 # > 历史数据对象  下列对象与 `history` API直接相关。  ::: noteclassic 历史数据对象会因为监控项的数据类型而有所不同.它们都是Zabbix Server创建的，不能通过API进行修改。 :::

en-us	#### History  Retrieve historical values gathered by Zabbix monitoring processes for presentation or further processing.  [History API](/manual/api/reference/history)
zh-cn	#### 历史记录  检索 Zabbix 监控进程收集的历史值，以便进行演示或进一步处理。  [History API](/manual/api/reference/history)

en-us	# History  This class is designed to work with history data.  Object references:\  -   [History](/manual/api/reference/history/object#history)  Available methods:\  -   [history.get](/manual/api/reference/history/get) - retrieving     history data.
zh-cn	 # 历史数据  该类旨在处理历史数据。  对象引用:\  -   [History](/manual/api/reference/history/object#history)  可用的方法:\  -   [history.get](/manual/api/reference/history/get) 检索历史数据

en-us	##### Host configuration  A host must be configured to process IPMI checks. An IPMI interface must be added, with the respective IP and port numbers, and IPMI authentication parameters must be defined.  See the [configuration of hosts](/manual/config/hosts/host) for more details.
zh-cn	##### 主机配置  主机必须配置为处理IPMI检查。必须添加IPMI接口，必须定义相应的IP和端口号，并且必须定义IPMI认证参数。  更多细节请查看 [主机配置](/manual/config/hosts/host) 。

en-us	##### Host configuration  You can specify that an individual host should be monitored by a proxy in the [host configuration](/manual/config/hosts/host) form, using the *Monitored by proxy* field.  ![](../../../assets/en/manual/proxies/proxy_set.png)  Host [mass update](/manual/config/hosts/hostupdate) is another way of specifying that hosts should be monitored by a proxy.
zh-cn	##### 主机配置  你可以在[主机配置](/manual/config/hosts/host)表单中指定一个单独的主机应该被一个proxy监控，使用*Monitored by proxy*字段。  ![](../../../assets/en/manual/proxies/proxy_set.png)  主机 [批量更新](/manual/config/hosts/hostupdate)是指定主机应该由proxy监视的另一种方式。

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

en-us	##### Host creation  A host is added if the *Add host* operation is selected. A host is also added, even if the *Add host* operation is missing, if you select operations resulting in actions on a host. Such operations are:  -   enable host -   disable host -   add host to a host group -   link template to a host  Created hosts are added to the *Discovered hosts* group (by default, configurable in *Administration* → *General* → *[Other](/manual/web_interface/frontend_sections/administration/general#other_parameters)*). If you wish hosts to be added to another group, add a *Remove from host groups* operation (specifying "Discovered hosts") and also add an *Add to host groups* operation (specifying another host group), because a host must belong to a host group.
zh-cn	##### 创建主机  选择 *添加主机* 操作来创建主机。但无需 *添加主机* 操作一样可以创建主机，只要该操作对主机造成了变更即可。此类操作有：  -   启用主机 -   禁用主机 -   添加主机到组 -   链接模板到主机  新建的主机会添加到 *发现的主机* 组 (默认设置，也可到  *管理* → *通用* → *[其它](/manual/web_interface/frontend_sections/administration/general#other_parameters)*界面自定义)。 如果想更改主机的主机组，可以执行 *从主机组中移除* 的操作(选定 "发现的主机"组) 并执行 *添加到主机组* 的操作(选定另一个主机组)，因为一个主机必须属于某个主机组。

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

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

en-us	##### Host graph tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |graphs| |\-| | |Root element for graphs.| | |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|<|\-|<|<|图形的根元素。| |<|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 - EXPLODED|图形类型。| |<|show\_legend|\-|`string`|0 - NO<br>1 - YES (默认)|显示图例。| |<|show\_3d|\-|`string`|0 - NO (默认)<br>1 - YES|开启3De风格。<br><br>用于饼图和分解饼图。| |<|percent\_left|\-|`double`|默认:0|显示左轴的百分位线。<br><br>仅用于普通图形。| |<|percent\_right|\-|`double`|默认:0|显示右轴的百分位线。 <br><br>仅用于普通图形。| |<|ymin\_type\_1|\-|`string`|0 - CALCULATED (默认)<br>1 - FIXED<br>2 - ITEM|Y轴的最小值。 <br><br>用于普通图和堆叠图。| |<|ymax\_type\_1|\-|`string`|0 - CALCULATED (默认)<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 - DOTTED\_LINE<br>4 - DASHED\_LINE<br>5 - GRADIENT\_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	# hostgroup.create
zh-cn	# 创建

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

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

en-us	# hostgroup.massadd
zh-cn	# 批量添加

en-us	# hostgroup.massremove
zh-cn	# 批量删除

en-us	# hostgroup.massupdate
zh-cn	# 批量更新

en-us	# > Host group object  The following objects are directly related to the `hostgroup` API.
zh-cn	 # > 主机组对象  以下对象是和`主机组`直接相关的API。

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

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

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

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

en-us	# hostinterface.massadd
zh-cn	# 批量添加

en-us	# hostinterface.massremove
zh-cn	# 批量删除

en-us	# > Host interface object  The following objects are directly related to the `hostinterface` API.
zh-cn	# > 主机接口对象  以下对象与 `主机接口` API 直接相关。

en-us	# hostinterface.replacehostinterfaces
zh-cn	# 替换

en-us	# Host interface  This class is designed to work with host interfaces.  Object references:\  -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)  Available methods:\  -   [hostinterface.create](/manual/api/reference/hostinterface/create) -     creating new host interfaces -   [hostinterface.delete](/manual/api/reference/hostinterface/delete) -     deleting host interfaces -   [hostinterface.get](/manual/api/reference/hostinterface/get) -     retrieving host interfaces -   [hostinterface.massadd](/manual/api/reference/hostinterface/massadd) -     adding host interfaces to hosts -   [hostinterface.massremove](/manual/api/reference/hostinterface/massremove) -     removing host interfaces from hosts -   [hostinterface.replacehostinterfaces](/manual/api/reference/hostinterface/replacehostinterfaces) -     replacing host interfaces on a host -   [hostinterface.update](/manual/api/reference/hostinterface/update) -     updating host interfaces
zh-cn	# 主机接口  这个类是设计用于处理主机接口.  对象引用:\  -   [Host     interface](/manual/api/reference/hostinterface/object#host_interface)  可用方法:\  -   [hostinterface.create](/manual/api/reference/hostinterface/create) -     创建新的主机接口 -   [hostinterface.delete](/manual/api/reference/hostinterface/delete) -     删除主机接口 -   [hostinterface.get](/manual/api/reference/hostinterface/get) -     获取主机接口 -   [hostinterface.massadd](/manual/api/reference/hostinterface/massadd) -     批量添加主机接口 -   [hostinterface.massremove](/manual/api/reference/hostinterface/massremove) -     批量删除主机接口 -   [hostinterface.replacehostinterfaces](/manual/api/reference/hostinterface/replacehostinterfaces) -     替换主机接口 -   [hostinterface.update](/manual/api/reference/hostinterface/update) -     更新主机接口

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

en-us	### Host inventory  The host inventory object has the following properties.  ::: notetip Each property has it's own unique ID number, which is used to associate host inventory fields with items. :::  |ID|Property|[Type](/manual/api/reference_commentary#data_types)|Description|Maximum length| |-|--|-|-----|-----| |4|alias|string|Alias.|128 characters| |11|asset\_tag|string|Asset tag.|64 characters| |28|chassis|string|Chassis.|64 characters| |23|contact|string|Contact person.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |32|contract\_number|string|Contract number.|64 characters| |47|date\_hw\_decomm|string|HW decommissioning date.|64 characters| |46|date\_hw\_expiry|string|HW maintenance expiry date.|64 characters| |45|date\_hw\_install|string|HW installation date.|64 characters| |44|date\_hw\_purchase|string|HW purchase date.|64 characters| |34|deployment\_status|string|Deployment status.|64 characters| |14|hardware|string|Hardware.|255 characters| |15|hardware\_full|string|Detailed hardware.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |39|host\_netmask|string|Host subnet mask.|39 characters| |38|host\_networks|string|Host networks.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |40|host\_router|string|Host router.|39 characters| |30|hw\_arch|string|HW architecture.|32 characters| |33|installer\_name|string|Installer name.|64 characters| |24|location|string|Location.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |25|location\_lat|string|Location latitude.|16 characters| |26|location\_lon|string|Location longitude.|16 characters| |12|macaddress\_a|string|MAC address A.|64 characters| |13|macaddress\_b|string|MAC address B.|64 characters| |29|model|string|Model.|64 characters| |3|name|string|Name.|128 characters| |27|notes|string|Notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |41|oob\_ip|string|OOB IP address.|39 characters| |42|oob\_netmask|string|OOB host subnet mask.|39 characters| |43|oob\_router|string|OOB router.|39 characters| |5|os|string|OS name.|128 characters| |6|os\_full|string|Detailed OS name.|255 characters| |7|os\_short|string|Short OS name.|128 characters| |61|poc\_1\_cell|string|Primary POC mobile number.|64 characters| |58|poc\_1\_email|string|Primary email.|128 characters| |57|poc\_1\_name|string|Primary POC name.|128 characters| |63|poc\_1\_notes|string|Primary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |59|poc\_1\_phone\_a|string|Primary POC phone A.|64 characters| |60|poc\_1\_phone\_b|string|Primary POC phone B.|64 characters| |62|poc\_1\_screen|string|Primary POC screen name.|64 characters| |68|poc\_2\_cell|string|Secondary POC mobile number.|64 characters| |65|poc\_2\_email|string|Secondary POC email.|128 characters| |64|poc\_2\_name|string|Secondary POC name.|128 characters| |70|poc\_2\_notes|string|Secondary POC notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |66|poc\_2\_phone\_a|string|Secondary POC phone A.|64 characters| |67|poc\_2\_phone\_b|string|Secondary POC phone B.|64 characters| |69|poc\_2\_screen|string|Secondary POC screen name.|64 characters| |8|serialno\_a|string|Serial number A.|64 characters| |9|serialno\_b|string|Serial number B.|64 characters| |48|site\_address\_a|string|Site address A.|128 characters| |49|site\_address\_b|string|Site address B.|128 characters| |50|site\_address\_c|string|Site address C.|128 characters| |51|site\_city|string|Site city.|128 characters| |53|site\_country|string|Site country.|64 characters| |56|site\_notes|string|Site notes.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |55|site\_rack|string|Site rack location.|128 characters| |52|site\_state|string|Site state.|64 characters| |54|site\_zip|string|Site ZIP/postal code.|64 characters| |16|software|string|Software.|255 characters| |18|software\_app\_a|string|Software application A.|64 characters| |19|software\_app\_b|string|Software application B.|64 characters| |20|software\_app\_c|string|Software application C.|64 characters| |21|software\_app\_d|string|Software application D.|64 characters| |22|software\_app\_e|string|Software application E.|64 characters| |17|software\_full|string|Software details.|Depends on the database used:<br>- 65535 characters for SQL databases<br>- 2048 characters for Oracle databases| |10|tag|string|Tag.|64 characters| |1|type|string|Type.|64 characters| |2|type\_full|string|Type details.|64 characters| |35|url\_a|string|URL A.|255 characters| |36|url\_b|string|URL B.|255 characters| |37|url\_c|string|URL C.|255 characters| |31|vendor|string|Vendor.|64 characters|
zh-cn	### 主机资产  主机资产对象具有以下属性。  ::: notetip 每个属性都有自己的唯一ID号，该ID号用于将主机资产字段与监控项关联起来。 :::  |ID|属性|[类型](/manual/api/reference_commentary#data_types)|描述|最大长度| |----|--------|--------|-------|-----------| |4|alias|string|别名。|128 个字符| |11|asset\_tag|string|资产标签。|64 个字符| |28|chassis|string|机箱。|64 个字符| |23|contact|string|联系人。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |32|contract\_number|string|合同号码。|64 个字符| |47|date\_hw\_decomm|string|硬件退役日期。|64 个字符| |46|date\_hw\_expiry|string|硬件维护到期日期。|64 个字符| |45|date\_hw\_install|string|硬件安装日期。|64 个字符| |44|date\_hw\_purchase|string|硬件购买日期。|64 个字符| |34|deployment\_status|string|部署状态。|64 个字符| |14|hardware|string|硬件。|255 个字符| |15|hardware\_full|string|硬件详细信息。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |39|host\_netmask|string|主机子网掩码。|39 个字符| |38|host\_networks|string|主机网络。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |40|host\_router|string|主机路由器。|39 个字符| |30|hw\_arch|string|硬件架构。|32 个字符| |33|installer\_name|string|安装程序名称。|64 个字符| |24|location|string|位置。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |25|location\_lat|string|位置纬度。|16 个字符| |26|location\_lon|string|位置经度。|16 个字符| |12|macaddress\_a|string|MAC 地址 A.|64 个字符| |13|macaddress\_b|string|MAC地址B.|64个字符| |29|model|string|模式。|64 个字符| |3|name|string|名称。|128 个字符| |27|notes|string|备注。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |41|oob\_ip|string|OOB IP 地址。|39 个字符| |42|oob\_netmask|string|OOB 主机子网掩码。|39 个字符| |43|oob\_router|string|OOB 路由器。|39 个字符| |5|os|string|操作系统名称。|128 个字符| |6|os\_full|string|详细的操作系统名称。|255 个字符| |7|os\_short|string|操作系统简称。|128 个字符| |61|poc\_1\_cell|string|主要 POC 手机号码。|64 个字符| |58|poc\_1\_email|string|主要电子邮件。|128 个字符| |57|poc\_1\_name|string|主要 POC 名称。|128 个字符| |63|poc\_1\_notes|string|主要 POC 注释。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |59|poc\_1\_phone\_a|string|主要 POC 电话 A.|64 个字符| |60|poc\_1\_phone\_b|string|主要 POC 电话 B.|64 个字符| |62|poc\_1\_screen|string|主要 POC 屏幕名称。|64 个字符| |68|poc\_2\_cell|string|辅助 POC 手机号码。|64 个字符| |65|poc\_2\_email|string|辅助 POC 电子邮件。|128 个字符| |64|poc\_2\_name|string|二级 POC 名称。|128 个字符| |70|poc\_2\_notes|string|次要 POC 注释。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |66|poc\_2\_phone\_a|string|辅助 POC 电话 A.|64 个字符| |67|poc\_2\_phone\_b|string|辅助 POC 电话 B.|64 个字符| |69|poc\_2\_screen|string|次要 POC 屏幕名称。|64 个字符| |8|serialno\_a|string|序列号A.|64个字符| |9|serialno\_b|string|序列号B.|64个字符| |48|site\_address\_a|string|站点地址A.|128个字符| |49|site\_address\_b|string|站点地址B.|128个字符| |50|site\_address\_c|string|站点地址C.|128个字符| |51|site\_city|string|站点城市。|128 个字符| |53|site\_country|string|网站国家。|64 个字符| |56|site\_notes|string|站点注释。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |55|site\_rack|string|站点机架位置。|128 个字符| |52|site\_state|string|站点状态。|64 个字符| |54|site\_zip|string|站点邮政编码。|64 个字符| |16|software|string|软件。|255 个字符| |18|software\_app\_a|string|软件应用程序 A.|64 个字符| |19|software\_app\_b|string|软件应用程序 B.|64 个字符| |20|software\_app\_c|string|软件应用程序 C.|64 个字符| |21|software\_app\_d|string|软件应用程序 D.|64 个字符| |22|software\_app\_e|string|软件应用程序 E.|64 个字符| |17|software\_full|string|软件详细信息。|取决于所使用的数据库：<br>- SQL 数据库为 65535 个字符<br>- Oracle 数据库为 2048 个字符| |10|tag|string|Tag.|64 个字符| |1|type|string|类型。|64 个字符| |2|type\_full|string|类型详细信息。|64 个字符| |35|url\_a|string|URL A.|255 个字符| |36|url\_b|string|URL B.|255 个字符| |37|url\_c|string|URL C.|255 个字符| |31|vendor|string|厂家。|64 个字符|

en-us	##### Host low-level discovery rule tags  |Element|Element property|Required|Type|Range^**[1](#footnotes)**^|Description| |--|--|-|--|----|--------| |discovery\_rules| |\-| | |Root element for low-level discovery rules.| | |*For most of the element tag values, see element tag values for a regular item. Only the tags that are specific to low-level discovery rules, are described below.*| | | | | | |type|\-|`string`|0 - ZABBIX\_PASSIVE (default)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|Item type.| | |lifetime|\-|`string`|Default: 30d|Time period after which items that are no longer discovered will be deleted. Seconds, time unit with suffix or user macro.| |filter| | | | |Individual filter.| | |evaltype|\-|`string`|0 - AND\_OR (default)<br>1 - AND<br>2 - OR<br>3 - FORMULA|Logic to use for checking low-level discovery rule filter conditions.| | |formula|\-|`string`| |Custom calculation formula for filter conditions.| |conditions| |\-| | |Root element for filter conditions.| | |macro|x|`string`| |Low-level discovery macro name.| | |value|\-|`string`| |Filter value: regular expression or global regular expression.| | |operator|\-|`string`|8 - MATCHES\_REGEX (default)<br>9 - NOT\_MATCHES\_REGEX|Condition operator.| | |formulaid|x|`character`| |Arbitrary unique ID that is used to reference a condition from the custom expression. Can only contain capital-case letters. The ID must be defined by the user when modifying filter conditions, but will be generated anew when requesting them afterward.| |lld\_macro\_paths| |\-| | |Root element for LLD macro paths.| | |lld\_macro|x|`string`| |Low-level discovery macro name.| | |path|x|`string`| |Selector for value which will be assigned to the corresponding macro.| |preprocessing| |\-| | |LLD rule value preprocessing.| |step| |\-| | |Individual LLD rule value preprocessing step.| | |*For most of the element tag values, see element tag values for a host item value preprocessing. Only the tags that are specific to low-level discovery value preprocessing, are described below.*| | | | | | |type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|Type of the item value preprocessing step.| |trigger\_prototypes| |\-| | |Root element for trigger prototypes.| | |*For trigger prototype element tag values, see regular [host trigger](/manual/xml_export_import/hosts#host_trigger_tags) tags.*| | | | | |graph\_prototypes| |\-| | |Root element for graph prototypes.| | |*For graph prototype element tag values, see regular [host graph](/manual/xml_export_import/hosts#host_graph_tags) tags.*| | | | | |host\_prototypes| |\-| | |Root element for host prototypes.| | |*For host prototype element tag values, see regular [host](/manual/xml_export_import/hosts#host_tags) tags.*| | | | | |item\_prototypes| |\-| | |Root element for item prototypes.| | |*For item prototype element tag values, see regular [host item](/manual/xml_export_import/hosts#host_item_tags) tags.*| | | | | |master\_item| |\-| | |Individual item prototype master item/item prototype data.| | |key|x|`string`| |Dependent item prototype master item/item prototype key value.<br><br>Required for a dependent item.|
zh-cn	##### 主机底层自动发现规则标签  |元素|元素属性|是否必须|类型|适用范围^**[1](#footnotes)**^|描述| |-------|----------------|--------|----|--------------------------|-----------| |discovery\_rules|<|\-|<|<|低级别自动发现根元素。| |<|*有关大多数图元标标签，请参见常规监控项的图元标签值。下面只描述特定于底层自动发现规则的标签。*|<|<|<|<| |<|type|\-|`string`|0 - ZABBIX\_PASSIVE (默认)<br>2 - TRAP<br>3 - SIMPLE<br>5 - INTERNAL<br>7 - ZABBIX\_ACTIVE<br>10 - EXTERNAL<br>11 - ODBC<br>12 - IPMI<br>13 - SSH<br>14 - TELNET<br>16 - JMX<br>18 - DEPENDENT<br>19 - HTTP\_AGENT<br>20 - SNMP\_AGENT|监控项类型| |<|lifetime|\-|`string`|默认: 30d|在该时间段之后，不再发现的监控项将被删除。支持秒，带后缀的时间单位或用户宏。| |filter|<|<|<|<|单个过滤器。| |<|evaltype|\-|`string`|0 - AND\_OR (默认)<br>1 - AND<br>2 - OR<br>3 - FORMULA|用于检查底层自动发现规则筛选器条件的逻辑。| |<|formula|\-|`string`|<|过滤条件的自定义计算公式。| |conditions|<|\-|<|<|过滤条件的根元素。| |<|macro|x|`string`|<|底层自动发现宏名称| |<|value|\-|`string`|<|筛选值：正则表达式或全局正则表达式。| |<|operator|\-|`string`|8 - MATCHES\_REGEX (默认)<br>9 - NOT\_MATCHES\_REGEX|条件操作者。| |<|formulaid|x|`character`|<|用于从自定义表达式引用条件的任意唯一ID。只能包含大写字母。用户在修改过滤条件时必须定义ID，但在之后请求时将重新生成ID。| |lld\_macro\_paths|<|\-|<|<|底层自动发现宏路径根元素。| |<|lld\_macro|x|`string`|<|底层自动发现宏名称| |<|path|x|`string`|<|将分配给相应宏的值的选择器。| |preprocessing|<|\-|<|<|底层自动发现值预处理。| |step|<|\-|<|<|单个底层自动发现规则值预处理步骤。| |<|*有关大多数图元标签值，请参见主体监控值预处理的图元标签值。下面只描述特定于底层自动发现值预处理的标签。*|<|<|<|<| |<|type|x|`string`|5 - REGEX<br>11 - XMLPATH<br>12 - JSONPATH<br>15 - NOT\_MATCHES\_REGEX<br>16 - CHECK\_JSON\_ERROR<br>17 - CHECK\_XML\_ERROR<br>20 - DISCARD\_UNCHANGED\_HEARTBEAT<br>21 - JAVASCRIPT<br>23 - PROMETHEUS\_TO\_JSON<br>24 - CSV\_TO\_JSON<br>25 - STR\_REPLACE<br>27 - XML\_TO\_JSON|监控项值预处理步骤的类型。| |trigger\_prototypes|<|\-|<|<|触发器原型的根元素。| |<|*有关触发器原型元素标签值，请参见常规 [主机触发器](/manual/xml_export_import/hosts#host_trigger_tags) 标签。*|<|<|<|<| |graph\_prototypes|<|\-|<|<|图形原型的根元素。| |<|*有关图形原型元素标签值，请参见常规 [主机图形](/manual/xml_export_import/hosts#host_graph_tags) 标签。*|<|<|<|<| |host\_prototypes|<|\-|<|<|主机原型的根元素。| |<|*有关主体原型图元标记值，请参见常规[主机](/manual/xml_export_import/hosts#host_tags) 标签。 *|<|<|<|<| |item\_prototypes|<|\-|<|<|监控项原型的根元素。| |<|*有关监控项原型元素标记值，请参见常规 [主机监控项](/manual/xml_export_import/hosts#host_item_tags) 标签。*|<|<|<|<| |master\_item|<|\-|<|<|单个监控项原型主监控项/监控项原型数据。| |<|key|x|`string`|<|依赖监控项原型 主监控项/监控项原型 键值的值.<br><br>依赖项所需。|

en-us	# host.massadd
zh-cn	# 批量添加

en-us	# host.massremove
zh-cn	# 配置批量删除

en-us	# host.massupdate
zh-cn	# 批量更新

en-us	##### Host naming  When adding hosts, a host name is the result of reverse DNS lookup or IP address if reverse lookup fails. Lookup is performed from the Zabbix server or Zabbix proxy, depending on which is doing the discovery. If lookup fails on the proxy, it is not retried on the server. If the host with such a name already exists, the next host would get **\_2** appended to the name, then **\_3** and so on.  It is also possible to override DNS/IP lookup and instead use an item value for host name, for example:  -   You may discover multiple servers with Zabbix agent running using a     Zabbix agent item for discovery and assign proper names to them     automatically, based on the string value returned by this item -   You may discover multiple SNMP network devices using an SNMP agent     item for discovery and assign proper names to them automatically,     based on the string value returned by this item  If the host name has been set using an item value, it is not updated during the following discovery checks. If it is not possible to set host name using an item value, default value (DNS name) is used.  If a host already exists with the discovered IP address, a new host is not created. However, if the discovery action contains operations (link template, add to host group, etc), they are performed on the existing host.
zh-cn	##### 命名主机  当添加主机时，主机名是反向DNS解析的结果，如果解析失败，则主机名设置为IP地址。如果Zabbix server执行网络发现，则解析就在Zabbix server上执行，如果Zabbix proxy执行网络发现，则解析在Zabbix proxy上执行。 如果在proxy上解析失败，不会再到Zabbix server上做解析。如果同名主机已经存在，新发现的主机会在名字后面添加 **\_2**后缀，后续新发现的同名主机的后缀数字依次增加。  可以使用监控项的主机名覆盖DNS/IP解析的主机名，比如：  -   可以使用安装在服务器上的Zabbix agent，通过agent的监控项来发现多台主机并自动给这些主机分配合适的主机名，主机名取决于监控项返回的字符串值 -   可以使用SNMP agent监控项发现多台网络设备并自动分配合适的主机名，主机名取决于监控项返回的字符串值  如果已经使用了监控项的返回值作为主机名，则接下来的网络发现不会更新主机名。如果不使用监控项的返回值作为主机名，则使用默认值(DNS名称)。  如果新发现的主机IP地址已经存在，那么不会创建该主机。然而如果发现动作中包含添加模板、添加到主机组等操作，则会在现有的主机上执行相应操作。

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

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

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

en-us	# hostprototype.get
zh-cn	# 查询

en-us	# > Host prototype object  The following objects are directly related to the `hostprototype` API.
zh-cn	# > 主机原型对象  以下对象与`主机原型` API直接相关。

en-us	# Host prototype  This class is designed to work with host prototypes.  Object references:\  -   [Host     prototype](/manual/api/reference/hostprototype/object#host_prototype) -   [Host prototype     inventory](/manual/api/reference/hostprototype/object#host_prototype_inventory) -   [Group link](/manual/api/reference/hostprototype/object#group_link) -   [Group     prototype](/manual/api/reference/hostprototype/object#group_prototype)  Available methods:\  -   [hostprototype.create](/manual/api/reference/hostprototype/create) -     creating new host prototypes -   [hostprototype.delete](/manual/api/reference/hostprototype/delete) -     deleting host prototypes -   [hostprototype.get](/manual/api/reference/hostprototype/get) -     retrieving host prototypes -   [hostprototype.update](/manual/api/reference/hostprototype/update) -     updating host prototypes
zh-cn	# 主机原型  该类被设计用来处理主机原型。  对象引用:\  -   [Host     prototype](/manual/api/reference/hostprototype/object#host_prototype) -   [Host prototype     inventory](/manual/api/reference/hostprototype/object#host_prototype_inventory) -   [Group link](/manual/api/reference/hostprototype/object#group_link) -   [Group     prototype](/manual/api/reference/hostprototype/object#group_prototype)  可用方法:\  -   [hostprototype.create](/manual/api/reference/hostprototype/create) -     创建新的主机原型 -   [hostprototype.delete](/manual/api/reference/hostprototype/delete) -     删除主机原型 -   [hostprototype.get](/manual/api/reference/hostprototype/get) -     获取主机原型 -   [hostprototype.update](/manual/api/reference/hostprototype/update) -     更新主机原型

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

en-us	##### Host removal  Hosts discovered by a network discovery rule are removed automatically from *Monitoring* → *Discovery* if a discovered entity is not in the rule's IP range any more. Hosts are removed immediately.
zh-cn	##### 删除主机   如果发现的主机不再属于发现规则定义的IP地址范围内，则该主机自动从 *监控* → *网络发现*  中删除。主机会立刻被删除。

en-us	#### Hosts and host groups  Manage host groups, hosts and everything related to them, including host interfaces, host macros and maintenance periods.  [Host API](/manual/api/reference/host) | [Host group API](/manual/api/reference/hostgroup) | [Host interface API](/manual/api/reference/hostinterface) | [User macro API](/manual/api/reference/usermacro) | [Value map API](/manual/api/reference/valuemap) | [Maintenance API](/manual/api/reference/maintenance)
zh-cn	#### 主机和主机组  管理主机组，主机及其相关的一切，包括主机接口，主机宏和维护期。  [Host API](/manual/api/reference/host) | [Host group API](/manual/api/reference/hostgroup) | [Host interface API](/manual/api/reference/hostinterface) | [User macro API](/manual/api/reference/usermacro) | [Value map API](/manual/api/reference/valuemap) | [Maintenance API](/manual/api/reference/maintenance)

en-us	#### Hosts/host prototypes  In a [host](/manual/config/hosts/host) and [host prototype](/manual/vm_monitoring#host_prototypes) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Interface IP/DNS|<|DNS only| |Interface port|<|no| |*SNMP v1, v2*|<|<| | |SNMP community|yes| |*SNMP v3*|<|<| | |Context name|yes| |^|Security name|yes| |^|Authentication passphrase|yes| |^|Privacy passphrase|yes| |*IPMI*|<|<| | |Username|yes| |^|Password|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### 主机/主机原型  在 [主机](/manual/config/hosts/host) 和 [主机原型](/manual/vm_monitoring#host_prototypes) 配置中，用户宏可用于以下地方:  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |接口IP/DNS|<|仅支持DNS| |接口端口|<|不支持| |*SNMP v1, v2*|<|<| | |SNMP团体名|支持| |*SNMP v3*|<|<| | |上下文名称|支持| |^|安全名称|支持| |^|身份验证密码|支持| |^|隐私密码|支持| |*IPMI*|<|<| | |用户名|支持| |^|密码|支持| |*标签*^[2](supported_by_location_user#footnotes)^|<|<| | |标签名称|支持| |^|标签值|支持|

en-us	# Host  This class is designed to work with hosts.  Object references:\  -   [Host](/manual/api/reference/host/object#host) -   [Host inventory](/manual/api/reference/host/object#host_inventory)  Available methods:\  -   [host.create](/manual/api/reference/host/create) - creating new     hosts -   [host.delete](/manual/api/reference/host/delete) - deleting hosts -   [host.get](/manual/api/reference/host/get) - retrieving hosts -   [host.massadd](/manual/api/reference/host/massadd) - adding related     objects to hosts -   [host.massremove](/manual/api/reference/host/massremove) - removing     related objects from hosts -   [host.massupdate](/manual/api/reference/host/massupdate) - replacing     or removing related objects from hosts -   [host.update](/manual/api/reference/host/update) - updating hosts
zh-cn	# 主机  这个类是设计用于处理主机。  对象引用:  -   [Host](/manual/api/reference/host/object#host) -   [Host inventory](/manual/api/reference/host/object#host_inventory)  相关方法:  -   [host.create](/manual/api/reference/host/create) - 创建新的主机 -   [host.delete](/manual/api/reference/host/delete) - 删除主机 -   [host.get](/manual/api/reference/host/get) - 获取主机信息 -   [host.massadd](/manual/api/reference/host/massadd) - 主机配置批量添加 -   [host.massremove](/manual/api/reference/host/massremove) - 主机配置批量删除 -   [host.massupdate](/manual/api/reference/host/massupdate) - 主机配置批量更新 -   [host.update](/manual/api/reference/host/update) - 更新主机

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

en-us	# housekeeping.get
zh-cn	# 查询

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

en-us	# Housekeeping  This class is designed to work with housekeeping.  Object references:\  -   [Housekeeping](/manual/api/reference/housekeeping/object#housekeeping)  Available methods:\  -   [housekeeping.get](/manual/api/reference/housekeeping/get) -     retrieve housekeeping -   [housekeeping.update](/manual/api/reference/housekeeping/update) -     update housekeeping
zh-cn	# 管家  该类被设计用于和管家一起工作。  对象参考:\  -   [Housekeeping](/manual/api/reference/housekeeping/object#housekeeping)  可用的方法:\  -   [housekeeping.get](/manual/api/reference/housekeeping/get) -     获取管家 -   [housekeeping.update](/manual/api/reference/housekeeping/update) -     更新管家

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

en-us	#### How it works  In log monitoring you may encounter lines similar to these:      Line1: Application 1 stopped     Line2: Application 2 stopped     Line3: Application 1 was restarted     Line4: Application 2 was restarted  The idea of event correlation is to be able to match the problem event from Line1 to the resolution from Line3 and the problem event from Line2 to the resolution from Line4, and close these problems one by one:      Line1: Application 1 stopped     Line3: Application 1 was restarted #problem from Line 1 closed      Line2: Application 2 stopped     Line4: Application 2 was restarted #problem from Line 2 closed  To do this you need to tag these related events as, for example, "Application 1" and "Application 2". That can be done by applying a regular expression to the log line to extract the tag value. Then, when events are created, they are tagged "Application 1" and "Application 2" respectively and problem can be matched to the resolution.
zh-cn	#### 工作原理  在日志监控中，可能会遇到下面类似地输出：      Line1: 应用1停止      Line2: 应用2停止      Line3: 应用1重启      Line4: 应用2重启  事件关联地想法是将从“Line1”的问题事件到“Line3”的恢复事件，从“Line2”的问题事件到“Line4”的恢复事件相匹配，并能逐个关闭这些问题：      Line1: 应用1停止      Line3: 应用1重启  #问题来自于Line1关闭      Line2: 应用2停止      Line4: 应用2重启  #问题来自于Line2关闭  为此，需要通过标签将这些事件相关联，例如，可以标识为“应用1”和“应用2”。这个过程也可以将正则表达式应用于日志中来提取标签的值。然后，当事件创建时，他们分别给标识为“应用1”和“应用2”，并且问题可以与解决方法相匹配。

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

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

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

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

en-us	#### Hysteresis  Sometimes an interval is needed between problem and recovery states, rather than a simple threshold. For example, if we want to define a trigger that reports a problem when server room temperature goes above 20°C and we want it to stay in the problem state until the temperature drops below 15°C, a simple trigger threshold at 20°C will not be enough.  Instead, we need to define a trigger expression for the problem event first (temperature above 20°C). Then we need to define an additional recovery condition (temperature below 15°C). This is done by defining an additional *Recovery expression* parameter when [defining](/manual/config/triggers/trigger) a trigger.  In this case, problem recovery will take place in two steps:  -   First, the problem expression (temperature above 20°C) will have to     evaluate to FALSE -   Second, the recovery expression (temperature below 15°C) will have     to evaluate to TRUE  The recovery expression will be evaluated only when the problem event is resolved first.  ::: notewarning The recovery expression being TRUE alone does not resolve a problem if the problem expression is still TRUE! :::
zh-cn	#### 滞后  有时，问题和恢复状态之间需要一个间隔，而不是一个简单的阈值。例如，如果我们想定义一个触发器，它在服务器机房温度高于20°C时报告问题，并且我们想让它在温度低于15°C之前保持问题状态，那么简单的触发器阈值为20°C是不够的。  相反，我们需要首先为问题事件定义一个触发器表达式(温度高于20°C)。然后我们需要定义一个额外的恢复条件(温度低于15°C)。这是通过在[defining定义](/manual/config/triggers/trigger)触发器时定义一个额外的*Recovery expression 恢复表达式*参数来实现的。  在这种情况下，问题恢复将分两步进行：  - 首先，问题表达式（温度高于 20°C）评估为 FALSE - 其次，恢复表达式（温度低于 15°C）评估为 TRUE  仅当问题事件为 先解决。  ::: notewarning 当问题表达式为TRUE时，即使恢复表达式为TRUE也不会恢复。 :::

en-us	#### ICMP pings  Zabbix uses external utility **fping** for processing of ICMP pings.  The utility is not part of Zabbix distribution and has to be additionally installed. If the utility is missing, has wrong permissions or its location does not match the location set in the Zabbix server/proxy configuration file ('FpingLocation' parameter), ICMP pings (**icmpping**, **icmppingloss**, **icmppingsec**) will not be processed.  See also: [known issues](/manual/installation/known_issues#simple_checks)  **fping** must be executable by the user Zabbix daemons run as and setuid root. Run these commands as user **root** in order to set up correct permissions:      shell> chown root:zabbix /usr/sbin/fping     shell> chmod 4710 /usr/sbin/fping  After performing the two commands above check ownership of the **fping** executable. In some cases the ownership can be reset by executing the chmod command.  Also check, if user zabbix belongs to group zabbix by running:      shell> groups zabbix  and if it's not add by issuing:      shell> usermod -a -G zabbix zabbix  Defaults, limits and description of values for ICMP check parameters:  |Parameter|Unit|Description|Fping's flag|Defaults set by|<|Allowed limits<br>by Zabbix|<| |--|--|--------|-|--|--|--|--| |||||**fping**|**Zabbix**|**min**|**max**| |packets|number|number of request packets to a target|-C||3|1|10000| |interval|milliseconds|time to wait between successive packets|-p|1000||20|unlimited| |size|bytes|packet size in bytes<br>56 bytes on x86, 68 bytes on x86_64|-b|56 or 68||24|65507| |timeout|milliseconds|**fping v3.x** - timeout to wait after last packet sent, affected by *-C* flag<br> **fping v4.x** - individual timeout for each packet|-t|**fping v3.x** - 500<br>**fping v4.x** - inherited from *-p* flag, but not more than 2000||50|unlimited|  In addition Zabbix uses fping options *-i interval ms* (do not mix up with the item parameter *interval* mentioned in the table above, which corresponds to fping option *-p*) and *-S source IP address* (or *-I* in older fping versions). Those options are auto-detected by running checks with different option combinations. Zabbix tries to detect the minimal value in milliseconds that fping allows to use with *-i* by trying 3 values: 0, 1 and 10. The value that first succeeds is then used for subsequent ICMP checks. This process is done by each [ICMP pinger](/manual/concepts/server#server_process_types) process individually.  Auto-detected fping options are invalidated every hour and detected again on the next attempt to perform ICMP check. Set DebugLevel>=4 in order to view details of this process in the server or proxy log file.  ::: notewarning Warning: fping defaults can differ depending on platform and version - if in doubt, check fping documentation. :::  Zabbix writes IP addresses to be checked by any of three *icmpping\** keys to a temporary file, which is then passed to **fping**. If items have different key parameters, only ones with identical key parameters are written to a single file.\ All IP addresses written to the single file will be checked by fping in parallel, so Zabbix icmp pinger process will spend fixed amount of time disregarding the number of IP addresses in the file.
zh-cn	#### ICMP pings  Zabbix 使用外部程序 **fping** 来处理 ICMP pings。  Fping不包含在Zabbix的发行版中，您需要另外安装。 如果程序未安装、程序权限错误或者程序路径与配置文件中('FpingLocation' 参数)定义的不匹配，则不会处理ICMP ping (**icmpping**, **icmppingloss**, **icmppingsec**)。  另请参考: [已知问题](/manual/installation/known_issues#simple_checks)  **fping** 必须可以被 Zabbix 守护进程以 root 身份执行，需要设置 setuid 权限。为设置正确的权限，请以 **root** 身份来执行这些命令:      shell> chown root:zabbix /usr/sbin/fping     shell> chmod 4710 /usr/sbin/fping  执行以上两句命令，然后检查**fping**的权限。在某些情况下，可以通过执行chmod命令来重置所有权。  还要检查一下，如果用户zabbix属于zabbix组，则运行:      shell> groups zabbix  如果没有添加成功，通过如下命令解决:      shell> usermod -a -G zabbix zabbix  ICMP检测参数的默认值、限制和以及数值的描述：  |参数|单位|描述|Fping 的参数|Fping 默认设置|<| Zabbix <br>允许的限制|<| |---------|----|-----------|------------|---------------|-|---------------------------|-| |||||**fping**|**Zabbix**|**min**|**max**| |packets|计数|发送到目标的请求报文数|-C||3|1|10000| |interval|毫秒|连续数据包之间的间隔时间|-p|1000||20|不限制| |size|byte|用字节描述的包大小<br>x86 架构是 56 byte, x86_64架构是68 byte|-b|56 or 68||24|65507| |timeout|毫秒|**fping v3.x** - 上次发送数据包后等待超时时间，影响 *-C* 参数<br> **fping v4.x** - 每个包的单独超时时间|-t|**fping v3.x** - 500<br>**fping v4.x** - 继承 *-p* 参数的值，但是不能超过 2000||50|不限制|  此外，Zabbix 使用 fping 参数 *-i interval ms* (不要和上边表格中的监控项参数 *interval* 混淆，它对应 fping 的 *-p* 参数)  和  *-S source IP address* (或者旧版本的 *-I* i)。这些参数通过使用不同的参数组合运行自动检测。 Zabbix尝试检测fping允许对*-i*参数一起使用的最小值(以毫秒为单位)，尝试 3个值: 0, 1 和 10。第一个成功的值将用于后续的ICMP检查. 这个过程是由每个 [ICMP pinger](/manual/concepts/server#server_process_types) 进程单独完成的。  从Zabbix 5.0.4版本开始，fping 自动检测的参数每小时都会失效，并且在下一次尝试执行ICMP检查时再次加载。设置 DebugLevel>=4 可以在服务器或代理日志文件中查看该进程的详细信息。  ::: notewarning 警告: 根据平台和版本的不同，fping的默认值也会有所不同 - 如有疑问, 请参考fping文档。 :::  Zabbix将三个 *icmpping\** 键值中任何一个IP地址写入一个临时文件中，然后传递给 **fping**。如果监控项有不同的键值参数，则只有具有相同键值参数的监控项IP才会被写入相同的单个文件。\ 所有写入到单个文件的IP地址将被fping并行检查，因此Zabbix icmp pinger进程将花费固定的时间来处理监控项，而不管文件中的IP地址数量。

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

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

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

en-us	# > Icon map object  The following objects are directly related to the `iconmap` API.
zh-cn	# > 图标映射对象  以下是和 `iconmap` API 直接相关的对象。

en-us	# Icon map  This class is designed to work with icon maps.  Object references:\  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Icon mapping](/manual/api/reference/iconmap/object#icon_mapping)  Available methods:\  -   [iconmap.create](/manual/api/reference/iconmap/create) - create new     icon maps -   [iconmap.delete](/manual/api/reference/iconmap/delete) - delete icon     maps -   [iconmap.get](/manual/api/reference/iconmap/get) - retrieve icon     maps -   [iconmap.update](/manual/api/reference/iconmap/update) - update icon     maps
zh-cn	# 图标映射  这个类被设计用来处理图标映射。  对象引用：\  -   [Icon map](/manual/api/reference/iconmap/object#icon_map) -   [Icon mapping](/manual/api/reference/iconmap/object#icon_mapping)  可用的方法：\  -   [iconmap.create](/manual/api/reference/iconmap/create) - 创建新的图标映射 -   [iconmap.delete](/manual/api/reference/iconmap/delete) - 删除图标映射 -   [iconmap.get](/manual/api/reference/iconmap/get) - 获取图标映射 -   [iconmap.update](/manual/api/reference/iconmap/update) - 更新图标映射

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

en-us	##### If installed as package  Zabbix agent runs as a daemon process. The agent can be started by executing:      shell> service zabbix-agent start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-agent start  Similarly, for stopping/restarting/viewing status of Zabbix agent, use the following commands:      shell> service zabbix-agent stop     shell> service zabbix-agent restart     shell> service zabbix-agent status
zh-cn	 ##### 通过二进制包安装的组件  Zabbix agent 进程以守护进程（Deamon）运行。Zabbix agent 的启动可以通过执行以下命令来完成：     shell> service zabbix-agent start  上述命令在大多数的 GNU/Linux 系统下都可以正常完成。如果是其他系统，你可能要尝试以下命令来运行：     shell> /etc/init.d/zabbix-agent start  类似的，停止、重启、查看状态，则需要执行以下命令：     shell> service zabbix-agent stop    shell> service zabbix-agent restart    shell> service zabbix-agent status

en-us	##### If installed as package  Zabbix proxy runs as a daemon process. The proxy can be started by executing:      shell> service zabbix-proxy start  This will work on most of GNU/Linux systems. On other systems you may need to run:      shell> /etc/init.d/zabbix-proxy start  Similarly, for stopping/restarting/viewing status of Zabbix proxy, use the following commands:      shell> service zabbix-proxy stop     shell> service zabbix-proxy restart     shell> service zabbix-proxy status
zh-cn	#### 如果通过包安装  Zabbix proxy 进程以守护进程（Deamon）运行。Zabbix proxy的启动可以通过执行以下命令来完成：      shell> service zabbix-proxy start  上述命令在大多数的 GNU/Linux系统下都可以正常完成。如果是其他系统，你可能要尝试以下命令来运行：      shell> /etc/init.d/zabbix-proxy start  类似的，Zabbix proxy 的停止、重启、查看状态，则需要执行以下命令：      shell> service zabbix-proxy stop     shell> service zabbix-proxy restart     shell> service zabbix-proxy status

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

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

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

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

en-us	# Image  This class is designed to work with images.  Object references:\  -   [Image](/manual/api/reference/image/object#image)  Available methods:\  -   [image.create](/manual/api/reference/image/create) - create new     images -   [image.delete](/manual/api/reference/image/delete) - delete images -   [image.get](/manual/api/reference/image/get) - retrieve images -   [image.update](/manual/api/reference/image/update) - update images
zh-cn	# 图像  此类旨在处理图像。  对象引用：  -   [图像](/manual/api/reference/image/object#图像)  可用方法：  -   [创建](/manual/api/reference/image/create) - 创建新图像 -   [删除](/manual/api/reference/image/delete) - 删除图像 -   [获取](/manual/api/reference/image/get) - 获取图像 -   [更新](/manual/api/reference/image/update) - 更新图像

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

en-us	#### Important notes  -   Database monitoring items will become unsupported if no *odbc poller* processes are started in the server or proxy configuration. To activate ODBC pollers, set *StartODBCPollers* parameter in Zabbix [server](/manual/appendix/config/zabbix_server) configuration file or, for checks performed by proxy, in Zabbix [proxy](/manual/appendix/config/zabbix_proxy) configuration file. -   Zabbix does not limit the query execution time. It is up to the user     to choose queries that can be executed in a reasonable amount of     time. -   The [Timeout](/manual/appendix/config/zabbix_server) parameter value     from Zabbix server is used as the ODBC login timeout (note that     depending on ODBC drivers the login timeout setting might be     ignored). -   The SQL command must return a result set like any query with     `select ...`. The query syntax will depend on the RDBMS which will     process them. The syntax of request to a storage procedure must be     started with `call` keyword.
zh-cn	#### 注意事项  -   Zabbix不限制查询执行时间。 用户可以选择在合理时间内执行的查询。 -   Zabbix server的 [Timeout](/manual/appendix/config/zabbix_server)参数值也用作于ODBC登陆超时时间（请注意，根据ODBC驱动，登录超时设置可能会被忽略）。 -   查询只能返回一个值。 -   如果查询返回多个列，则只读取第一列。 -   如果查询返回多行，则只读取第一行。 -   SQL命令必须以`select`开头。 -   SQL命令不能包含任何换行符。 -   另请参阅ODBC检查的 [已知问题](/manual/installation/known_issues#odbc_checks)

en-us	#### Important notes  -   If more than one user macro with context exists, Zabbix will try to     match the simple context macros first and then context macros with     regular expressions in an undefined order.  ::: notewarning Do not create different context macros matching the same string to avoid undefined behavior. :::  -   If a macro with its context is not found on host, linked templates     or globally, then the macro without context is searched for. -   Only low-level discovery macros are supported in the context. Any     other macros are ignored and treated as plain text.  Technically, macro context is specified using rules similar to [item key](/manual/config/items/item/key) parameters, except macro context is not parsed as several parameters if there is a `,` character:  -   Macro context must be quoted with `"` if the context contains a `}`     character or starts with a `"` character. Quotes inside quoted     context must be escaped with the `\` character. -   The `\` character itself is not escaped, which means it's impossible     to have a quoted context ending with the `\` character - the macro     {$MACRO:"a:\\b\\c\\"} is invalid. -   The leading spaces in context are ignored, the trailing spaces are     not:     -   For example {$MACRO:A} is the same as {$MACRO: A}, but not         {$MACRO:A }. -   All spaces before leading quotes and after trailing quotes are     ignored, but all spaces inside quotes are not:     -   Macros {$MACRO:"A"}, {$MACRO: "A"}, {$MACRO:"A" } and {$MACRO:         "A" } are the same, but macros {$MACRO:"A"} and {$MACRO:" A "}         are not.  The following macros are all equivalent, because they have the same context: {$MACRO:A}, {$MACRO: A} and {$MACRO:"A"}. This is in contrast with item keys, where 'key\[a\]', 'key\[ a\]' and 'key\["a"\]' are the same semantically, but different for uniqueness purposes.
zh-cn	#### 重要笔记  - 如果存在多个具有上下文的用户宏，Zabbix 将尝试首先匹配简单的上下文宏，然后匹配上下文宏未定义顺序的正则表达式。  ::: notewarning 不要创建不同的上下文宏匹配相同的字符串以避免未定义的行为。 :::  - 如果在主机上找不到带有上下文的宏，则链接模板或全局，然后搜索没有上下文的宏。 - 上下文中仅支持低级发现宏。任何其他宏被忽略并被视为纯文本。  从技术上讲，宏上下文是使用类似于 [item key](/manual/config/items/item/key) 参数，除了宏上下文是如果有 `,` 字符，则不被解析为多个参数：  - 如果上下文包含 `}`，则必须用 `"` 引用宏上下文字符或以 `"` 字符开头。引号内的引号context 必须用 `\` 字符转义。 - `\` 字符本身没有被转义，这意味着它是不可能的有一个以 `\` 字符结尾的引用上下文 - 宏     {$MACRO:"a:\\b\\c\\"} 无效。 - 上下文中的前导空格被忽略，尾随空格是不是：     - 例如 {$MACRO:A} 与 {$MACRO:A} 相同，但不同{$宏：A}。 - 前导引号和尾随引号后的所有空格都是忽略，但引号内的所有空格都不是：     - 宏 {$MACRO:"A"}、{$MACRO:"A"}、{$MACRO:"A"} 和 {$MACRO:"A" } 相同，但宏{$MACRO:"A"} 和 {$MACRO:"A"}不是。  以下宏都是等价的，因为它们具有相同的上下文：{$MACRO:A}、{$MACRO:A} 和 {$MACRO:"A"}。这是相反的带有项目键，其中 'key\[a\]'、'key\[a\]' 和 'key\["a"\]' 是语义上相同，但出于唯一性目的而不同。

en-us	 ### Important notes  - Make sure to back up the database before the upgrade. - If the database uses partitions, contact the DB administrator or Zabbix support team for help. - Stopping Zabbix server for the time of the upgrade is strongly recommended. However, if absolutely necessary, there is a way to perform an upgrade while the server is running (only for MySQL, MariaDB and PostgreSQL without TimescaleDB). - CSV files can be removed after a successful upgrade to primary keys. - Optionally, Zabbix frontend may be switched to [maintenance mode](/manual/web_interface/maintenance_mode). - Upgrade to primary keys should be done after upgrading Zabbix server to 6.0. - On proxy, history tables that are not used can be upgraded by executing history_pk_prepare.sql.
zh-cn	#### 重要提示  - 确保在升级前备份数据库。 - 如果数据库使用分区，请联系数据库管理员或 Zabbix 支持团队寻求帮助。 - 强烈建议在升级时停止 Zabbix 服务器。 但是，如果绝对必要，有一种方法可以在服务器运行时执行升级（仅适用于没有 TimescaleDB 的 MySQL、MariaDB 和 PostgreSQL）。 - 成功升级到主键后，可以删除 CSV 文件。 - 可选地，Zabbix 前端可以切换到[维护模式](/manual/web_interface/maintenance_mode)。 - 升级到主键应该在将 Zabbix 服务器升级到 6.0 之后完成。 - 在代理上，未使用的历史表可以通过执行 history_pk_prepare.sql 进行升级。

en-us	#### Important rules  -   A whitelist without a deny rule is only allowed for system.run\[\*\]     items. For all other items, AllowKey parameters are not allowed     without a DenyKey parameter; in this case Zabbix agent **will not     start** with only AllowKey parameters. -   The order matters. The specified parameters are checked one by one     according to their appearance order in the configuration file:     -   As soon as an item key matches an allow/deny rule, the item is         either allowed or denied; and rule checking stops. So if an item         matches both an allow rule and a deny rule, the result will         depend on which rule comes first.     -   The order affects also EnableRemoteCommands parameter (if used). -   Unlimited numbers of AllowKey/DenyKey parameters is supported. -   AllowKey, DenyKey rules do not affect HostnameItem,     HostMetadataItem, HostInterfaceItem configuration parameters. -   Key pattern is a wildcard expression where the wildcard (\*)     character matches any number of any characters in certain position.     It might be used in both the key name and parameters. -   If a specific item key is disallowed in the agent configuration, the     item will be reported as unsupported (no hint is given as to the     reason); -   Zabbix agent with --print (-p) command line option will not show     keys that are not allowed by configuration; -   Zabbix agent with --test (-t) command line option will return     "Unsupported item key." status for keys that are not allowed by     configuration; -   Denied remote commands will not be logged in the agent log (if     LogRemoteCommands=1).
zh-cn	#### 重要规则  -   没有拒绝规则的白名单只允许 system.run\[\*\]监控项。对于所有其它监控项，如果没有DenyKey参数，则不允许使用AllowKey 参数； 这种只有AllowKey参数情况下， Zabbix agent **将不会**启动。 -   顺序很重要。指定参数在配置文件中按其出现顺序逐一检查:     -   一旦监控项键值与允许/拒绝规则匹配，该项即被允许或拒绝；并且规则检查停止。因此，如果一个项同时满足允许规则和拒绝规则，那么结果取决于最先匹配到的那个规则。     -   顺序还影响EnableRemoteCommands参数（如果使用）。 -   支持无限数量的AllowKey/DenyKey参数。 -   -   AllowKey、DenyKey规则不影响HostnameItem、HostMetadataItem、HostInterfaceItem配置参数。 -   -   键模式是一个通配符表达式，其中通配符 (\*)与特定位置的任意数量的任意字符匹配。它可以用于关键字名称和参数。 -   如果在agent配置中不允许某个特定的监控项，则该监控项将被报告为不受支持（没有给出有关原因的提示）; -   Zabbix agent命令行使用带--print（-p）选项将不显示配置为不允许的键值; -   Zabbix agent命令行使用有--test（-t）选项将会显示配置不允许的键值为"Unsupported item key"状态; -   拒绝的远程命令不会记录在agent日志中（如果LogRemoteCommands=1）。

en-us	##### Importing data  Import initial schema:      # cat /usr/share/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix  For proxy with PostgreSQL (or SQLite):      # cat /usr/share/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix     # cat /usr/share/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db
zh-cn	#####导入数据  导入初始schema：    · # cat /usr/share/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix  对于 PostgreSQL（或 SQLite）的代理：    · # cat /usr/share/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix   · # cat /usr/share/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db

en-us	#### Importing data with Timescale DB  With TimescaleDB, in addition to the import command for PostgreSQL, also run:      # cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: notewarning TimescaleDB is supported with Zabbix server only. :::
zh-cn	#### 使用时序数据库导入数据  使用 TimescaleDB，除了 PostgreSQL 的导入命令外，还需运行：    · # cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix  ::: notewarning 只有 Zabbix 服务器支持 TimescaleDB。 ::::

en-us	##### In accepting-side log:      ...failed to accept an incoming connection: from 127.0.0.1: support for TLS was not compiled in
zh-cn	##### 在接受连接端的日志中有如下显示：      ...failed to accept an incoming connection: from 127.0.0.1: support for TLS was not compiled in

en-us	##### In connecting-side log:  Linux:      ...In zbx_tls_init_child()     ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK test sender"     ...End of zbx_tls_connect():FAIL error:'connection closed by peer'     ...send value error: TCP successful, cannot establish TLS to [[localhost]:10051]: connection closed by peer  Windows:      ...OpenSSL library (version OpenSSL 1.1.1a  20 Nov 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK test sender"     ...zbx_psk_client_cb() requested PSK identity "PSK test sender"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() I/O error: [0x00000000] The operation completed successfully.'     ...send value error: TCP successful, cannot establish TLS to [[192.168.1.2]:10051]: SSL_connect() I/O error: [0x00000000] The operation completed successfully.
zh-cn	##### 在发起连接方的日志中有如下显示：  Linux:      ...In zbx_tls_init_child()     ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK test sender"     ...End of zbx_tls_connect():FAIL error:'connection closed by peer'     ...send value error: TCP successful, cannot establish TLS to [[localhost]:10051]: connection closed by peer  Windows:      ...OpenSSL library (version OpenSSL 1.1.1a  20 Nov 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK test sender"     ...zbx_psk_client_cb() requested PSK identity "PSK test sender"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() I/O error: [0x00000000] The operation completed successfully.'     ...send value error: TCP successful, cannot establish TLS to [[192.168.1.2]:10051]: SSL_connect() I/O error: [0x00000000] The operation completed successfully.

en-us	#### Indexed macros  The indexed macro syntax of {MACRO**<1-9>**} works only in the context of **trigger expressions**. It can be used to reference hosts or functions in the order in which they appear in the expression. Macros like {HOST.IP1}, {HOST.IP2}, {HOST.IP3} will resolve to the IP of the first, second, and third host in the trigger expression (providing the trigger expression contains those hosts). Macros like {FUNCTION.VALUE1}, {FUNCTION.VALUE2}, {FUNCTION.VALUE3} will resolve to the value of the first, second, and third item-based function in the trigger expression at the time of the event (providing the trigger expression contains those functions).  Additionally the {HOST.HOST<1-9>} macro is also supported within the `{?func(/host/key,param)}` expression macro in **graph names**. For example, `{?func(/{HOST.HOST2}/key,param)}` in the graph name will refer to the host of the second item in the graph.  ::: notewarning Indexed macros will not resolve in any other context, except the two cases mentioned here. For other contexts, use macros **without** index (i. e.{HOST.HOST}, {HOST.IP}, etc) instead. :::
zh-cn	 #### 索引宏   宏索引{MACRO<1-9>}语法仅限于**触发器表达式的上下文**。它能用于按顺序引用表达式中包含的设备。例如：在表达式中包含了设备1，设备2，设备3，那么宏{HOST.IP1},{HOST.IP2}, {HOST.IP3}将分别引用设备1，设备2，设备3的IP地址信息。 在提供触发器表达式包含这些函数时，宏{FUNCTION.VALUE1}，{FUNCTION.VALUE2}，{FUNCTION.VALUE3} 将解析为事件发生时触发器表达式中第一个、第二个和第三个基于监控项函数的值。  另外，可以在**图形名称**中使用宏`{?func(/host/key,param)}` ，同时再叠加使用宏{HOST.HOST<1-9>}。例如，图形名称中的宏`{{HOST.HOST2}:key.func()}`代表引用图形中的第二个监控项。  ::: notewarning 除了这里提到的两种情况外，索引宏不会在任何其他场境中解析。对于其他场景可以使用**不带**索引的宏。(即{HOST.HOST}，{HOST.IP}，等) ::: 

en-us	#### Index lookup caching  When a dynamic index item is requested, Zabbix retrieves and caches whole SNMP table under base OID for index, even if a match would be found sooner. This is done in case another item would refer to the same base OID later - Zabbix would look up index in the cache, instead of querying the monitored host again. Note that each poller process uses separate cache.  In all subsequent value retrieval operations only the found index is verified. If it has not changed, value is requested. If it has changed, cache is rebuilt - each poller that encounters a changed index walks the index SNMP table again.
zh-cn	#### 索引查找缓存  当请求动态索引项时，Zabbix检索并缓存基础OID下的整个SNMP表用于索引（即使早发现了匹配）。这是为了在另一个监控项稍后引用相同的基础OID -Zabbix将在缓存中查找索引，而不是再次查询被监视的主机。请注意，每个轮询器进程使用单独的缓存。  在所有随后的值检索操作中，仅验证找到的索引。如果没有改变，则请求结果值；如果已更改，则会重建高速缓存- 遇到已更改索引的每个轮询器再次建立SNMP索引表。

en-us	##### Installation  After this is done use the following command to install Zabbix agent as Windows service:      C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i  Now you should be able to configure "Zabbix agent" service normally as any other Windows service.  See [more details](/manual/appendix/install/windows_agent#installing_agent_as_windows_service) on installing and running Zabbix agent on Windows.
zh-cn	 ##### 安装  完成此操作后，使用以下命令将 Zabbix agent 安装为 Windows 服务：     C:\> c:\zabbix\zabbix_agentd.exe -c c:\zabbix\zabbix_agentd.conf -i  现在您可以像任何其他 Windows 服务一样配置“Zabbix agent”服务。  有关在 Windows 上安装和运行 Zabbix agent 的详细信息，请查阅[于此](https://www.zabbix.com/documentation/5.0/zh/manual/appendix/install/windows_agent#installing-agent-as-windows-service)。

en-us	##### Installation  See the [package installation](/manual/installation/install_from_packages) section for instructions on how to install Zabbix agent as package.  Alternatively see instructions for [manual installation](/manual/installation/install#installing_zabbix_daemons) if you do not want to use packages.  ::: noteimportant In general, 32bit Zabbix agents will work on 64bit systems, but may fail in some cases. :::
zh-cn	##### 安装  有关通过二进制包安装 Zabbix agent 的详细信息，请查阅  [以二进制包安装](https://www.zabbix.com/documentation/5.0/zh/manual/installation/install_from_packages)  章节。  此外，如果您不想使用二进制包，请查阅[以源码包安装](https://www.zabbix.com/documentation/5.0/zh/manual/installation/install#installing-zabbix-daemons)的说明。  ::: noteimportant 通常，32位 Zabbix agent 可以在 64 位系统上运行，但在某些情况下可能会失败。 :::

en-us	#### Install  If installing Zabbix from sources, download the configuration file and place it under conf/ in the webserver HTML documents subdirectory where you copied Zabbix PHP files to.  ![](../../../assets/en/manual/installation/install_6.png){width="550"}  ![](../../../assets/en/manual/installation/saving_zabbix_conf.png){width="350"}  ::: notetip Providing the webserver user has write access to conf/ directory the configuration file would be saved automatically and it would be possible to proceed to the next step right away. :::  Finish the installation.  ![](../../../assets/en/manual/installation/install_7.png){width="550"}
zh-cn	#### 安装  若采用从源代码安装 Zabbix，请下载配置文件并将其 Zabbix PHP 文件复制到所在网站服务器 HTML 文件子目录中的 conf/ 下。  ![](../../../assets/en/manual/installation/install_6.png){width="550"}  ![](../../../assets/en/manual/installation/saving_zabbix_conf.png){width="350"}  ::: notetip 若网站服务器用户对 conf/ 目录具有写入权限，则配置文件将自动保存，并且可以立即执行下一步。 :::  完成安装。  ![](../../../assets/en/manual/installation/install_7.png){width="550"}

en-us	#### Installing agent as Windows service  To install a single instance of Zabbix agent with the default configuration file `c:\zabbix_agentd.conf`:      zabbix_agentd.exe --install  ::: noteimportant On a 64-bit system, a 64-bit Zabbix agent version is required for all checks related to running 64-bit processes to work correctly. :::  If you wish to use a configuration file other than `c:\zabbix_agentd.conf`, you should use the following command for service installation:      zabbix_agentd.exe --config <your_configuration_file> --install  A full path to the configuration file should be specified.  Multiple instances of Zabbix agent can be installed as services like this:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --install --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --install --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents  The installed service should now be visible in Control Panel.
zh-cn	#### 安装 agent 并注册 Windows 服务  使用默认配置文件安装 Zabbix agent的单个实例  `c:\zabbix_agentd.conf`:      zabbix_agentd.exe --install  ::: noteimportant 在 64 位操作系统上 , 务必检查 64 位的 Zabbix agent 版本与运行 64 位进程相关的一切，以便它可以正确的工作。 :::  如果您希望使用除`c:\zabbix_agentd.conf`以外的配置, 您应该使用以下命令进行服务安装:      zabbix_agentd.exe --config <your_configuration_file> --install  应指定配置文件的完整路径。.  Zabbix agent的多个实例可以这样安装服务:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --install --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --install --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents  安装的服务现在应该在"控制面板"中可见。

en-us	##### Installing Elasticsearch and creating mapping  Final two steps of making things work are installing Elasticsearch itself and creating mapping process.  To install Elasticsearch please refer to [Elasticsearch installation guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html).  ::: noteclassic Mapping is a data structure in Elasticsearch (similar to a table in a database). Mapping for all history data types is available here: `database/elasticsearch/elasticsearch.map`. :::  ::: notewarning Creating mapping is mandatory. Some functionality will be broken if mapping is not created according to the instruction. :::  To create mapping for `text` type send the following request to Elasticsearch:  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/text \  -H 'content-type:application/json' \  -d '{    "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"          }       }    } }' ```  Similar request is required to be executed for `Character` and `Log` history values mapping creation with corresponding type correction.  ::: noteclassic To work with Elasticsearch please refer to [Requirement page](/manual/installation/requirements#server) for additional information. :::  ::: noteclassic [Housekeeper](/manual/installation/requirements?s[]=housekeeper) is not deleting any data from Elasticsearch. :::
zh-cn	##### 安装 Elasticsearch 并创建映射  安装Elasticsearchit及创建映射是整个安装过程的最后两步了。   如何安装 Elasticsearch，请参阅[Elasticsearch installation guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup.html).  ::: noteclassic 映射是 Elasticsearch 中的一种数据结构（类似于数据库中的表）。所有历史数据类型的映射都可用: `database/elasticsearch/elasticsearch.map`. :::  ::: notewarning 创建映射是必需的。如未根据指令创建映射，某些功能将不可用。 ::: 要为`text`类型创建映射，请将以下请求发送到Elasticsearch  ``` {.java} curl -X PUT \  http://your-elasticsearch.here:9200/text \  -H 'content-type:application/json' \  -d '{    "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"          }       }    } }' ``` 对于 `Character` 和 `Log`历史值映射创建，需要执行类似的请求，并将相应的类型进行修改  ::: noteclassic 要使用Elasticsearch，请参阅[Requirement page](/manual/installation/requirements#server) 以获取更多信息. :::  ::: noteclassic [Housekeeper](/manual/installation/requirements?s[]=housekeeper)不会从 Elasticsearch 中删除任何数据。 :::

en-us	##### Installing frontend  Please see [Web interface installation](/manual/installation/frontend) page for information about Zabbix frontend installation wizard.
zh-cn	 ##### 安装前端  关于 Zabbix 前端的安装，请参考[网页界面安装](/manual/installation/frontend)页面的信息。

en-us	#### Installing locales  To list all installed languages, run:      locale -a  If some languages that are needed are not listed, open the */etc/locale.gen* file and uncomment the required locales. Since Zabbix uses UTF-8 encoding, you need to select locales with UTF-8 charset.  Now run:      locale-gen   Restart the web server.  The locales should now be installed. It may be required to reload Zabbix frontend page in browser using Ctrl + F5 for new languages to appear.
zh-cn	#### 安装区域配置  要列出所有已安装的语言，请运行:      locale -a  如果未列出所需的某些语言，请打开*/etc/locale.gen* 文件并取消注释所需的语言环境。由于 Zabbix 使用 UTF-8 编码，因此您需要选择具有 UTF-8 字符集的区域设置。  运行:      locale-gen   重新启动web服务.  安装完区域设置后。可能需要用Ctrl + F5在浏览器中重新加载Zabbix前端页面才能显示新语言。

en-us	#### Installing MIB files  On Debian-based systems:      # apt install snmp-mibs-downloader     # download-mibs  On RedHat-based systems:      # dnf install net-snmp-libs
zh-cn	#### 安装 MIB 文件  在基于 Debian 的系统上：      # apt install snmp-mibs-downloader     # download-mibs  在基于 RedHat 的系统上：      # dnf install net-snmp-libs

en-us	#### Installing OpenSSL development libraries  1\. Download 32 and 64 bit builds from <https://curl.se/windows/>\ 2. Extract files into *c:\\dev\\openssl32* and *c:\\dev\\openssl* directories accordingly.\ 3. After that remove extracted *\*.dll.a* (dll call wrapper libraries) as MinGW prioritizes them before static libraries.
zh-cn	#### 安装OpenSSL开发库  1\. 从 <https://curl.se/windows/>\ 下载32和64位版本\ 2. 相应地将文件提取到*c:\\dev\\openssl32* 和*c:\\dev\\openssl*。\ 3. 然后删除提取的*\*.dll.a* (dll call wrapper libraries) ，因为MinGW在静态库前会优先考虑它们。

en-us	#### - Installing Zabbix daemons
zh-cn	 #### - 安装Zabbix守护进程

en-us	#### Installing Zabbix  If installing Zabbix directly from [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), translation files should be generated manually. To generate translation files, run:      make gettext     locale/make_mo.sh  This step is not needed when installing Zabbix from packages or source tar.gz files.
zh-cn	#### 安装 Zabbix  如果直接从 [Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse), 安装Zabbix，则应手动生成翻译文件，运行:      make gettext     locale/make_mo.sh  从软件包或 源码tar.gz文件 安装 Zabbix 时不需要此步骤

en-us	#### - Installing Zabbix web interface
zh-cn	 #### - 安装 Zabbix 网页界面

en-us	### Integer history  The integer 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|integer|Received value.|
zh-cn	 ### 整数型历史数据  整数型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |clock|timestamp|收到数值的时间。| |itemid|string|相关监控项的 ID。| |ns|integer|收到数值时的纳秒数。| |value|integer|收到的数值。|

en-us	#### Internal event actions  The following conditions can be set for actions based on internal events:  |Condition type|Supported operators|Description| |--|--|------| |*Event type*|equals|**Item in "not supported" state** - matches events where an item goes from a 'normal' to 'not supported' state.<br>**Low-level discovery rule in "not supported" state** - matches events where a low-level discovery rule goes from a 'normal' to 'not supported' state.<br>**Trigger in "unknown" state** - matches events where a trigger goes from a 'normal' to 'unknown' state.| |*Host group*|equals<br>does not equal|Specify host groups or host groups to exclude.<br>**equals** - event belongs to this host group.<br>**does not equal** - event does not belong to this host group.| |*Tag name*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag or event tag to exclude.<br>**equals** - event has this tag.<br>**does not equal** - event does not have this tag.<br>**contains** - event has a tag containing this string.<br>**does not contain** - event does not have a tag containing this string.| |*Tag value*|equals<br>does not equal<br>contains<br>does not contain|Specify event tag and value combination or tag and value combination to exclude.<br>**equals** - event has this tag and value.<br>**does not equal** - event does not have this tag and value.<br>**contains** - event has a tag and value containing these strings.<br>**does not contain** - event does not have a tag and value containing these strings.| |*Template*|equals<br>does not equal|Specify templates or templates to exclude.<br>**equals** - event belongs to an item/trigger/low-level discovery rule inherited from this template.<br>**does not equal** - event does not belong to an item/trigger/low-level discovery rule inherited from this template.| |*Host*|equals<br>does not equal|Specify hosts or hosts to exclude.<br>**equals** - event belongs to this host.<br>**does not equal** - event does not belong to this host.|
zh-cn	#### 内部事件动作  可以为基于内部事件的动作设置以下条件:  |条件类型|支持的操作符|说明| |--------------|-------------------|-----------| |*事件类型*|等于|**处于“不支持”状态的监控项** - 匹配监控项从'正常' 变为 '不支持'状态的事件<br>**处于“不支持”状态的底层自动发现规则** - 匹配底层自动发现规则从'正常' 变为 '不支持'状态的事件<br>**处于“未知”状态的触发器** - 匹配触发器从'正常' 变为 '未知'状态的事件| |*主机组*|等于<br>不等于|主机组或要排除的主机组<br>**等于** - 属于该主机组的事件<br>**不等于** - 不属于该主机组的事件| |*标签名称*|等于<br>不等于<br>包含<br>不包含|标签名称或者要排除的标签名称<br>**等于** - 具备该标签的事件<br>**不等于** - 不具备该标签的事件<br>**包含** - 标签名称中包含该字符串的事件<br>**不包含** - 标签名称中不包含该字符串的事件| |*标签值*|等于<br>不等于<br>包含<br>不包含|事件标签和值组合或要排除的标签和值组合<br>**等于** - 具备该标签并且值等于给定值的事件<br>**不等于** - 具备该标签但值不等于给定值的事件<br>**包含** - 具备该标签并且值包含指定字符串的事件<br>**不包含** - 具备该标签但值不包含指定字符串的事件| |*模板*|等于<br>不等于|模板或要排除的模板<br>**等于** - 属于从此模板继承的监控项/触发器/底层自动发现规则的事件<br>**不等于** - 不属于从此模板继承的监控项/触发器/底层自动发现规则的事件| |*主机*|等于<br>不等于|主机或要排除的主机<br>**等于** - 属于此主机的事件<br>**不等于** - 不属于此主机的事件|

en-us	#### Internal queue items  There are also another two items specifically allowing to remote query internal queue stats on another Zabbix instance:  -   `zabbix[stats,<ip>,<port>,queue,<from>,<to>]` internal item - for     direct internal queue queries to remote Zabbix server/proxy -   `zabbix.stats[<ip>,<port>,queue,<from>,<to>]` agent item - for     agent-based internal queue queries to remote Zabbix server/proxy  See also: [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)
zh-cn	#### 内部队列监控项  另外还有两个监控项可以远程查询另一个Zabbix实例上的内部队列统计信息:  -   `zabbix[stats,<ip>,<port>,queue,<from>,<to>]`  内部监控项 - 用于将内部队列查询直接发送到Zabbix server/proxy -   `zabbix.stats[<ip>,<port>,queue,<from>,<to>]`  agent监控项 - 用于将内部队列查询直接发送到Zabbix server/proxy  参考:  [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)

en-us	#### Inventory details  The **Overview** tab contains some general information about the host along with links to predefined scripts, latest monitoring data and host configuration options:  ![](../../../../../assets/en/manual/web_interface/inventory_host.png){width="600"}  The **Details** tab contains all available inventory details for the host:  ![](../../../../../assets/en/manual/web_interface/inventory_host2.png){width="600"}  The completeness of inventory data depends on how much inventory information is maintained with the host. If no information is maintained, the *Details* tab is disabled.
zh-cn	#### 资产详情  在 **概览** 选项卡中，包含有关主机的一些通用信息以及预定义脚本的链接，最新的监视数据和主机配置选项：  ![](../../../../../assets/en/manual/web_interface/inventory_host.png){width="600"}  在 **细节** 选项卡包含主机的所有可用资产记录明细：  ![](../../../../../assets/en/manual/web_interface/inventory_host2.png){width="600"}  资产数据的完整性取决于与主机保持多少库存信息。 如果没有维护信息， 则*细节* 选项卡禁用。

en-us	##### Item configuration  Configure a log monitoring [item](/manual/config/items/item#overview).  ![](../../../../../assets/en/manual/config/items/itemtypes/logfile_item.png)  All mandatory input fields are marked with a red asterisk.  Specifically for log monitoring items you enter:  |   |   | |--|--------| |*Type*|Select **Zabbix agent (active)** here.| |*Key*|Use one of the following item keys:<br>**log\[\]** or **logrt\[\]**:<br>These two item keys allow to monitor logs and filter log entries by the content regexp, if present.<br>For example: `log[/var/log/syslog,error]`. Make sure that the file has read permissions for the 'zabbix' user otherwise the item status will be set to 'unsupported'.<br>**log.count\[\]** or **logrt.count\[\]**:<br>These two item keys allow to return the number of matching lines only.<br>See supported [Zabbix agent item](zabbix_agent#supported_item_keys) key section for details on using these item keys and their parameters.| |*Type of information*|Prefilled automatically:<br>For log\[\] or logrt\[\] items - `Log`;<br>For log.count\[\] or logrt.count\[\] items - `Numeric (unsigned)`.<br>If optionally using the `output` parameter, you may manually select the appropriate type of information other than `Log`.<br>Note that choosing a non-Log type of information will lead to the loss of local timestamp.| |*Update interval (in sec)*|The parameter defines how often Zabbix agent will check for any changes in the log file. Setting it to 1 second will make sure that you get new records as soon as possible.| |*Log time format*|In this field you may optionally specify the pattern for parsing the log line timestamp.<br>If left blank the timestamp will not be parsed.<br>Supported placeholders:<br>\* **y**: *Year (0001-9999)*<br>\* **M**: *Month (01-12)*<br>\* **d**: *Day (01-31)*<br>\* **h**: *Hour (00-23)*<br>\* **m**: *Minute (00-59)*<br>\* **s**: *Second (00-59)*<br>For example, consider the following line from the Zabbix agent log file:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>It begins with six character positions for PID, followed by date, time, and the rest of the line.<br>Log time format for this line would be "pppppp:yyyyMMdd:hhmmss".<br>Note that "p" and ":" chars are just placeholders and can be anything but "yMdhms".|
zh-cn	##### 监控项配置  配置一个日志 [监控项](/manual/config/items/item#overview)  ![](../../../../../assets/en/manual/config/items/itemtypes/logfile_item.png)  所有标有红色星号的为必填字段。  具体日志监控项的输入：  |   |   | |---|---| |*类型*|这里选择 **Zabbix agent (主动)**| |*键值*|使用以下项键之一：<br>**log\[\]** 或 **logrt\[\]**：<br>这两个监控项键允许监控日志和过滤日志内容正则表达式的条目（如果存在）。<br>例如：`log[/var/log/syslog,error]`。确保文件对“zabbix”用户具有读取权限，否则监控项状态将设置为“不支持”。<br>**log.count\[\]** 或 **logrt.count\[\] **：<br>这两个监控项键只允许返回匹配的行数。<br>有关使用这些监控项键及其参数的详细信息，请参阅支持的 [Zabbix agent监控项](zabbix_agent#supported_item_keys) 键部分。| |*信息类型*|自动预填：<br>对于 log\[\] 或 logrt\[\] 项 - `Log`；<br>对于 log.count\[\] 或 logrt.count\[\] items - `Numeric (unsigned)`。<br>如果可选地使用 `output` 参数，您可以手动选择除 `Log` 之外的适当类型的信息。<br>请注意，选择非 Log 类型的信息将导致本地时间戳丢失。| |*更新间隔 (秒)*|该参数定义了Zabbix agent检查日志文件中任何更改的频率。 将其设置为1秒将确保你能尽快的获得新记录。| |*日志时间格式*|在此字段中，您可以选择指定解析日志行的时间戳的模式。<br>如果留空，则不会解析时间戳。<br>支持的占位符:<br>\* **y**: *年 (0001-9999)*<br>\* **M**: *月 (01-12)*<br>\* **d**: *日 (01-31)*<br>\* **h**: *小时 (00-23)*<br>\* **m**: *分 (00-59)*<br>\* **s**: *秒 (00-59)*<br>例如, 从Zabbix agent日志文件中查看以下行:<br>" 23480:20100328:154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."<br>它以PID的六个字符位置开始，后面跟日期、时间和行的其余部分。<br>此行的日志时间格式为 "pppppp:yyyyMMdd:hhmmss"。<br>注意， “p”和“：”字符只是占位符，而且只能是“yMdhms”|

en-us	##### Item configuration  When [configuring an item](/manual/config/items/item) on a host level:  -   Select 'IPMI agent' as the *Type* -   Enter an item [key](/manual/config/items/item/key) that is unique     within the host (say, ipmi.fan.rpm) -   For *Host interface* select the relevant IPMI interface (IP and     port). Note that an IPMI interface must exist on the host. -   Specify the *IPMI sensor* (for example 'FAN MOD 1A RPM' on Dell     Poweredge) to retrieve the metric from. By default, the sensor ID     should be specified. It is also possible to use prefixes before the     value:     -   `id:` - to specify sensor ID;     -   `name:` - to specify sensor full name. This can be useful in         situations when sensors can only be distinguished by specifying         the full name. -   Select the respective type of information ('Numeric (float)' in this     case; for discrete sensors - 'Numeric (unsigned)'), units (most     likely 'rpm') and any other required item attributes
zh-cn	 ##### 监控项 配置  配置主机级别的 [监控项](/manual/config/items/item):  -   选择 'IPMI agent' 作为 *类型* -   在主机中输入唯一的监控项 [键值](/manual/config/items/item/key) (比如, ipmi.fan.rpm) -   对于 *主机接口* 选择 IPMI 接口 (IP 和端口). 注意IPMI接口在主机上必须存在. -   指定 *IPMI 传感器* (比如在Dell Poweredge型号服务器上的  'FAN MOD 1A RPM' ) 用于检索对应的指标。默认情况下，应指定传感器ID。 也可以在值之前使用前缀:     -   `id:` - 指定传感器 ID;     -   `name:` - 指定传感器全名。 这在传感器只能通过指定全名来区分的情况下非常有用. -   选择相应的信息类型 ('浮点数' 在这个例子中；对于离散传感器使用 '数字(无正负)'), units (类似 'rpm') 和任何其它必需监控项属性

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

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

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

en-us	#### Item key  SQL queries are performed using a "Database monitor" item type. Therefore, most of the instructions on [ODBC monitoring](/manual/config/items/itemtypes/odbc_checks) page apply in order to get a working "Database monitor" discovery rule.  Two item keys may be used in "Database monitor" discovery rules:  -   **db.odbc.discovery**\[<unique short     description>,<dsn>,<connection string>\] - this item     transforms the SQL query result into a JSON array, turning the     column names from the query result into low-level discovery macro     names paired with the discovered field values. These macros can be     used in creating item, trigger, etc prototypes. See also: [Using     db.odbc.discovery](#using_dbodbcdiscovery).  ```{=html} <!-- --> ``` -   **db.odbc.get**\[<unique short     description>,<dsn>,<connection string>\] - this item     transforms the SQL query result into a JSON array, keeping the     original column names from the query result as a field name in JSON     paired with the discovered values. Compared to     `db.odbc.discovery[]`, this item does not create low-level discovery     macros in the returned JSON, therefore there is no need to check if     the column names can be valid macro names. The low-level discovery     macros can be defined as an additional step as required, using the     [custom LLD     macro](/manual/discovery/low_level_discovery#custom_macros)     functionality with JSONPath pointing to the discovered values in the     returned JSON. See also: [Using db.odbc.get](#using_dbodbcget).
zh-cn	#### 监控项的键  设置监控项类型为 "数据库监控" 来执行SQL查询。 所以为了让一个"数据库监控"类型的自动发现规则正常工作，可以参考[ODBC监控](/manual/config/items/itemtypes/odbc_checks) 页面中的大部分指南。  "数据库监控"类型的自动发现规则会用到两个键：  -   **db.odbc.discovery**\[<唯一简短描述>,<dsn(数据来源名称)>,<连接字符串>\] - 此监控项将SQL查询结果转换为一个JSON数组，其中表的字段名称会转换为宏的名称，宏的名称与发现的对应值成对匹配。这些宏可用于创建监控项和触发器等原型。另请参阅: [使用db.odbc.discovery](#using_dbodbcdiscovery)。  ```{=html} <!-- --> ``` -   **db.odbc.get**\[<唯一简短描述>,<dsn(数据来源名称)>,<连接字符串>\] - 此监控项将SQL查询结果转换为一个JSON数组，保留原始表字段名称作为输入框的名称，以JSON格式表示，并与对应的已发现的值成对匹配。相比于     `db.odbc.discovery[]`, 此监控项不在返回的JSON数组中创建低级别自动发现的宏, 因此无需检查表字段名称是否是有效的宏名称。通过使用     [自定义LLD     宏](/manual/discovery/low_level_discovery#custom_macros), 将JSONPath指向对应JSON值，可作为额外步骤按需定义低级别自动发现的宏。另请参阅: [使用db.odbc.get](#using_dbodbcget)。

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      net.if.discovery  This item is supported since Zabbix agent 2.0.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      net.if.discovery  从Zabbix agent 2.0起支持使用此监控项。

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      system.cpu.discovery  This item is supported since Zabbix agent 2.4.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的监控项的键是      system.cpu.discovery  从Zabbix agent 2.4起支持此监控项。

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      vfs.dev.discovery  This item is supported on Linux platforms only, since Zabbix agent 4.4.  You may create discovery rules using this discovery item and:  -   filter: **{\#DEVNAME} matches `sd[\D]$`** - to discover devices     named "sd0", "sd1", "sd2", ... -   filter: **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match     `^loop.*`** - to discover disk type devices whose name does not     start with "loop"
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      vfs.dev.discovery  从Zabbix agent 4.4起支持此监控项, 仅限Linux平台。  可以使用此监控项和下列配置来创建自动发现规则：  -   过滤器: **{\#DEVNAME} matches `sd[\D]$`** - 发现名为 "sd0", "sd1", "sd2", ... 的设备 -   过滤器: **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match     `^loop.*`** - 发现硬盘类型不以 "loop" 开头的设备

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      perf_instance.discovery[object]  or, to be able to provide the object name in English only, independently of OS localization:      perf_instance_en.discovery[object]  For example:      perf_instance.discovery[Processador]     perf_instance_en.discovery[Processor]  These items are supported since Zabbix Windows agent 5.0.1.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的监控项是      perf_instance.discovery[object]  或者可以提供对象名称，仅支持英文名称，此名称不受操作系统本地化设置控制:      perf_instance_en.discovery[object]  例如:      perf_instance.discovery[Processador]     perf_instance_en.discovery[Processor]  从Zabbix Windows agent 5.0.1起支持这些监控项.

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      service.discovery  This item is supported since Zabbix Windows agent 3.0.
zh-cn	#### 监控项的键  此监控项在[自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      service.discovery  从Zabbix Windows agent 3.0起支持此监控项。

en-us	### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the      systemd.unit.discovery  ::: noteimportant This [item](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) key is only supported in Zabbix agent 2. :::  This item returns a JSON with information about systemd units, for example:      [{         "{#UNIT.NAME}": "mysqld.service",         "{#UNIT.DESCRIPTION}": "MySQL Server",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": "",         "{#UNIT.JOBPATH}": "/",         "{#UNIT.UNITFILESTATE}": "enabled"     }, {         "{#UNIT.NAME}": "systemd-journald.socket",         "{#UNIT.DESCRIPTION}": "Journal Socket",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": "",         "{#UNIT.JOBPATH}": "/",         "{#UNIT.UNITFILESTATE}": "enabled"     }]
zh-cn	#### 监控项的键  在[自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用这个监控项      systemd.unit.discovery  ::: noteimportant 此[监控项](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) 的键只有Zabbix agent 2版本支持. :::  此监控项返回一个包含系统单元的JSON数据，如下所示:      [{         "{#UNIT.NAME}": "mysqld.service",         "{#UNIT.DESCRIPTION}": "MySQL Server",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": ""         "{#UNIT.JOBPATH}": "/",         "{#UNIT.UNITFILESTATE}": "enabled"     }, {         "{#UNIT.NAME}": "systemd-journald.socket",         "{#UNIT.DESCRIPTION}": "Journal Socket",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": "",         "{#UNIT.JOBPATH}": "/"         "{#UNIT.UNITFILESTATE}": "enabled"     }]

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the      zabbix[host,discovery,interfaces]  internal item. This item is supported since Zabbix server 3.4.  This item returns a JSON with the description of interfaces, including:  -   IP address/DNS hostname (depending on the “Connect to” host setting) -   Port number -   Interface type (Zabbix agent, SNMP, JMX, IPMI) -   If it is the default interface or not -   If the bulk request feature is enabled - for SNMP interfaces only.  For example:      [{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}]    With multiple interfaces their records in JSON are ordered by:  -   Interface type, -   Default - the default interface is put before non-default     interfaces, -   Interface ID (in ascending order).
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule)中使用的键是      zabbix[host,discovery,interfaces]  内部监控项。 从Zabbix server 3.4起支持此监控项。  此监控项返回一个JSON数组，包含以下关于接口的描述：  -   IP 地址/DNS 主机名(取决于 “连接到” 主机设置) -   端口号 -   接口类型 (Zabbix agent, SNMP, JMX, IPMI) -   是否是默认接口 -   批量请求(bulk request)特性是否启用 - 只适用于SNMP接口。  例如：      [{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}]    多个接口的JSON数据按以下规则排序：  -   接口类型, -   默认 - 默认接口在非默认接口前面, -   接口 ID (升序排列)。

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      wmi.getall[<namespace>,<query>]  This [item](/manual/config/items/itemtypes/zabbix_agent/win_keys) transforms the query result into a JSON array. For example:      select * from Win32_DiskDrive where Name like '%PHYSICALDRIVE%'  may return something like this:  ``` {.java} [     {         "DeviceID" : "\\.\PHYSICALDRIVE0",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 0,         "InterfaceType" : "IDE"     },     {         "DeviceID" : "\\.\PHYSICALDRIVE1",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 1,         "InterfaceType" : "IDE"     } ] ```  This item is supported since Zabbix Windows agent 4.4.
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule)中使用的监控项是      wmi.getall[<命名空间>,<查询>]  此[监控项](/manual/config/items/itemtypes/zabbix_agent/win_keys) 将查询结果转换成一个JSON数组. 比如:      select * from Win32_DiskDrive where Name like '%PHYSICALDRIVE%'  会转换成下面的数据:  ``` {.java} [     {         "DeviceID" : "\\.\PHYSICALDRIVE0",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 0,         "InterfaceType" : "IDE"     },     {         "DeviceID" : "\\.\PHYSICALDRIVE1",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 1,         "InterfaceType" : "IDE"     } ] ```  从Zabbix Windows agent 4.4起支持此监控项。

en-us	#### Item net.tcp.service parameters  **ftp**  Creates a TCP connection and expects the first 4 characters of the response to be "220 ", then sends "QUIT\\r\\n". Default port 21 is used if not specified.  **http**  Creates a TCP connection without expecting and sending anything. Default port 80 is used if not specified.  **https**  Uses (and only works with) libcurl, does not verify the authenticity of the certificate, does not verify the host name in the SSL certificate, only fetches the response header (HEAD request). Default port 443 is used if not specified.  **imap**  Creates a TCP connection and expects the first 4 characters of the response to be "\* OK", then sends "a1 LOGOUT\\r\\n". Default port 143 is used if not specified.  **ldap**  Opens a connection to an LDAP server and performs an LDAP search operation with filter set to (objectClass=\*). Expects successful retrieval of the first attribute of the first entry. Default port 389 is used if not specified.  **nntp**  Creates a TCP connection and expects the first 3 characters of the response to be "200" or "201", then sends "QUIT\\r\\n". Default port 119 is used if not specified.  **pop**  Creates a TCP connection and expects the first 3 characters of the response to be "+OK", then sends "QUIT\\r\\n". Default port 110 is used if not specified.  **smtp**  Creates a TCP connection and expects the first 3 characters of the response to be "220", followed by a space, the line ending or a dash. The lines containing a dash belong to a multiline response and the response will be re-read until a line without the dash is received. Then sends "QUIT\\r\\n". Default port 25 is used if not specified.  **ssh**  Creates a TCP connection. If the connection has been established, both sides exchange an identification string (SSH-major.minor-XXXX), where major and minor are protocol versions and XXXX is a string. Zabbix checks if the string matching the specification is found and then sends back the string "SSH-major.minor-zabbix\_agent\\r\\n" or "0\\n" on mismatch. Default port 22 is used if not specified.  **tcp**  Creates a TCP connection without expecting and sending anything. Unlike the other checks requires the port parameter to be specified.  **telnet**  Creates a TCP connection and expects a login prompt (':' at the end). Default port 23 is used if not specified.
zh-cn	#### 监控项 net.tcp.service 参数  **FTP**  创建 TCP 连接并期望响应的前 4 个字符为“220”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 21。  **http**  创建一个 TCP 连接而不期望和发送任何东西。 如果未指定，则使用默认端口 80。  **https**  使用（并且仅适用于）libcurl，不验证证书的真实性，不验证 SSL 证书中的主机名，仅获取响应标头（HEAD 请求）。 如果未指定，则使用默认端口 443。  **imap**  创建 TCP 连接并期望响应的前 4 个字符为“\* OK”，然后发送“a1 LOGOUT\\r\\n”。 如果未指定，则使用默认端口 143。  **ldap**  打开与 LDAP 服务器的连接并执行 LDAP 搜索操作，过滤器设置为 (objectClass=\*)。 期望成功检索第一个条目的第一个属性。 如果未指定，则使用默认端口 389。  **nntp**  创建 TCP 连接并期望响应的前 3 个字符为“200”或“201”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 119。  **pop**  创建 TCP 连接并期望响应的前 3 个字符为“+OK”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 110。  **smtp**  创建一个 TCP 连接并期望响应的前 3 个字符为“220”，后跟空格、行尾或破折号。包含破折号的行属于多行响应，响应将被重新读取直到收到没有破折号的行。 然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 25。  **ssh**  创建 TCP 连接。 如果连接已经建立，双方交换一个标识字符串（SSH-major.minor-XXXX），其中major和minor是协议版本，XXXX是一个字符串。 Zabbix 检查是否找到与规范匹配的字符串，然后在不匹配时发回字符串“SSH-major.minor-zabbix\_agent\\r\\n”或“0\\n”。 如果未指定，则使用默认端口 22。  **TCP**  创建一个 TCP 连接而不期望和发送任何东西。 与其他检查不同，需要指定端口参数。  **telnet**  创建一个 TCP 连接并期望登录提示（末尾为“:”）。如果未指定，则使用默认端口 23。

en-us	#### Item net.udp.service parameters  **ntp**  Sends an SNTP packet over UDP and validates the response according to [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5). Default port 123 is used if not specified.
zh-cn	#### 监控项 net.udp.service 参数  **ntp**  在UDP上发送一个SNTP包，并根据  [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5)需要验证响应。 如果未指定，则使用默认端口123。

en-us	# > Item object  The following objects are directly related to the `item` API.
zh-cn	# > 监控项对象  以下对象直接调用 `item` API 进行操作。

en-us	# itemprototype.create
zh-cn	# 创建监控项原型

en-us	# itemprototype.delete
zh-cn	# 删除监控项原型

en-us	# itemprototype.get
zh-cn	# 获取监控项原型

en-us	# > Item prototype object  The following objects are directly related to the `itemprototype` API.
zh-cn	# > 监控项原型对象  以下对象与 `监控项原型` API 直接相关。

en-us	# Item prototype  This class is designed to work with item prototypes.  Object references:\  -   [Item     prototype](/manual/api/reference/itemprototype/object#item_prototype)  Available methods:\  -   [itemprototype.create](/manual/api/reference/itemprototype/create) -     creating new item prototypes -   [itemprototype.delete](/manual/api/reference/itemprototype/delete) -     deleting item prototypes -   [itemprototype.get](/manual/api/reference/itemprototype/get) -     retrieving item prototypes -   [itemprototype.update](/manual/api/reference/itemprototype/update) -     updating item prototypes
zh-cn	#  监控项原型  此类用于管理监控项原型。  对象引用:\  -   [监控项原型](/manual/api/reference/itemprototype/object#监控项原型)  可用的方法:\  -   [itemprototype.create](/manual/api/reference/itemprototype/create) 创建监控项原型 -   [itemprototype.delete](/manual/api/reference/itemprototype/delete) 删除监控项原型 -   [itemprototype.get](/manual/api/reference/itemprototype/get) 搜索监控项原型 -   [itemprototype.update](/manual/api/reference/itemprototype/update) 更新监控项原型

en-us	# itemprototype.update
zh-cn	# 更新监控项原型

en-us	##### Item prototype  You may want to create an item prototype like this:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom.png)  with preprocessing options:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom_b.png)
zh-cn	##### 监控项原型  可以创建这样的监控项原型:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom.png)  并配置预处理选项:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom_b.png)

en-us	#### Items  Define items to monitor.  [Item API](/manual/api/reference/item)
zh-cn	#### 监控项  定义要监控的监控项。  [Item API](/manual/api/reference/item)

en-us	#### Items  To configure querying of internal stats on another Zabbix instance, you may use two items:  -   `zabbix[stats,<ip>,<port>]` internal item - for direct remote     queries of Zabbix server/proxy. <ip> and <port> are used     to identify the target instance. -   `zabbix.stats[<ip>,<port>]` agent item - for agent-based remote     queries of Zabbix server/proxy. <ip> and <port> are used     to identify the target instance.  See also: [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)  The following diagram illustrates the use of either item depending on the context.  ![](../../../../assets/en/manual/appendix/items/ext_stats.png)  -   ![](../../../../assets/en/manual/appendix/items/green.png) - Server     → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/pink.png) - Server →     proxy → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/blue.png) - Server →     agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/red.png) - Server →     proxy → agent → external Zabbix instance     (`zabbix.stats[<ip>,<port>]`)  To make sure that the target instance allows querying it by the external instance, list the address of the external instance in the 'StatsAllowedIP' parameter on the target instance.
zh-cn	 #### 监控项  要在另一个Zabbix实例上配置内部统计信息的查询，可以使用两项：  -   `zabbix[stats,<ip>,<port>]`  内部监控项 - 用于直接远程查询Zabbix server/proxy。<ip>和<port>用于标识目标实例。 -   `zabbix.stats[<ip>,<port>]`  Agent监控项 - 用于基于代理的Zabbix server/proxy的远程查询。<ip>和<port>用于标识目标实例。  另请参见:   [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)  下图根据上下文说明了这两个项的用法。  ![](../../../../assets/en/manual/appendix/items/ext_stats.png)  -   ![](../../../../assets/en/manual/appendix/items/green.png) - Server     → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/pink.png) - Server →     proxy → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/blue.png) - Server →     agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/red.png) - Server →     proxy → agent → external Zabbix instance     (`zabbix.stats[<ip>,<port>]`)  要确保目标实例允许外部实例查询它，请在目标实例的“StatsAllowedIP”参数中列出外部实例的地址。

en-us	# Item  This class is designed to work with items.  Object references:\  -   [Item](/manual/api/reference/item/object#item)  Available methods:\  -   [item.create](/manual/api/reference/item/create) - creating new     items -   [item.delete](/manual/api/reference/item/delete) - deleting items -   [item.get](/manual/api/reference/item/get) - retrieving items -   [item.update](/manual/api/reference/item/update) - updating items
zh-cn	# 监控项  此部分旨在介绍如何对监控项进行操作。  引用对象：  -   [监控项](/manual/api/reference/item/object#item)  可用方法：  -   [创建](/manual/api/reference/item/create) - 创建新监控项 -   [删除](/manual/api/reference/item/delete) - 删除监控项 -   [检索](/manual/api/reference/item/get) - 检索监控项 -   [更新](/manual/api/reference/item/update) - 更新监控项

en-us	##### Item  To begin with, you may want to set up an item that monitors a log file, for example:      log[/var/log/syslog]  ![](../../../../assets/en/manual/config/event_correlation/correlation_item.png)  With the item set up, wait a minute for the configuration changes to be picked up and then go to [Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) to make sure that the item has started collecting data.
zh-cn	##### 监控项  首先，你可能想设置一个监控日志文件的监控项，例如：      log[/var/log/syslog]  ![](../../../../assets/en/manual/config/event_correlation/correlation_item.png)  设置监控项后，等待一分钟，等待配置更改，然后去[最新数据](/manual/web_interface/frontend_sections/monitoring/latest_data)  确认该监控项已经开始收集数据。

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

en-us	##### Item value preprocessing  The **Preprocessing** tab allows to define [transformation rules](/manual/config/items/preprocessing) for the received values.
zh-cn	##### 监控项值预处理   **预处理** 选项卡允许为接收到的值定义[转换规则](/zh/manual/config/items/preprocessing) 。

en-us	### Java gateway installation  It is required to install [Java gateway](/manual/concepts/java) only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database.  Once the required repository is added, you can install Zabbix Java gateway by running:      # apt install zabbix-java-gateway  Proceed to [setup](/manual/concepts/java/from_debian_ubuntu) for more details on configuring and running Java gateway.
zh-cn	### 安装 Java gateway  只有当你想监控 JMX 应用程序时，才需要安装 [Java gateway](/manual/concepts/java) 。 Java gateway 是轻量级的不需要数据库。  添加了所需的软件源之后，就可执行如下命令安装 Zabbix Java gateway：      # apt install zabbix-java-gateway  了解更多关于配置和运行 Java gateway 的详细信息可跳转至 [java 设置](/manual/concepts/java/from_debian_ubuntu) 。

en-us	### Java gateway installation  It is required to install [Java gateway](/manual/concepts/java) only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database.  Once the required repository is added, you can install Zabbix Java gateway by running:      # dnf install zabbix-java-gateway  Proceed to [setup](/manual/concepts/java/from_rhel) for more details on configuring and running Java gateway.
zh-cn	### Java网关安装  只有在以下情况下才需要安装 [Java 网关](/manual/concepts/java) 您想要监视 JMX 应用程序。 Java网关是轻量级的，不需要数据库。  添加所需的存储库后，您可以通过运行以下命令安装 Zabbix Java 网关：   · # dnf install zabbix-java-gateway  继续 [setup](/manual/concepts/java/from_rhel) 了解有关配置和运行 Java 网关的更多详细信息。

en-us	#### Keeping trends  Trends is a built-in historical data reduction mechanism which stores minimum, maximum, average and the total number of values per every hour for numeric data types.  You can set for how many days trends will be kept:  -   in the item properties [form](/manual/config/items/item) -   when mass-updating items -   when setting up Housekeeper tasks  Trends usually can be kept for much longer than history. Any older data will be removed by the housekeeper.  Zabbix server accumulates trend data in runtime in the trend cache, as the data flows in. Server flushes **previous hour** trends of every item into the database (where frontend can find them) in these situations:  -   server receives the first current hour value of the item -   5 or less minutes of the current hour left and still no current hour     values of the item -   server stops  To see trends on a graph you need to wait at least to the beginning of the next hour (if item is updated frequently) and at most to the end of the next hour (if item is updated rarely), which is 2 hours maximum.  When server flushes trend cache and there are already trends in the database for this hour (for example, server has been restarted mid-hour), server needs to use update statements instead of simple inserts. Therefore on a bigger installation if restart is needed it is desirable to stop server in the end of one hour and start in the beginning of the next hour to avoid trend data overlap.  History tables do not participate in trend generation in any way.  ::: noteimportant If trends are set to '0', Zabbix server does not calculate or store trends at all. :::  ::: noteclassic The trends are calculated and stored with the same data type as the original values. As a result the average value calculations of unsigned data type values are rounded and the less the value interval is the less precise the result will be. For example if item has values 0 and 1, the average value will be 0, not 0.5.  Also restarting server might result in the precision loss of unsigned data type average value calculations for the current hour. :::
zh-cn	#### 趋势数据的留存  趋势数据是一种内建的历史数据压缩机制，可以用来存储数字类型监控项的每小时的最小值、最大值、平均值和记录数量。  通过设置趋势存储时间，可以指定趋势数据留存的时长。 在以下位置，你可以找到相关的输入框：  -   监控项属性 [表单](/manual/config/items/item) -   批量更新监控项 -   [管家配置页](/manual/web_interface/frontend_sections/administration/general#管家)  通常趋势数据设置的的留存时间应当比历史数据留存时间设置的长。任何过旧的趋势数据会被管家从数据库删除。  Zabbix server在运行时会在趋势缓存中积累趋势数据，因为有数据流入。 在这些情况下，Zabbix Server会将每个监控项的**前一个小时**趋势数据写入数据库(在前端可以看到):    - 服务器接收到监控项首个当前一小时的值   - 在还差5分钟或更少时间达到一小时，仍然没有该监控项当前一小时的值   - 服务器停止    要查看图表上的趋势，你需要至少等待到下一个小时的开始(如果监控项经常更新)，最多等待到下一个小时的结束(如果监控项很少更新)，最多2个小时。    当服务器刷新趋势缓存时，如果数据库中已经有这一小时的趋势(例如，服务器在这一小时中已经重新启动)，服务器需要使用更新语句，而不是简单的插入。 因此，在大型环境的安装中，如果需要重新启动，最好在一个小时结束时停止服务器，在下一个小时开始时开始，以避免趋势数据重叠。  趋势数据生成和历史表没有关系。  ::: noteimportant 如果趋势存储时间被设置为“0”，Zabbix server将不再计算或存储该监控项的趋势数据 :::  ::: noteclassic 趋势数据的计算和存储将会使用与原值相同的数据类型。无符号数字（unsigned Numeric）数据类型的值，平均值计算的结果小数点后会被舍去，所以记录值之间的间隔越小，计算结果结果将会精确度越低。例如：如果监控项的得到了得到了两个值，分别是“0”和“1”，那么平均值的计算结果将会是“0”，而不是“0.5”。  此外，重启服务器可能会导致当前小时无符号数字类型的数据，平均值计算的精度损失。 :::

en-us	#### Kiosk mode  The kiosk mode in supported frontend pages can be activated using URL parameters. For example, in dashboards:  -   `/zabbix.php?action=dashboard.view&kiosk=1` - activate kiosk mode -   `/zabbix.php?action=dashboard.view&kiosk=0` - activate normal mode
zh-cn	#### 信息亭（Kiosk）模式  可以使用 URL 参数激活支持的前端页面中的信息亭模式。 例如，在仪表板中：  -   `/zabbix.php?action=dashboard.view&kiosk=1` - 激活信息亭模式 -   `/zabbix.php?action=dashboard.view&kiosk=0` - 激活普通模式

en-us	#### Known issues  See [known issues](/manual/installation/known_issues#graphs) for graphs.
zh-cn	#### 已知的问题  有关图表，请参阅 [已知问题](/manual/installation/known_issues#graphs)。

en-us	##### Large file support  Zabbix has large file support for SNMP trapper files. The maximum file size that Zabbix can read is 2\^63 (8 EiB). Note that the filesystem may impose a lower limit on the file size.
zh-cn	##### 大文件支持  Zabbix为SNMP trap文件提供了“大文件支持”。Zabbix可以读取的最大文件大小为2^63（8 EiB）。请注意，文件系统可能会对文件大小添加下限。

en-us	##### Limitations  -   Only same host (template) dependencies are allowed -   An item prototype can depend on another item prototype or regular     item from the same host -   Maximum count of dependent items for one master item is limited to     29999 (regardless of the number of dependency levels) -   Maximum 3 dependency levels allowed -   Dependent item on a host with master item from template will not be     exported to XML
zh-cn	##### 局限性  -   只允许相同的主机（模板）从属项 -   监控项原型可以依赖于来自同一主机的另一个监控项原型或常规监控项 -   主要监控项的从属项最大计数被限制为29999（不考虑从属级别的数量） -   最大允许3个从属级别 -   当从属监控项使用主机上来自模板的监控项作为主要监控项时，不允许导出为XML

en-us	#### Limitations  -   Private keys are stored in plain text in files readable by Zabbix     components during startup -   Pre-shared keys are entered in Zabbix frontend and stored in Zabbix     database in plain text -   Built-in encryption does not protect communications:     -   Between the web server running Zabbix frontend and user web         browser     -   Between Zabbix frontend and Zabbix server -   Currently each encrypted connection opens with a full TLS handshake,     no session caching and tickets are implemented -   Adding encryption increases the time for item checks and actions,     depending on network latency:     -   For example, if packet delay is 100ms then opening a TCP         connection and sending unencrypted request takes around 200ms.         With encryption about 1000 ms are added for establishing the TLS         connection;     -   Timeouts may need to be increased, otherwise some items and         actions running remote scripts on agents may work with         unencrypted connections, but fail with timeout with encrypted. -   Encryption is not supported by [network     discovery](/manual/discovery/network_discovery). Zabbix agent checks     performed by network discovery will be unencrypted and if Zabbix     agent is configured to reject unencrypted connections such checks     will not succeed.
zh-cn	 #### 限制因素  -   私钥以纯文本形式存储在Zabbix组件启动时可读的文件中 -   预共享密钥在Zabbix前端输入，并以明文形式存储在Zabbix数据库中 -   内置加密不能保护通信:     -   运行Zabbix前端的web服务器和用户web浏览器之间     -   Zabbix前端和Zabbix server之间 -   目前，每个加密连接都使用完整的TLS握手打开，没有实现会话缓存和票据 -   根据网络延迟，添加加密会增加监控项检查和操作的时间:     -   例如，如果包延迟100ms，那么打开TCP连接并发送未加密的请求大约需要200ms。 在建立TLS连接时，增加约1000毫秒的加密;     -   超时可能需要增加，否则在代理上运行远程脚本的某些监控项和操作可能会在未加密的连接中工作，但在加密的连接中超时则会失败。 -   不支持加密 [网络设备自动发现](/manual/discovery/network_discovery)。由网络发现执行的Zabbix agent 检查将不加密，如果Zabbix agent被配置为拒绝未加密的连接，这样的检查将不会成功。

en-us	##### Limitations  There are some limitations associated with the algorithm of creating LLD macro names from MBean property names:  -   attribute names are changed to uppercase -   attribute names are ignored (no LLD macros are generated) if they     consist of unsupported characters for LLD macro names. Supported     characters can be described by the following regular expression:     `A-Z0-9_\.` -   if an attribute is called "obj" or "domain" they will be ignored     because of the overlap with the values of the reserved Zabbix     properties {\#JMXOBJ} and {\#JMXDOMAIN} (supported since Zabbix     3.4.3.)  Please consider this jmx.discovery (with "beans" mode) example. MBean has the following properties defined:      name=test     тип=Type     attributes []=1,2,3     Name=NameOfTheTest     domAin=some  As a result of JMX discovery, the following LLD macros will be generated:  -   {\#JMXDOMAIN} - Zabbix internal, describing the domain of MBean -   {\#JMXOBJ} - Zabbix internal, describing MBean object -   {\#JMXNAME} - created from "name" property  Ignored properties are:  -   тип : its name contains unsupported characters (non-ASCII) -   attributes\[\] : its name contains unsupported characters (square     brackets are not supported) -   Name : it's already defined (name=test) -   domAin : it's a Zabbix reserved name
zh-cn	##### 限制  从MBean属性的名称中创建LLD宏的名称时，有一些规则上的限制:  -   属性名称被改为大写 -   如果LLD宏名称中包含不支持的字符，则属性名称被忽略 (未生成LLD宏) 。支持的字符可用下面的正则表达式来表示:     `A-Z0-9_\.` -   如果属性名称是 "obj" 或 "domain" 则会被忽略     因为这与预留的Zabbix属性 {\#JMXOBJ} 和{\#JMXDOMAIN}的值重叠(从 Zabbix     3.4.3起支持此特性。)  请思考这个 jmx.discovery (使用 "beans" 模式) 的例子。MBean 中定义了下面的属性:      name=test     тип=Type     attributes []=1,2,3     Name=NameOfTheTest     domAin=some  作为JMX自动发现的结果，会产生下面的LLD宏:  -   {\#JMXDOMAIN} - Zabbix内部创建, 描述了MBean的域 -   {\#JMXOBJ} - Zabbix内部创建, 描述了MBean对象 -   {\#JMXNAME} - 从 "名称" 属性中创建  被忽略的属性有:  -   тип : 该名称包含不支持的字符 (非ASCII) -   attributes\[\] : 该名称包含不支持的字符(不支持方括号) -   Name: 已经定义过了 (name=test) -   domAin: Zabbix的保留名称

en-us	 #### Limitations  Zabbix agent for Windows does not support non-standard Windows configurations where CPUs are distributed non-uniformly across NUMA nodes. If logical CPUs are distributed non-uniformly, then CPU performance metrics may not be available for some CPUs. For example, if there are 72 logical CPUs with 2 NUMA nodes, both nodes must have 36 CPUs each.
zh-cn	#### 局限性  用于 Windows 的 Zabbix 代理不支持非标准的 Windows 配置，cpu 在 NUMA 节点上非均匀分布。如果逻辑 CPU 是非均匀分布的，那么某些 CPU 的 CPU 性能指标可能不可用。 例如, 如果有72个逻辑CPU分布在2个NUMA节点，那么每个节点必须有36个CPU。

en-us	##### Linking pre-defined templates to hosts  As you may have noticed, Zabbix comes with a set of predefined templates for various OS, devices and applications. To get started with monitoring very quickly, you may link the appropriate one of them to a host, but beware that these templates need to be fine-tuned for your environment. Some checks may not be needed, and polling intervals may be way too frequent.  More information about [templates](/manual/config/templates) is available.
zh-cn	##### 链接预定义模版到主机  正如您可能已经注意到的，Zabbix为各种操作系统、设备和应用程序提供了一组预定义的模板。要快速开始监控，您可以将适当的模板链接到主机，但要注意，这些模板需要根据您的环境进行微调。一些检查可能不需要，轮询间隔可能过于频繁。  可参考该链接，查看更多关于[模板](/manual/config/templates)的信息。

en-us	#### Linux kernel threads
zh-cn	#### Linux 内核线程

en-us	#### Linux  See values supported for 'memtype' parameter on Linux in the table.  |Supported value|Description|Source in /proc/<pid>/status file| |--|------|--| |vsize ^[1](proc_mem_notes#footnotes)^|Virtual memory size|VmSize| |pmem|Percentage of real memory|(VmRSS/total\_memory) \* 100| |rss|Resident set size|VmRSS| |data|Size of data segment|VmData| |exe|Size of code segment|VmExe| |hwm|Peak resident set size|VmHWM| |lck|Size of locked memory|VmLck| |lib|Size of shared libraries|VmLib| |peak|Peak virtual memory size|VmPeak| |pin|Size of pinned pages|VmPin| |pte|Size of page table entries|VmPTE| |size|Size of process code + data + stack segments|VmExe + VmData + VmStk| |stk|Size of stack segment|VmStk| |swap|Size of swap space used|VmSwap|  Notes for Linux:  1.  Not all 'memtype' values are supported by older Linux kernels. For     example, Linux 2.4 kernels do not support `hwm`, `pin`, `peak`,     `pte` and `swap` values. 2.  We have noticed that self-monitoring of the Zabbix agent active     check process with `proc.mem[...,...,...,...,data]` shows a value     that is 4 kB larger than reported by `VmData` line in the agent's     /proc/<pid>/status file. At the time of self-measurement the     agent's data segment increases by 4 kB and then returns to the     previous size.
zh-cn	#### Linux  请参见表中Linux上的“memtype”参数支持的值。  |支持值|描述|来源/proc/<pid>/status 文件| |---------------|-----------|---------------------------------------| |vsize ^[1](proc_mem_notes#footnotes)^|虚拟内存大小|VmSize| |pmem|实际内存百分比|(VmRSS/total\_memory) \* 100| |rss|驻留内存大小|VmRSS| |data|数据段大小|VmData| |exe|代码段大小|VmExe| |hwm|驻留集峰值大小|VmHWM| |lck|锁定内存大小|VmLck| |lib|共享库的大小|VmLib| |peak|峰值虚拟内存大小|VmPeak| |pin|固定页面的大小|VmPin| |pte|页表条目的大小|VmPTE| |size|进程代码 + 数据 + 堆栈段的大小|VmExe + VmData + VmStk| |stk|堆栈段大小|VmStk| |swap|使用的交换空间大小|VmSwap|  Linux上注意事项:  1.  一些旧版本Linux 内核并不是支持所有'memtype' 值的。例如, Linux 内核版本2.4就不支持  `hwm`,  `pin`,  `peak`,  `pte`  和  `swap`  等值。 2.  我们发现 Zabbix agent 主动检查进程参数`proc.mem[...,...,...,...,data]`  显示的值比agent 的 /proc/<pid>/status 文件中  `VmData`行的值大 4 kB。在agent自我监控管理时，agent的数据碎片增长率4 kB ，然后又返回到先前的值。

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

en-us	# LLD rule  This class is designed to work with low level discovery rules.  Object references:\  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld_rule)  Available methods:\  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) -     copying LLD rules -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) -     creating new LLD rules -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) -     deleting LLD rules -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) -     retrieving LLD rules -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) -     updating LLD rules
zh-cn	# LLD 规则  此类用于底层发现规则。  对象引用：  -   [LLD rule](/manual/api/reference/discoveryrule/object#lld规则)  可用方法：  -   [discoveryrule.copy](/manual/api/reference/discoveryrule/copy) - 复制LLD规则 -   [discoveryrule.create](/manual/api/reference/discoveryrule/create) - 创建LLD规则 -   [discoveryrule.delete](/manual/api/reference/discoveryrule/delete) - 删除LLD规则 -   [discoveryrule.get](/manual/api/reference/discoveryrule/get) - 获取LLD规则 -   [discoveryrule.update](/manual/api/reference/discoveryrule/update) - 更新LLD规则

en-us	#### Locale  Note that the agent requires a UTF-8 locale so that some textual agent items can return the expected content. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.
zh-cn	 #### 本地环境  值得注意的是，Zabbix agent 需要 UTF-8 语言环境，以便某些文本 Zabbix agent 监控项可以返回预期的内容。 大多数现代类 Unix 系统都默认使用 UTF-8 语言环境，但是，有些系统可能需要特定的设置。

en-us	#### Locale  Note that the server requires a UTF-8 locale so that some textual items can be interpreted correctly. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically.
zh-cn	#### 语言环境  值得注意的是，Zabbix server 需要 UTF-8语言环境，以便可以正确解释某些文本项。 大多数现代类 Unix 系统都默认使用UTF-8 语言环境，但是，有些系统可能需要做特定的设置。

en-us	### Log entry  The log entry object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |level|integer|Log level.| |ms|string|The time elapsed in milliseconds since the script was run before log entry was added.| |message|string|Log message.|
zh-cn	### 日志条目 日志条目对象有如下属性。 |属性|[类型](/manual/api/reference_commentary#数据_类型)|描述| |--------|---------------------------------------------------|-----------| |level|integer|日志等级。| |ms|string|从脚本开始运行到添加日志条目前经过时间（毫秒）。| |message|string|日志信息。|

en-us	### Log history  The log history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |logeventid|integer|Windows event log entry ID.| |ns|integer|Nanoseconds when the value was received.| |severity|integer|Windows event log entry level.| |source|string|Windows event log entry source.| |timestamp|timestamp|Windows event log entry time.| |value|text|Received value.|
zh-cn	 ### 日志型历史数据  日志型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |id|string|历史条目的 ID。| |clock|timestamp|收到值的时间。| |itemid|string|相关监控项的 ID。| |logeventid|integer|Windows 事件日志条目的 ID。| |ns|integer|收到值时的纳秒数。| |severity|integer|Windows 事件日志条目的级别。| |source|string|Windows 事件日志条目的来源。| |timestamp|timestamp|Windows 事件日志条目的时间。| |value|text|收到的值。|

en-us	#### Login and systemd  We recommend [creating](/manual/installation/install#create_user_account) a *zabbix* user as system user, that is, without ability to log in. Some users ignore this recommendation and use the same account to log in (e. g. using SSH) to host running Zabbix. This might crash Zabbix daemon on log out. In this case you will get something like the following in Zabbix server log:      zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument     zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument     zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument  and in Zabbix agent log:      zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument  This happens because of default systemd setting `RemoveIPC=yes` configured in `/etc/systemd/logind.conf`. When you log out of the system the semaphores created by Zabbix previously are removed which causes the crash.  A quote from systemd documentation:      RemoveIPC=      Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the     user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources     after the last of the user's sessions terminated. This covers System V semaphores, shared memory     and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the     root user and other system users are excluded from the effect of this setting. Defaults to "yes".  There are 2 solutions to this problem:  1.  (recommended) Stop using *zabbix* account for anything else than     Zabbix processes, create a dedicated account for other things. 2.  (not recommended) Set `RemoveIPC=no` in `/etc/systemd/logind.conf`     and reboot the system. Note that `RemoveIPC` is a system-wide     parameter, changing it will affect the whole system.
zh-cn	#### Login 和 systemd  我们建议[创建](/manual/installation/install#create_user_account) 一个 *zabbix*用户作为系统用户，但不允许登录。一些用户忽略此建议并使用相同的帐户登录（例如使用 SSH）来登录运行 Zabbix 的主机。这可能会使 Zabbix 守护进程在注销时崩溃。在这种情况下，您将在 Zabbix server 日志中获得类似以下内容：      zabbix_server [27730]: [file:'selfmon.c',line:375] lock failed: [22] Invalid argument     zabbix_server [27716]: [file:'dbconfig.c',line:5266] lock failed: [22] Invalid argument     zabbix_server [27706]: [file:'log.c',line:238] lock failed: [22] Invalid argument  并且在 Zabbix agent 日志中：      zabbix_agentd [27796]: [file:'log.c',line:238] lock failed: [22] Invalid argument  这是因为默认的 systemd 设置 `RemoveIPC=yes`在`/etc/systemd/logind.conf`中配置。 当您退出系统时，Zabbix 之前创建的信号量会被删除，这会导致崩溃。  来自 systemd 文档的引用：      RemoveIPC=      Controls whether System V and POSIX IPC objects belonging to the user shall be removed when the     user fully logs out. Takes a boolean argument. If enabled, the user may not consume IPC resources     after the last of the user's sessions terminated. This covers System V semaphores, shared memory     and message queues, as well as POSIX shared memory and message queues. Note that IPC objects of the     root user and other system users are excluded from the effect of this setting. Defaults to "yes".  这个问题有2个解决方案：  1. （推荐）停止使用*zabbix* 帐户来处理除 Zabbix 进程之外的任何事情，为其他事情创建一个专用帐户。 2. （不推荐）设置`RemoveIPC=no` 在`/etc/systemd/logind.conf`中并重新启动系统。  请注意， `RemoveIPC` 是一个系统范围的参数，更改它会影响整个系统。

en-us	###      Log level control targets     *process-type*   All processes of specified type (active checks, collector, listener)     *process-type,N*   Process type and number (e.g., listener,3)     *pid*   Process identifier, up to 65535. For larger values specify target as "process-type,N"  ```{=html} <!-- --> ``` **-p**, **--print**   Print known items and exit. For each item either generic defaults are used, or specific defaults for testing are supplied. These defaults are listed in square brackets as item key parameters. Returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. For user parameters type is always **t**, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix\_get when querying a running agent daemon as permissions or environment may be different. Returned value types are:     d   Number with a decimal part.     m   Not supported. This could be caused by querying an item that only works in the active mode like a log monitoring item or an item that requires multiple collected values. Permission issues or incorrect user parameters could also result in the not supported state.     s   Text. Maximum length not limited.     t   Text. Same as **s**.     u   Unsigned integer.  **-t**, **--test** *item-key*   Test single item and exit. See **--print** for output description.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAH}
zh-cn	 ###     日志级别控制目标     *process-type*   所有指定类型的进程（活动检查、收集器、侦听器）     *process-type,N*   进程类型和编号（例如，listener,3）    *pid*   进程标识符，最多65535。对于较大的值，将目标指定为"process-type,N"  ```{=html} <!-- --> ``` **-p**, **--print**   打印已知项目并退出。对于每个项目，要么使用通用默认值，要么提供用于测试的特定默认值。这些默认值作为项目关键参数列在方括号中。返回值括在方括号中，以返回值的类型为前缀，用竖线字符分隔。对于用户参数，类型始终为 **t**，因为agent无法确定所有可能的返回值。当查询正在运行的agent守护程序时，因为权限或环境可能不同，不保证在 Zabbix 服务器或 zabbix\_get中显示为工作中的项目。返回值类型包括：     d   带有小数部分的数字。     m   不支持。这可能是由于查询仅在活动模式下工作的项目（如日志监视项目或需要多个收集值的项目）引起的。权限问题或不正确的用户参数也可能导致"不支持"状态。     s   文本。最大长度不受限制。     t   文本。和 **s** 一样。     u   无符号整数。  **-t**, **--test** *item-key*   测试单个项目并退出。查看 **--print** 部分的输出描述。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAH}

en-us	##### Log rotation  Zabbix does not provide any log rotation system - that should be handled by the user. The log rotation should first rename the old file and only later delete it so that no traps are lost:\  1.  Zabbix opens the trap file at the last known location and goes to     step 3 2.  Zabbix checks if the currently opened file has been rotated by     comparing the inode number to the defined trap file's inode number.     If there is no opened file, Zabbix resets the last location and goes     to step 1. 3.  Zabbix reads the data from the currently opened file and sets the     new location. 4.  The new data are parsed. If this was the rotated file, the file is     closed and goes back to step 2. 5.  If there was no new data, Zabbix sleeps for 1 second and goes back     to step 2.
zh-cn	##### 日志轮询  Zabbix不提供任何日志轮询系统（它应由用户处理）。 日志轮询应该首先重命名旧文件，然后才能将其删除，以免丢失trap：\  1.   Zabbix在最后一个已知位置打开trap文件，并转到步骤3 2.   Zabbix通过比较inode号和定义trap文件的inode号，检查当前打开的文件是否已经轮换。如果没有打开的文件，Zabbix将重置最后一个位置并转到步骤1。 3.   Zabbix从当前打开的文件中读取数据并设置新的位置。 4.   新数据被解析。如果这是轮询的文件，文件将关闭并返回到步骤2。 5.   如果没有新的数据，Zabbix 等待1秒钟后，然后回到步骤2。

en-us	#### Low-level discovery  Configure low-level discovery rules as well as item, trigger and graph prototypes to monitor dynamic entities.  [LLD rule API](/manual/api/reference/discoveryrule) | [Item prototype API](/manual/api/reference/itemprototype) | [Trigger prototype API](/manual/api/reference/triggerprototype) | [Graph prototype API](/manual/api/reference/graphprototype) | [Host prototype API](/manual/api/reference/hostprototype)
zh-cn	#### 低级别自动发现  配置低级发现规则以及项目，触发器和图形原型来监视动态实体。  [LLD rule API](/manual/api/reference/discoveryrule) | [Item prototype API](/manual/api/reference/itemprototype) | [Trigger prototype API](/manual/api/reference/triggerprototype) | [Graph prototype API](/manual/api/reference/graphprototype) | [Host prototype API](/manual/api/reference/hostprototype)

en-us	#### Low-level discovery  In a [low-level discovery rule](/manual/discovery/low_level_discovery#configuring_low-level_discovery), user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Key parameters|<|yes| |Update interval|<|no| |Custom interval|<|no| |Keep lost resources period|<|no| |Description|<|yes| |*SNMP agent*|<|<| | |SNMP OID|yes| |*SSH agent*|<|<| | |Username|yes| |^|Public key file|yes| |^|Private key file|yes| |^|Password|yes| |^|Script|yes| |*TELNET agent*|<|<| | |Username|yes| |^|Password|yes| |^|Script|yes| |*Zabbix trapper*|<|<| | |Allowed hosts|yes| |*Database monitor*|<|<| | |Username|yes| |^|Password|yes| |^|SQL query|yes| |*JMX agent*|<|<| | |JMX endpoint|yes| |*HTTP agent*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|yes| |^|Query fields|yes| |^|Timeout|no| |^|Request body|yes| |^|Headers (names and values)|yes| |^|Required status codes|yes| |^|HTTP authentication username|yes| |^|HTTP authentication password|yes| |*Filters*|<|<| | |Regular expression|yes| |*Overrides*|<|<| | |Filters: regular expression|yes| |^|Operations: update interval (for item prototypes)|no| |^|Operations: history storage period (for item prototypes)|no| |^|Operations: trend storage period (for item prototypes)|no|
zh-cn	#### 底层自动发现  在[底层自动发现规则](/manual/discovery/low_level_discovery#configuring_low-level_discovery)中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |键参数|<|支持| |更新间隔|<|不支持| |自定义间隔|<|不支持| |保留失效资源的时间|<|不支持| |描述|<|支持| |*SNMP 代理*|<|<| | |SNMP OID|支持| |*SSH 代理*|<|<| | |用户名|支持| |^|公钥文件|支持| |^|私钥文件|支持| |^|密码|支持| |^|脚本|支持| |*TELNET 代理*|<|<| | |用户名|支持| |^|密码|支持| |^|脚本|支持| |*Zabbix采集器*|<|<| | |允许的主机|支持| |*数据库监控*|<|<| | |用户名|支持| |^|密码|支持| |^|SQL查询|支持| |*JMX 代理*|<|<| | |JMX 端点|支持| |*HTTP 代理*|<|<| | |URL^[3](supported_by_location_user#footnotes)^|支持| |^|查询字段|支持| |^|超时时间|不支持| |^|请求正文|支持| |^|请求头部 (名字和值)|支持| |^|返回状态码|支持| |^|HTTP认证用户名|支持| |^|HTTP认证密码|支持| |*过滤器*|<|<| | |正则表达式|支持| |*覆盖*|<|<| | |过滤器：正则表达式|支持| |^|操作: 更新间隔 (对于监控项原型)|不支持| |^|操作: 历史存储周期 (对于监控项原型)|不支持| |^|操作: 趋势存储周期 (对于监控项原型)|不支持|

en-us	#### Low-level discovery macros  Even though no low-level discovery macros are created in the returned JSON, these macros can be defined by the user as an additional step, using the [custom LLD macro](/manual/discovery/low_level_discovery#custom_macros) functionality with JSONPath pointing to the discovered values in the returned JSON.  The macros then can be used to create item, trigger, etc prototypes.
zh-cn	#### 低级别自动发现的宏  就算低级别自动发现返回的JSON数组中未创建任何宏，也可以使用一个额外步骤来定义宏，通过使用 [自定义LLD 宏](/manual/discovery/low_level_discovery#custom_macros)，将JSONPath指向返回的JSON值。  然后这些宏就可用于创建监控项、触发器等原型。

en-us	# maintenance.create
zh-cn	# 创建维护模式

en-us	# maintenance.delete
zh-cn	# 删除维护模式

en-us	# maintenance.get
zh-cn	# 获取维护期

en-us	# > Maintenance object  The following objects are directly related to the `maintenance` API.
zh-cn	# > 维护模式对象  如下对象与`维护模式`API关联。

en-us	# Maintenance  This class is designed to work with maintenances.  Object references:\  -   [Maintenance](/manual/api/reference/maintenance/object#maintenance) -   [Time period](/manual/api/reference/maintenance/object#time_period)  Available methods:\  -   [maintenance.create](/manual/api/reference/maintenance/create) -     creating new maintenances -   [maintenance.delete](/manual/api/reference/maintenance/delete) -     deleting maintenances -   [maintenance.get](/manual/api/reference/maintenance/get) -     retrieving maintenances -   [maintenance.update](/manual/api/reference/maintenance/update) -     updating maintenances
zh-cn	# 维护  此类用于维护. 对象引用:\  -   [维护](/manual/api/reference/maintenance/object#维护模式) -   [时间段](/manual/api/reference/maintenance/object#时间段)  可用方法:\  -   [maintenance.create](/manual/api/reference/maintenance/create)创建维护 -   [maintenance.delete](/manual/api/reference/maintenance/delete) 删除维护 -   [maintenance.get](/manual/api/reference/maintenance/get)检索维护 -   [maintenance.update](/manual/api/reference/maintenance/update)更新维护

en-us	# maintenance.update
zh-cn	# 更新维护期设置

en-us	# map.create
zh-cn	# 拓扑图创建

en-us	# map.delete
zh-cn	# 拓扑图删除