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 access rights to persistent storage files are removed during agent operation or other errors occur (e.g. disk full) then errors are logged into the agent log file but the log item does not become NOTSUPPORTED.  
zh-cn	如果在代理操作期间删除了对持久存储文件的访问权限或发生其他错误（例如磁盘已满），则错误将记录到代理日志文件中，但日志项不会变为 NOTSUPPORTED。

en-us	##### If the webhook test fails  -   *"Media type test failed."* message is displayed, followed by     additional failure details.
zh-cn	##### 当 webhook 类型测试失败  -   操作界面会提示信息*"Media type test failed."* ，有关测试失败的详细信息也会同时展示。

en-us	##### If the webhook test is successful  -   *"Media type test successful."* message is displayed -   Server response appears in the gray *Response* field -   Response type (JSON or String) is specified below the *Response*     field
zh-cn	##### 当 webhook 类型测试成功  -   界面将显示*"Media type test successful."* -   服务器响应会提示在 *Response* 灰色信息栏中 -   *Response* 信息栏下方会详细标注响应类型（JSON 或 String）

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	#### - Images  The Images section displays all the images available in Zabbix. Images are stored in the database.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_images.png){width="600"}  The *Type* dropdown allows you to switch between icon and background images:  -   Icons are used to display [network     map](/manual/config/visualization/maps/map) elements -   Backgrounds are used as background images of network maps  **Adding image**  You can add your own image by clicking on the *Create icon* or *Create background* button in the top right corner.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_img_upload.png)  Image attributes:  |Parameter|Description| |---------|-----------| |*Name*|Unique name of an image.| |*Upload*|Select the file (PNG, JPEG, GIF) from a local system to be uploaded to Zabbix.<br>*Note* that it may be possible to upload other formats that will be converted to PNG during upload. GD library is used for image processing, therefore formats that are supported depend on the library version used (2.0.28 or higher is required by Zabbix).|  ::: noteclassic Maximum size of the upload file is limited by the value of ZBX\_MAX\_IMAGE\_SIZE that is 1024x1024 bytes or 1 MB.\ \ The upload of an image may fail if the image size is close to 1 MB and the `max_allowed_packet` MySQL configuration parameter is at a default of 1MB. In this case, increase the [max\_allowed\_packet](http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_max_allowed_packet) parameter. :::
zh-cn	#### - 图片  图片部分显示了 Zabbix 中所有可用的图片。图像存储在数据库中。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_images.png){width="600"}  *Type* 下拉菜单允许您在图标和背景图像之间切换：  - · 图标用于显示[network map](/manual/config/visualization/maps/map) 元素 - · 背景用作网络地图的背景图片  **添加图片**  您可以通过单击右上角的*创建图标*或*创建背景*按钮来添加自己的图像。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_img_upload.png)  图片属性：  |参数|说明| |---------|------------| |*名称*|图像的唯一名称。| |*上传*|从本地系统中选择要上传到 Zabbix 的文件（PNG、JPEG、GIF）。<br>*注意*可能会上传其他在上传过程中会转换为 PNG 的格式。 GD 库用于图像处理，因此支持的格式取决于使用的库版本（Zabbix 需要 2.0.28 或更高版本）。|  ::: 经典笔记 上传文件的最大大小受 ZBX\_MAX\_IMAGE\_SIZE 值的限制，即 1024x1024 字节或 1 MB。 如果图像大小接近 1 MB，并且 MySQL 配置参数的“max_allowed_pa​​cket”默认为 1MB，则图像上传可能会失败。在这种情况下，增加 [max\_allowed\_packet](http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_max_allowed_pa​​cket) 范围。 :::

en-us	### Image  The image object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |imageid|string|*(readonly)* ID of the image.| |**name**<br>(required)|string|Name of the image.| |imagetype|integer|Type of image.<br><br>Possible values:<br>1 - *(default)* icon;<br>2 - background image.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 图像  图像对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |imageid|string|*（只读）*图像 ID。| |**name**<br>（必需）|string|图像名称。| |imagetype|integer|图像类型。<br><br>可用值：<br>1 - *（默认）* 图标；<br>2 - 背景图。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

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	 ### Implementation details  The high availability (HA) cluster is an opt-in solution and it is supported for Zabbix server. The native HA solution is designed to be simple in use, it will work across sites and does not have specific requirements for the databases that Zabbix recognizes. Users are free to use the native Zabbix HA solution, or a third party HA solution, depending on what best suits the high availability requirements in their environment.  The solution consists of multiple zabbix\_server instances or nodes. Every node:  -   is configured separately -   uses the same database -   may have several modes: active, standby, unavailable, stopped  Only one node can be active (working) at a time. A standby node runs only one  process - the HA manager. A standby node does no data collection,  processing or other regular server activities; they do not listen  on ports; they have minimum database connections.  Both active and standby nodes update their last access time every 5 seconds. Each standby node monitors the last access time of the active node. If the last access time of the active node is over 'failover delay' seconds, the standby node switches itself to be the active node and assigns 'unavailable' status to the previously active node.  The active node monitors its own database connectivity - if it is lost for more than `failover delay-5` seconds, it must stop all processing and switch to standby mode. The active node also monitors the status of the standby nodes - if the last access time of a standby node is over 'failover delay' seconds, the standby node is assigned the 'unavailable' status.  The nodes are designed to be compatible across minor Zabbix versions.
zh-cn	### 实施细节  Zabbix server 支持高可用性(HA)集群是一个可选择的解决方案。本地HA解决方案被设计为易于使用，它可以跨站点工作，并且对Zabbix识别的数据库没有特定的要求。用户可以自由地使用本地Zabbix HA解决方案或第三方HA解决方案，这取决于什么最适合其环境中的高可用性需求。  该解决方案由多个zabbix\_server实例或节点组成。  每一个节点: -   单独配置 -   使用相同的数据库 -   可能有几种模式: active, standby, unavailable, stopped  一次只能有一个节点处于活动状态(工作)。 备节点只运行一个进程——HA管理器。备用节点不进行数据收集、处理或其他常规server活动; 它不监听端口; 它们拥有最少的数据库连接。  主节点和备节点每5秒更新一次上次访问时间。每个备节点监控主节点的最后一次访问时间。如果主节点的最后一次访问时间超过了“故障转移延迟”秒，备用节点将自己切换为主节点，并将“不可用”状态分配给先前的主节点。  主节点监视自己的数据库连接—如果丢失超过“故障转移延迟-5”秒，它必须停止所有处理并切换到备用模式。主节点还监视备用节点的状态——如果备用节点的最后访问时间超过了“故障转移延迟”秒，备用节点将被分配为“不可用”状态。  这些节点被设计成跨较小的Zabbix版本兼容。

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/doc/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix  For proxy with PostgreSQL (or SQLite):      # cat /usr/share/doc/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix     # cat /usr/share/doc/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db
zh-cn	 ##### 导入数据  导入初始数据库模式      # cat /usr/share/doc/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix  对于使用 PostgreSQL（或 SQLite）的 proxy：      # cat /usr/share/doc/zabbix-sql-scripts/postgresql/proxy.sql | sudo -u zabbix psql zabbix     # cat /usr/share/doc/zabbix-sql-scripts/sqlite3/proxy.sql | sqlite3 zabbix.db

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

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

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

en-us	#### Importing data  Now import initial schema and data for the **server** with MySQL:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/mysql/create.sql.gz | mysql -uzabbix -p zabbix  You will be prompted to enter your newly created database password.  With PostgreSQL:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/create.sql.gz | sudo -u zabbix psql zabbix  With TimescaleDB, in addition to the previous command, also run:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u <username> psql zabbix  ::: notewarning TimescaleDB is supported with Zabbix server only. :::  For proxy, import initial schema:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/mysql/schema.sql.gz | mysql -uzabbix -p zabbix  For proxy with PostgreSQL:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/schema.sql.gz | sudo -u zabbix psql zabbix
zh-cn	#### 数据导入  使用MySQL导入**server** 初始模式和数据：      # zcat /usr/share/doc/packages/zabbix-sql-scripts/mysql/create.sql.gz | mysql -uzabbix -p zabbix  系统将提示你输入新创建的数据库密码。  使用PostgreSQL:      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/create.sql.gz | sudo -u zabbix psql zabbix  使用TimescaleDB，除了前面的命令，还要运行：      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u <username> psql zabbix  ::: notewarning 仅Zabbix server支持TimescaleDB。 :::  对于proxy，导入初始模式：      # zcat /usr/share/doc/packages/zabbix-sql-scripts/mysql/schema.sql.gz | mysql -uzabbix -p zabbix  对于带有PostgreSQL的proxy：      # zcat /usr/share/doc/packages/zabbix-sql-scripts/postgresql/schema.sql.gz | sudo -u zabbix psql zabbix

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

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

en-us	#### Importing data with Timescale DB  With TimescaleDB, in addition to the import command for PostgreSQL, also run:      # zcat /usr/share/doc/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u zabbix psql zabbix  ::: notewarning TimescaleDB is supported with Zabbix server only. :::  
zh-cn	#### 使用 Timescale DB导入数据  对于 TimescaleDB, 除了PostgreSQL的导入的命令外，还可运行:      # zcat /usr/share/doc/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u zabbix psql zabbix  ::: 警示 仅Zabbix server支持TimescaleDB。 :::  

en-us	#### Importing data with Timescale DB  With TimescaleDB, in addition to the import command for PostgreSQL, also run:      # zcat /usr/share/doc/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u zabbix psql zabbix  ::: notewarning TimescaleDB is supported with Zabbix server only. :::  
zh-cn	#### 使用 Timescale DB导入数据  对于 TimescaleDB, 除了PostgreSQL的导入的命令外, 还可运行:      # zcat /usr/share/doc/zabbix-sql-scripts/postgresql/timescaledb.sql.gz | sudo -u zabbix psql zabbix  ::: 警告 仅Zabbix server支持TimescaleDB。 :::  

en-us	#### Importing hosts and items  Import the host and items contained in the XML string. If any items in XML are missing, they will be deleted from the database, and everything else will be left unchanged.  Request:  ```json {     "jsonrpc": "2.0",     "method": "configuration.import",     "params": {         "format": "xml",         "rules": {             "valueMaps": {                 "createMissing": true,                 "updateExisting": false             },             "hosts": {                 "createMissing": true,                 "updateExisting": true             },             "items": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             }         },         "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>5.4</version><date>2020-03-13T15:31:45Z</date><groups><group><uuid>6f6799aa69e844b4b3918f779f2abf08</uuid><name>Zabbix servers</name></group></groups><hosts><host><host>Export host</host><name>Export host</name><groups><group><name>Zabbix servers</name></group></groups><interfaces><interface><interface_ref>if1</interface_ref></interface></interfaces><items><item><name>Item</name><key>item.key</key><delay>30s</delay><valuemap><name>Host status</name></valuemap><interface_ref>if1</interface_ref><request_method>POST</request_method></item></items><valuemaps><valuemap><name>Host status</name><mappings><mapping><value>0</value><newvalue>Up</newvalue></mapping><mapping><value>2</value><newvalue>Unreachable</newvalue></mapping></mappings></valuemap></valuemaps></host></hosts></zabbix_export>"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ```json {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```
zh-cn	#### 导入主机和监控项  导入的主机和监控项包含在 XML 字符串中。 如果在 XML 中遗漏了任何监控项，这些监控项将会在数据库中被删除，其他的则不改变。  请求:  ```json {     "jsonrpc": "2.0",     "method": "configuration.import",     "params": {         "format": "xml",         "rules": {             "valueMaps": {                 "createMissing": true,                 "updateExisting": false             },             "hosts": {                 "createMissing": true,                 "updateExisting": true             },             "items": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             }         },         "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<zabbix_export><version>5.4</version><date>2020-03-13T15:31:45Z</date><groups><group><uuid>6f6799aa69e844b4b3918f779f2abf08</uuid><name>Zabbix servers</name></group></groups><hosts><host><host>Export host</host><name>Export host</name><groups><group><name>Zabbix servers</name></group></groups><interfaces><interface><interface_ref>if1</interface_ref></interface></interfaces><items><item><name>Item</name><key>item.key</key><delay>30s</delay><valuemap><name>Host status</name></valuemap><interface_ref>if1</interface_ref><request_method>POST</request_method></item></items><valuemaps><valuemap><name>Host status</name><mappings><mapping><value>0</value><newvalue>Up</newvalue></mapping><mapping><value>2</value><newvalue>Unreachable</newvalue></mapping></mappings></valuemap></valuemaps></host></hosts></zabbix_export>"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {     "jsonrpc": "2.0",     "result": true,     "id": 1 } ```

en-us	#### Importing hosts and items  Import the template and items contained in the YAML string. If any items in YAML are missing, they will be shown as deleted, and everything else will be left unchanged.  Request:  ```json {     "jsonrpc": "2.0",     "method": "configuration.import",     "params": {         "format": "xml",         "rules": {             "groups": {                 "createMissing": true,                 "updateExisting": true             },             "templates": {                 "createMissing": true,                 "updateExisting": true             },             "items": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "triggers": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "discoveryRules": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "valueMaps": {                 "createMissing": true,                 "updateExisting": false             }         },         "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><zabbix_export><version>5.4</version><date>2021-05-27T07:12:07Z</date><groups><group><uuid>6f6799aa69e844b4b3918f779f2abf08</uuid><name>Zabbix servers</name></group></groups><templates><template><uuid>e1bde9bf2f0544f5929f45b82502e744</uuid><template>Export template</template><name>Export template</name><groups><group><name>Zabbix servers</name></group></groups><items><item><uuid>3237bc89226e42ed8207574022470e83</uuid><name>Item</name><key>item.key</key><delay>30s</delay><valuemap><name>Host status</name></valuemap><triggers><trigger><uuid>bd1ed0089e4b4f35b762c9d6c599c348</uuid><expression>last(/Export template/item.key)=0</expression><name>Trigger</name></trigger></triggers></item></items><discovery_rules><discovery_rule><uuid>c91616bcf4a44f349539a1b40cb0979d</uuid><name>Discovery rule</name><key>rule.key</key><item_prototypes><item_prototype><uuid>7e164881825744248b3039af3435cf4b</uuid><name>Item prototype</name><key>prototype.key</key></item_prototype></item_prototypes></discovery_rule></discovery_rules><valuemaps><valuemap><uuid>7e666857c5df4af3a338349586f2afc3</uuid><name>Host status</name><mappings><mapping><value>0</value><newvalue>Up</newvalue></mapping><mapping><value>2</value><newvalue>Unreachable</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  Response:  ``` {.java} {    "jsonrpc":"2.0",    "result":{       "templates":{          "updated":[             {                "before":{                   "uuid":"e1bde9bf2f0544f5929f45b82502e744",                   "template":"Export template",                   "name":"Export template"                },                "after":{                   "uuid":"e1bde9bf2f0544f5929f45b82502e744",                   "template":"Export template",                   "name":"Export template"                },                "items":{                   "added":[                      {                         "after":{                            "uuid":"3237bc89226e42ed8207574022470e83",                            "name":"Item",                            "key":"item.key",                            "delay":"30s",                            "valuemap":{                               "name":"Host status"                            }                         },                         "triggers":{                            "added":[                               {                                  "after":{                                     "uuid":"bd1ed0089e4b4f35b762c9d6c599c348",                                     "expression":"last(/Export template/item.key)=0",                                     "name":"Trigger"                                  }                               }                            ]                         }                      }                   ],                   "removed":[                      {                         "before":{                            "uuid":"bd3e7b28b3d544d6a83ed01ddaa65ab6",                            "name":"Old Item",                            "key":"ite_old.key",                            "delay":"30s",                            "valuemap":{                               "name":"Host status"                            }                         }                      }                   ]                },                "discovery_rules":{                   "updated":[                      {                         "before":{                            "uuid":"c91616bcf4a44f349539a1b40cb0979d",                            "name":"Discovery rule",                            "key":"rule.key"                         },                         "after":{                            "uuid":"c91616bcf4a44f349539a1b40cb0979d",                            "name":"Discovery rule",                            "key":"rule.key"                         },                         "item_prototypes":{                            "updated":[                               {                                  "before":{                                     "uuid":"7e164881825744248b3039af3435cf4b",                                     "name":"Old item prototype",                                     "key":"prototype_old.key"                                  },                                  "after":{                                     "uuid":"7e164881825744248b3039af3435cf4b",                                     "name":"Item prototype",                                     "key":"prototype.key"                                  }                               }                            ]                         }                      }                   ]                }             }          ]       }    },    "id":1 } ```
zh-cn	#### 导入主机和监控项  导入YAML字符串中包含的模板和监控项。如果在YAML中缺失的监控项，它们将显示为已删除，其它内容将保持不变。  请求:  ```json {     "jsonrpc": "2.0",     "method": "configuration.import",     "params": {         "format": "xml",         "rules": {             "groups": {                 "createMissing": true,                 "updateExisting": true             },             "templates": {                 "createMissing": true,                 "updateExisting": true             },             "items": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "triggers": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "discoveryRules": {                 "createMissing": true,                 "updateExisting": true,                 "deleteMissing": true             },             "valueMaps": {                 "createMissing": true,                 "updateExisting": false             }         },         "source": "<?xml version=\"1.0\" encoding=\"UTF-8\"?><zabbix_export><version>5.4</version><date>2021-05-27T07:12:07Z</date><groups><group><uuid>6f6799aa69e844b4b3918f779f2abf08</uuid><name>Zabbix servers</name></group></groups><templates><template><uuid>e1bde9bf2f0544f5929f45b82502e744</uuid><template>Export template</template><name>Export template</name><groups><group><name>Zabbix servers</name></group></groups><items><item><uuid>3237bc89226e42ed8207574022470e83</uuid><name>Item</name><key>item.key</key><delay>30s</delay><valuemap><name>Host status</name></valuemap><triggers><trigger><uuid>bd1ed0089e4b4f35b762c9d6c599c348</uuid><expression>last(/Export template/item.key)=0</expression><name>Trigger</name></trigger></triggers></item></items><discovery_rules><discovery_rule><uuid>c91616bcf4a44f349539a1b40cb0979d</uuid><name>Discovery rule</name><key>rule.key</key><item_prototypes><item_prototype><uuid>7e164881825744248b3039af3435cf4b</uuid><name>Item prototype</name><key>prototype.key</key></item_prototype></item_prototypes></discovery_rule></discovery_rules><valuemaps><valuemap><uuid>7e666857c5df4af3a338349586f2afc3</uuid><name>Host status</name><mappings><mapping><value>0</value><newvalue>Up</newvalue></mapping><mapping><value>2</value><newvalue>Unreachable</newvalue></mapping></mappings></valuemap></valuemaps></template></templates></zabbix_export>"     },     "auth": "038e1d7b1735c6a5436ee9eae095879e",     "id": 1 } ```  响应:  ```json {    "jsonrpc":"2.0",    "result":{       "templates":{          "updated":[             {                "before":{                   "uuid":"e1bde9bf2f0544f5929f45b82502e744",                   "template":"Export template",                   "name":"Export template"                },                "after":{                   "uuid":"e1bde9bf2f0544f5929f45b82502e744",                   "template":"Export template",                   "name":"Export template"                },                "items":{                   "added":[                      {                         "after":{                            "uuid":"3237bc89226e42ed8207574022470e83",                            "name":"Item",                            "key":"item.key",                            "delay":"30s",                            "valuemap":{                               "name":"Host status"                            }                         },                         "triggers":{                            "added":[                               {                                  "after":{                                     "uuid":"bd1ed0089e4b4f35b762c9d6c599c348",                                     "expression":"last(/Export template/item.key)=0",                                     "name":"Trigger"                                  }                               }                            ]                         }                      }                   ],                   "removed":[                      {                         "before":{                            "uuid":"bd3e7b28b3d544d6a83ed01ddaa65ab6",                            "name":"Old Item",                            "key":"ite_old.key",                            "delay":"30s",                            "valuemap":{                               "name":"Host status"                            }                         }                      }                   ]                },                "discovery_rules":{                   "updated":[                      {                         "before":{                            "uuid":"c91616bcf4a44f349539a1b40cb0979d",                            "name":"Discovery rule",                            "key":"rule.key"                         },                         "after":{                            "uuid":"c91616bcf4a44f349539a1b40cb0979d",                            "name":"Discovery rule",                            "key":"rule.key"                         },                         "item_prototypes":{                            "updated":[                               {                                  "before":{                                     "uuid":"7e164881825744248b3039af3435cf4b",                                     "name":"Old item prototype",                                     "key":"prototype_old.key"                                  },                                  "after":{                                     "uuid":"7e164881825744248b3039af3435cf4b",                                     "name":"Item prototype",                                     "key":"prototype.key"                                  }                               }                            ]                         }                      }                   ]                }             }          ]       }    },    "id":1 } ```

en-us	#### Importing  To import hosts, do the following:  -   Go to: *Configuration* → *Hosts* -   Click on *Import* to the right -   Select the import file -   Mark the required options in import rules -   Click on *Import*  ![](../../../assets/en/manual/xml_export_import/import_hosts.png)  A success or failure message of the import will be displayed in the frontend.  Import rules:  |Rule|Description| |----|-----------| |*Update existing*|Existing elements will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new elements using data from the import file. Otherwise it will not add them.| |*Delete missing*|The import will remove existing elements not present in the import file. Otherwise it will not remove them.<br>If *Delete missing* is marked for template linkage, existing template linkage not present in the import file will be removed from the host along with all entities inherited from the potentially unlinked templates (items, triggers, etc).|
zh-cn	 #### 导入  导入主机，按照如下操作：  -   切换到：_配置（Configuration）_  →  _主机（Hosts）_ -   单击右侧的_导入（Import）_按钮 -   选择导入文件 -   标记导入规则里的必选项 -   单击_导入（Import）_按钮  ![](../../../assets/en/manual/xml_export_import/import_hosts.png)  导入的成功或失败消息将显示在前端。  导入规则:  |规则|描述| |----|-----------| |*更新已经存在*|现有元素将使用从导入文件中获取的数据进行更新。否则它们将不会被更新。| |*创建新的*|导入将使用导入文件中的数据添加新元素。否则它就不会添加它们。| |*删除缺失值*|导入将删除导入文件中不存在的现有元素。否则它不会移除它们<br>如果为模板链接标记了*Delete missing*，则导入文件中不存在的现有模板链接将与从可能未链接的模板继承的所有实体（监控项、触发器等）一起从主机中删除。|

en-us	#### Importing  To import media types, do the following:  -   Go to: *Administration* → *Media types* -   Click on *Import* to the right -   Select the import file -   Mark the required options in import rules -   Click on *Import*  ![](../../../assets/en/manual/xml_export_import/import_media.png)  A success or failure message of the import will be displayed in the frontend.  Import rules:  |Rule|Description| |----|-----------| |*Update existing*|Existing elements will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new elements using data from the import file. Otherwise it will not add them.| |*Delete missing*|The import will remove existing elements not present in the import file. Otherwise it will not remove them.|
zh-cn	 #### 导入时  导入媒介类型步骤如下：  -   前往: *Administration* → *Media types* -   点击右边的*导入* -   选择要导入的文件 -   在导入规则中标记所需的选项 -   点击 *导入*  ![](../../../assets/en/manual/xml_export_import/import_media.png)  导入成功或失败的消息将在前端页面上显示。  导入规则:  |规则|描述| |----|-----------| |*Update existing*|从导入文件中获取的数据更新。否则它们将不会被更新。| |*Create new*|文件中的数据添加新元素。否则将不会添加它们。| |*Delete missing*|在导入的文件中，该元素将会被删除。否则不会删除它们。|

en-us	#### Importing  To import network maps, do the following:  -   Go to: *Monitoring* → *Maps* -   Click on *Import* to the right -   Select the import file -   Mark the required options in import rules -   Click on *Import*  ![](../../../assets/en/manual/xml_export_import/import_maps.png)  All mandatory input fields are marked with a red asterisk.  A success or failure message of the import will be displayed in the frontend.  Import rules:  |Rule|Description| |----|-----------| |*Update existing*|Existing maps will be updated with data taken from the import file. Otherwise they will not be updated.| |*Create new*|The import will add new maps using data from the import file. Otherwise it will not add them.|  If you uncheck both map options and check the respective options for images, images only will be imported. Image importing is only available to Super Admin users.  ::: notewarning If replacing an existing image, it will affect all maps that are using this image. :::
zh-cn	 #### 导入时  导入网络拓扑图，请执行以下操作:  -   前往: *Monitoring* → *Maps* -   点击右边的 *Import* -   选择导入文件 -   在导入规则中标记所需的选项 -   点击 *Import*  ![](../../../assets/en/manual/xml_export_import/import_maps.png)  所有强制输入字段都用红色星号标记。  前端将显示导入成功或失败的消息。  导入规则：  |规则|描述| |----|-----------| |*Update existing*|现有的拓扑图将使用从导入文件中获取的数据进行更新。 否则它们将不会被更新。| |*Create new*|导入将使用导入文件中的数据添加新的拓扑图。 否则它将不会添加它们。|  如果您取消这两个拓扑图选项，并检查图像的相应选项，则只会导入图像。 图像导入只对超级管理员用户有效。  ::: 警告注意 如果替换现有的图像，将影响使用该图像的所有拓扑图 :::

en-us	#### Importing  To import templates, do the following:  -   Go to: *Configuration* → *Templates* -   Click on *Import* to the right -   Select the import file -   Mark the required options in import rules -   Click on *Import*  ![](../../../assets/en/manual/xml_export_import/import_templates.png)  All mandatory input fields are marked with a red asterisk.  Import rules:  |Rule|Description| |----|-----------| |*Update existing*|Existing elements will be updated with data taken from the import file. Otherwise, they will not be updated.| |*Create new*|The import will add new elements using data from the import file. Otherwise, it will not add them.| |*Delete missing*|The import will remove existing elements not present in the import file. Otherwise, it will not remove them.<br>If *Delete missing* is marked for template linkage, existing template linkage not present in the import file will be removed from the template along with all entities inherited from the potentially unlinked templates (items, triggers, etc).|  On the next screen, you will be able to view the content of a template being imported. If this is a new template all elements will be listed in green. If updating an existing template, new template elements are highlighted in green; removed template elements are highlighted in red; elements that have not changed are listed on a gray background.  ![](../../../assets/en/manual/xml_export_import/import_templates1.png){width="600"}  The menu on the left can be used to navigate through the list of changes. Section *Updated* highlights all changes made to existing template elements. Section *Added* lists new template elements. The elements in each section are grouped by element type; press on the gray arrow down to expand or collapse the group of elements.  ![](../../../assets/en/manual/xml_export_import/templates_import_menu.png)  Review template changes, then press *Import* to perform template import. A success or failure message of the import will be displayed in the frontend.
zh-cn	 #### 导入时  导入模板的步骤如下:  -   前往: *配置* → *模板* -   点击右边的*Import* -   选择导入文件 -   在导入规则中标记所需的选项 -   点击 *导入*  ![](../../../assets/en/manual/xml_export_import/import_templates.png)  所有强制输入字段都用红色星号标记。  导入规则：  |规则|描述| |----|-----------| |*更新现有的*|现有元素将使用从导入文件中获取的数据进行更新。 否则，它们将不会被更新。| |*创建新的*|导入将使用导入文件中的数据添加新元素。 否则，它将不会添加它们。| |*删除错误*|导入将删除导入文件中不存在的现有元素。 否则，它将不会删除它们。<br>如果将 *删除错误*标记为模板链接，则导入文件中不存在的现有模板链接将从模板中移除，同时移除从可能未链接的模板中继承的所有实体(监控项, 触发器, 等等)。|  在下一个屏幕上，您将能够查看导入的模板的内容。 如果这是一个新模板，所有的元素将以绿色列出。 如果更新一个现有的模板，新的模板元素会以绿色高亮显示; 删除的模板元素用红色高亮显示; 未更改的元素以灰色背景列出。  ![](../../../assets/en/manual/xml_export_import/import_templates1.png){width="600"}  可以使用左边的菜单浏览更改列表。 部分*被更新*突出显示了对现有模板元素所做的所有更改。 章节*被添加*列出了新的模板元素。 每个部分中的元素按元素类型分组; 向下按灰色箭头以展开或折叠元素组。  ![](../../../assets/en/manual/xml_export_import/templates_import_menu.png)  查看模板更改，然后按*导入*执行模板导入。 前端将显示导入成功或失败的消息。

en-us	### Improved performance of history syncers  The performance of history syncers has been improved by introducing a new read-write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only by the configuration syncer performing a configuration cache reload.
zh-cn	### 改进了历史同步器的性能  通过引入新的读写锁提高了历史同步器的性能。这通过在访问配置缓存时使用共享读锁减少了历史同步器、捕获器和代理轮询器之间的锁定。新锁只能由 配置同步器执行配置缓存重新加载。

en-us	### Improved performance of history syncers  The performance of history syncers has been improved by introducing a new read-write lock. This reduces locking between history syncers, trappers and proxy pollers by using a shared read lock while accessing the configuration cache. The new lock can be write locked only by the configuration syncer performing a configuration cache reload.
zh-cn	### 改进了历史同步器的性能  通过引入新的读写锁提高了历史同步器的性能。这通过在访问配置缓存时使用共享读锁减少了历史同步器、捕获器和代理轮询器之间的锁定。新锁只能由 配置同步器执行配置缓存重新加载。

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 addition to the parameters that are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets, you may set the following specific options:  |   |   | |---|---| |*Host groups*|Select host groups to be displayed on the map. This field is auto-complete so starting to type the name of a group will offer a dropdown of matching groups. Scroll down to select. Click on 'x' to remove selected groups. <br>If nothing is selected in both *Host groups* and *Hosts* fields, all hosts with valid coordinates will be displayed.| |*Hosts*|Select hosts to be displayed all the map. This field is auto-complete so starting to type the name of a host will offer a dropdown of matching hosts. Scroll down to select. Click on 'x' to remove selected hosts. <br>If nothing is selected in both *Host groups* and *Hosts* fields, all hosts with valid coordinates will be displayed.| |*Tags*|Specify tags to limit the number of hosts displayed in the widget. It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br>There are several operators available for each condition:<br>**Exists** - include the specified tag names<br>**Equals** - include the specified tag names and values (case-sensitive)<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>**Does not exist** - exclude the specified tag names<br>**Does not equal** - exclude the specified tag names and values (case-sensitive)<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive)<br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition<br>**Or** - enough if one condition is met| |*Initial view*|Comma-separated center coordinates and an optional zoom level to display when the widget is initially loaded in the format `<latitude>,<longitude>,<zoom>`<br>If initial zoom is specified, the Geomap widget is loaded at the given zoom level. Otherwise, initial zoom is calculated as half of the [max zoom](/manual/web_interface/frontend_sections/administration/general#geographical_maps) for the particular tile provider.<br>The initial view is ignored if the default view is set (see below).<br>Examples:<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891|
zh-cn	[通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的配置参数对所有组件都是可用的，您还可以设置下列专属配置项：  | | | |---|---| |*主机组*|选择要在地图上显示的主机组。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机组名称。点击'x'来移除已选择的主机组。<br>如果在 *主机组* 和 *主机* 字段中均未选择任何内容，所有具有有效坐标的主机都会被显示出来。| |*主机*|选择要在地图上显示的主机。这个字段支持自动补全，输入一个组的名称在下拉框选择你需要的主机名称。点击'x'来移除已选择的主机。 <br>如果在 *主机组* 和 *主机*两个字段都没有选择内容，所有具有有效坐标的主机都会被显示出来。| |*标签*|指定标签以控制组件中显示的主机数量。支持包含以及排除特定的标签和标签值。支持多条件限定。标签名称匹配区分大小写。<br>可用的判断运算符：<br>**Exists** - 包含指定的标签名称<br>**Equals** - 包含指定的标记名称和值（区分大小写）<br>**Contains** - 指定的标签值包含输入的字符串（支持通配，不区分大小写）<br>**Does not exist** - 排除指定的标签名称<br>**Does not equal** - 排除指定的标签名称和值（区分大小写）<br>**Does not contain** - 不包括标签值包含输入字符串的指定标签名称（支持通配，不区分大小写）<br>有两种条件的计算类型：<br>**And/Or** - 必须满足所有条件，具有相同标签名称的条件将被Or条件分组<br >**Or** - 任一条件满足即可| |*初始视图*|逗号分隔的中心坐标和一个可选的缩放级别，以便在小组件最初加载时显示，格式为  `<latitude>,<longitude>,<zoom>`<br>如果指定了初始缩放，Geomap小组件将以给定的缩放级别加载。否则，初始缩放为 [最大缩放](/manual/web_interface/frontend_sections/administration/general#geographical_maps) 的一半。<br>如果设置了默认视图，初始视图将被忽略（见下文）。<br>示例：<br>=> 40.6892494,-74.0466891,14<br>=> 40.6892494,-122.0466891|

en-us	In addition, Zabbix provides the zabbix-selinux-policy package as part of source RPM packages for [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) and [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). This package provides a basic default policy for SELinux and makes zabbix components work out-of-the-box by allowing Zabbix to create and use sockets and enabling httpd connection to PostgreSQL (used by frontend).   The source *zabbix_policy.te* file contains the following rules:        module zabbix_policy 1.2;      require {       type zabbix_t;       type zabbix_port_t;       type zabbix_var_run_t;       type postgresql_port_t;       type httpd_t;       class tcp_socket name_connect;       class sock_file { create unlink };       class unix_stream_socket connectto;     }          #============= zabbix_t ==============     allow zabbix_t self:unix_stream_socket connectto;     allow zabbix_t zabbix_port_t:tcp_socket name_connect;     allow zabbix_t zabbix_var_run_t:sock_file create;     allow zabbix_t zabbix_var_run_t:sock_file unlink;     allow httpd_t zabbix_port_t:tcp_socket name_connect;          #============= httpd_t ==============     allow httpd_t postgresql_port_t:tcp_socket name_connect;  This package has been created to prevent users from turning off SELinux because of the configuration complexity. It contains the default policy that is sufficient to speed up Zabbix deployment and configuration. For maximum security level, it is recommended to set custom SELinux settings. 
zh-cn	此外，Zabbix 提供 zabbix-selinux-policy 包作为 [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) 和 [RHEL 7] 源 RPM 包的一部分 （http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/）。 这个包为 SELinux 提供了一个基本的默认策略，并通过允许 Zabbix 创建和使用套接字并启用到 PostgreSQL 的 httpd 连接（由前端使用）使 zabbix 组件开箱即用。  源 *zabbix_policy.te* 文件包含以下规则： ·   · module zabbix_policy 1.2;   · require {  · type zabbix_t;  · type zabbix_port_t;  · type zabbix_var_run_t;  · type postgresql_port_t;  · type httpd_t;  · class tcp_socket name_connect;  · class sock_file { create unlink };  · class unix_stream_socket connectto;  · }   ·  · #============= zabbix_t ==============  · allow zabbix_t self:unix_stream_socket connectto;  · allow zabbix_t zabbix_port_t:tcp_socket name_connect;  · allow zabbix_t zabbix_var_run_t:sock_file create;  · allow zabbix_t zabbix_var_run_t:sock_file unlink;  · allow httpd_t zabbix_port_t:tcp_socket name_connect;  ·   · #============= httpd_t ==============  · allow httpd_t postgresql_port_t:tcp_socket name_connect;  这个包的创建是为了防止用户因为配置复杂而关闭 SELinux。 它包含足以加速 Zabbix 部署和配置的默认策略。 为获得最高安全级别，建议设置自定义 SELinux 设置。

en-us	In addition, Zabbix provides the zabbix-selinux-policy package as part of source RPM packages for [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) and [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/). This package provides a basic default policy for SELinux and makes zabbix components work out-of-the-box by allowing Zabbix to create and use sockets and enabling httpd connection to PostgreSQL (used by frontend).   The source *zabbix_policy.te* file contains the following rules:        module zabbix_policy 1.2;      require {       type zabbix_t;       type zabbix_port_t;       type zabbix_var_run_t;       type postgresql_port_t;       type httpd_t;       class tcp_socket name_connect;       class sock_file { create unlink };       class unix_stream_socket connectto;     }          #============= zabbix_t ==============     allow zabbix_t self:unix_stream_socket connectto;     allow zabbix_t zabbix_port_t:tcp_socket name_connect;     allow zabbix_t zabbix_var_run_t:sock_file create;     allow zabbix_t zabbix_var_run_t:sock_file unlink;     allow httpd_t zabbix_port_t:tcp_socket name_connect;          #============= httpd_t ==============     allow httpd_t postgresql_port_t:tcp_socket name_connect;  This package has been created to prevent users from turning off SELinux because of the configuration complexity. It contains the default policy that is sufficient to speed up Zabbix deployment and configuration. For maximum security level, it is recommended to set custom SELinux settings. 
zh-cn	 此外，Zabbix 提供 zabbix-selinux-policy 包作为 [RHEL 8](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/)  和 [RHEL 7](http://repo.zabbix.com/zabbix/6.0/rhel/8/SRPMS/) 源 RPM 包的一部分。这个包为 SELinux 提供了一个基本的默认策略，并通过允许 Zabbix 创建和使用套接字并启用与 PostgreSQL 的 httpd 连接（由前端使用）使 zabbix 组件开箱即用。  源 *zabbix_policy.te*文件包含以下规则：      module zabbix_policy 1.2;      require {       type zabbix_t;       type zabbix_port_t;       type zabbix_var_run_t;       type postgresql_port_t;       type httpd_t;       class tcp_socket name_connect;       class sock_file { create unlink };       class unix_stream_socket connectto;     }          #============= zabbix_t ==============     allow zabbix_t self:unix_stream_socket connectto;     allow zabbix_t zabbix_port_t:tcp_socket name_connect;     allow zabbix_t zabbix_var_run_t:sock_file create;     allow zabbix_t zabbix_var_run_t:sock_file unlink;     allow httpd_t zabbix_port_t:tcp_socket name_connect;          #============= httpd_t ==============     allow httpd_t postgresql_port_t:tcp_socket name_connect;  创建这个包是为了防止用户因为配置复杂而关闭 SELinux。它包含足以加速 Zabbix 部署和配置的默认策略。为获得最高安全级别，建议设置自定义 SELinux 设置。 

en-us	##### Incoming connections  It is a bit more complicated with incoming connections because rules are specific for components and configuration.  For Zabbix **agent**:  |Agent connection setup|Cipher configuration| |----------------------|--------------------| |TLSConnect=cert|TLSCipherCert, TLSCipherCert13| |TLSConnect=psk|TLSCipherPSK, TLSCipherPSK13| |TLSAccept=cert|TLSCipherCert, TLSCipherCert13| |TLSAccept=psk|TLSCipherPSK, TLSCipherPSK13| |TLSAccept=cert,psk|TLSCipherAll, TLSCipherAll13|  For Zabbix **server** and \*\* proxy\*\*:  |Connection setup|Cipher configuration| |----------------|--------------------| |Outgoing connections using PSK|TLSCipherPSK, TLSCipherPSK13| |Incoming connections using certificates|TLSCipherAll, TLSCipherAll13| |Incoming connections using PSK if server has no certificate|TLSCipherPSK, TLSCipherPSK13| |Incoming connections using PSK if server has certificate|TLSCipherAll, TLSCipherAll13|  Some pattern can be seen in the two tables above:  -   TLSCipherAll and TLSCipherAll13 can be specified only if a combined     list of certificate- **and** PSK-based ciphersuites is used. There     are two cases when it takes place: server (proxy) with a configured     certificate (PSK ciphersuites are always configured on server, proxy     if crypto library supports PSK), agent configured to accept both     certificate- and PSK-based incoming connections -   in other cases TLSCipherCert\* and/or TLSCipherPSK\* are sufficient  The following tables show the `TLSCipher*` built-in default values. They could be a good starting point for your own custom values.  |Parameter|GnuTLS 3.6.12| |---------|-------------| |TLSCipherCert|NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509| |TLSCipherPSK|NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL| |TLSCipherAll|NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509|  |Parameter|OpenSSL 1.1.1d ^**1**^| |---------|----------------------| |TLSCipherCert13|<| |TLSCipherCert|EECDH+aRSA+AES128:RSA+aRSA+AES128| |TLSCipherPSK13|TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256| |TLSCipherPSK|kECDHEPSK+AES128:kPSK+AES128| |TLSCipherAll13|<| |TLSCipherAll|EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128|  ^**1**^ Default values are different for older OpenSSL versions (1.0.1, 1.0.2, 1.1.0), for LibreSSL and if OpenSSL is compiled without PSK support.  \*\* Examples of user-configured ciphersuites \*\*  See below the following examples of user-configured ciphersuites:  -   [Testing cipher strings and allowing only PFS     ciphersuites](#testing_cipher_strings_and_allowing_only_pfs_ciphersuites) -   [Switching from AES128 to AES256](#switching_from_aes128_to_aes256)
zh-cn	 ##### 传入连接  对于传入连接来说，这有点复杂，因为规则是特定于组件和配置的。  对 Zabbix **agent**:  |Agent 连接步骤|密码配置| |----------------------|--------------------| |TLSConnect=cert|TLSCipherCert, TLSCipherCert13| |TLSConnect=psk|TLSCipherPSK, TLSCipherPSK13| |TLSAccept=cert|TLSCipherCert, TLSCipherCert13| |TLSAccept=psk|TLSCipherPSK, TLSCipherPSK13| |TLSAccept=cert,psk|TLSCipherAll, TLSCipherAll13|  对 Zabbix **server** 和\*\*proxy\*\* :  |连接步骤|密码配置| |----------------|--------------------| |Outgoing connections using PSK|TLSCipherPSK, TLSCipherPSK13| |Incoming connections using certificates|TLSCipherAll, TLSCipherAll13| |Incoming connections using PSK if server has no certificate|TLSCipherPSK, TLSCipherPSK13| |Incoming connections using PSK if server has certificate|TLSCipherAll, TLSCipherAll13|  在上面的两个表中可以看到一些模式:  -  TLSCipherAll和TLSCipherAll13只能在使用基于证书**和** PSK加密套件的组合列表时指定。发生这种情况有两种情况:server(proxy)配置证书(PSK密码套件总是在server、proxy上配置如果加密库支持PSK)，agent被配置为接受基于证书和基于PSK的传入连接 -   在其他情况下，TLSCipherCert和/或TLSCipherPSK\*就足够了  下表显示了' TLSCipher* '的内置默认值。 对于您自己的定制值来说，它们可能是一个很好的起点。  |参数|GnuTLS 3.6.12| |---------|-------------| |TLSCipherCert|NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509| |TLSCipherPSK|NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL| |TLSCipherAll|NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509|  |参数|OpenSSL 1.1.1d ^**1**^| |---------|----------------------| |TLSCipherCert13|<| |TLSCipherCert|EECDH+aRSA+AES128:RSA+aRSA+AES128| |TLSCipherPSK13|TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256| |TLSCipherPSK|kECDHEPSK+AES128:kPSK+AES128| |TLSCipherAll13|<| |TLSCipherAll|EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128|  ^**1**^ 对于较早的OpenSSL版本(1.0.1,1.0.2,1.1.0)，对于LibreSSL和如果在没有PSK支持的情况下编译OpenSSL，默认值是不同的。  **用户配置的密码套件示例**  请参阅以下用户配置的密码套件示例:  -   [测试密码字符串并只允许PFS密码套件](#testing_cipher_strings_and_allowing_only_pfs_ciphersuites) -   [从AES128切换到AES256](#switching_from_aes128_to_aes256)

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	#### Incorrect request method parameter in items  The request method parameter, used only in HTTP checks, may be incorrectly set to '1', a non-default value for all items as a result of upgrade from a pre-4.0 Zabbix version. For details on how to fix this situation, see [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308).
zh-cn	#### 监控项中的请求方法参数不正确  在 HTTP 检查中使用的 request_method 参数可能被错误地设置为 “1”，监控项的非默认值是由于从 Zabbix 4.0 之前的版本升级造成的。点击 [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308) 查看解决方法。

en-us	#### Incorrect request method parameter in items  The request method parameter, used only in HTTP checks, may be incorrectly set to '1', a non-default value for all items as a result of upgrade from a pre-4.0 Zabbix version. For details on how to fix this situation, see [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308).  
zh-cn	#### 监控项中的请求方法参数不正确  在 HTTP 检查中使用的 request_method 参数可能被错误地设置为 “1”，监控项的非默认值是由于从 Zabbix 4.0 之前的版本升级造成的。点击 [ZBX-19308](https://support.zabbix.com/browse/ZBX-19308) 查看解决方法。

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	#### Individual migration of history tables  * Prepare directories for Data Pump for each history table. Data Pump must have read and write permissions to these directories.  Example:  ``` {.bash} mkdir -pv /export/history /export/history_uint /export/history_str /export/history_log /export/history_text chown -R oracle:oracle /export ```  * Create a directory object and grant read and write permissions to this object to the user used for Zabbix authentication ('zabbix' in the example below). Under *sysdba* role, run:  ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix;  create directory history_uint as '/export/history_uint'; grant read,write on directory history_uint to zabbix;  create directory history_str as '/export/history_str'; grant read,write on directory history_str to zabbix;  create directory history_log as '/export/history_log'; grant read,write on directory history_log to zabbix;  create directory history_text as '/export/history_text'; grant read,write on directory history_text to zabbix; ```  * Export and import each table. Replace N with the desired thread count.  ``` {.bash} expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old REMAP_TABLE=history_old:history data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old REMAP_TABLE=history_uint_old:history_uint data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old REMAP_TABLE=history_str_old:history_str data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old REMAP_TABLE=history_log_old:history_log data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old REMAP_TABLE=history_text_old:history_text data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ```  * Follow [post-migration instructions](#after-migration) to drop the old tables.
zh-cn	####历史表的单独迁移  * 为每个历史表准备数据泵目录。Data Pump 必须对这些目录具有读写权限。  例子：  ``` {.bash} mkdir -pv /export/history /export/history_uint /export/history_str /export/history_log /export/history_text chown -R oracle:oracle /导出 ```  * 创建一个目录对象，并将该对象的读写权限授予用于 Zabbix 身份验证的用户（下例中的“zabbix”）。 在 *sysdba* 角色下，运行：  ``` {.sql} create directory history as '/export/history'; grant read,write on directory history to zabbix;  create directory history_uint as '/export/history_uint'; grant read,write on directory history_uint to zabbix;  create directory history_str as '/export/history_str'; grant read,write on directory history_str to zabbix;  create directory history_log as '/export/history_log'; grant read,write on directory history_log to zabbix;  create directory history_text as '/export/history_text'; grant read,write on directory history_text to zabbix; ```  * 导出和导入每个表。 将 N 替换为所需的线程数。  ``` {.bash} expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history TABLES=history_old REMAP_TABLE=history_old:history data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_uint TABLES=history_uint_old REMAP_TABLE=history_uint_old:history_uint data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_str TABLES=history_str_old REMAP_TABLE=history_str_old:history_str data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_log TABLES=history_log_old REMAP_TABLE=history_log_old:history_log data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only  expdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N  impdp zabbix/password@oracle_host:1521/xe DIRECTORY=history_text TABLES=history_text_old REMAP_TABLE=history_text_old:history_text data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND PARALLEL=N CONTENT=data_only ```  * 按照 [post-migration instructions](#after-migration) 删除旧表。

en-us	### Informational
zh-cn	### 一般性的

en-us	##### Informix  Standard Informix utility **onstat** can be used for monitoring of virtually every aspect of Informix database. Also, Zabbix can retrieve information provided by Informix SNMP agent.
zh-cn	##### Informix  标准 Informix 实用程序 **onstat** 可用于监视 Informix 数据库的几乎所有方面。此外，Zabbix 可以检索 Informix 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 from packages  An official zabbix-web-service package is available for RHEL/CentOS 8, SLES 15, Debian 10, Ubuntu 18.04, Ubuntu 20.04 in the [Zabbix repository](http://repo.zabbix.com/). Google Chrome browser is not included into these packages and has to be installed separately.  
zh-cn	##### Installation from packages  An official zabbix-web-service package is available for RHEL/CentOS 8, SLES 15, Debian 10, Ubuntu 18.04, Ubuntu 20.04 in the [Zabbix repository](http://repo.zabbix.com/). Google Chrome browser is not included into these packages and has to be installed separately.  

en-us	##### Installation from sources  A configured Go version 1.13+ environment is required for building Zabbix agent 2.  To compile Zabbix web service from sources, run the `./configure` script with `--enable-webservice` option (see [Installing Zabbix web service](/manual/installation/install#installing_zabbix_web_service) for additional details).  A sample ./configure command for installing or upgrading Zabbix with addition of Zabbix web service may look like this:      ./configure --enable-server --enable-proxy --enable-agent --enable-webservice --with-mysql --enable-ipv6 --with-net-snmp --with-libcurl --with-unixodbc --with-libxml2 --with-openssl    
zh-cn	##### Installation from sources  A configured Go version 1.13+ environment is required for building Zabbix agent 2.  To compile Zabbix web service from sources, run the `./configure` script with `--enable-webservice` option (see [Installing Zabbix web service](/manual/installation/install#installing_zabbix_web_service) for additional details).  A sample ./configure command for installing or upgrading Zabbix with addition of Zabbix web service may look like this:      ./configure --enable-server --enable-proxy --enable-agent --enable-webservice --with-mysql --enable-ipv6 --with-net-snmp --with-libcurl --with-unixodbc --with-libxml2 --with-openssl    

en-us	#### Installation  Please always read the installation manual for a particular module. It is recommended to install new modules one by one to catch failures easily.  Just before you install a module:  -   Make sure you have downloaded the module from a trusted source.     Installation of harmful code may lead to consequences, such as data     loss -   Different versions of the same module (same ID) can be installed in     parallel, but only a single version can be enabled at once  Steps to install a module:  -   Unpack your module within its own folder in the `modules` folder of     the Zabbix frontend -   Ensure that your module folder contains at least the manifest.json     file -   Navigate to [Module     administration](/manual/web_interface/frontend_sections/administration/general#modules)     and click the *Scan directory* button -   New module will appear in the list along with its version, author,     description and status -   Enable module by clicking on its status  Troubleshooting:  |Problem|Solution| |-------|--------| |*Module did not appear in the list*|Make sure that the manifest.json file exists in `modules/your-module/` folder of the Zabbix frontend. If it does that means the module does not suit the current Zabbix version. If manifest.json file does not exist, you have probably unpacked in the wrong directory.| |*Frontend crashed*|The module code is not compatible with the current Zabbix version or server configuration. Please delete module files and reload the frontend. You'll see a notice that some modules are absent. Go to [Module administration](/manual/web_interface/frontend_sections/administration/general#modules) and click *Scan directory* again to remove non-existent modules from the database.| |*Error message about identical namespace, ID or actions appears*|New module tried to register a namespace, ID or actions which are already registered by other enabled modules. Disable the conflicting module (mentioned in error message) prior to enabling the new one.| |*Technical error messages appear*|Report errors to the developer of the module.|
zh-cn	 #### 安装  请始终阅读特定模块的安装手册。建议逐个安装新模块，以便更容易的找到故障。  在安装模块之前：  - 确保您已从受信任的来源下载了该模块。安装有害代码可能会导致后果，例如数据丢失 - 同一模块的不同版本（相同的ID）可以并行安装，但一次只能启用一个版本  安装模块的步骤：  - 将模块解压缩到Zabbix前端的"modules"文件夹中的自己的文件夹中 - 确保您的模块文件夹至少包含 manifest.json 文件 -   导航到 [Module administration](/manual/web_interface/frontend_sections/administration/general#modules)    并且单击 *Scan directory* 按钮 - 新模块将与其版本，作者，描述和状态一起出现在列表中 - 通过单击其状态启用模块  排错：  |问题|解决方案| |-------|--------| |*模块未出现在列表中*|确保 manifest.json 文件存在于 Zabbix 前端的 'modules/your-module/' 文件夹中。如果这样做，则意味着该模块不适合当前的Zabbix版本。如果 manifest.json 文件不存在，则可能是因为您解压到了错误的目录中。| |*前端崩溃*|模块代码与当前的Zabbix版本或服务器配置不兼容。请删除模块文件并重新加载前端。您将收到一条通知，指出某些模块不存在。转到 [Module administration](/manual/web_interface/frontend_sections/administration/general#modules) 然后再次单击 *Scan directory* 以从数据库中删除不存在的模块。| |*出现有关相同命名空间、ID 或操作的错误消息*|这是由于新模块尝试注册已由其他已启用模块注册的命名空间、ID 或操作。在启用新模块之前，禁用冲突的模块（在错误消息中提到的）。| |*出现技术错误消息*|向默块开发者报告错误|

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	#### Installation steps  To install, double-click the downloaded MSI file.  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_b.png)  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_c.png)  Accept the license to proceed to the next step.  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_d.png)  Specify the following parameters.  |Parameter|Description| |---------|-----------| |*Host name*|Specify host name.| |*Zabbix server IP/DNS*|Specify IP/DNS of Zabbix server.| |*Agent listen port*|Specify agent listen port (10050 by default).| |*Server or Proxy for active checks*|Specify IP/DNS of Zabbix server/proxy for active agent checks.| |*Enable PSK*|Mark the checkbox to enable TLS support via pre-shared keys.| |*Add agent location to the PATH*|Add agent location to the PATH variable.|  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_e.png)  Enter pre-shared key identity and value. This step is only available if you checked *Enable PSK* in the previous step.  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_f.png)  Select Zabbix components to install - [Zabbix agent daemon](/manual/concepts/agent), [Zabbix sender](/manual/concepts/sender), [Zabbix get](/manual/concepts/get).  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_g.png)  Zabbix components along with the configuration file will be installed in a *Zabbix Agent* folder in Program Files. zabbix\_agentd.exe will be set up as Windows service with automatic startup.  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_h.png)
zh-cn	 #### 安装步骤  请双击已下载的MSI文件进行安装。  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_b.png)  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_c.png)  接受许可证已进入下一步。  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_d.png)  具体参数。  |参数|描述| |---------|-----------| |*主机名*|指定主机名。| |*Zabbix server IP/DNS*|指定Zabbix server的IP/DNS。| |*Agent监听端口*|指定代理监听端口 (默认为10050)。| |*主动检查Server或Proxy*|为激活agent主动检查指定Zabbix server/proxy的IP/DNS。| |*启用PSK*|选中校验框，通过预共享密钥激活TLS支持。| |*将agent位置添加到PATH*|将agent位置添加至PATH变量。|  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_e.png)  输入预共享密钥的标识和对应值。 此步骤仅在上一步中选中 *Enable PSK* 之后才有用。  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_f.png)  选择要安装的Zabbix组件- [Zabbix agent daemon](/manual/concepts/agent), [Zabbix sender](/manual/concepts/sender), [Zabbix get](/manual/concepts/get).  ![](../../../../assets/en/manual/installation/install_from_packages/msi0_g.png)  Zabbix组件和配置文件将安装在程序文件 *Zabbix Agent* 文件夹中。 zabbix\_agentd.exe 在Windows服务中将被设置为自动启动。   ![](../../../../assets/en/manual/installation/install_from_packages/msi0_h.png)

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 agent  The agent can be installed using the graphical user interface or from the command line, for example:      sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target /  Make sure to use the correct Zabbix package version in the command. It must match the name of the downloaded package.
zh-cn	#### 安装 agent  可以使用图形用户界面安装代理，也可以从命令行。 例如:      sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target /  确保在命令中使用正确的 Zabbix 包版本。它必须与下载的程序包的名称匹配。

en-us	#### Installing agent  The agent can be installed using the graphical user interface or from the command line, for example:      sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target /  Make sure to use the correct Zabbix package version in the command. It must match the name of the downloaded package.  
zh-cn	#### 安装 agent  可以使用图形用户界面安装代理，也可以从命令行。 例如:      sudo installer -pkg zabbix_agent-5.4.0-macos-amd64-openssl.pkg -target /  确保在命令中使用正确的 Zabbix 包版本。它必须与下载的程序包的名称匹配。

en-us	### Installing debuginfo packages  ::: noteclassic  Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5.  ::: To enable debuginfo repository edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository.      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.4/rhel/8/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  This will allow you to install the zabbix-debuginfo package.      # yum install zabbix-debuginfo  This single package contains debug information for all binary Zabbix components.  
zh-cn	### 安装debuginfo包  ::: noteclassic  Debuginfo包目前适用于 RHEL/CentOS 7, 6和5版本.  ::: 为 zabbix-debuginfo 存储库启用debuginfo 存储库编辑 */etc/yum.repos.d/zabbix.repo* file. 将 `enabled=0` 改为 `enabled=1`       [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.4/rhel/8/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  就可以安装 zabbix-debuginfo包了。      # yum install zabbix-debuginfo  这个包包含所有二进制Zabbix组件的调试信息。  

en-us	### Installing debuginfo packages  :::noteclassic  Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5.  :::   To enable debuginfo repository, edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository.      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.4/rhel/8/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  This will allow you to install the zabbix-debuginfo package.      # yum install zabbix-debuginfo  This single package contains debug information for all binary Zabbix components.  
zh-cn	### 安装debuginfo包  :::noteclassic  Debuginfo软件包目前可用于 RHEL/CentOS 版本7, 6 和 5。  :::   要启用 debuginfo存储库，请编辑 */etc/yum.repos.d/zabbix.repo* 文件。将 `enabled=0` 改为`enabled=1` 用于 zabbix-debuginfo 存储库。      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.4/rhel/8/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  然后就可以安装zabbix-debuginfo软件包了。      # yum install zabbix-debuginfo  这个包包含所有二进制Zabbix组件的debug信息。  

en-us	### Installing debuginfo packages  :::noteclassic  Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5.  :::   To enable debuginfo repository, edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository.      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  This will allow you to install the zabbix-debuginfo package.      # yum install zabbix-debuginfo  This single package contains debug information for all binary Zabbix components.
zh-cn	 ### 安装debuginfo包  :::noteclassic  Debuginfo软件包目前可用于 RHEL/CentOS 版本7, 6 和 5。  :::   要启用 debuginfo 软件源，请编辑 */etc/yum.repos.d/zabbix.repo* 文件。将  `enabled=0` 改为`enabled=1` 用于 zabbix-debuginfo 存储库。      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.4/rhel/8/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  然后就可以安装zabbix-debuginfo软件包了。      # yum install zabbix-debuginfo  这个软件包里包含所有二进制 Zabbix 组件的 debug 信息。

en-us	### Installing debuginfo packages  :::noteclassic  Debuginfo packages are currently available for RHE versions 7, 6 and 5.  :::   To enable debuginfo repository, edit */etc/yum.repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository.      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo - $basearch     baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/     enabled=0     gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591     gpgcheck=1  This will allow you to install the zabbix-debuginfo package.      # yum install zabbix-debuginfo  This single package contains debug information for all binary Zabbix components.
zh-cn	### 安装调试信息包  :::noteclassic   Debuginfo 包目前可用于 RHE 版本 7、6 和 5。 ::::  要启用 debuginfo 存储库，请编辑*/etc/yum.repos.d/zabbix.repo* 文件。 将 `enabled=0` 更改为 `enabled=1`用于 zabbix-debuginfo 存储库。   · [zabbix-debuginfo]  · name=Zabbix Official Repository debuginfo - $basearch  · baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/  · enabled=0  · gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591  · gpgcheck=1  这将允许您安装 zabbix-debuginfo 包。    · # yum install zabbix-debuginfo  这个单一的包包含所有二进制 Zabbix 的调试信息组件。

en-us	### Installing debuginfo packages  To enable debuginfo repository edit */etc/zypp/repos.d/zabbix.repo* file. Change `enabled=0` to `enabled=1` for zabbix-debuginfo repository.      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo     type=rpm-md     baseurl=http://repo.zabbix.com/zabbix/4.5/sles/15/x86_64/debuginfo/     gpgcheck=1     gpgkey=http://repo.zabbix.com/zabbix/4.5/sles/15/x86_64/debuginfo/repodata/repomd.xml.key     enabled=0     update=1  This will allow you to install zabbix-***<component>***-debuginfo packages.
zh-cn	### 安装debuginfo 软件包  为了启用 debuginfo 软件源，编辑 */etc/zypp/repos.d/zabbix.repo*文件。请为 zabbix-debuginfo 软件源将`enabled=0`改为`enabled=1`。      [zabbix-debuginfo]     name=Zabbix Official Repository debuginfo     type=rpm-md     baseurl=http://repo.zabbix.com/zabbix/4.5/sles/15/x86_64/debuginfo/     gpgcheck=1     gpgkey=http://repo.zabbix.com/zabbix/4.5/sles/15/x86_64/debuginfo/repodata/repomd.xml.key     enabled=0     update=1  然后就可安装 zabbix-***<component>***-debuginfo 包了。

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 MinGW Compiler  1\. Download MinGW-w64 with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2. Extract and move to *c:\\mingw*\ 3. Setup environmental variable      @echo off     set PATH=%PATH%;c:\mingw\bin     cmd  When compiling use Windows prompt instead of MSYS terminal provided by MinGW
zh-cn	#### 安装MinGW编译器  1\. 下载带有SJLJ (设置跳转/长跳转) 异常处理和窗口线程的MinGW-w64 (例如 *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2. 提取并移动到 *c:\\mingw*\ 3. 设置环境变量      @echo off     set PATH=%PATH%;c:\mingw\bin     cmd  编译时使用Windows提示符代替MinGW提供的MSYS终端。

en-us	#### Installing MinGW Compiler  1\. Download MinGW-w64 with SJLJ (set jump/long jump) Exception Handling and Windows threads (for example *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2. Extract and move to *c:\\mingw*\ 3. Setup environmental variable      @echo off     set PATH=%PATH%;c:\mingw\bin     cmd  When compiling use Windows prompt instead of MSYS terminal provided by MinGW  
zh-cn	#### 安装MinGW编译器  1\. 下载带有SJLJ (设置跳转/长跳转) 异常处理和窗口线程的MinGW-w64 (例如 *x86\_64-8.1.0-release-win32-sjlj-rt\_v6-rev0.7z*)\ 2. 提取并移动到 *c:\\mingw*\ 3. 设置环境变量      @echo off     set PATH=%PATH%;c:\mingw\bin     cmd  编译时使用Windows提示符代替MinGW提供的MSYS终端。

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	### 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	### Integer trend  The integer trend object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |clock|timestamp|Timestamp of an hour for which the value was calculated. E. g. timestamp of 04:00:00 means values calculated for period 04:00:00-04:59:59.| |itemid|integer|ID of the related item.| |num|integer|Number of values that were available for the hour.| |value\_min|integer|Hourly minimum value.| |value\_avg|integer|Hourly average value.| |value\_max|integer|Hourly maximum value.|
zh-cn	### 整数型趋势  整数型趋势对象具有以下属性.  | 属性       | [类型](/manual/api/reference_commentary#data_types) | 描述                                                         | | ---------- | --------------------------------------------------- | ------------------------------------------------------------ | | clock      | timestamp                                           | 根据时间戳计算出一个小时内监控项的值， 例如，04:00:00 的时间戳表示为 04:00:00-04:59:59 期间计算出来的监控项的值. | | itemid     | integer                                             | 相关监控项的ID.                                              | | num        | integer                                             | 一小时内可用的值的数量是多少个.                              | | value\_min | integer                                             | 每小时内的最小值.                                            | | value\_avg | integer                                             | 每小时内的平均值.                                            | | value\_max | integer                                             | 每小时内的最大值.                                            |

en-us	### Integer trend  The integer trend object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |clock|timestamp|Timestamp of an hour for which the value was calculated. E. g. timestamp of 04:00:00 means values calculated for period 04:00:00-04:59:59.| |itemid|integer|ID of the related item.| |num|integer|Number of values that were available for the hour.| |value\_min|integer|Hourly minimum value.| |value\_avg|integer|Hourly average value.| |value\_max|integer|Hourly maximum value.|
zh-cn	### 整数型趋势  整数型趋势对象具有以下属性.  | 属性       | [类型](/manual/api/reference_commentary#data_types) | 描述                                                         | | ---------- | --------------------------------------------------- | ------------------------------------------------------------ | | clock      | timestamp                                           | 根据时间戳计算出一个小时内监控项的值， 例如，04:00:00 的时间戳表示为 04:00:00-04:59:59 期间计算出来的监控项的值. | | itemid     | integer                                             | 相关监控项的ID.                                              | | num        | integer                                             | 一小时内可用的值的数量是多少个.                              | | value\_min | integer                                             | 每小时内的最小值.                                            | | value\_avg | integer                                             | 每小时内的平均值.                                            | | value\_max | integer                                             | 每小时内的最大值.                                            |

en-us	##### Interface creation when adding hosts  When hosts are added as a result of network discovery, they get interfaces created according to these rules:  -   the services detected - for example, if an SNMP check succeeded, an     SNMP interface will be created -   if a host responded both to Zabbix agent and SNMP requests, both     types of interfaces will be created -   if uniqueness criteria are Zabbix agent or SNMP-returned data, the     first interface found for a host will be created as the default one.     Other IP addresses will be added as additional interfaces. -   if a host responded to agent checks only, it will be created with an     agent interface only. If it would start responding to SNMP later,     additional SNMP interfaces would be added. -   if 3 separate hosts were initially created, having been discovered     by the "IP" uniqueness criteria, and then the discovery rule is     modified so that hosts A, B and C have identical uniqueness criteria     result, B and C are created as additional interfaces for A, the     first host. The individual hosts B and C remain. In *Monitoring →     Discovery* the added interfaces will be displayed in the "Discovered     device" column, in black font and indented, but the "Monitored host"     column will only display A, the first created host.     "Uptime/Downtime" is not measured for IPs that are considered to be     additional interfaces.
zh-cn	##### 创建主机接口  当通过网络发现规则添加主机时，主机接口遵循以下原则创建：  -   检测到的服务 - 比如，如果一个SNMP服务被检测到，则会创建一个SNMP接口 -   如果一个主机同时对Zabbix agent和SNMP请求做出响应，则会同时创建两种接口(Zabbix agent接口和SNMP接口) -   如果设备唯一标识设置为Zabbix agent或SNMP，则会创建所发现的第一个接口并将其设置为默认接口。     发现的其它IP地址会设置为额外的接口。 -   如果主机只对Zabbix agent作出响应，则只有agent接口会被创建。如果主机以后对SNMP请求做出响应，则额外的SNMP接口会被创建。 -   如果通过网络发现规则创建三台独立的主机，并且规则中配置了设备唯一标识为"IP"，但该规则后续被修改了，并且主机A、B和C通过设备唯一标识计算出相同的结果(相同IP地址)，则B和C会变成第一台主机(主机A)的额外接口。主机B和主机C会保留。添加的接口会显示在*监控 →网络发现* 界面的"发现的设备" 一栏，用黑体字和缩进标识，但"监控的主机"一栏只显示第一个创建的主机A。     不会对额外接口的IP地址检测"运行时长/停机时长"(Uptime/Downtime)。

en-us	### Internal authentication  The *Authentication* tab allows defining custom password complexity requirements for internal Zabbix users.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth.png)  The following password policy options can be configured:  |Parameter|Description| |---------|-----------| |Minimum password length|By default, the minimum password length is set to 8. Supported range: 1-70. Note that passwords longer than 72 characters will be truncated.| |Password must contain|Mark one or several checkboxes to require usage of specified characters in a password:<br>-an uppercase and a lowercase Latin letter<br>-a digit<br>-a special character<br><br>Hover over the question mark to see a hint with the list of characters for each option.| |Avoid easy-to-guess passwords|If marked, a password will be checked against the following requirements:<br>- must not contain user's name, surname, or username<br>- must not be one of the common or context-specific passwords.<br><br>The list of common and context-specific passwords is generated automatically from the list of NCSC "Top 100k passwords", the list of SecLists "Top 1M passwords" and the list of Zabbix context-specific passwords. Internal users will not be allowed to set passwords included in this list as such passwords are considered weak due to their common use.|  Changes in password complexity requirements will not affect existing user passwords, but if an existing user chooses to change a password, the new password will have to meet current requirements. A hint with the list of requirements will be displayed next to the *Password* field in the [user profile](/manual/web_interface/user_profile) and in the [user configuration form](/manual/config/users_and_usergroups/user) accessible from the *Administration→Users* menu.
zh-cn	### 内部认证  *Authentication* 选项卡允许定义自定义密码复杂性 内部 Zabbix 用户的要求。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/auth.png)  可以配置以下密码策略选项：  |参数|说明| |---------|------------| |最小密码长度|默认情况下，最小密码长度设置为 8。支持范围：1-70。请注意，超过 72 个字符的密码将被截断。| |密码必须包含|标记一个或多个复选框以要​​求在密码中使用指定字符：<br>-一个大写和一个小写拉丁字母<br>-一个数字<br>-一个特殊字符<br><br>将鼠标悬停在问号上可查看每个选项的字符列表提示。| |避免使用容易猜到的密码|如果标记，将根据以下要求检查密码：<br>- 不得包含用户名、姓氏或用户名<br>- 不得为常见或上下文之一-特定密码。<br><br>常用密码和上下文特定密码列表是从 NCSC“前 100k 密码”列表、SecLists“前 1M 密码”列表和 Zabbix 上下文特定密码列表自动生成的.不允许内部用户设置此列表中包含的密码，因为此类密码因其常见用途而被视为弱密码。|  密码复杂性要求的变化不会影响现有的用户密码，但如果现有用户选择更改密码，新密码必须满足当前要求。一个提示要求列表将显示在 *Password* 字段旁边[用户配置](/manual/web_interface/user_profile) 和 [用户配置表单](/manual/config/users_and_usergroups/user) 可访问从*管理→用户*菜单。

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 events  Internal events happen when:  -   an item changes state from 'normal' to 'unsupported' -   an item changes state from 'unsupported' to 'normal' -   a low-level discovery rule changes state from 'normal' to     'unsupported' -   a low-level discovery rule changes state from 'unsupported' to     'normal' -   a trigger changes state from 'normal' to 'unknown' -   a trigger changes state from 'unknown' to 'normal'  Internal events are supported since Zabbix 2.2. The aim of introducing internal events is to allow users to be notified when any internal event takes place, for example, an item becomes unsupported and stops gathering data.  Internal events are only created when internal actions for these events are enabled. To stop generation of internal events (for example, for items becoming unsupported), disable all actions for internal events in Configuration → Actions → Internal actions.  ::: noteclassic  If internal actions are disabled, while an object is in the 'unsupported' state, recovery event for this object will still be created.\ \ If internal actions are enabled, while an object is in the 'unsupported' state, recovery event for this object will be created, even though 'problem event' has not been created for the object.  :::  See also: [Receiving notification on unsupported items](/manual/config/notifications/unsupported_item)
zh-cn	#### 内部事件  内部事件发生在以下情况：  -   一个监控项的状态从“正常”改变为“不支持” -   一个监控项的状态从“不支持”改变为“正常” -   一个底层发现规则的状态从“正常”改变为“不支持” -   一个底层发现规则的状态从“不支持”改变为“正常” -   一个触发器的状态从“正常”改变为“未知” -   一个触发器的状态从“未知”改变为“正常”  自从Zabbix 2.2开始支持内部事件。引入内部事件的目的是允许用户在发生任何内部事件时都收到通知发生，例如，一个监控项变得不支持并且停止收集数据。  只有启用了内部动作才会生成内部事件。要停止生成内部事件（例如，当监控项变得不支持），请在“配置”→“动作”→“内部事件”里为内部事件禁用所有动作。  ::: noteclassic  如果禁用了内部动作，当一个对象处于“不支持”状态时，这个对象的恢复事件仍会创建。\ \ 如果启用了内部动作，当一个对象处于“不支持”状态时，这个对象的恢复事件仍会创建，即使该对象没有创建过“问题事件”。  :::  另请参阅：[接收关于不支持的监控项的通知](/manual/config/notifications/unsupported_item)

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	#### Introduction  MIB stands for a Management Information Base. MIB files allow you to use textual representation of the OID (Object Identifier).  For example,      ifHCOutOctets  is textual representation of OID      1.3.6.1.2.1.31.1.1.1.10  You can use either, when monitoring SNMP devices with Zabbix, but if you feel more comfortable when using textual representation you have to install MIB files.
zh-cn	#### 介绍  MIB 代表管理信息库。 MIB 文件允许您使用OID（对象标识符）的文本表示。  例如，      ifHCOutOctets  是 OID 的文本表示      1.3.6.1.2.1.31.1.1.1.10  在使用 Zabbix 监控 SNMP 设备时，您可以使用其中任何一种，但如果您使用文本表示时感觉更舒服，你必须安装 MIB 文件。

en-us	Introduction of external plugins caused the following configuration parameter changes:  - *Plugins.\<PluginName>.Path* parameter has been moved to *Plugins.\<PluginName>.System.Path*. - *Plugins.\<PluginName>.Capacity* parameter, while still supported, has been deprecated, please use *Plugins.\<PluginName>.System.Capacity* instead.
zh-cn	外部插件的引入导致以下配置参数更改： - *Plugins.\<PluginName>.Path* 参数已移至 *Plugins.\<PluginName>.System.Path*。 - *Plugins.\<PluginName>.Capacity* 参数虽然仍受支持，但已被弃用，请改用 *Plugins.\<PluginName>.System.Capacity* 。

en-us	#### Invalid regular expressions after switching to PCRE2  In Zabbix 6.0 support for PCRE2 has been added. Even though PCRE is still supported, Zabbix installation packages for RHEL/CentOS 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer have been updated to use PCRE2. While providing many benefits, switching to PCRE2 may cause certain existing PCRE regexp patterns becoming invalid or behaving differently. In particular, this affects the pattern *^[\w-\.]*. In order to make this regexp valid again without affecting semantics, change the expression to *^[-\w\.]* . This happens due to the fact that PCRE2 treats the dash sign as a delimiter, creating a range inside a character class. The following Zabbix installation packages have been updated and now use PCRE2:  
zh-cn	#### Invalid regular expressions after switching to PCRE2  In Zabbix 6.0 support for PCRE2 has been added. Even though PCRE is still supported, all Zabbix installation packages have been updated to use PCRE2. While providing many benefits, switching to PCRE2 may cause certain existing PCRE regexp patterns becoming invalid or behaving differently. In particular, this affects the pattern *^[\w-\.]*. In order to make this regexp valid again without affecting semantics, change the expression to *^[-\w\.]* . This happens due to the fact that PCRE2 treats the dash sign as a delimiter, creating a range inside a character class.  

en-us	#### Invalid regular expressions after switching to PCRE2  In Zabbix 6.0 support for PCRE2 has been added. Even though PCRE is still supported, Zabbix installation packages for RHEL/CentOS 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer have been updated to use PCRE2. While providing many benefits, switching to PCRE2 may cause certain existing PCRE regexp patterns becoming invalid or behaving differently. In particular, this affects the pattern *\^[\\w-\\.]*. In order to make this regexp valid again without affecting semantics, change the expression to *\^[-\\w\\.]* . This happens due to the fact that PCRE2 treats the dash sign as a delimiter, creating a range inside a character class. The following Zabbix installation packages have been updated and now use PCRE2:  RHEL/CentOS 7 and newer, SLES (all versions), Debian 9 and newer, Ubuntu 16.04 and newer.
zh-cn	#### 切换到 PCRE2 后正则表达式无效  在 Zabbix 6.0 中添加了对 PCRE2 的支持。尽管 PCRE 仍受支持 ，但 RHEL/CentOS 7 及更高版本、SLES（所有版本）、Debian 9 及更高版本、Ubuntu 16.04 及更高版本的 Zabbix 安装包已更新为使用 PCRE2。尽管有很多好处，但是切换到 PCRE2 可能导致某些现有的 PCRE 正则表达式无效或无法正确解析。特别是 *\^[\\w-\\.]* 表达式会受影响。为了使该正则表达式再次生效且不影响语义，请将表达式更改为 *\^[-\\w\\.]* 。 这是因为 PCRE2 将破折号视为分隔符，在字符类中创建了一个范围。  以下 Zabbix 安装包已更新为使用 PCRE2：RHEL/CentOS 7 及更新版本、SLES（所有版本）、Debian 9 及更新版本、Ubuntu 16.04 及更新版本。

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	#### Inventory macros  There are host inventory macros {INVENTORY.\*} available for use in notifications, for example:  "Server in {INVENTORY.LOCATION1} has a problem, responsible person is {INVENTORY.CONTACT1}, phone number {INVENTORY.POC.PRIMARY.PHONE.A1}."  For more details, see the [supported macro](/manual/appendix/macros/supported_by_location) page.
zh-cn	#### 资产清单宏  有可用于通知的主机资产清单宏 {INVENTORY.\*} ，例如：  ”{INVENTORY.LOCATION1}的服务器出现问题，负责人是{INVENTORY.CONTACT1}，联系电话{INVENTORY.POC.PRIMARY.PHONE.A1}。“  更多详细信息，请参阅 [supported macro（支持的宏）](/zh/manual/appendix/macros/supported_by_location)页面。

en-us	##### Inventory mode selection  Inventory mode can be selected in the host configuration form.  Inventory mode by default for new hosts is selected based on the *Default host inventory mode* setting in *Administration* → *General* → *[Other](/manual/web_interface/frontend_sections/administration/general#other_parameters)*.  For hosts added by network discovery or autoregistration actions, it is possible to define a *Set host inventory mode* operation selecting manual or automatic mode. This operation overrides the *Default host inventory mode* setting.
zh-cn	##### 资产模式选择  可以在主机配置表单中选择资产模式。  默认情况下，新主机的资产模式是根据 *Administration（管理）* → *General（一般）* → *[Other（其他）](/zh/manual/web_interface/frontend_sections/administration/general#other_parameters)* 中的*Default host inventory mode（默认主机资产记录模式）*设置选择的。  对于通过网络发现或自动注册操作添加的主机，可以定义 *Set host inventory mode（设置主机资产记录模式）* 操作，选择手动或自动模式。 此操作将覆盖 *Default host inventory mode（默认主机资产记录模式）* 设置。

en-us	#### Inventory overview  The details of all existing inventory data are available in the *Inventory* menu.  In *Inventory → Overview* you can get a host count by various fields of the inventory.  In *Inventory → Hosts* you can see all hosts that have inventory information. Clicking on the host name will reveal the inventory details in a form.  ![](../../../../assets/en/manual/web_interface/inventory_host.png){width="600"}  The **Overview** tab shows:  |Parameter|Description| |--|--------| |*Host name*|Name of the host.<br>Clicking on the name opens a menu with the scripts defined for the host.<br>Host name is displayed with an orange icon, if the host is in maintenance.| |*Visible name*|Visible name of the host (if defined).| |*Host (Agent, SNMP, JMX, IPMI)<br>interfaces*|This block provides details of the interfaces configured for the host.| |*OS*|Operating system inventory field of the host (if defined).| |*Hardware*|Host hardware inventory field (if defined).| |*Software*|Host software inventory field (if defined).| |*Description*|Host description.| |*Monitoring*|Links to monitoring sections with data for this host: *Web*, *Latest data*, *Problems*, *Graphs*, *Dashboards*.| |*Configuration*|Links to configuration sections for this host: *Host*, *Applications*, *Items*, *Triggers*, *Graphs*, *Discovery*, *Web*.<br>The amount of configured entities is listed in parenthesis after each link.|  The **Details** tab shows all inventory fields that are populated (are not empty).
zh-cn	#### 资产清单概述  *资产记录*菜单中提供了所有现有资产数据的详细信息。  在 *资产记录 → 概览* 你可以通过资产的各个字段获取主机数。  在 *资产记录 → 主机* 你可以看到所有具有资产信息的主机。单击主机名将以表单显示资产明细。  ![](../../../../assets/en/manual/web_interface/inventory_host.png){width="600"}   **概览**标签内容如下:  |参数|描述| |--|--------| |*主机名*|主机名。<br>单击该名称将打开一个菜单，其中包含为主机定义的脚本。<br>如果主机处于维护状态，则主机名将显示为橙色图标。| |*可见名称*|主机的可见名称（如果已定义）。| |*主机（Agent、SNMP、JMX、IPMI）<br>接口*|此块提供为主机配置的接口的详细信息。| |*操作系统*|主机的操作系统清单字段（如果已定义）。| |*硬件*|主机硬件清单字段（如果已定义）。| |*软件*|主机软件清单字段（如果已定义）。| |*描述*|主机描述。| |*监控*|链接到包含此主机数据的监控部分：*Web*、*最新数据*、*问题*、*图表*、*仪表板*。| |*配置*|此主机配置部分的链接：*主机*、*应用程序*、*监控项*、*触发器*、*图形*、*发现*、*Web*。<br>配置的实体数量是在每个链接后的括号中列出。|  **详细信息** 选项卡显示所有已填充（非空）的资产清单字段。

en-us	#### IPMI checks  IPMI checks will not work with the standard OpenIPMI library package on Debian prior to 9 (stretch) and Ubuntu prior to 16.04 (xenial). To fix that, recompile OpenIPMI library with OpenSSL enabled as discussed in [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139).
zh-cn	#### IPMI 检查  用 Debian 9 (stretch) 和 Ubuntu 16.04 (xenial) 之前版本的标准 OpenIPMI 库包运行 IPMI 检查会无法正常运行。要解决此问题，请重新编译 OpenIPMI 库并启用 OpenSSL，参考 [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139)。

en-us	#### IPMI checks  IPMI checks will not work with the standard OpenIPMI library package on Debian prior to 9 (stretch) and Ubuntu prior to 16.04 (xenial). To fix that, recompile OpenIPMI library with OpenSSL enabled as discussed in [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139).  
zh-cn	#### IPMI 检查  用 Debian 9 (stretch) 和 Ubuntu 16.04 (xenial) 之前版本的标准 OpenIPMI 库包运行 IPMI 检查会无法正常运行。要解决此问题，请重新编译 OpenIPMI 库并启用 OpenSSL，参考 [ZBX-6139](https://support.zabbix.com/browse/ZBX-6139)。

en-us	#### IPMI remote commands  For IPMI remote commands the following syntax should be used:      <command> [<value>]  where  -   <command> - one of IPMI commands without spaces -   <value> - 'on', 'off' or any unsigned integer. <value>     is an optional parameter.
zh-cn	#### IPMI远程命令  对于IPMI远程命令应使用如下语法：      <command> [<value>]  其中  -   \<command\>——表示一个没有空格的IPMI命令。 -   \<value\>——其值为‘on’、‘off’或任何无符号整数，\<value\>是可选参数。

en-us	# IPMI template operation  IPMI templates do not require any specific setup. To start monitoring, [link](/manual/config/templates/linking#linking_a_template) the template to a target host (if the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\  ::: notetip  This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name).  :::  |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[Chassis by IPMI](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/chassis_ipmi/README.md)|**{$IPMI.USER}**, **{$IPMI.PASSWORD}** - credentials for access to BMC (default: none)|\-|
zh-cn	 # IPMI 模板操作  IPMI模板不需要任何特定的设置. 要开始监控，请将模板 [链接](/manual/config/templates/linking#linking_a_template) 到目标主机。 (如果Zabbix安装中没有该模板，则可能需要先导入该模板的.xml文件 - 有关说明，请参见 [开箱即用的模板](/manual/config/templates_out_of_the_box) 部分)。  ::: notetip 页面仅包含最小的一组宏和正确的模板操作所需的设置步骤。 在模板的Readme.md文件中提供了模板的详细说明，包括宏，项和触发器的完整列表（可通过单击模板名称访问）。 :::  |模板|必配宏|附加步骤/注释| |--------|----------------|-------------------------| |[Chassis by IPMI](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/server/chassis_ipmi/README.md)|**{\$IPMI.USER}**, **{\$IPMI.PASSWORD}** - 访问BMC的凭据 (默认: none)|\-|

en-us	#### IPv6 address issue in SNMPv3 traps  Due to a net-snmp bug, IPv6 address may not be correctly displayed when using SNMPv3 in SNMP traps. For more details and a possible workaround, see [ZBX-14541](https://support.zabbix.com/browse/ZBX-14541).
zh-cn	#### SNMPv3 trap 中的 IPv6 地址问题  由于 net-snmp bug，在 SNMP trap 中使用 SNMPv3 时可能无法正确显示 IPv6 地址。有关更多详细信息和可能的解决方法，请参阅 [ZBX-14541](https://support.zabbix.com/browse/ZBX-14541)。

en-us	 #### Issues in Zabbix 6.0.11  ##### JSONPath parsing errors  JSONPath parsing errors occur in case of leading whitespace and empty array/object. Fixed in Zabbix 6.0.12.  ##### AND/OR evaluation in LLD filters  The evaluation of AND/OR expressions in the low-level discovery filters/overrides may fail in this version. Fixed in Zabbix 6.0.12.
zh-cn	#### Zabbix 6.0.11 中的问题  ##### JSONPath解析错误  JSONPath 解析错误发生在前导空格和空数组/对象的情况下。 在 Zabbix 6.0.12 中修复。  ##### LLD 过滤器中的 AND/OR 评估  在此版本中，底层发现过滤器/覆盖中的 AND/OR 表达式的评估可能会失败。 在 Zabbix 6.0.12 中修复。

en-us	#### item  Bug fixes:\ [ZBX-19118](https://support.zabbix.com/browse/ZBX-19118) `item.create`, `item.update`: property `interfaceid` is no longer required to create/update a HTTP agent type item.\
zh-cn	#### 发现规则  Bug修复：\ [ZBX-19118](https://support.zabbix.com/browse/ZBX-19118) `item.create`、`item.update`：不再需要属性 `interfaceid` 来创建/更新 HTTP 代理类型的监控项。\

en-us	#### Item changes   Native support for the [items](/manual/config/items/itemtypes/zabbix_agent) **net.dns** and **net.dns.record** has been added to Zabbix agent 2. On Zabbix agent 2 for Windows, these items now allow custom DNS IP addresses in the `ip` parameter and no longer ignore `timeout` and `count` parameters. 
zh-cn	#### 监控项变化  Zabbix agent 2 中添加了对 [监控项](/manual/config/items/itemtypes/zabbix_agent) **net.dns** 和 **net.dns.record** 的原生支持。在 Zabbix agent 2 for Windows 中，这些监控项现在允许在 `ip` 参数中自定义 DNS IP 地址，并且不再忽略 `timeout` 和 `count` 参数。

en-us	#### item  Changes:\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `item.get`, `item.create`, `item.update`: added the third parameter to the Prometheus pattern preprocessing step. The second parameter will now determine an aggregation method: `value`, `label`, `function`. The third parameter will now contain Prometheus output for the aggregation method `label` or an aggregation function for the aggregation method `function`.\
zh-cn	 #### 监控项  变更：\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `item.get`，`item.create`，`item.update`：为Prometheus 模式预处理步骤添加第三个参数。第二个参数现在将会决定一个聚合方法：`value`，`label`，`function`。第三个参数现在将包含聚合方法`label`或聚合方法`function`的一个聚合函数的Prometheus输出。\

en-us	#### item  Changes:\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `item.get`, `item.create`, `item.update`: added the third parameter to the Prometheus pattern preprocessing step. The second parameter will now determine an aggregation method: `value`, `label`, `function`. The third parameter will now contain Prometheus output for the aggregation method `label` or an aggregation function for the aggregation method `function`. \
zh-cn	 #### 监控项  变更：\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `item.get`，`item.create`，`item.update`：为Prometheus 模式预处理步骤添加第三个参数。第二个参数现在将会决定一个聚合方法：`value`，`label`，`function`。第三个参数现在将包含聚合方法`label`或聚合方法`function`的一个聚合函数的Prometheus输出。\

en-us	##### Item configuration  Actual command(s) to be executed must be placed in the **Executed script** field in the item configuration.  Multiple commands can be executed one after another by placing them on a new line. In this case returned values also will be formatted as multilined.  ![](../../../../../assets/en/manual/config/items/itemtypes/ssh_item.png)  All mandatory input fields are marked with a red asterisk.  The fields that require specific information for SSH items are:  |Parameter|Description|Comments| |--|------|------| |*Type*|Select **SSH agent** here.| | |*Key*|Unique (per host) item key in format **ssh.run\[<unique short description>,<ip>,<port>,<encoding>\]**|<unique short description> is required and should be unique for all SSH items per host<br>Default port is 22, not the port specified in the interface to which this item is assigned| |*Authentication method*|One of the "Password" or "Public key"| | |*User name*|User name to authenticate on remote host.<br>Required| | |*Public key file*|File name of public key if *Authentication method* is "Public key". Required|Example: *id\_rsa.pub* - default public key file name generated by a command [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen)| |*Private key file*|File name of private key if *Authentication method* is "Public key". Required|Example: *id\_rsa* - default private key file name| |*Password* or<br>*Key passphrase*|Password to authenticate or<br>Passphrase **if** it was used for the private key|Leave the *Key passphrase* field empty if passphrase was not used<br>See also [known issues](/manual/installation/known_issues#ssh_checks) regarding passphrase usage| |*Executed script*|Executed shell command(s) using SSH remote session|Examples:<br>*date +%s*<br>*service mysql-server status*<br>*ps auxww \| grep httpd \| wc -l*|  ::: noteimportant libssh2 library may truncate executable scripts to \~32kB. :::
zh-cn	#####监控项配置  要执行的命令必须放在监控项配置中的“执行的脚本”字段中。  通过将多个命令放在一行上，可以遍历执行多个命令。在这种情况下，返回的值也将被格式化为多行。  ![](../../../../../assets/en/manual/config/items/itemtypes/ssh_item.png)  所有必填字段都标有红色星号。  SSH监控项需要特定信息的字段：  |参数|说明|备注| |---------|-----------|--------| |*类型*|在此处选择**SSH 客户端**。|<| |*Key*|唯一（每个主机）监控项键，格式为 **ssh.run\[<unique short description>,<ip>,<port>,<encoding>\]**|<unique short description> 是必需的并且对于每个主机的所有 SSH 监控项应该是唯一的<br>默认端口是 22，而不是在分配此监控项的接口中指定的端口| |*认证方式*|“密码”或“公钥”  选一个|<| |*用户名*|在远程主机上进行身份验证的用户名。<br>必填|<| |*公钥文件*|如果 *Authentication method* 是“Public key”，则公钥的文件名。必需|示例：*id\_rsa.pub* - 命令生成的默认公钥文件名 [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen)| |*私钥文件*|如果 *Authentication method* 是“Public key”，则私钥的文件名。必需|示例：*id\_rsa* - 默认私钥文件名| |*Password* or<br>*密钥密码*|验证密码或<br>Passphrase **如果**它用于私钥|如果没有使用密码，则将 *Key passphrase* 字段留空<br>另请参阅 [已知问题](/manual/installation/known_issues#ssh_checks) 关于密码短语的使用| |*执行的脚本*|使用 SSH 远程会话执行的 shell 命令|示例：<br>*date +%s*<br>*service mysql-server status* <br> *ps auxww \| grep httpd \| wc -l*|  ::: noteimportant libssh2 库可能会将可执行脚本截断为\~32kB.  :::

en-us	#### Item configuration  A dependent item depends on its master item for data. That is why the **master item** must be configured (or exist) first:  -   Go to: *Configuration* → *Hosts* -   Click on *Items* in the row of the host -   Click on *Create item* -   Enter parameters of the item in the form  ![](../../../../../assets/en/manual/config/items/itemtypes/master_item.png)  All mandatory input fields are marked with a red asterisk.  Click on *Add* to save the master item.  Then you can configure a **dependent item**.  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item.png)  All mandatory input fields are marked with a red asterisk.  The fields that require specific information for dependent items are:  |   |   | |--|--------| |*Type*|Select **Dependent item** here.| |*Key*|Enter a key that will be used to recognize the item.| |*Master item*|Select the master item. Master item value will be used to populate dependent item value.| |*Type of information*|Select the type of information that will correspond the format of data that will be stored.|  You may use item value [preprocessing](/manual/config/items/item#item_value_preprocessing) to extract the required part of the master item value.  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_preprocessing.png){width="600"}  Without preprocessing, the dependent item value will be exactly the same as the master item value.  Click on *Add* to save the dependent item.  A shortcut to creating a dependent item quicker can be accessed by clicking on the ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_button.png) button in the item list and selecting *Create dependent item*.  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_menu.png)
zh-cn	#### 监控项配置  相关监控项依赖于主要监控项的数据，这就是为什么必须首先配置 **主要监控项** (或主要监控项已存在)。  -   进入:  *配置*  →  *主机* -   在主机那一行点击  *监控项* -   点击  *创建监控项* -   下表中输入监控项的参数  ![](../../../../../assets/en/manual/config/items/itemtypes/master_item.png)  所有标有红色星号的为必填字段。  点击 *添加* 保存主监控项。  接着，你可以配置 **从属监控项**。  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item.png)  所有标有红色星号的为必填字段。  必要的相关监控项的特定信息的字段是：  |   |   | |---|---| |*类型*|这里选择 **Dependent item** 。| |*键值*|输入一个用于识别监控项的键。| |*主要项*|选择主要监控项。 主要监控项的值将用于填充从属监控项的值。| |*信息类型*|选择与将要存储的数据格式相对应的信息类型 |  你可以使用监控项值的 [预处理](/manual/config/items/item#item_value_preprocessing) 从主要监控项提取数据。  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_preprocessing.png){width="600"}  如果不进行预处理，相关监控项的值将与主要监控项的值完全相同。  点击  *添加*  保存相关监控项。  单击 ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_button.png) 按钮可以访问更快地创建相关项的快捷方式，并在监控项列表中选择*创建相关监控项*。  ![](../../../../../assets/en/manual/config/items/itemtypes/dependent_item_menu.png)

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 keys  The table provides details on the item keys that you can use with Zabbix agent 2 only.  See also: [Plugins supplied out-of-the-box](/manual/config/items/plugins#plugins_supplied_out-of-the-box)  ::: noteclassic  Parameters without angle brackets are mandatory. Parameters marked with angle brackets **<** **>** are optional. :::  |Key|<|<|<|<| |---|-|-|-|-| |<|**Description**|**Return value**|**Parameters**|**Comments**| |ceph.df.details \[connString, <user>, <apikey>\]|<|<|<|<| |<|Cluster’s data usage and distribution among pools.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.stats \[connString, <user>, <apikey>\]|<|<|<|<| |<|Aggregated and per OSD statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.discovery \[connString, <user>, <apikey>\]|<|<|<|<| |<|List of discovered OSDs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.dump \[connString, <user>, <apikey>\]|<|<|<|<| |<|Usage thresholds and statuses of OSDs.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.ping \[connString, <user>, <apikey>\]|<|<|<|<| |<|Tests whether a connection to Ceph can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.pool.discovery \[connString, <user>, <apikey>\]|<|<|<|<| |<|List of discovered pools. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.status \[connString, <user>, <apikey>\]|<|<|<|<| |<|Overall cluster's status.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |docker.container\_info \[<ID>\]|<|<|<|<| |<|Low-level information about a container.|An output of the [ContainerInspect](https://docs.docker.com/engine/api/v1.28/#operation/ContainerInspect) API call serialized as JSON|**ID** - ID or name of the container|This item is supported since Zabbix 5.0.0 for the Docker plugin.<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.container\_stats \[<ID>\]|<|<|<|<| |<|Container resource usage statistics.|An output of the [ContainerStats](https://docs.docker.com/engine/api/v1.28/#operation/ContainerStats) API call and CPU usage percentage serialized as JSON|**ID** - ID or name of the container|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers|<|<|<|<| |<|A list of containers.|An output of the [ContainerList](https://docs.docker.com/engine/api/v1.28/#operation/ContainerList) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers.discovery\[<options>\]|<|<|<|<| |<|A list of containers. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object.|**options** - specifies whether all or only running containers should be discovered. Supported values:<br>*true* - return all containers;<br>*false* - return only running containers (default).|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.data\_usage|<|<|<|<| |<|Information about current data usage.|An output of the [SystemDataUsage](https://docs.docker.com/engine/api/v1.28/#operation/SystemDataUsage) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images|<|<|<|<| |<|A list of images.|An output of the [ImageList](https://docs.docker.com/engine/api/v1.28/#operation/ImageList) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images.discovery|<|<|<|<| |<|A list of images. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object.|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.info|<|<|<|<| |<|System information.|An output of the [SystemInfo](https://docs.docker.com/engine/api/v1.28/#operation/SystemInfo) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.ping|<|<|<|<| |<|Test if a Docker daemon is alive or not.|1 - connection is alive<br><br>0 - connection is broken|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |memcached.ping\[connString,<user>,<password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.|This item is supported for the [Memchached plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |memcached.stats\[connString,<user>,<password>,<type>\]|<|<|<|<| |<|Gets the output of the STATS command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**user, password** - Memchached login credentials.<br>**type** - stat type to be returned: *items*, *sizes*, *slabs* or *settings* (empty by default, returns general statistics).|This item is supported for the [Memchached plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collection.stats\[connString,<user>,<password>,<database>,collection\]|<|<|<|<| |<|Returns a variety of storage statistics for a given collection.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).<br>**collection** — collection name.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collections.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered collections. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collections.usage\[connString,<user>,<password>\]|<|<|<|<| |<|Returns usage statistics for collections.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.connpool.stats\[connString,<user>,<password>\]|<|<|<|<| |<|Returns information regarding the open outgoing connections from the current database instance to other members of the sharded cluster or replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.db.stats\[connString,<user>,<password>,<database>\]|<|<|<|<| |<|Returns statistics reflecting a given database system state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.db.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.jumbo\_chunks.count\[connString,<user>,<password>\]|<|<|<|<| |<|Returns count of jumbo chunks.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.oplog.stats\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a status of the replica set, using data polled from the oplog.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.ping\[connString,<user>,<password>\]|<|<|<|<| |<|Tests if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.rs.config\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a current configuration of the replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.rs.status\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a replica set status from the point of view of the member where the method is run.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.server.status\[connString,<user>,<password>\]|<|<|<|<| |<|Returns database state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.sh.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered shards present in the cluster.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<|<| |<|Subscribes to a specific topic or topics (with wildcards) of the provided broker and waits for publications.|Depending on topic content.<br><br>If wildcards are used, returns topic content as JSON.|**broker\_url** - MQTT broker URL (if empty, *localhost* with port 1883 is used).<br>**topic** - MQTT topic (mandatory). Wildcards (+,\#) are supported.<br>**username,password** - authentication credentials (if required)|This item is supported for the [MQTT plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (active)' item type).<br><br>TLS encryption certificates can be used by saving them into a default location (e.g. `/etc/ssl/certs/` directory for Ubuntu). For TLS, use the `tls://` scheme.| |mysql.db.discovery\[connString, <username>, <password>\]|<|<|<|<| |<|List of MySQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show databases" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.db.size\[connString, <username>, <password>,dbName\]|<|<|<|<| |<|Database size in bytes.|Result of the "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" SQL query for specific database in bytes.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**dbName** - Database name.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.get\_status\_variables\[connString, <username>, <password>\]|<|<|<|<| |<|Values of global status variables.|Result of the "show global status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.ping\[connString, <username>, <password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.replication.discovery\[connString, <username>, <password>\]|<|<|<|<| |<|List of MySQL replications. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show slave status" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.replication.get\_slave\_status\[connString, <username>, <password>, <masterHost>\]|<|<|<|<| |<|Replication status.|Result of the "show slave status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**masterHost** - Replication master host name.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.version\[connString, <username>, <password>\]|<|<|<|<| |<|MySQL version.|String with MySQL instance version.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|ASM disk groups statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.diskgroups.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of ASM disk groups. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.archive.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Archive logs statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.cdb.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|CDBs info.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.custom.query\[connString,<user>,<password>,<service>, queryName, <args...>\]|<|<|<|<| |<|Result of a custom query.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**queryName** — name of a custom query (must be equal to a name of an sql file without an extension).<br>**args...** — one or several comma-separated arguments to pass to a query.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.datafiles.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Data files statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.db.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|FRA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.instance.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Instance statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pdb.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|PDBs info.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pdb.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of PDBs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|PGA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ping\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Tests whether a connection to Oracle can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.proc.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Processes statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.redolog.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Log file information from the control file.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|SGA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sessions.stats\[connString,<user>,<password>,<service>,<lockMaxTime>\]|<|<|<|<| |<|Sessions statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**lockMaxTime** - maximum session lock duration in seconds to count the session as a prolongedly locked. Default: 600 seconds.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sys.metrics\[connString,<user>,<password>,<service>,<duration>\]|<|<|<|<| |<|A set of system metric values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**duration** - capturing interval (in seconds) of system metric values. Possible values: *60* — long duration (default), *15* — short duration.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sys.params\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|A set of system parameter values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ts.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Tablespaces statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ts.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.user.info\[connString,<user>,<password>,<username>\]|<|<|<|<| |<|List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**username** - a username, for which the information is needed. Lowercase usernames are not supported. Default: current user.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.autovacuum.count\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of autovacuum workers.|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.archive\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Information about archived files.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.archive.count\_archived\_files** - the number of WAL files that have been successfully archived.<br>**pgsql.archive.failed\_trying\_to\_archive** - the number of failed attempts for archiving WAL files.<br>**pgsql.archive.count\_files\_to\_archive** - the number of files to archive.<br>**pgsql.archive.size\_files\_to\_archive** -the size of files to archive.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.bgwriter\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Combined number of checkpoints for the database cluster, broken down by checkpoint type.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.bgwriter.buffers\_alloc** - the number of buffers allocated.<br>**pgsql.bgwriter.buffers\_backend** -the number of buffers written directly by a backend.<br>**pgsql.bgwriter.maxwritten\_clean** - the number of times the background writer stopped a cleaning scan, because it had written too many buffers.<br>**pgsql.bgwriter.buffers\_backend\_fsync** -the number of times a backend had to execute its own fsync call instead of the background writer.<br>**pgsql.bgwriter.buffers\_clean** - the number of buffers written by the background writer.<br>**pgsql.bgwriter.buffers\_checkpoint** - the number of buffers written during checkpoints.<br>**pgsql.bgwriter.checkpoints\_timed** - the number of scheduled checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoints\_req** - the number of requested checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoint\_write\_time** - the total amount of time spent in the portion of checkpoint processing where files are written to disk, in milliseconds.<br>**pgsql.bgwriter.sync\_time** - the total amount of time spent in the portion of checkpoint processing where files are synchronized with disk.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.cache.hit\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|PostgreSQL buffer cache hit rate.|SQL query in percentage.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.connections\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Connections by type.|JSON object.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.connections.active** - the backend is executing a query.<br>**pgsql.connections.fastpath\_function\_call** -the backend is executing a fast-path function.<br>**pgsql.connections.idle** - the backend is waiting for a new client command.<br>**pgsql.connections.idle\_in\_transaction** - the backend is in a transaction, but is not currently executing a query.<br>**pgsql.connections.prepared** - the number of prepared connections.<br>**pgsql.connections.total** - the total number of connections.<br>**pgsql.connections.total\_pct** - percantange of total connections in respect to ‘max\_connections’ setting of the PostgreSQL server.<br>**pgsql.connections.waiting** - number of connections in a query.<br>**pgsql.connections.idle\_in\_transaction\_aborted** - the backend is in a transaction, but is not currently executing a query and one of the statements in the transaction caused an error.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.dbstat\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Collects statistics per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.dbstat.numbackends\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_read\_time\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time\["{\#DBNAME}"\]** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures\["{\#DBNAME}"\]** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled.(PostgreSQL version 12 only)<br>**pgsql.dbstat.blks\_read.rate\["{\#DBNAME}"\]** - the number of disk blocks read in this database.<br>**pgsql.dbstat.deadlocks.rate\["{\#DBNAME}"\]** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.blks\_hit.rate\["{\#DBNAME}"\]** - the number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL Pro buffer cache, not the operating system's file system cache).<br>**pgsql.dbstat.xact\_rollback.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been rolled back.<br>**pgsql.dbstat.xact\_commit.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.tup\_updated.rate\["{\#DBNAME}"\]** - the number of rows updated by queries in this database.<br>**pgsql.dbstat.tup\_returned.rate\["{\#DBNAME}"\]** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.tup\_inserted.rate\["{\#DBNAME}"\]** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.tup\_fetched.rate\["{\#DBNAME}"\]** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.tup\_deleted.rate\["{\#DBNAME}"\]** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.conflicts.rate\["{\#DBNAME}"\]** - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers).<br>**pgsql.dbstat.temp\_files.rate\["{\#DBNAME}"\]** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.temp\_bytes.rate\["{\#DBNAME}"\]** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.dbstat.sum\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Summarized data for all databases in a cluster.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by the dependent items:<br>**pgsql.dbstat.numbackends** - the number of backends currently connected to this database.<br>**pgsql.dbstat.sum.blk\_read\_time** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled (PostgreSQL version 12 only).<br>**pgsql.dbstat.sum.xact\_commit** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.sum.conflicts** - database statistics about query cancels due to conflict with recovery on standby servers.<br>**pgsql.dbstat.sum.deadlocks** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.sum.blks\_read** - the number of disk blocks read in this database.<br>**pgsql.dbstat.sum.blks\_hit** - the number of times disk blocks were found already in the buffer cache, so a read was not necessary (only hits in the PostgreSQL Pro buffer cache are included).<br>**pgsql.dbstat.sum.temp\_bytes** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.temp\_files** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.xact\_rollback** - the number of rolled-back transactions in this database.<br>**pgsql.dbstat.sum.tup\_deleted** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.sum.tup\_fetched** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.sum.tup\_inserted** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.sum.tup\_returned** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.sum.tup\_updated** - the number of rows updated by queries in this database.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.age\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Age of the oldest FrozenXID of the database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query for specific database in transactions.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.bloating\_tables\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of bloating tables per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.discovery\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|List of the PostgreSQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query in the LLD JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.size\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Database size in bytes. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query for specific database in bytes.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.locks\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Information about granted locks per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQl query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.locks.shareupdateexclusive\["{\#DBNAME}"\]** - the number of share update exclusive locks.<br>**pgsql.locks.accessexclusive\["{\#DBNAME}"\]** - the number of access exclusive locks.<br>**pgsql.locks.accessshare\["{\#DBNAME}"\]** - the number of access share locks.<br>**pgsql.locks.exclusive\["{\#DBNAME}"\]** - the number of exclusive locks.<br>**pgsql.locks.rowexclusive\["{\#DBNAME}"\]** - the number of row exclusive locks.<br>**pgsql.locks.rowshare\["{\#DBNAME}"\]** - the number of row share locks.<br>**pgsql.locks.share\["{\#DBNAME}"\]** - the number of shared locks.<br>**pgsql.locks.sharerowexclusive\["{\#DBNAME}"\]** - the number of share row exclusive locks.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.oldest.xid\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Age of the oldest XID.|SQl query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.ping\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Tests whether a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.count\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of standby servers.|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.recovery\_role\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Recovery status.|0 - master mode<br>1 - recovery is still in progress (standby mode)|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.status\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The status of replication.|0 - streaming is down<br>1 - streaming is up<br>2 - master mode|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication\_lag.b\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Replication lag in bytes.|SQL query in bytes.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication\_lag.sec\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Replication lag in seconds.|SQL query in seconds.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.uptime\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|PostgreSQL uptime in milliseconds.|SQL query in milliseconds.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.wal.stat\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|WAL statistics.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.wal.count** — the number of WAL files.<br>**pgsql.wal.write** - the WAL lsn used (in bytes).<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.config\[connString,<password>,<pattern>\]|<|<|<|<| |<|Gets the configuration parameters of a Redis instance that match the pattern.|JSON - if a glob-style pattern was used<br><br>single value - if a pattern did not contain any wildcard character|**connString** - URI or session name.<br>**password** - Redis password.<br>**pattern** - glob-style pattern (*\** by default).|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.info\[connString,<password>,<section>\]|<|<|<|<| |<|Gets the output of the INFO command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**password** - Redis password.<br>**section** - [section](https://redis.io/commands/info) of information (*default* by default).|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.ping\[connString,<password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.<br>**password** - Redis password.|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.slowlog.count\[connString,<password>\]|<|<|<|<| |<|The number of slow log entries since Redis was started.|Integer|**connString** - URI or session name.<br>**password** - Redis password.|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.attribute.discovery|<|<|<|<| |<|Returns a list of S.M.A.R.T. device attributes.|JSON object|<|The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#ID}, {\#ATTRNAME}, {\#THRESH}.<br>HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"}<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.disk.discovery|<|<|<|<| |<|Returns a list of S.M.A.R.T. devices.|JSON object|<|The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#MODEL}, {\#SN}.<br>HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"}<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.disk.get|<|<|<|<| |<|Returns all available properties of S.M.A.R.T. devices.|JSON object|<|HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID.<br>The data includes smartctl version and call arguments, and additional fields:<br>*disk\_name* - holds the name with the required add-ons for RAID discovery, e.g: {"disk\_name": "/dev/sda cciss,2"}<br>*disk\_type* - holds the disk type HDD, SSD, or NVME, e.g: {"disk\_type": "ssd"})<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |systemd.unit.get\[unit name,<interface>\]|<|<|<|<| |<|Returns all properties of a systemd unit.|JSON object|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**interface** - unit interface type, possible values: *Unit* (default), *Service*, *Socket*, *Device*, *Mount*, *Automount*, *Swap*, *Target*, *Path*|This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.<br><br>LoadState, ActiveState and UnitFileState for Unit interface are returned as text and integer:<br>`"ActiveState":{"state":1,"text":"active"}`| |systemd.unit.info\[unit name,<property>,<interface>\]|<|<|<|<| |<|Systemd unit information.|String|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**property** - unit property (e.g. ActiveState (default), LoadState, Description)<br>**interface** - unit interface type (e.g. Unit (default), Socket, Service)|This item allows to retrieve a specific property from specific type of interface as described in [dbus API](https://www.freedesktop.org/wiki/Software/systemd/dbus/).<br><br>This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.<br><br>Examples:<br>=> systemd.unit.info\["{\#UNIT.NAME}"\] - collect active state (active, reloading, inactive, failed, activating, deactivating) info on discovered systemd units<br>=> systemd.unit.info\["{\#UNIT.NAME}",LoadState\] - collect load state info on discovered systemd units<br>=> systemd.unit.info\[mysqld.service,Id\] - retrieve service technical name (mysqld.service)<br>=> systemd.unit.info\[mysqld.service,Description\] - retrieve service description (MySQL Server)<br>=> systemd.unit.info\[mysqld.service,ActiveEnterTimestamp\] - retrieve the last time the service entered the active state (1562565036283903)<br>=> systemd.unit.info\[dbus.socket,NConnections,Socket\] - collect the number of connections from this socket unit| |systemd.unit.discovery\[<type>\]|<|<|<|<| |<|List of systemd units and their details. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**type** - possible values: *all*, *automount*, *device*, *mount*, *path*, *service* (default), *socket*, *swap*, *target*|This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.| |web.certificate.get\[hostname,<port>,<address>\]|<|<|<|<| |<|Validates certificates and returns certificate details.|JSON object|**hostname** - can be either IP or DNS.<br>May contain the URL scheme (*https* only), path (it will be ignored), and port.<br>If a port is provided in both the first and the second parameters, their values must match.<br>If address (the 3rd parameter) is specified, the hostname is only used for SNI and hostname verification.<br>**port** - port number (default is 443 for HTTPS).<br>**address** - can be either IP or DNS. If specified, it will be used for connection, and hostname (the 1st parameter) will be used for SNI, and host verification.<br>In case, the 1st parameter is an IP and the 3rd parameter is DNS, the 1st parameter will be used for connection, and the 3rd parameter will be used for SNI and host verification.|This item turns unsupported if the resource specified in `host` does not exist or is unavailable or if TLS handshake fails with any error except an invalid certificate.<br><br>Currently, AIA (Authority Information Access) X.509 extension, CRLs and OCSP (including OCSP stapling), Certificate Transparency, and custom CA trust store are not supported.|  
zh-cn	#### Item keys  The table provides details on the item keys that you can use with Zabbix agent 2 only.  See also: [Plugins supplied out-of-the-box](/manual/config/items/plugins#plugins_supplied_out-of-the-box)  ::: noteclassic  Parameters without angle brackets are mandatory. Parameters marked with angle brackets **<** **>** are optional. :::  |Key|<|<|<|<| |---|-|-|-|-| |<|**Description**|**Return value**|**Parameters**|**Comments**| |ceph.df.details \[connString, <user>, <apikey>\]|<|<|<|<| |<|Cluster’s data usage and distribution among pools.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.stats \[connString, <user>, <apikey>\]|<|<|<|<| |<|Aggregated and per OSD statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.discovery \[connString, <user>, <apikey>\]|<|<|<|<| |<|List of discovered OSDs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.osd.dump \[connString, <user>, <apikey>\]|<|<|<|<| |<|Usage thresholds and statuses of OSDs.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.ping \[connString, <user>, <apikey>\]|<|<|<|<| |<|Tests whether a connection to Ceph can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.pool.discovery \[connString, <user>, <apikey>\]|<|<|<|<| |<|List of discovered pools. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |ceph.status \[connString, <user>, <apikey>\]|<|<|<|<| |<|Overall cluster's status.|JSON object|**connString** - URI or session name.<br>**user, password** - Ceph login credentials.|This item is supported for the [Ceph plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |docker.container\_info \[<ID>\]|<|<|<|<| |<|Low-level information about a container.|An output of the [ContainerInspect](https://docs.docker.com/engine/api/v1.28/#operation/ContainerInspect) API call serialized as JSON|**ID** - ID or name of the container|This item is supported since Zabbix 5.0.0 for the Docker plugin.<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.container\_stats \[<ID>\]|<|<|<|<| |<|Container resource usage statistics.|An output of the [ContainerStats](https://docs.docker.com/engine/api/v1.28/#operation/ContainerStats) API call and CPU usage percentage serialized as JSON|**ID** - ID or name of the container|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers|<|<|<|<| |<|A list of containers.|An output of the [ContainerList](https://docs.docker.com/engine/api/v1.28/#operation/ContainerList) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.containers.discovery\[<options>\]|<|<|<|<| |<|A list of containers. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object.|**options** - specifies whether all or only running containers should be discovered. Supported values:<br>*true* - return all containers;<br>*false* - return only running containers (default).|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.data\_usage|<|<|<|<| |<|Information about current data usage.|An output of the [SystemDataUsage](https://docs.docker.com/engine/api/v1.28/#operation/SystemDataUsage) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images|<|<|<|<| |<|A list of images.|An output of the [ImageList](https://docs.docker.com/engine/api/v1.28/#operation/ImageList) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.images.discovery|<|<|<|<| |<|A list of images. Used for [low-level discovery](/manual/discovery/low_level_discovery/).|JSON object.|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.info|<|<|<|<| |<|System information.|An output of the [SystemInfo](https://docs.docker.com/engine/api/v1.28/#operation/SystemInfo) API call serialized as JSON|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |docker.ping|<|<|<|<| |<|Test if a Docker daemon is alive or not.|1 - connection is alive<br><br>0 - connection is broken|\-|This item is supported for the [Docker plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The Agent2 user ('zabbix') must be added to the 'docker' [group](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) for sufficient privileges. Otherwise the check will fail.| |memcached.ping\[connString,<user>,<password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.|This item is supported for the [Memchached plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |memcached.stats\[connString,<user>,<password>,<type>\]|<|<|<|<| |<|Gets the output of the STATS command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**user, password** - Memchached login credentials.<br>**type** - stat type to be returned: *items*, *sizes*, *slabs* or *settings* (empty by default, returns general statistics).|This item is supported for the [Memchached plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collection.stats\[connString,<user>,<password>,<database>,collection\]|<|<|<|<| |<|Returns a variety of storage statistics for a given collection.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).<br>**collection** — collection name.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collections.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered collections. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.collections.usage\[connString,<user>,<password>\]|<|<|<|<| |<|Returns usage statistics for collections.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.connpool.stats\[connString,<user>,<password>\]|<|<|<|<| |<|Returns information regarding the open outgoing connections from the current database instance to other members of the sharded cluster or replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.db.stats\[connString,<user>,<password>,<database>\]|<|<|<|<| |<|Returns statistics reflecting a given database system state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.<br>**database** - database name (default: admin).|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.db.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.jumbo\_chunks.count\[connString,<user>,<password>\]|<|<|<|<| |<|Returns count of jumbo chunks.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.oplog.stats\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a status of the replica set, using data polled from the oplog.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.ping\[connString,<user>,<password>\]|<|<|<|<| |<|Tests if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.rs.config\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a current configuration of the replica set.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.rs.status\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a replica set status from the point of view of the member where the method is run.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.server.status\[connString,<user>,<password>\]|<|<|<|<| |<|Returns database state.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mongodb.sh.discovery\[connString,<user>,<password>\]|<|<|<|<| |<|Returns a list of discovered shards present in the cluster.|JSON object|**connString** - URI or session name.<br>**user, password** - MongoDB login credentials.|This item is supported for the [MongoDB plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mqtt.get\[<broker\_url>,topic,<username>,<password>\]|<|<|<|<| |<|Subscribes to a specific topic or topics (with wildcards) of the provided broker and waits for publications.|Depending on topic content.<br><br>If wildcards are used, returns topic content as JSON.|**broker\_url** - MQTT broker URL (if empty, *localhost* with port 1883 is used).<br>**topic** - MQTT topic (mandatory). Wildcards (+,\#) are supported.<br>**username,password** - authentication credentials (if required)|This item is supported for the [MQTT plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).<br><br>The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks) ('Zabbix agent (active)' item type).<br><br>TLS encryption certificates can be used by saving them into a default location (e.g. `/etc/ssl/certs/` directory for Ubuntu). For TLS, use the `tls://` scheme.| |mysql.db.discovery\[connString, <username>, <password>\]|<|<|<|<| |<|List of MySQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show databases" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.db.size\[connString, <username>, <password>,dbName\]|<|<|<|<| |<|Database size in bytes.|Result of the "select coalesce(sum(data\_length + index\_length),0) as size from information\_schema.tables where table\_schema=?" SQL query for specific database in bytes.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**dbName** - Database name.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.get\_status\_variables\[connString, <username>, <password>\]|<|<|<|<| |<|Values of global status variables.|Result of the "show global status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.ping\[connString, <username>, <password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.replication.discovery\[connString, <username>, <password>\]|<|<|<|<| |<|List of MySQL replications. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|Result of the "show slave status" SQL query in LLD JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.replication.get\_slave\_status\[connString, <username>, <password>, <masterHost>\]|<|<|<|<| |<|Replication status.|Result of the "show slave status" SQL query in JSON format.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.<br>**masterHost** - Replication master host name.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |mysql.version\[connString, <username>, <password>\]|<|<|<|<| |<|MySQL version.|String with MySQL instance version.|**connString** - URI or session name.<br>**username, password** - MySQL login credentials.|This item is supported for the [MySQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|ASM disk groups statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.diskgroups.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of ASM disk groups. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.archive.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Archive logs statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.cdb.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|CDBs info.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.custom.query\[connString,<user>,<password>,<service>, queryName, <args...>\]|<|<|<|<| |<|Result of a custom query.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**queryName** — name of a custom query (must be equal to a name of an sql file without an extension).<br>**args...** — one or several comma-separated arguments to pass to a query.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.datafiles.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Data files statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.db.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|FRA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.instance.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Instance statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pdb.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|PDBs info.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pdb.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of PDBs. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|PGA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ping\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Tests whether a connection to Oracle can be established.|0 - connection is broken (if there is any error presented including AUTH and configuration issues)<br>1 - connection is successful.|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.proc.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Processes statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.redolog.info\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Log file information from the control file.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|SGA statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sessions.stats\[connString,<user>,<password>,<service>,<lockMaxTime>\]|<|<|<|<| |<|Sessions statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**lockMaxTime** - maximum session lock duration in seconds to count the session as a prolongedly locked. Default: 600 seconds.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sys.metrics\[connString,<user>,<password>,<service>,<duration>\]|<|<|<|<| |<|A set of system metric values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**duration** - capturing interval (in seconds) of system metric values. Possible values: *60* — long duration (default), *15* — short duration.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.sys.params\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|A set of system parameter values.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ts.stats\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|Tablespaces statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.ts.discovery\[connString,<user>,<password>,<service>\]|<|<|<|<| |<|List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |oracle.user.info\[connString,<user>,<password>,<username>\]|<|<|<|<| |<|List of tablespaces. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**username** - a username, for which the information is needed. Lowercase usernames are not supported. Default: current user.|This item is supported for the [Oracle plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.autovacuum.count\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of autovacuum workers.|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.archive\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Information about archived files.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.archive.count\_archived\_files** - the number of WAL files that have been successfully archived.<br>**pgsql.archive.failed\_trying\_to\_archive** - the number of failed attempts for archiving WAL files.<br>**pgsql.archive.count\_files\_to\_archive** - the number of files to archive.<br>**pgsql.archive.size\_files\_to\_archive** -the size of files to archive.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.bgwriter\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Combined number of checkpoints for the database cluster, broken down by checkpoint type.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.bgwriter.buffers\_alloc** - the number of buffers allocated.<br>**pgsql.bgwriter.buffers\_backend** -the number of buffers written directly by a backend.<br>**pgsql.bgwriter.maxwritten\_clean** - the number of times the background writer stopped a cleaning scan, because it had written too many buffers.<br>**pgsql.bgwriter.buffers\_backend\_fsync** -the number of times a backend had to execute its own fsync call instead of the background writer.<br>**pgsql.bgwriter.buffers\_clean** - the number of buffers written by the background writer.<br>**pgsql.bgwriter.buffers\_checkpoint** - the number of buffers written during checkpoints.<br>**pgsql.bgwriter.checkpoints\_timed** - the number of scheduled checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoints\_req** - the number of requested checkpoints that have been performed.<br>**pgsql.bgwriter.checkpoint\_write\_time** - the total amount of time spent in the portion of checkpoint processing where files are written to disk, in milliseconds.<br>**pgsql.bgwriter.sync\_time** - the total amount of time spent in the portion of checkpoint processing where files are synchronized with disk.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.cache.hit\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|PostgreSQL buffer cache hit rate.|SQL query in percentage.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.connections\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Connections by type.|JSON object.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.connections.active** - the backend is executing a query.<br>**pgsql.connections.fastpath\_function\_call** -the backend is executing a fast-path function.<br>**pgsql.connections.idle** - the backend is waiting for a new client command.<br>**pgsql.connections.idle\_in\_transaction** - the backend is in a transaction, but is not currently executing a query.<br>**pgsql.connections.prepared** - the number of prepared connections.<br>**pgsql.connections.total** - the total number of connections.<br>**pgsql.connections.total\_pct** - percantange of total connections in respect to ‘max\_connections’ setting of the PostgreSQL server.<br>**pgsql.connections.waiting** - number of connections in a query.<br>**pgsql.connections.idle\_in\_transaction\_aborted** - the backend is in a transaction, but is not currently executing a query and one of the statements in the transaction caused an error.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.dbstat\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Collects statistics per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.dbstat.numbackends\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_read\_time\["{\#DBNAME}"\]** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time\["{\#DBNAME}"\]** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures\["{\#DBNAME}"\]** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled.(PostgreSQL version 12 only)<br>**pgsql.dbstat.blks\_read.rate\["{\#DBNAME}"\]** - the number of disk blocks read in this database.<br>**pgsql.dbstat.deadlocks.rate\["{\#DBNAME}"\]** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.blks\_hit.rate\["{\#DBNAME}"\]** - the number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL Pro buffer cache, not the operating system's file system cache).<br>**pgsql.dbstat.xact\_rollback.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been rolled back.<br>**pgsql.dbstat.xact\_commit.rate\["{\#DBNAME}"\]** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.tup\_updated.rate\["{\#DBNAME}"\]** - the number of rows updated by queries in this database.<br>**pgsql.dbstat.tup\_returned.rate\["{\#DBNAME}"\]** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.tup\_inserted.rate\["{\#DBNAME}"\]** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.tup\_fetched.rate\["{\#DBNAME}"\]** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.tup\_deleted.rate\["{\#DBNAME}"\]** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.conflicts.rate\["{\#DBNAME}"\]** - the number of queries canceled due to conflicts with recovery in this database (the conflicts occur only on standby servers).<br>**pgsql.dbstat.temp\_files.rate\["{\#DBNAME}"\]** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.temp\_bytes.rate\["{\#DBNAME}"\]** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.dbstat.sum\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Summarized data for all databases in a cluster.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by the dependent items:<br>**pgsql.dbstat.numbackends** - the number of backends currently connected to this database.<br>**pgsql.dbstat.sum.blk\_read\_time** - time spent reading data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.blk\_write\_time** - time spent writing data file blocks by backends in this database, in milliseconds.<br>**pgsql.dbstat.sum.checksum\_failures** - the number of data page checksum failures detected (or on a shared object), or NULL if data checksums are not enabled (PostgreSQL version 12 only).<br>**pgsql.dbstat.sum.xact\_commit** - the number of transactions in this database that have been committed.<br>**pgsql.dbstat.sum.conflicts** - database statistics about query cancels due to conflict with recovery on standby servers.<br>**pgsql.dbstat.sum.deadlocks** - the number of deadlocks detected in this database.<br>**pgsql.dbstat.sum.blks\_read** - the number of disk blocks read in this database.<br>**pgsql.dbstat.sum.blks\_hit** - the number of times disk blocks were found already in the buffer cache, so a read was not necessary (only hits in the PostgreSQL Pro buffer cache are included).<br>**pgsql.dbstat.sum.temp\_bytes** - the total amount of data written to temporary files by queries in this database. Includes data from all temporary files, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.temp\_files** - the number of temporary files created by queries in this database. All temporary files are counted, regardless of the log\_temp\_files settings and reasons for which the temporary file was created (e.g., sorting or hashing).<br>**pgsql.dbstat.sum.xact\_rollback** - the number of rolled-back transactions in this database.<br>**pgsql.dbstat.sum.tup\_deleted** - the number of rows deleted by queries in this database.<br>**pgsql.dbstat.sum.tup\_fetched** - the number of rows fetched by queries in this database.<br>**pgsql.dbstat.sum.tup\_inserted** - the number of rows inserted by queries in this database.<br>**pgsql.dbstat.sum.tup\_returned** - the number of rows returned by queries in this database.<br>**pgsql.dbstat.sum.tup\_updated** - the number of rows updated by queries in this database.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.age\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Age of the oldest FrozenXID of the database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query for specific database in transactions.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.bloating\_tables\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of bloating tables per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.discovery\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|List of the PostgreSQL databases. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query in the LLD JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.db.size\[uri,<username>,<password>, dbName\]|<|<|<|<| |<|Database size in bytes. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQL query for specific database in bytes.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.locks\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Information about granted locks per database. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|SQl query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.locks.shareupdateexclusive\["{\#DBNAME}"\]** - the number of share update exclusive locks.<br>**pgsql.locks.accessexclusive\["{\#DBNAME}"\]** - the number of access exclusive locks.<br>**pgsql.locks.accessshare\["{\#DBNAME}"\]** - the number of access share locks.<br>**pgsql.locks.exclusive\["{\#DBNAME}"\]** - the number of exclusive locks.<br>**pgsql.locks.rowexclusive\["{\#DBNAME}"\]** - the number of row exclusive locks.<br>**pgsql.locks.rowshare\["{\#DBNAME}"\]** - the number of row share locks.<br>**pgsql.locks.share\["{\#DBNAME}"\]** - the number of shared locks.<br>**pgsql.locks.sharerowexclusive\["{\#DBNAME}"\]** - the number of share row exclusive locks.<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.oldest.xid\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Age of the oldest XID.|SQl query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.ping\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Tests whether a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues).|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.count\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The number of standby servers.|SQL query.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.recovery\_role\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Recovery status.|0 - master mode<br>1 - recovery is still in progress (standby mode)|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication.status\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|The status of replication.|0 - streaming is down<br>1 - streaming is up<br>2 - master mode|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication\_lag.b\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Replication lag in bytes.|SQL query in bytes.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.replication\_lag.sec\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|Replication lag in seconds.|SQL query in seconds.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.uptime\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|PostgreSQL uptime in milliseconds.|SQL query in milliseconds.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |pgsql.wal.stat\[uri,<username>,<password>, <dbName>\]|<|<|<|<| |<|WAL statistics.|SQL query in JSON format.|**uri** - URI or session name.<br>**username, password** - PostgreSQL credentials.<br>**dbName** - Database name.|Returned data are processed by dependent items:<br>**pgsql.wal.count** — the number of WAL files.<br>**pgsql.wal.write** - the WAL lsn used (in bytes).<br><br>This item is supported since Zabbix 5.0.1 for the [PostgreSQL plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.config\[connString,<password>,<pattern>\]|<|<|<|<| |<|Gets the configuration parameters of a Redis instance that match the pattern.|JSON - if a glob-style pattern was used<br><br>single value - if a pattern did not contain any wildcard character|**connString** - URI or session name.<br>**password** - Redis password.<br>**pattern** - glob-style pattern (*\** by default).|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.info\[connString,<password>,<section>\]|<|<|<|<| |<|Gets the output of the INFO command.|JSON - output is serialized as JSON|**connString** - URI or session name.<br>**password** - Redis password.<br>**section** - [section](https://redis.io/commands/info) of information (*default* by default).|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.ping\[connString,<password>\]|<|<|<|<| |<|Test if a connection is alive or not.|1 - connection is alive<br><br>0 - connection is broken (if there is any error presented including AUTH and configuration issues)|**connString** - URI or session name.<br>**password** - Redis password.|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |redis.slowlog.count\[connString,<password>\]|<|<|<|<| |<|The number of slow log entries since Redis was started.|Integer|**connString** - URI or session name.<br>**password** - Redis password.|This item is supported since Zabbix 4.4.5 for the [Redis plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.attribute.discovery|<|<|<|<| |<|Returns a list of S.M.A.R.T. device attributes.|JSON object|<|The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#ID}, {\#ATTRNAME}, {\#THRESH}.<br>HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"}<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.disk.discovery|<|<|<|<| |<|Returns a list of S.M.A.R.T. devices.|JSON object|<|The following macros and their values are returned: {\#NAME}, {\#DISKTYPE}, {\#MODEL}, {\#SN}.<br>HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID. {\#NAME} will have an add-on in case of RAID, e.g: {"{\#NAME}": "/dev/sda cciss,2"}<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |smart.disk.get|<|<|<|<| |<|Returns all available properties of S.M.A.R.T. devices.|JSON object|<|HDD, SSD and NVME drive types are supported. Drives can be alone or combined in a RAID.<br>The data includes smartctl version and call arguments, and additional fields:<br>*disk\_name* - holds the name with the required add-ons for RAID discovery, e.g: {"disk\_name": "/dev/sda cciss,2"}<br>*disk\_type* - holds the disk type HDD, SSD, or NVME, e.g: {"disk\_type": "ssd"})<br><br>This item is supported for the [Smart plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box).| |systemd.unit.get\[unit name,<interface>\]|<|<|<|<| |<|Returns all properties of a systemd unit.|JSON object|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**interface** - unit interface type, possible values: *Unit* (default), *Service*, *Socket*, *Device*, *Mount*, *Automount*, *Swap*, *Target*, *Path*|This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.<br><br>LoadState, ActiveState and UnitFileState for Unit interface are returned as text and integer:<br>`"ActiveState":{"state":1,"text":"active"}`| |systemd.unit.info\[unit name,<property>,<interface>\]|<|<|<|<| |<|Systemd unit information.|String|**unit name** - unit name (you may want to use the {\#UNIT.NAME} macro in item prototype to discover the name)<br>**property** - unit property (e.g. ActiveState (default), LoadState, Description)<br>**interface** - unit interface type (e.g. Unit (default), Socket, Service)|This item allows to retrieve a specific property from specific type of interface as described in [dbus API](https://www.freedesktop.org/wiki/Software/systemd/dbus/).<br><br>This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.<br><br>Examples:<br>=> systemd.unit.info\["{\#UNIT.NAME}"\] - collect active state (active, reloading, inactive, failed, activating, deactivating) info on discovered systemd units<br>=> systemd.unit.info\["{\#UNIT.NAME}",LoadState\] - collect load state info on discovered systemd units<br>=> systemd.unit.info\[mysqld.service,Id\] - retrieve service technical name (mysqld.service)<br>=> systemd.unit.info\[mysqld.service,Description\] - retrieve service description (MySQL Server)<br>=> systemd.unit.info\[mysqld.service,ActiveEnterTimestamp\] - retrieve the last time the service entered the active state (1562565036283903)<br>=> systemd.unit.info\[dbus.socket,NConnections,Socket\] - collect the number of connections from this socket unit| |systemd.unit.discovery\[<type>\]|<|<|<|<| |<|List of systemd units and their details. Used for [low-level discovery](/manual/discovery/low_level_discovery/examples/systemd).|JSON object|**type** - possible values: *all*, *automount*, *device*, *mount*, *path*, *service* (default), *socket*, *swap*, *target*|This item is supported for the [Systemd plugin](/manual/config/items/plugins#plugins_supplied_out-of-the-box) on Linux platform only.| |web.certificate.get\[hostname,<port>,<address>\]|<|<|<|<| |<|Validates certificates and returns certificate details.|JSON object|**hostname** - can be either IP or DNS.<br>May contain the URL scheme (*https* only), path (it will be ignored), and port.<br>If a port is provided in both the first and the second parameters, their values must match.<br>If address (the 3rd parameter) is specified, the hostname is only used for SNI and hostname verification.<br>**port** - port number (default is 443 for HTTPS).<br>**address** - can be either IP or DNS. If specified, it will be used for connection, and hostname (the 1st parameter) will be used for SNI, and host verification.<br>In case, the 1st parameter is an IP and the 3rd parameter is DNS, the 1st parameter will be used for connection, and the 3rd parameter will be used for SNI and host verification.|This item turns unsupported if the resource specified in `host` does not exist or is unavailable or if TLS handshake fails with any error except an invalid certificate.<br><br>Currently, AIA (Authority Information Access) X.509 extension, CRLs and OCSP (including OCSP stapling), Certificate Transparency, and custom CA trust store are not supported.|  