en-us	##### Notification about canceled escalations  When configuring [action operations](/manual/config/notifications/action/operation#configuring-an-operation), it is now possible to cancel notifications about canceled escalations by unmarking the checkbox of the corresponding option.  ##### Monitoring → Overview removed  The Overview section in the Monitoring menu has been removed completely. The same functionality can be still accessed by using the *Data overview* and *Trigger overview* dashboard [widgets](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets).  
zh-cn	#### Miscellaneous  -   The default language of Zabbix web interface has been changed from     British to American English. Support of British English has been     dropped. -   The Share link in the main menu has been replaced by an Integrations     link, leading to the     [Integrations](https://www.zabbix.com/integrations) page on the     Zabbix website. -   If Zabbix web interface is opened in one of the languages available     on the Zabbix website, clicking the Integrations link will open the     Integrations page in the appropriate language. For all other     languages, including English, the Integrations page will be opened     in English.  

en-us	#### Numeric (float) data type range with PostgreSQL 11 and earlier  PostgreSQL 11 and earlier versions only support floating point value range of approximately -1.34E-154 to 1.34E+154.
zh-cn	#### PostgreSQL 11 及更早版本的数据库支持的浮点数类型范围  PostgreSQL 11 及更早版本仅支持大约 -1.34E-154 到 1.34E+154 的浮点数范围。

en-us	#### Numeric representation  Windows maintains numeric representations (indexes) for object and performance counter names. Zabbix supports these numeric representations as parameters to the `perf_counter`, `perf_counter_en` item keys and in `PerfCounter`, `PerfCounterEn` configuration parameters.  However, it's not recommended to use them unless you can guarantee your numeric indexes map to correct strings on specific hosts. If you need to create portable items that work across different hosts with various localized Windows versions, you can use the `perf_counter_en` key or `PerfCounterEn` configuration parameter which allow to use English names regardless of system locale.  To find out the numeric equivalents, run **regedit**, then find *HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*.  The registry entry contains information like this:      1     1847     2     System     4     Memory     6     % Processor Time     10     File Read Operations/sec     12     File Write Operations/sec     14     File Control Operations/sec     16     File Read Bytes/sec     18     File Write Bytes/sec     ....  Here you can find the corresponding numbers for each string part of the performance counter, like in '\\System\\% Processor Time':      System → 2     % Processor Time → 6  Then you can use these numbers to represent the path in numbers:      \2\6
zh-cn	#### 数字表示  由于性能计数器的命名在不同的Windows服务器上可能不同，这取决于服务器的地区设置。因此，在创建用于监控具有不同地区设置的多台Windows设备的模板时，会引发一定的问题。\  同时，每个新能计数器也可以通过其数字形式来引用，无论如何，数字形式都是唯一的，因此你可以使用数字表示而不是字符串。\  为了找到同义的数字，需要运行 **regedit**，然后找到*HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib\\009*这个注册表。\  注册表中包含形如下面所示的信息：       · 1      · 1847      · 2      · System      · 4      · Memory      · 6      · % Processor Time      · 10      · File Read Operations/sec      · 12      · File Write Operations/sec      · 14      · File Control Operations/sec      · 16      · File Read Bytes/sec      · 18      · File Write Bytes/sec      · ....  这样你就可以找到性能计数器每个字符串对应的数字，例如：       · System → 2      · % Processor Time → 6  然后你就可以使用这些数字来表示性能计数器路径：       · \2\6

en-us	#### Obtaining sensor names  Sensor labels, as printed by the *sensors* command, cannot always be used directly because the naming of labels may be different for each sensor chip vendor. For example, *sensors* output might contain the following lines:      $ sensors     in0:         +2.24 V  (min =  +0.00 V, max =  +3.32 V)        Vcore:       +1.15 V  (min =  +0.00 V, max =  +2.99 V)        +3.3V:       +3.30 V  (min =  +2.97 V, max =  +3.63 V)        +12V:       +13.00 V  (min =  +0.00 V, max = +15.94 V)     M/B Temp:    +30.0°C  (low  = -127.0°C, high = +127.0°C)  Out of these, only one label may be used directly:      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in0]     2.240000  Attempting to use other labels (like *Vcore* or *+12V*) will not work.      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,Vcore]     ZBX_NOTSUPPORTED  To find out the actual sensor name, which can be used by Zabbix to retrieve the sensor readings, run *sensors -u*. In the output, the following may be observed:      $ sensors -u     ...     Vcore:       in1_input: 1.15       in1_min: 0.00       in1_max: 2.99       in1_alarm: 0.00     ...         +12V:       in4_input: 13.00       in4_min: 0.00       in4_max: 15.94       in4_alarm: 0.00     ...  So *Vcore* should be queried as *in1*, and *+12V* should be queried as *in4*.[^1]      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in1]     1.301000  Not only voltage (in), but also current (curr), temperature (temp) and fan speed (fan) readings can be retrieved by Zabbix.  [^1]: According to     [specification](https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface)     these are voltages on chip pins and generally speaking may need     scaling.
zh-cn	 #### 获取传感器的名字  传感器标签，由 sensors 命令打印，不能总是被直接使用，因为标签的命名对于每个传感器芯片供应商来说可能是不同的。 例如,   sensors  输出可能包含以下几行:      $ sensors     in0:         +2.24 V  (min =  +0.00 V, max =  +3.32 V)        Vcore:       +1.15 V  (min =  +0.00 V, max =  +2.99 V)        +3.3V:       +3.30 V  (min =  +2.97 V, max =  +3.63 V)        +12V:       +13.00 V  (min =  +0.00 V, max = +15.94 V)     M/B Temp:    +30.0°C  (low  = -127.0°C, high = +127.0°C)  在这些情况下，只有一个标签可以直接使用:      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in0]     2.240000  尝试使用其他标签 (像   Vcore   或   +12V ) 是不会起作用的。      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,Vcore]     ZBX_NOTSUPPORTED  为了找到实际的Zabbix可以使用它来检索读数的传感器名称，运行   sensors -u 命令。 在输出中，可以看到到以下内容:      $ sensors -u     ...     Vcore:       in1_input: 1.15       in1_min: 0.00       in1_max: 2.99       in1_alarm: 0.00     ...         +12V:       in4_input: 13.00       in4_min: 0.00       in4_max: 15.94       in4_alarm: 0.00     ...  所有 Vcore  应该检索   in1 , +12V  应该检索  in4.[1]      $ zabbix_get -s 127.0.0.1 -k sensor[lm85-i2c-0-2e,in1]     1.301000  不止 电压 (in), 还有 电流 (curr), 温度 (temp) 和 风扇转速 (fan) 的读数都可以被Zabbix 检索到。  [^1]:  根据  [声明](https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface)  这些是芯片引脚上的电压，一般来说可能需要缩放。

en-us	#### ODBC checks  -   MySQL unixODBC driver should not be used with Zabbix server or     Zabbix proxy compiled against MariaDB connector library and vice     versa, if possible it is also better to avoid using the same     connector as the driver due to an [upstream     bug](https://bugs.mysql.com/bug.php?id=73709). Suggested setup:  ```{=html} <!-- --> ```     PostgreSQL, SQLite or Oracle connector → MariaDB or MySQL unixODBC driver     MariaDB connector → MariaDB unixODBC driver     MySQL connector → MySQL unixODBC driver  Please see [ZBX-7665](https://support.zabbix.com/browse/ZBX-7665) for more information and available workarounds.  -   XML data queried from Microsoft SQL Server may get truncated in     various ways on Linux and UNIX systems.  ```{=html} <!-- --> ``` -   It has been observed that using ODBC checks on CentOS 8 for     monitoring Oracle databases using Oracle Instant Client for Linux     11.2.0.4.0 causes the Zabbix server to crash. The issue can be     solved by upgrading Oracle Instant Client to 12.1.0.2.0, 12.2.0.1.0,     18.5.0.0.0 or 19. See also     [ZBX-18402](https://support.zabbix.com/browse/ZBX-18402).
zh-cn	#### ODBC 检查  -   不要在针对 MariaDB connector library 编译的 Zabbix server 或 Zabbix proxy 上使用 MySQL unixODBC 驱动程序，反之亦然。如果可以，由于 [上游 bug](https://bugs.mysql.com/bug.php?id=73709)，最好避免使用与驱动程序相同的连接器。建议设置：  ```{=html} <!-- --> ```     PostgreSQL, SQLite or Oracle connector → MariaDB or MySQL unixODBC driver     MariaDB connector → MariaDB unixODBC driver     MySQL connector → MySQL unixODBC driver  请参阅 [ZBX-7665](https://support.zabbix.com/browse/ZBX-7665) 了解更多信息和可用的解决方案。  -   从 Microsoft SQL Server 查询的 XML 数据在 Linux 和 UNIX 系统上可能会以各种方式被截断。  ```{=html} <!-- --> ```  -   在 CentOS 8 上用  Oracle Instant Client for Linux 11.2.0.4.0 通过 ODBC 检查监控 Oracle 数据库会导致 Zabbix server 崩溃。该问题可以通过将 Oracle Instant Client 升级到 12.1.0.2.0、12.2.0.1.0、18.5.0.0.0 或 19 来解决。另请参见 [ZBX-18402](https://support.zabbix.com/browse/ZBX-18402)。

en-us	# ODBC template operation  Steps to ensure correct operation of templates that collect metrics via [ODBC monitoring](/manual/config/items/itemtypes/odbc_checks):  1\. Make sure that required ODBC driver is installed on Zabbix server or proxy.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to a target host (if the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions).\ 3. Adjust the values of mandatory macros as needed.\ If a password placed in the macro value contains semicolon (;) it should be wrapped in curly brackets, see [ODBC monitoring](https://www.zabbix.com/documentation/6.0/en/manual/config/items/itemtypes/odbc_checks?hl=ODBC%2Cmonitoring) for details. 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column.  ::: notetip  This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items and triggers, is available in the template's Readme.md file (accessible by clicking on a template name).  :::  |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[MSSQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mssql_odbc/README.md)|**{$MSSQL.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$MSSQL.PORT}** - the TCP port of Microsoft SQL Server (default: 1433)<br>**{$MSSQL.USER}, {$MSSQL.PASSWORD}** - Microsoft SQL login credentials (default: not set)|Create a Microsoft SQL user for monitoring and grant the user the following permissions: View Server State; View Any Definition (see Microsoft SQL [documentation](https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/grant-a-permission-to-a-principal?view=sql-server-ver15) for details).<br><br>The "Service's TCP port state" item uses {HOST.CONN} and {$MSSQL.PORT} macros to check the availability of the Microsoft SQL instance.| |[MySQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_odbc/README.md)|**{$MYSQL.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$MYSQL.USER}, {$MYSQL.PASSWORD}** - MySQL login credentials; password can be blank (default: not set)|To grant required privileges to MySQL user that will be used for monitoring, run:<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br><br>See [MYSQL documentation](https://dev.mysql.com/doc/refman/8.0/en/grant.html) for details.| |[Oracle by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_odbc/README.md)|**{$ORACLE.DSN}** - the system data source name (default: <Put your DSN here>)<br>**{$ORACLE.PORT}** - the TCP port of Oracle DB (default: 1521)<br>**{$ORACLE.USER}, {$ORACLE.PASSWORD}** - Oracle login credentials (default: not set)|1\. To create an Oracle user for monitoring, run:<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Grant access to the zabbix_mon user.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon;`<br>`GRANT SELECT ON V_$instance TO zabbix_mon;`<br>`GRANT SELECT ON V_$database TO zabbix_mon;`<br>`GRANT SELECT ON v_$sysmetric TO zabbix_mon;`<br>`GRANT SELECT ON v$recovery_file_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$active_session_history TO zabbix_mon;`<br>`GRANT SELECT ON v$osstat TO zabbix_mon;`<br>`GRANT SELECT ON v$restore_point TO zabbix_mon;`<br>`GRANT SELECT ON v$process TO zabbix_mon;`<br>`GRANT SELECT ON v$datafile TO zabbix_mon;`<br>`GRANT SELECT ON v$pgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$sgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$log TO zabbix_mon;`<br>`GRANT SELECT ON v$archive_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$asm_diskgroup TO zabbix_mon;`<br>`GRANT SELECT ON sys.dba_data_files TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br><br>2. Make sure, that ODBC connects to Oracle with session parameter `NLS_NUMERIC_CHARACTERS= '.,'`<br><br>3. Add a new record to odbc.ini:<br>`[$ORACLE.DSN]`<br>`Driver = Oracle 19 ODBC driver`<br>`Servername = $ORACLE.DSN`<br>`DSN = $ORACLE.DSN`<br><br>4. Check the connection via isql:<br>`isql $TNS_NAME $DB_USER $DB_PASSWORD`<br><br>5. Configure Zabbix server or Zabbix proxy for Oracle ENV Usage. Edit or add a new file: */etc/sysconfig/zabbix-server*, or for the proxy: */etc/sysconfig/zabbix-proxy*. Then add the following lines to the file:<br>`export ORACLE_HOME=/usr/lib/oracle/19.6/client64`<br>`export PATH=$PATH:$ORACLE_HOME/bin`<br>`export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib64:/usr/lib:$ORACLE_HOME/bin`<br>`export TNS_ADMIN=$ORACLE_HOME/network/admin`<br><br>6. Restart Zabbix server or proxy.|
zh-cn	# ODBC模板操作  确保通过[ODBC monitoring](/manual/config/items/itemtypes/odbc_checks)收集模板指标的正确步骤:  1. 确保在 Zabbix 服务器或代理上安装了所需的 ODBC 驱动程序。 2. [链接](/manual/config/templates/linking#linking_a_template) 模板到目标主机（如果模板在您的 Zabbix 安装中不可用，您可能需要先导入模板的 .xml 文件 - 请参阅 [开箱即用的模板]（/manual/config/templates_out_of_the_box）部分的说明）。 3.根据需要调整必需宏的值。如果宏值中的密码包含分号（;），则应该用大括号括起来，参见[ODBC监控]（https://www.zabbix.com/documentation/ 6.0/en/manual/config/items/itemtypes/odbc_checks?hl=ODBC%2Cmonitoring) 了解详情。 4. 配置被监控的实例以允许与 Zabbix 共享数据 - 请参阅 *其他步骤/注释* 列中的说明。  ::: notetip 此页面仅包含正确模板操作所需的最小宏集和设置步骤。 模板的 Readme.md 文件中提供了模板的详细说明，包括宏、监控项和触发器的完整列表（可通过单击模板名称访问）。 :::  |模板|强制宏|附加步骤/注释| |--------|----------------|-------------------- --| |[MSSQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mssql_odbc/README.md)|**{$MSSQL.DSN}** - 系统数据源名称（默认：<填写你的DSN>）<br>**{$MSSQL.PORT}** - Microsoft SQL Server 的 TCP 端口（默认：1433）<br>**{$MSSQL.USER }, {$MSSQL.PASSWORD}** - Microsoft SQL 登录凭据（默认值：未设置）|创建用于监控的 Microsoft SQL 用户并授予用户以下权限：查看服务器状态； 查看任何定义（请参阅 Microsoft SQL [文档](https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/grant-a-permission-to-a-principal?view =sql-server-ver15) 以获得详细信息）。<br><br>“服务的 TCP 端口状态”监控项使用 {HOST.CONN} 和 {$MSSQL.PORT} 宏来检查 Microsoft SQL 实例的可用性。| |[MySQL by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/mysql_odbc/README.md)|**{$MYSQL.DSN}** - 系统数据源名称（默认：<填写你的DSN>）<br>**{$MYSQL.USER}, {$MYSQL.PASSWORD}** - MySQL 登录凭据； 密码可以为空（默认值：未设置）|要向将用于监控的 MySQL 用户授予所需的权限，请运行：<br>`GRANT USAGE,REPLICATION CLIENT,PROCESS,SHOW DATABASES,SHOW VIEW ON %% *.* TO '<username>'@'%';%%`<br><br>详见[MYSQL文档](https://dev.mysql.com/doc/refman/8.0/en/grant.html) .| |[Oracle by ODBC](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/oracle_odbc/README.md)|**{$ORACLE.DSN}** - 系统数据源名称（默认：<Put your DSN here>）<br>**{$ORACLE.PORT}** - Oracle DB 的 TCP 端口（默认：1521）<br>**{$ORACLE.USER} , {$ORACLE.PASSWORD}** - Oracle 登录凭据（默认值：未设置）|1。 要创建用于监控的 Oracle 用户，请运行：<br>`CREATE USER zabbix_mon IDENTIFIED BY <PASSWORD>;`<br>`-- Grant access to the zabbix_mon user.`<br>`GRANT CONNECT, CREATE SESSION TO zabbix_mon; `<br>`GRANT SELECT ON V_$instance TO zabbix_mon;`<br>`GRANT SELECT ON V_$database TO zabbix_mon;`<br>`GRANT SELECT ON v_$sysmetric TO zabbix_mon;`<br>`GRANT SELECT ON v$recovery_file_dest TO zabbix_mon;`<br>`GRANT SELECT ON v$active_session_history TO zabbix_mon;`<br>`GRANT SELECT ON v$osstat TO zabbix_mon;`<br>`GRANT SELECT ON v$restore_point TO zabbix_mon;`< br>`GRANT SELECT ON v$process TO zabbix_mon;`<br>`GRANT SELECT ON v$datafile TO zabbix_mon;`<br>`GRANT SELECT ON v$pgastat TO zabbix_mon;`<br>`GRANT SELECT ON v$ sgastat 到 zabbix_mon;`<br>`GRANT SELECT ON v$log 到 zabbix_mon;`<br>`GRANT SELECT ON v$archive_dest 到 zabbix_mon;`<br>`GRANT SELECT ON v$asm_diskgroup 到 zabbix_mon;`<br> `GRANT SELECT ON sys.dba_data_files TO zabbix_mon;`<br>`GRANT SELECT ON DBA_TABLESPACES TO zabbix_mon;`<br>`GRAN T SELECT ON DBA_TABLESPACE_USAGE_METRICS TO zabbix_mon;`<br>`GRANT SELECT ON DBA_USERS TO zabbix_mon;`<br><br>2. 确保 ODBC 使用会话参数连接到 Oracle `NLS_NUMERIC_CHARACTERS= '.,'`<br><br>3. 向 odbc.ini 添加一条新记录：<br>`[$ORACLE.DSN]`<br>`Driver = Oracle 19 ODBC driver`<br>`Servername = $ORACLE.DSN`<br>`DSN = $ORACLE .DSN`<br><br>4. 通过 isql 检查连接：<br>`isql $TNS_NAME $DB_USER $DB_PASSWORD`<br><br>5. 为 Oracle ENV 使用配置 Zabbix 服务器或 Zabbix 代理。 编辑或添加一个新文件：*/etc/sysconfig/zabbix-server*，或者对于代理：*/etc/sysconfig/zabbix-proxy*。 然后将以下行添加到文件中：<br>`export ORACLE_HOME=/usr/lib/oracle/19.6/client64`<br>`export PATH=$PATH:$ORACLE_HOME/bin`<br>`export LD_LIBRARY_PATH=$ ORACLE_HOME/lib:/usr/lib64:/usr/lib:$ORACLE_HOME/bin`<br>`export TNS_ADMIN=$ORACLE_HOME/network/admin`<br><br>6. 重新启动 Zabbix 服务器或代理。

en-us	#### OK events  An OK event closes the related problem event(s) and may be created by 3 components:  -   triggers - based on 'OK event generation' and 'OK event closes'     settings; -   event correlation -   task manager – when an event is [manually     closed](/manual/config/events/manual_close)
zh-cn	#### 正常事件  一个正常事件会关闭关联的问题事件，可能由以下3个组件生成：  -   触发器——基于“正常事件生成”和“正常事件关闭” -   事件关联 -   任务管理器——当一个事件[手动关闭](/manual/config/events/manual_close)时

en-us	#### Okta configuration  1\. Go to <https://okta.com> and register or sign in to your account.  2\. In the Okta web interface navigate to *Applications → Applications* and press "Add Application" button (![](../../../../assets/en/manual/appendix/install/okta_add_app.png)).  3\. Press "Create New App" button (![](../../../../assets/en/manual/appendix/install/okta_create_app.png)). In a popup window select *Platform:* Web, *Sign on method:* SAML 2.0 and press "Create" button.  ![](../../../../assets/en/manual/appendix/install/okta_app1.png){width="600"}  4\. Fill in the fields in the *General settings* tab (the first tab that appears) according to your preferences and press "Next".  5\. In the *Configure SAML* tab enter the values provided below, then press "Next".  -   In the **GENERAL** section:     -   *Single sign on URL*:         https://<your-zabbix-url>/ui/index\_sso.php?acs\         The checkbox *Use this for Recipient URL and Destination URL*         should be marked)     -   *Audience URI (SP Entity ID)*: zabbix\         Note, that this value will be used within the SAML assertion as         a unique service provider identifier (if not matching, the         operation will be rejected). It is possible to specify a URL or         any string of data in this field.     -   *Default RelayState*:\         Leave this field blank; if a custom redirect is required, it can         be added in Zabbix in the *Administration → Users* settings.     -   Fill in other fields according to your preferences.  ![](../../../../assets/en/manual/appendix/install/okta_app2.png)  ::: noteclassic  If planning to use encrypted connection, generate private and public encryption certificates, then upload public certificate to Okta. Certificate upload form appears when *Assertion Encryption* is set to Encrypted (click *Show Advanced Settings* to find this parameter).  :::  -   In the **ATTRIBUTE STATEMENTS (OPTIONAL)** section add an attribute     statement with:     -   *Name:* usrEmail     -   *Name format:* Unspecified     -   *Value:* user.email  ![](../../../../assets/en/manual/appendix/install/okta_app3.png)  6\. At the next tab, select "I'm a software vendor. I'd like to integrate my app with Okta" and press "Finish".  7\. Now, navigate to *Assignments* tab and press the "Assign" button, then select *Assign to People* from the drop-down.  ![](../../../../assets/en/manual/appendix/install/okta_assign.png)  8\. In a popup that appears, assign created app to people that will use SAML 2.0 to authenticate with Zabbix, then press "Save and go back".  9\. Navigate to the *Sign On* tab and press the "View Setup Instructions" button. Setup instructions will be displayed in a new tab; keep this tab open while configuring Zabbix.  ![](../../../../assets/en/manual/appendix/install/okta_setup.png)
zh-cn	#### Okta 配置  1\. 前往 <https://okta.com> 注册或登录您的帐户.  2\. 在 Okta 页面中找到*Applications → Applications*并点击 "Add Application" (![](../../../../assets/en/manual/appendix/install/okta_add_app.png)).  3\. 点击 "Create New App"  (![](../../../../assets/en/manual/appendix/install/okta_create_app.png)). 在弹出窗口中，选择 *Platform:* , *Sign on method:* SAML 2.0 并点击 "Create" 按钮.  ![](../../../../assets/en/manual/appendix/install/okta_app1.png){width="600"}  4\. 根据您的喜好填写 *General settings* 选项卡（第一个选项卡）并点击 "Next".  5\. 在 *Configure SAML* 选项中输入下面提供的值并点击"Next"按钮.  -   在 **GENERAL** 部分:     -   *Single sign on URL*:         https://<your-zabbix-url>/ui/index\_sso.php?acs\         复选框 *Use this for Recipient URL and Destination URL*         应为勾选的)     -   *Audience URI (SP Entity ID)*: zabbix\         请注意，此值将在 SAML 用作程序唯一的标识符（如果不匹配，则将拒绝操作）。可以在此字段中指定 URL 或任何数据字符串     -   *Default RelayState*:\        将此字段为空;如果需要自定义, 可以在Zabbix的 *Administration → Users* 设置中添加它.     -   根据您的喜好填写其他字段。  ![](../../../../assets/en/manual/appendix/install/okta_app2.png)  ::: noteclassic 如果计划使用加密连接，请生成私有和公有加密证书，然后将公有证书上传到Okta。当*Assertion Encryption* 设置为 "已加密"时，则将显示证书上传表单（单击*Show Advanced Settings* 以查找此参数）。 :::  -   在 **ATTRIBUTE STATEMENTS (OPTIONAL)** 添加一个属性语句:     -   *Name:* usrEmail     -   *Name format:* Unspecified     -   *Value:* user.email  ![](../../../../assets/en/manual/appendix/install/okta_app3.png)  6\. 在下一个选项卡中，选择"I'm a software vendor. I'd like to integrate my app with Okta"，然后点击"Finish"。  7\. 导航至 *Assignments* 选项，并点击"Assign" , 然后从下拉列表中选择 *Assign to People* .  ![](../../../../assets/en/manual/appendix/install/okta_assign.png)  8\. 在弹出窗口中，将创建的应用分配给使用SAML 2.0身份验证的Zabbix人员，然后按 "Save and go back".  9\. 导航到*Sign On*选项卡，然后按"View Setup Instructions"按钮。新选项卡将显示设置说明;在配置Zabbix时保持此选项卡打开。  ![](../../../../assets/en/manual/appendix/install/okta_setup.png)

en-us	#### Older XML protocol  ::: noteclassic Zabbix will take up to 16 MB of XML Base64-encoded data, but a single decoded value should be no longer than 64 KB otherwise it will be truncated to 64 KB while decoding. :::
zh-cn	#### 较旧的 XML 协议  ::: noteclassic Zabbix将占用16 MB的XML base64编码的数据, 但单个解码值应该不超过64kb，否则，在解码时将被截断到64 KB。 :::

en-us	#### One side connects with certificate but other side accepts only PSK or vice versa  In any log (with *GnuTLS*):      failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\         -21 Could not negotiate a supported cipher suite.  In any log (with *OpenSSL* 1.0.2c):      failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\         file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\         TLS write fatal alert "handshake failure"
zh-cn	#### 一端使用证书连接，但另一端仅接受 PSK，反之亦然  在任意日志当中有如下显示 (对于 *GnuTLS*)：      failed to accept an incoming connection: from 127.0.0.1: zbx_tls_accept(): gnutls_handshake() failed:\         -21 Could not negotiate a supported cipher suite.  在任意日志当中有如下显示 (对于 *OpenSSL* 1.0.2c)：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake returned error code 1:\         file .\ssl\s3_srvr.c line 1411: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher:\         TLS write fatal alert "handshake failure"

en-us	#### One side connects with PSK but other side uses LibreSSL or has been compiled without encryption support  LibreSSL does not support PSK.  In connecting-side log:      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success  In accepting-side log:      ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in  In Zabbix frontend:      Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success
zh-cn	#### 一端使用 PSK 连接，但另一端使用 LibreSSL 或已编译为无加密支持  LibreSSL 不支持 PSK。  在发起连接端的日志中有如下显示：      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success  在接受连接端的日志中：      ...failed to accept an incoming connection: from 192.168.1.2: support for PSK was not compiled in  在Zabbix前端有如下显示：      Get value from agent failed: TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() I/O error: [0] Success

en-us	#### One side connects with PSK but other side uses OpenSSL with PSK support disabled  In connecting-side log:      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure"  In accepting-side log:      ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure"
zh-cn	#### 一端使用 PSK 连接，但另一端使用禁用 PSK 支持的 OpenSSL  在发起连接端的日志中有如下显示：      ...TCP successful, cannot establish TLS to [[192.168.1.2]:10050]: SSL_connect() set result code to SSL_ERROR_SSL: file ../ssl/record/rec_layer_s3.c line 1536: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure: SSL alert number 40: TLS read fatal alert "handshake failure"  在接受连接端的日志中有如下显示：      ...failed to accept an incoming connection: from 192.168.1.2: TLS handshake set result code to 1: file ssl/statem/statem_srvr.c line 1422: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher: TLS write fatal alert "handshake failure"

en-us	##### On Linux 2.4:  (Sensor readings are obtained from /proc/sys/dev/sensors directory)  -   **device** - device name (if <mode> is used, it is a regular     expression); -   **sensor** - sensor name (if <mode> is used, it is a regular     expression); -   **mode** - possible values: avg, max, min (if this parameter is     omitted, device and sensor are treated verbatim).  Example key: sensor\[w83781d-i2c-0-2d,temp1\]  Prior to Zabbix 1.8.4, the sensor\[temp1\] format was used.
zh-cn	##### 当 Linux 2.4:  (传感器读数从/proc/sys/dev/sensor目录获得)  -   **device**  - 设备名字 (如果使用了<mode>， 则是正则表达式); -   **sensor**  - 传感器名字 (如果使用了<mode>， 则是正则表达式); -   **mode**  - 可能的值: avg, max, min (如果忽略了这个参数，设备和传感器将逐字处理)。  例子: sensor[w83781d-i2c-0-2d,temp1]  在Zabbix 1.8.4之前，使用了sensor[temp1]格式。

en-us	##### On Linux 2.6+:  (Sensor readings are obtained from /sys/class/hwmon directory)  -   **device** - device name (non regular expression). The device name     could be the actual name of the device (e.g 0000:00:18.3) or the     name acquired using sensors program (e.g. k8temp-pci-00c3). It is up     to the user to choose which name to use; -   **sensor** - sensor name (non regular expression); -   **mode** - possible values: avg, max, min (if this parameter is     omitted, device and sensor are treated verbatim).  Example key:  sensor\[k8temp-pci-00c3,temp,max\] or sensor\[0000:00:18.3,temp1\]  sensor\[smsc47b397-isa-0880,in,avg\] or sensor\[smsc47b397.2176,in1\]
zh-cn	##### 当 Linux 2.6+: (传感器读数从/sys/class/hwmon目录获得)  -   **device**  - 设备名称(非正则表达式)。 设备名称可以是设备的实际名称(e.g 0000:00:18.3)或使用传感器程序获取得的名称(例如:k8temp-pci-00c3)，这由用户决定使用哪个名称; -   **sensor**  - 传感器名称(非正则表达式); -   **mode**  - 可能的值: avg, max, min (如果忽略了这个参数，设备和传感器将逐字处理)。  例如:  sensor[k8temp-pci-00c3,temp, max] 或 sensor[0000:00:18.3,temp1]  sensor[smsc47b397-isa-0880,in, avg] 或 sensor[smsc47b397.2176,in1]

en-us	### Open file descriptor limit increase for Zabbix agent 2  The systemd service file shipped in Zabbix agent 2 packages now declares the open file descriptor limit of 8196. Previously, the system default limit of 1024 has been used. The new limit is sufficient for the default Zabbix agent 2 configuration. If you have a non-standard agent 2 configuration, for example, use additional plugins or extended features, this limit may need to be manually increased further. In this case, adjust the `LimitNOFILE` parameter in the systemd unit file.
zh-cn	### Zabbix agent 2 打开文件描述符限制增加  Zabbix agent 2 包中提供的 systemd 服务文件现在声明打开文件描述符限制为 8196。以前，系统默认限制为 1024。 新限制足以满足默认的 Zabbix agent 2 配置。 如果您有非标准agent 2 配置，例如，使用额外的插件或扩展功能，则可能需要手动进一步增加此限制。 在这种情况下，调整 systemd 单元文件中的 `LimitNOFILE` 参数。

en-us	### Open file descriptor limit increase for Zabbix agent 2  The systemd service file shipped in Zabbix agent 2 packages now declares the open file descriptor limit of 8196. Previously, the system default limit of 1024 has been used. The new limit is sufficient for the default Zabbix agent 2 configuration. If you have a non-standard agent 2 configuration, for example, use additional plugins or extended features, this limit may need to be manually increased further. In this case, adjust the `LimitNOFILE` parameter in the systemd unit file.
zh-cn	### Zabbix agent 2 打开文件描述符限制增加  Zabbix agent 2 包中附带的 systemd 服务文件现在声明打开文件描述符限制为 8196。以前，系统默认限制为 1024。新限制足以满足默认 Zabbix agent 2 配置。如果您有非 -standard agent 2 配置，例如，使用额外的插件或扩展功能，此限制可能需要手动进一步增加。在这种情况下，调整 systemd 单元文件中的 `LimitNOFILE` 参数。

en-us	 ### OpenSSL 3.0 support  OpenSSL 3.0.x is now supported. Note that this change does not affect frontend  encryption (which uses its own openssl-php package) and Java gateway JMX encrypted  connections to monitoring targets (which uses its own Java encrypted libraries). 
zh-cn	 ### OpenSSL 3.0 支持  现已支持 OpenSSL 3.0.x。请注意，此更改不会影响前端加密（使用自己的 openssl-php 包）和 Java 网关到监控目标的 JMX 加密连接（使用自己的 Java 加密库）。

en-us	#### OpenSSL used with CRLs and for some CA in the certificate chain its CRL is not included in `TLSCRLFile`  In TLS server log in case of *OpenSSL* peer:      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \         TLS write fatal alert "unknown CA"  In TLS server log in case of *GnuTLS* peer:      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\         block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin
zh-cn	#### OpenSSL 与 CRL 一起使用，对于证书链中的某些 CA，其 CRL 不包括在 "TLSCRLFile" 中  在 *OpenSSL* 对端的情况下，在 TLS 服务器日志中，会有如下显示：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file s3_srvr.c line 3251: error:14089086: SSL routines:ssl3_get_client_certificate:certificate verify failed: \         TLS write fatal alert "unknown CA"  在 *GnuTLS* 对端的情况下，在 TLS 服务器日志中，会有如下显示：      failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error code 1: \         file rsa_pk1.c line 103: error:0407006A: rsa routines:RSA_padding_check_PKCS1_type_1:\         block type is not 01 file rsa_eay.c line 705: error:04067072: rsa routines:RSA_EAY_PUBLIC_DECRYPT:paddin

en-us	#### Operating system  -   Use latest (stable!) version of OS -   Exclude unnecessary functionality from kernel -   Tune kernel parameters
zh-cn	 ####  操作系统  -   使用最新（稳定！）版本的操作系统 -   从内核中排除不必要的功能 -   调整内核参数

en-us	 #### Operation type: notify all involved  |Parameter|Description| |--|--------| |*Custom message*|If selected, a custom message can be defined.| |*Subject*|Subject of the custom message. The subject may contain macros.| |*Message*|The custom message. The message may contain macros.|
zh-cn	 #### 操作类型：通知所有相关人员  |参数|描述| |--|--------| |*自定义消息*|如果选中，则可以定义自定义消息。| |*主题*|自定义消息的主题。 主题可能包含宏。| |*消息*|自定义消息，消息可能包含宏。|

en-us	 #### Operation type: [remote command](/manual/config/notifications/action/operation/remote_command)  |Parameter|Description| |--|--------| |*Target list*|Select targets to execute the command on:<br>**Current host** - command is executed on the host of the trigger that caused the problem event. This option will not work if there are multiple hosts in the trigger.<br>**Host** - select host(s) to execute the command on.<br>**Host group** - select host group(s) to execute the command on. Specifying a parent host group implicitly selects all nested host groups. Thus the remote command will also be executed on hosts from nested groups.<br>A command on a host is executed only once, even if the host matches more than once (e.g. from several host groups; individually and from a host group).<br>The target list is meaningless if the command is executed on Zabbix server. Selecting more targets in this case only results in the command being executed on the server more times.<br>Note that for global scripts, the target selection also depends on the *Host group* setting in global script [configuration](/manual/web_interface/frontend_sections/administration/scripts#configuring_a_global_script).|
zh-cn	####操作类型：[远程命令](/manual/config/notifications/action/operation/remote_command)  |参数|说明| |--|--------| |*Target list*|选择要在其上执行命令的目标：<br>**当前主机** - 命令在导致问题事件的触发器的主机上执行。 如果触发器中有多个主机，此选项将不起作用。<br>**主机** - 选择要在其上执行命令的主机。<br>**主机组** - 选择执行命令的主机组。 指定父主机组会隐式选择所有嵌套的主机组。 因此远程命令也将在来自嵌套组的主机上执行。<br>主机上的命令只执行一次，即使主机匹配不止一次（例如来自多个主机组；单独和来自主机组）。 <br>如果命令是在Zabbix server上执行的，目标列表是没有意义的。 在这种情况下选择更多目标只会导致命令在服务器上执行更多次。<br>请注意，对于全局脚本，目标选择还取决于全局脚本[配置](/manual/ web_interface/frontend_sections/administration/scripts#configuring_a_global_script).|

en-us	 #### Operation type: [send message](/manual/config/notifications/action/operation/message)  |Parameter|Description| |--|--------| |*Send to user groups*|Click on *Add* to select user groups to send the recovery message to.<br>The user group must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |*Send to users*|Click on *Add* to select users to send the recovery message to.<br>The user must have at least "read" [permissions](/manual/config/users_and_usergroups/permissions) to the host in order to be notified.| |*Send only to*|Send default recovery message to all defined media types or a selected one only.| |*Custom message*|If selected, a custom message can be defined.| |*Subject*|Subject of the custom message. The subject may contain macros.| |*Message*|The custom message. The message may contain macros.|
zh-cn	####操作类型：[发送消息](/manual/config/notifications/action/operation/message)  |参数|说明| |--|--------| |*Send to user groups*|点击*添加*选择要将恢复消息发送到的用户组。<br>用户组必须至少具有“读取”[权限](/manual/config/users_and_usergroups/permissions) 给主机以便得到通知。| |*Send to users*|点击*添加*选择要将恢复消息发送到的用户。<br>用户必须至少具有对主机的“读取”[权限](/manual/config/users_and_usergroups/permissions) 为了得到通知。| |*Send only to*|将默认恢复消息发送至所有定义的媒体类型或仅选定的媒体类型。| |*Custom message*|如果选中，可以定义自定义消息。| |*Subject*|自定义消息的主题。 主题可能包含宏。| |*Message*|自定义消息。 该消息可能包含宏。|

en-us	#### Operators  The following operators are supported for triggers **(in descending priority of execution)**:  |Priority|Operator|Definition|**Notes for [unknown values](/manual/config/triggers/expression#expressions_with_unsupported_items_and_unknown_values)**|Force cast operand to float ^**1**^| |--------|--------|----------|------------------------------------------------------------------------------------------------------------------------|-----------------------------------| |**1**|**-**|Unary minus|**-**Unknown → Unknown|Yes| |**2**|**not**|Logical NOT|**not** Unknown → Unknown|Yes| |**3**|**\***|Multiplication|0 **\*** Unknown → Unknown<br>(yes, Unknown, not 0 - to not lose<br>Unknown in arithmetic operations)<br>1.2 **\*** Unknown → Unknown|Yes| |<|**/**|Division|Unknown **/** 0 → error<br>Unknown **/** 1.2 → Unknown<br>0.0 **/** Unknown → Unknown|Yes| |**4**|**+**|Arithmetical plus|1.2 **+** Unknown → Unknown|Yes| |<|**-**|Arithmetical minus|1.2 **-** Unknown → Unknown|Yes| |**5**|**\<**|Less than. The operator is defined as:<br><br>A<B ⇔ (A<B-0.000001)|1.2 **<** Unknown → Unknown|Yes| |<|**<=**|Less than or equal to. The operator is defined as:<br><br>A<=B ⇔ (A≤B+0.000001)|Unknown **<=** Unknown → Unknown|Yes| |<|**>**|More than. The operator is defined as:<br><br>A>B ⇔ (A>B+0.000001)|<|Yes| |<|**>=**|More than or equal to. The operator is defined as:<br><br>A>=B ⇔ (A≥B-0.000001)|<|Yes| |**6**|**=**|Is equal. The operator is defined as:<br><br>A=B ⇔ (A≥B-0.000001) and (A≤B+0.000001)|<|No ^**1**^| |<|**<>**|Not equal. The operator is defined as:<br><br>A<>B ⇔ (A<B-0.000001) or (A>B+0.000001)|<|No ^**1**^| |**7**|**and**|Logical AND|0 **and** Unknown → 0<br>1 **and** Unknown → Unknown<br>Unknown **and** Unknown → Unknown|Yes| |**8**|**or**|Logical OR|1 **or** Unknown → 1<br>0 **or** Unknown → Unknown<br>Unknown **or** Unknown → Unknown|Yes|  ^**1**^ String operand is still cast to numeric if:  -   another operand is numeric -   operator other than **=** or **<>** is used on an operand  (If the cast fails - numeric operand is cast to a string operand and both operands get compared as strings.)  **not**, **and** and **or** operators are case-sensitive and must be in lowercase. They also must be surrounded by spaces or parentheses.  All operators, except unary **-** and **not**, have left-to-right associativity. Unary **-** and **not** are non-associative (meaning **-(-1)** and **not (not 1)** should be used instead of **--1** and **not not 1**).  Evaluation result:  -   **<**, **<=**, **>**, **>=**, **=**, **<>**     operators shall yield '1' in the trigger expression if the specified     relation is true and '0' if it is false. If at least one operand is     Unknown the result is Unknown; -   **and** for known operands shall yield '1' if both of its operands     compare unequal to '0'; otherwise, it yields '0'; for unknown     operands **and** yields '0' only if one operand compares equal to     '0'; otherwise, it yields 'Unknown'; -   **or** for known operands shall yield '1' if either of its operands     compare unequal to '0'; otherwise, it yields '0'; for unknown     operands **or** yields '1' only if one operand compares unequal to     '0'; otherwise, it yields 'Unknown'; -   The result of the logical negation operator **not** for a known     operand is '0' if the value of its operand compares unequal to '0';     '1' if the value of its operand compares equal to '0'. For unknown     operand **not** yields 'Unknown'.
zh-cn	 #### 运算符  触发器支持下列运算符 **（在执行中优先级递减）**  |优先级|运算符|定义|**注意 [unknown values（未知值）](/manual/config/triggers/expression#expressions_with_unsupported_items_and_unknown_values)**|强制转换操作为浮点数 ^**1**^| |--------|--------|----------|------------------------------------------------------------------------------------------------------------------------|-----------------------------------| |**1**|**-**|负数|**-**Unknown → Unknown|Yes| |**2**|**not**|逻辑非|**not** Unknown → Unknown|Yes| |**3**|**\***|乘法|0 **\*** Unknown → Unknown<br>(yes, Unknown, not 0 - to not lose<br>算术运算中的未知数)<br>1.2 **\*** Unknown → Unknown|Yes| |<|**/**|除法|Unknown **/** 0 → error<br>Unknown **/** 1.2 → Unknown<br>0.0 **/** Unknown → Unknown|Yes| |**4**|**+**|算术加|1.2 **+** Unknown → Unknown|Yes| |<|**-**|算术减|1.2 **-** Unknown → Unknown|Yes| |**5**|**\<**|少于. 运算符定义为:<br><br>A<B ⇔ (A<B-0.000001)|1.2 **<** Unknown → Unknown|Yes| |<|**<=**|小于或等于。运算符定义为:<br><br>A<=B ⇔ (A≤B+0.000001)|Unknown **<=** Unknown → Unknown|Yes| |<|**>**|多于。运算符定义为：<br><br>A>B ⇔ (A>B+0.000001)|<|Yes| |<|**>=**|More than or equal to. The operator is defined as:<br><br>A>=B ⇔ (A≥B-0.000001)|<|Yes| |**6**|**=**|等于。运算符定义为：<br><br>A=B ⇔ (A≥B-0.000001) and (A≤B+0.000001)|<|No ^**1**^| |<|**<>**|不等于。运算符定义为:<br><br>A<>B ⇔ (A<B-0.000001) or (A>B+0.000001)|<|No ^**1**^| |**7**|**and**|逻辑与|0 **and** Unknown → 0<br>1 **and** Unknown → Unknown<br>Unknown **and** Unknown → Unknown|Yes| |**8**|**or**|逻辑或|1 **or** Unknown → 1<br>0 **or** Unknown → Unknown<br>Unknown **or** Unknown → Unknown|Yes|  ^**1**^ 如果字符串操作数仍然转换为数字:  -   另一个操作数是数字 -   运算符以外的 **=** or **<>** 在操作数上使用  （如果转换失败 - 数字操作数被转换为字符串操作数并且 两个操作数都作为字符串进行比较。  **not**、**and** 和 **or** 运算符区分大小写，并且必须在 小写。它们还必须用空格或括号括起来。  除 **-** 和 **not** 外，所有运算符都从左到右 关联性。 **-** 和 **not** 是非关联的（意思是 **-(-1)** 和 **not (not 1)** 应该用来代替 **--1** 和 **不是不是 1**)。  评价结果：  -  **<**, **<=**, **>**, **>=**, **=**, **<>**     如果指定的运算符应在触发器表达式中产生“1” 关系为真，如果为假，则为“0”。如果至少有一个操作数是 未知结果为未知； - **and** 对于已知操作数，如果它的两个操作数都将产生“1” 则不等于'0'；否则，它产生“0”；对于未知 仅当一个操作数比较等于时，操作数**and**才会产生“0” '0';否则，它会产生“未知”. - **or** 对于已知的操作数，如果它的任何一个操作数都将产生“1” 则不等于'0'；否则，它产生“0”；对于未知 仅当一个操作数比较不等于0时，操作数**or**才会产生“1”;否则，它会产生“未知”； - 逻辑否定运算符 **not** 的结果 如果其操作数的值比较不等于“0”，则操作数为“0”； 如果其操作数的值比较等于“0”，则为“1”。对于未知 操作数 **not** 产生“未知”。

en-us	 ### Optimized API queries  API database queries, created when searching through names in *hosts* and *items* tables, have been optimized and will now be processed more efficiently. 
zh-cn	### 优化的 API 查询  API 数据库查询，在搜索 *hosts* 和 *items* 表中的名称时创建，已经过优化，现在可以更有效地处理。

en-us	 ### Optimized API queries  API database queries, created when searching through names in the *hosts* and *items* tables, have been optimized and will now be processed more efficiently. As a result of this change, deterministic triggers need to be created during an upgrade.   On MySQL and MariaDB, this requires `GLOBAL log_bin_trust_function_creators = 1` to be set if binary logging is enabled and there is no superuser privileges and `log_bin_trust_function_creators = 1` is not set in MySQL configuration file. To set the variable using MySQL console, run:      mysql> SET GLOBAL log_bin_trust_function_creators = 1;  Once the upgrade has been successfully completed, `log_bin_trust_function_creators` can be disabled:      mysql> SET GLOBAL log_bin_trust_function_creators = 0;  Triggers are also created for PostgreSQL and Oracle database.
zh-cn	### 优化的 API 查询  在 *hosts* 和 *items* 表中搜索名称时创建的 API 数据库查询已经过优化，现在可以更有效地处理。 由于此更改，需要在升级期间创建确定性触发器。  在 MySQL 和 MariaDB 上，如果启用了二进制日志记录并且没有超级用户权限并且 MySQL 配置文件中未设置 log_bin_trust_function_creators = 1，则需要设置 GLOBAL log_bin_trust_function_creators = 1。 要使用 MySQL 控制台设置变量，请运行：    · mysql> SET GLOBAL log_bin_trust_function_creators = 1;  升级成功完成后，可以禁用 log_bin_trust_function_creators：    · mysql> SET GLOBAL log_bin_trust_function_creators = 0;  还为 PostgreSQL 和 Oracle 数据库创建了触发器。

en-us	##### - Optional interface  The optional functions are **zbx\_module\_init()**, **zbx\_module\_item\_list()**, **zbx\_module\_item\_timeout()**, **zbx\_module\_history\_write\_cbs()** and **zbx\_module\_uninit()**:  ``` {.c} int zbx_module_init(void); ```  This function should perform the necessary initialization for the module (if any). If successful, it should return ZBX\_MODULE\_OK. Otherwise, it should return ZBX\_MODULE\_FAIL. In the latter case Zabbix will not start.  ``` {.c} ZBX_METRIC  *zbx_module_item_list(void); ```  This function should return a list of items supported by the module. Each item is defined in a ZBX\_METRIC structure, see the section below for details. The list is terminated by a ZBX\_METRIC structure with "key" field of NULL.  ``` {.c} void    zbx_module_item_timeout(int timeout); ```  If module exports **zbx\_module\_item\_list()** then this function is used by Zabbix to specify the timeout settings in Zabbix configuration file that the item checks implemented by the module should obey. Here, the "timeout" parameter is in seconds.  ``` {.c} ZBX_HISTORY_WRITE_CBS   zbx_module_history_write_cbs(void); ```  This function should return callback functions Zabbix server will use to export history of different data types. Callback functions are provided as fields of ZBX\_HISTORY\_WRITE\_CBS structure, fields can be NULL if module is not interested in the history of certain type.  ``` {.c} int zbx_module_uninit(void); ```  This function should perform the necessary uninitialization (if any) like freeing allocated resources, closing file descriptors, etc.  All functions are called once on Zabbix startup when the module is loaded, with the exception of zbx\_module\_uninit(), which is called once on Zabbix shutdown when the module is unloaded.
zh-cn	##### - 可选接口  可选的函数是**zbx\_module\_init()**, **zbx\_module\_item\_list()**, **zbx\_module\_item\_timeout()**, **zbx\_module\_history\_write\_cbs()** and **zbx\_module\_uninit()**:\  ``` {.c} int zbx_module_init(void); ```  这个函数应该对模块的执行进行必要的初始化（如果有的话）。如果成功，则返回ZBX\_MODULE\_OK。否则它应该返回ZBX\_MODULE\_FAIL 。若为后一种情况，ZABBIX 将无法启动。\  ``` {.c} ZBX_METRIC  *zbx_module_item_list(void); ```  此函数应当返回模块支持的监控项列表。每个监控项被定义为ZBX\_METRIC的结构下，详细信息请见后文。这个列表应以“key”字段为NULL作为ZBX\_METRIC结构的终止。\  ``` {.c} void    zbx_module_item_timeout(int timeout); ```  如果模块导出**zbx\_module\_item\_list()**，此函数用于定义Zabbix 配置文件中的超时设置，基于这个模块的监控项检查应遵守这个设置。这边，“timeout”参数以秒为单位。\  ``` {.c} ZBX_HISTORY_WRITE_CBS   zbx_module_history_write_cbs(void); ```  这个函数应当返回ZABBIX服务器将用于导出不同数据类型历史记录的回调函数。回调函数应以ZBX\_HISTORY\_WRITE\_CBS结构的字段提供，如果模块对于某种类型的历史纪录不感兴趣，则字段可以为NULL 。\  ``` {.c} int zbx_module_uninit(void); ```  这个函数应当执行必要的反初始化（如果有的话），如释放分配的资源、关闭文件描述符等。\  所有的函数会在ZABBIX启动的时候加载模块时，除了zbx\_module\_uninit()都将被调用一次。在卸载模块时，zbx\_module\_uninit()会被ZABBIX调用。\

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix agent in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
zh-cn	 ## 选项  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-f**, **--foreground**   在前台运行Zabbix agent。  **-R**, **--runtime-control** *runtime-option*   根据*runtime-option*执行管理功能。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-f**, **--foreground**   Run Zabbix proxy in foreground.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.  [ ]{#lbAF}
zh-cn	 ## OPTIONS  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-f**, **--foreground**   在前台运行Zabbix proxy。  **-R**, **--runtime-control** *runtime-option*   根据*runtime-option*执行管理功能。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
zh-cn	## 选项  **-c**, **--config** *config-file*   使用指定的*config-file*而不是默认文件。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAF}

en-us	## OPTIONS  **-c**, **--config** *config-file*   Use the alternate *config-file* instead of the default one.  **-R**, **--runtime-control** *runtime-option*   Perform administrative functions according to *runtime-option*.
zh-cn	 ## 选项  **-c**, **--config** *config-file*   使用指定的 *配置文件*而不是默认文件。  **-R**, **--runtime-control** *runtime-option*   根据 *运行时选项* 执行管理功能。

en-us	#### Options  |Parameter|Description| |---------|-----------| |-V --version|Print the plugin version and license information.| |-h --help|Print help information (shorthand).|
zh-cn	#### 选项  |参数|描述| |---------|-----------| |-V --version|打印插件版本及license信息。| |-h --help|打印帮助信息（简化版）。|

en-us	## OPTIONS  **-s**, **--host** *host-name-or-IP*   Specify host name or IP address of a host.  **-p**, **--port** *port-number*   Specify port number of agent running on the host. Default is 10050.  **-I**, **--source-address** *IP-address*   Specify source IP address.  **-t**, **--timeout** *seconds*   Specify timeout. Valid range: 1-30 seconds (default: 30)  **-k**, **--key** *item-key*   Specify key of item to retrieve value for.  **--tls-connect** *value*   How to connect to agent. Values:  [ ]{#lbAF}
zh-cn	 ## 选项  **-s**, **--host** *host-name-or-IP*   指定主机的主机名或IP地址。  **-p**, **--port** *port-number*   指定主机上运行的agent的端口号。默认值为10050。  **-I**, **--source-address** *IP-address*   指定源IP地址。  **-t**, **--timeout** *seconds*   指定超时。有效范围：1-30秒（默认值：30）  **-k**, **--key** *item-key*   指定要为其检索值的项的key。  **--tls-connect** *value*   如何连接到agent。值  [ ]{#lbAF}

en-us	## OPTIONS  **-s**, **--script** *script-file*   Specify the file name of the script to execute. If '-' is specified as file name, the script will be read from stdin.  **-p**, **--param** *input-param*   Specify the input parameter.  **-i**, **--input** *input-file*   Specify the file name of the input parameter. If '-' is specified as file name, the input will be read from stdin.  **-l**, **--loglevel** *log-level*   Specify the log level.  **-t**, **--timeout** *timeout*   Specify the timeout in seconds. Valid range: 1\-60 seconds (default: 10)  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAF}
zh-cn	## OPTIONS  **-s**, **--script** *script-file*   指定要执行的脚本的文件名。如果将“-”指定为文件名，则将从标准输入读取脚本。  **-p**, **--param** *input-param*   指定输入参数。  **-i**, **--input** *input-file*   指定输入参数的文件名。如果将“-”指定为文件名，则将从准输入读取输入。  **-l**, **--loglevel** *log-level*   指定日志级别。  **-t**, **--timeout** *timeout*   以秒为单位指定超时。有效范围：1\-60 秒（默认值：10）  **-h**, **--help**   显示此帮助并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAF}

en-us	 #### Oracle  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Importing/exporting history tables in one attempt  * Install Oracle Data Pump ([Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) contains it).   Additionally, consider [performance tips](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for Oracle Data Pump.  * Rename tables using `history_pk_prepare.sql`.  ``` shell> cd /path/to/zabbix-sources/database/oracle shell> sqlplus zabbix/password@oracle_host/ORCL sqlplus> @history_pk_prepare.sql ```  * Prepare directories for datapump  Example:  ``` # mkdir -pv /export/history # chown -R oracle:oracle /export ```  * Create a directory object, grant permissions to it. Run the following under sysdba role:  ``` create directory history as '/export/history'; grant read,write on directory history to zabbix; ```  * Export tables. Replace N with your desired thread count.  ``` expdp zabbix/password@172.20.0.3:1521/z \  DIRECTORY=history \  TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \  PARALLEL=N ```  * Import tables. Replace N with your desired thread count.  ``` impdp zabbix/password@172.20.0.3:1521/z \  DIRECTORY=history \  TABLES=history_uint_old \  REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \  data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND  PARALLEL=N CONTENT=data_only ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### Importing/exporting history tables individually  * Install Oracle Data Pump ([Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) contains it).   Additionally, consider [performance tips](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for Oracle Data Pump.  * Rename tables using `history_pk_prepare.sql`.  ``` shell> cd /path/to/zabbix-sources/database/oracle shell> sqlplus zabbix/password@oracle_host/ORCL sqlplus> @history_pk_prepare.sql ```  * Prepare directories for datapump  Example:  ``` # 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, grant permissions to it. Run the following under sysdba role:  ``` 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 your desired thread count.  ``` expdp zabbix/password@172.20.0.3:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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 ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  
zh-cn	 #### Oracle  Export and import must be performed in tmux/screen, so that the session isn't dropped.  ##### Importing/exporting history tables in one attempt  * Install Oracle Data Pump ([Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) contains it).   Additionally, consider [performance tips](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for Oracle Data Pump.  * Rename tables using [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/fa073f5697a8a6d1a2b3b34b0335c88a02dc8365)  * Prepare directories for datapump  Example:  ``` # mkdir -pv /export/history # chown -R oracle:oracle /export ```  * Create a directory object, grant permissions to it. Run the following under sysdba role:  ``` create directory history as '/export/history'; grant read,write on directory history to zabbix; ```  * Export tables. Replace N with your desired thread count.  ``` expdp zabbix/password@172.20.0.3:1521/z \  DIRECTORY=history \  TABLES=history_old,history_uint_old,history_str_old,history_log_old,history_text_old \  PARALLEL=N ```  * Import tables. Replace N with your desired thread count.  ``` impdp zabbix/password@172.20.0.3:1521/z \  DIRECTORY=history \  TABLES=history_uint_old \  REMAP_TABLE=history_old:history,history_uint_old:history_uint,history_str_old:history_str,history_log_old:history_log,history_text_old:history_text \  data_options=SKIP_CONSTRAINT_ERRORS table_exists_action=APPEND  PARALLEL=N CONTENT=data_only ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  ##### Importing/exporting history tables individually  * Install Oracle Data Pump ([Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) contains it).   Additionally, consider [performance tips](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for Oracle Data Pump.  * Rename tables using [history_pk_prepare.sql](https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/fa073f5697a8a6d1a2b3b34b0335c88a02dc8365)  * Prepare directories for datapump  Example:  ``` # 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, grant permissions to it. Run the following under sysdba role:  ``` 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 your desired thread count.  ``` expdp zabbix/password@172.20.0.3:1521/xe DIRECTORY=history TABLES=history_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_uint TABLES=history_uint_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_str TABLES=history_str_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_log TABLES=history_log_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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@172.20.0.3:1521/xe DIRECTORY=history_text TABLES=history_text_old PARALLEL=N  impdp zabbix/password@172.20.0.3: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 ```  * Verify that everything works as supposed  * Drop old tables  ``` DROP TABLE history_old; DROP TABLE history_uint_old; DROP TABLE history_str_old; DROP TABLE history_log_old; DROP TABLE history_text_old; ```  

en-us	 ### Oracle  Export and import must be performed in tmux/screen to ensure that the session isn't dropped. Zabbix server should be down during the upgrade.  See also: [Important notes](#important-notes)  #### Table upgrade  * Install Oracle Data Pump (available in the [Instant Client Tools package](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html)).   See Oracle Data Pump [documentation](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html) for performance tips.  * Rename tables using `history_pk_prepare.sql`.  ``` {.bash} cd /usr/share/zabbix/zabbix-sql-scripts/database/oracle sqlplus zabbix/password@oracle_host/service sqlplus> @history_pk_prepare.sql ```
zh-cn	### Oracle  导出和导入必须在 tmux/screen 中执行，以确保会话不会被丢弃。Zabbix 服务器应该在升级期间关闭。  另请参阅：[重要说明](#important-notes)  #### 表升级  * 安装 Oracle 数据泵（在 [即时客户端工具包](https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html) 中可用）。  有关性能提示，请参阅 Oracle Data Pump [文档](https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-performance-tips.html)。  * 使用 `history_pk_prepare.sql` 重命名表。  ``` {.bash} cd /usr/share/zabbix/zabbix-sql-scripts/database/oracle sqlplus zabbix/password@oracle_host/service sqlplus> @history_pk_prepare.sql ```

en-us	#### Oracle  Instructions for creating and configuring Oracle database are provided in a separate [section](/manual/appendix/install/oracle).  
zh-cn	#### Oracle  创建和配置 Oracle 数据库的操作在单独的 [章节](/manual/appendix/install/oracle) 中说明。

en-us	 ### Oracle  |Key|<|<|<| |--|--|------|------| |**Description**|**Return value**|**Parameters**|**Comments**| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>,<diskgroup>\]|<|<|<| |Automatic Storage Management (ASM) disk groups statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**diskgroup** - name of the ASM disk group to query.| | |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.| | |oracle.archive.info\[connString,<user>,<password>,<service>,<destination>\]|<|<|<| |Archive logs statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**destination** - name of the destination to query.| | |oracle.cdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Container Databases (CDBs) information.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**database** - name of the database to query.| | |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.| | |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.| | |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.| | |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Fast Recovery Area (FRA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |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.| | |oracle.pdb.info\[connString,<user>,<password>,<service>,<database>\]|<|<|<| |Pluggable Databases (PDBs) information.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**database** - name of the database to query.| | |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.| | |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |Program Global Area (PGA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |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.| | |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.| | |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.| | |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |System Global Area (SGA) statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.| | |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.| | |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.| | |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.| | |oracle.ts.stats\[connString,<user>,<password>,<service>,<tablespace>,<type>\]|<|<|<| |Tablespaces statistics.|JSON object|**connString** - URI or session name.<br>**user, password** - Oracle login credentials.<br>**service** - Oracle service name.<br>**tablespace** - name of the tablespace to query. Default (if left empty and `type` is set):<br>- "TEMP" (if `type` is set to "TEMPORARY");<br>- "USERS" (if `type` is set to "PERMANENT").<br>**type** - type of the tablespace to query. Default (if `tablespace` is set): "PERMANENT".| | |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.| | |oracle.user.info\[connString,<user>,<password>,<service>,<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.| |
zh-cn	### Oracle  |Key|<|<|<| |---|---|---|---| |**描述**|**返回值**|**参数**|**注释**| |oracle.diskgroups.stats\[connString,<user>,<password>,<service>\]|<|<|<| |自动存储管理 (ASM) 磁盘组统计信息。|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。<br>**diskgroup** - 要查询的 ASM 磁盘组的名称。| | |oracle.diskgroups.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd) 列出 ASM 磁盘组列表.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。| | |oracle.archive.info\[connString,<user>,<password>,<service>\]|<|<|<| |归档日志的统计数据.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。<br> **destination** - 要查询的目的地的名称。| | |oracle.cdb.info\[connString,<user>,<password>,<service>\]|<|<|<| |CDB 信息.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。<br>**database** - 要查询的数据库名称。| | |oracle.custom.query\[connString,<user>,<password>,<service>, queryName, <args...>\]|<|<|<| |自定义查询的结果.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。<br>**queryName** — 自定义查询的名称（必须等于不带扩展名的 sql 文件的名称）。<br>**args...** — 要传递给查询的一个或多个逗号分隔参数。| | |oracle.datafiles.stats\[connString,<user>,<password>,<service>\]|<|<|<| |数据文件的统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。| | |oracle.db.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)列出数据库列表.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证。<br>**service** - Oracle 服务名。| | |oracle.fra.stats\[connString,<user>,<password>,<service>\]|<|<|<| |快速恢复区 (FRA) 统计信息。|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle 服务名。| | |oracle.instance.info\[connString,<user>,<password>,<service>\]|<|<|<| |实例统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.pdb.info\[connString,<user>,<password>,<service>\]|<|<|<| |可插拔数据库 (PDB) 信息。|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.pdb.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)列出 PDB 列表.|JSON 对象|**connString** - URI 或者 session name.<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle service name.| | |oracle.pga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |PGA 统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.ping\[connString,<user>,<password>,<service>\]|<|<|<| |测试是否可以建立到 Oracle 的连接.|0 - 连接失败 (如果出现包括认证和配置问题的错误提示)<br>1 - 连接成功.|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.proc.stats\[connString,<user>,<password>,<service>\]|<|<|<| |进程统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.redolog.info\[connString,<user>,<password>,<service>\]|<|<|<| |来自控制文件的日志文件信息.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.sga.stats\[connString,<user>,<password>,<service>\]|<|<|<| |系统全局区 (SGA) 统计信息。|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.sessions.stats\[connString,<user>,<password>,<service>,<lockMaxTime>\]|<|<|<| |会话统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。<br>**lockMaxTime** - 一个长期 Session 被锁定的最长 Session 锁定时间，单位是秒. 缺省值: 600 seconds.| | |oracle.sys.metrics\[connString,<user>,<password>,<service>,<duration>\]|<|<|<| |一组系统的指标值.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。<br>**duration** - 获取系统指标值的间隔，单位是秒. 可能的值: *60* — 长的间隔 (缺省值), *15* — 短的间隔.| | |oracle.sys.params\[connString,<user>,<password>,<service>\]|<|<|<| |一组系统参数值.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.ts.stats\[connString,<user>,<password>,<service>\]|<|<|<| |表空间统计数据.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.ts.discovery\[connString,<user>,<password>,<service>\]|<|<|<| |用于 [底层自动发现](/manual/discovery/low_level_discovery/examples/systemd)列出表空间列表。|JSON 对象|**connString** - URI或者会话名称。 <br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。| | |oracle.user.info\[connString,<user>,<password>,<service>,<username>\]|<|<|<| |用户信息.|JSON 对象|**connString** - URI或者会话名称。<br>**user, password** - Oracle 登陆凭证.<br>**service** - Oracle服务名。<br>**username** - 一个用户名，这些信息是必要的. 用户名不支持小写. 缺省值: 当前用户.| |

en-us	#### Ordering shapes and lines  To bring one shape in front of the other (or vice versa) click on the shape with the right mouse button bringing up the map shape menu.  ![](../../../../../assets/en/manual/config/visualization/map_shape_menu.png)
zh-cn	#### 排序形状和线条  要将一个形状放在另一个形状前面（反之亦然），请用鼠标单击右键调出地图形状菜单。  ![](../../../../../assets/en/manual/config/visualization/map_shape_menu.png)

en-us	### Other changes and bug fixes
zh-cn	 ### 其他变更和Bug修复

en-us	#### Other details  -   An Admin level user with *Read-write* access to a host will not be     able to link/unlink templates, if he has no access to the     *Templates* group. With *Read* access to *Templates* group he will     be able to link/unlink templates to the host, however, will not see     any templates in the template list and will not be able to operate     with templates in other places. -   An Admin level user with *Read* access to a host will not see the     host in the configuration section host list; however, the host     triggers will be accessible in IT service configuration. -   Any non-Super Admin user (including 'guest') can see network maps as     long as the map is empty or has only images. When hosts, host groups     or triggers are added to the map, permissions are respected. -   Zabbix server will not send notifications to users defined as action     operation recipients if access to the concerned host is explicitly     "denied".
zh-cn	#### 其他详情  - 对主机具有 *Read-write* 访问权限的管理员级别用户将无法链接/取消链接模板，如果他无权访问 *Templates* 组。 拥有对 *Templates* 组的 *Read* 访问权限，他将能够将模板链接/取消链接到主机，但是，在模板列表中将看不到任何模板，并且将无法在其他地方使用模板。 - 对主机具有 *Read* 访问权限的管理员级别用户将不会在配置部分主机列表中看到该主机； 但是，可以在 IT 服务配置中访问主机触发器。 - 只要地图为空或只有图像，任何非超级管理员用户（包括“访客”）都可以查看网络地图。 将主机、主机组或触发器添加到映射时，会尊重权限。 - 如果对相关主机的访问被明确“拒绝”，Zabbix 服务器将不会向定义为操作操作接收者的用户发送通知。

en-us	##### Other expressions  Function parameters may contain other expressions, as in the following syntax:      min(min(/host/key,1h),min(/host2/key2,1h)*10)  Note that other expressions may not be used, if the function references item history. For example, the following syntax is not allowed:  ~~`min(/host/key,#5*10)`~~
zh-cn	##### 其他表达式  函数参数可能包含其他表达式，如下所示 语法:      min(min(/host/key,1h),min(/host2/key2,1h)*10)  请注意，如果函数引用，则可能不会使用其他表达式 监控项历史。例如，不允许使用以下语法：  ~~`min(/host/key,#5*10)`~~

en-us	##### Other expressions  Function parameters may contain other expressions,​ as in the following syntax:      min(min(/​host/​key,​1h),​min(/​host2/​key2,​1h)*10)  Note that other expressions may not be used, if the function references item history. For example, the following syntax is not allowed:  ~~`min(/​host/​key,#5*10)`~~  
zh-cn	 ##### 其他表达式  函数参数可能包含其他表达式，如下所示 句法：      min(min(/​host/​key,​1h),​min(/​host2/​key2,​1h)*10)  请注意，如果函数引用，则可能不会使用其他表达式 项目历史。例如，不允许使用以下语法：  ~~`min(/​host/​key,#5*10)`~~  

en-us	##### Other hardware  A serial communication port and a serial GSM modem are required for using SMS notification support in Zabbix. USB-to-serial converter will also work.  
zh-cn	##### 其它硬件  如果需要启用短信（SMS）通知功能，需要串行通讯口（serial communication port）和串行GSM调制解调器（serial GSM modem）。USB转串行转接器也同样可以工作。

en-us	#### - Other parameters  This section allows configuring miscellaneous other frontend parameters.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_other.png)  |Parameter|Description| |---------|-----------| |*Frontend URL*|URL to Zabbix web interface. This parameter is used by Zabbix web service for communication with frontend and should be specified to enable scheduled reports.| |*Group for discovered hosts*|Hosts discovered by [network discovery](/manual/discovery/network_discovery) and [agent autoregistration](/manual/discovery/auto_registration) will be automatically placed in the host group, selected here.| |*Default host inventory mode*|Default [mode](/manual/config/hosts/inventory) for host inventory. It will be followed whenever a new host or host prototype is created by server or frontend unless overridden during host discovery/autoregistration by the *Set host inventory mode* operation.| |*User group for database down message*|User group for sending alarm message or 'None'.<br>Zabbix server depends on the availability of the backend database. It cannot work without a database. If the database is down, selected users can be notified by Zabbix. Notifications will be sent to the user group set here using all configured user media entries. Zabbix server will not stop; it will wait until the database is back again to continue processing.<br>Notification consists of the following content:<br>`[MySQL\|PostgreSQL\|Oracle] database <DB Name> [on <DB Host>:<DB Port>] is not available: <error message depending on the type of DBMS (database)>`<br><DB Host> is not added to the message if it is defined as an empty value and <DB Port> is not added if it is the default value ("0"). The alert manager (a special Zabbix server process) tries to establish a new connection to the database every 10 seconds. If the database is still down the alert manager repeats sending alerts, but not more often than every 15 minutes.| |*Log unmatched SNMP traps*|Log [SNMP trap](/manual/config/items/itemtypes/snmptrap) if no corresponding SNMP interfaces have been found.|
zh-cn	#### - 其他参数  本节允许配置其他各种前端参数。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/general_other.png)  |参数|说明| |---------|------------| |*前端 URL*|Zabbix Web 界面的 URL。此参数由 Zabbix Web 服务用于与前端通信，应指定以启用计划报告。| |*已发现主机组*|由 [network discovery](/manual/discovery/network_discovery) 和 [agent autoregistration](/manual/discovery/auto_registration) 发现的主机将自动放置在此处选择的主机组中。| |*默认主机清单模式*|主机清单的默认 [模式](/manual/config/hosts/inventory)。每当服务器或前端创建新主机或主机原型时都会遵循它，除非在主机发现/自动注册期间被 *Set host inventory mode* 操作覆盖。| |*数据库关闭消息的用户组*|发送警报消息的用户组或“无”。<br>Zabbix 服务器取决于后端数据库的可用性。没有数据库它就无法工作。如果数据库关闭，Zabbix 可以通知选定的用户。通知将使用所有配置的用户媒体条目发送到此处设置的用户组。 Zabbix 服务器不会停止；它将等到数据库再次返回以继续处理。<br>通知包含以下内容：<br>`[MySQL\|PostgreSQL\|Oracle] 数据库 <DB Name> [on <DB Host>:<DB Port>] 不可用：<错误消息取决于 DBMS（数据库）的类型>`<br><DB Host> 如果定义为空值且未添加 <DB Port>，则不会将其添加到消息中如果它是默认值（“0”）。警报管理器（一个特殊的 Zabbix 服务器进程）每 10 秒尝试建立一个到数据库的新连接。如果数据库仍处于关闭状态，警报管理器会重复发送警报，但频率不会超过每 15 分钟一次。| |*记录不匹配的 SNMP 陷阱*|如果没有找到对应的 SNMP 接口，则记录 [SNMP 陷阱](/manual/config/items/itemtypes/snmptrap)。|

en-us	#### Other uses  Unit symbols are also used for a human-readable representation of data in the frontend.  In both Zabbix server and frontend these symbols are supported:  -   **K** - kilo -   **M** - mega -   **G** - giga -   **T** - tera  When item values in B, Bps are displayed in the frontend, base 2 is applied (1K = 1024). Otherwise a base of 10 is used (1K = 1000).  Additionally the frontend also supports the display of:  -   **P** - peta -   **E** - exa -   **Z** - zetta -   **Y** - yotta
zh-cn	#### 其他用途  单位符号也用于前端数据可读的表示法。  Zabbix server 和前端都支持这些符号：  -   **K** - 千 -   **M** - 兆 -   **G** - 吉 -   **T** - 太  当监控项值在前端显示为B、Bps时, 是基于二进制的(1K = 1024)。其他情况基于十进制(1K = 1000)。  此外，前端还支持显示：  -   **P** - 拍 -   **E** - 艾 -   **Z** - 泽 -   **Y** - 尧

en-us	#### Override  The **Override** tab allows setting rules to modify the list of item, trigger, graph and host prototypes or their attributes for discovered objects that meet given criteria.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_e.png)  Overrides (if any) are displayed in a reorderable drag-and-drop list and executed in the order in which they are defined.  To configure details of a new override, click on ![](../../../assets/en/manual/config/add_link.png) in the *Overrides* block. To edit an existing override, click on the override name. A popup window will open allowing to edit the override rule details.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override.png)  All mandatory parameters are marked with red asterisks.  |Parameter|Description| |--|--------| |*Name*|A unique (per LLD rule) override name.| |*If filter matches*|Defines whether next overrides should be processed when filter conditions are met:<br>**Continue overrides** - subsequent overrides will be processed.<br>**Stop processing** - operations from preceding (if any) and this override will be executed, subsequent overrides will be ignored for matched LLD rows.| |*Filters*|Determines to which discovered entities the override should be applied. Override filters are processed after discovery rule [filters](low_level_discovery#filter) and have the same functionality.| |*Operations*|Override operations are displayed with these details:<br>**Condition** - an object type (item prototype/trigger prototype/graph prototype/host prototype) and a condition to be met (equals/does not equal/contains/does not contain/matches/does not match)<br>**Action** - links for editing and removing an operation are displayed.|  **Configuring an operation**  To configure details of a new operation, click on ![](../../../assets/en/manual/config/add_link.png) in the Operations block. To edit an existing operation, click on ![](../../../assets/en/manual/config/edit_link.png) next to the operation. A popup window where you can edit the operation details will open.  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override_op.png)  |Parameter|<|<|Description| |-|-|----------|----------------------------------------| |*Object*|<|<|Four types of objects are available:<br>Item prototype<br>Trigger prototype<br>Graph prototype<br>Host prototype| |*Condition*|<|<|Allows filtering entities to which the operation should be applied.| | |Operator|<|Supported operators:<br>**equals** - apply to this prototype<br>**does not equal** - apply to all prototypes, except this<br>**contains** - apply, if prototype name contains this string<br>**does not contain** - apply, if prototype name does not contain this string<br>**matches** - apply, if prototype name matches regular expression<br>**does not match** - apply, if prototype name does not match regular expression<br>| |^|Pattern|<|A [regular expression](/manual/regular_expressions) or a string to search for.| |^|Object: *Item prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original item prototype settings:<br>*Yes* - the item will be added in an enabled state.<br>*No* - the item will be added to a discovered entity but in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original item prototype settings:<br>*Yes* - the item will be added.<br>*No* - the item will not be added.| |^|^|*Update interval*|When the checkbox is marked, two options will appear, allowing to set different interval for the item:<br>*Delay* - Item update interval. [User macros](/manual/config/macros/user_macros) and [time suffixes](/manual/appendix/suffixes) (e.g. 30s, 1m, 2h, 1d) are supported. Should be set to 0 if *Custom interval* is used.<br>*Custom interval* - click ![](../../../assets/en/manual/config/add_link.png) to specify flexible/scheduling intervals. For detailed information see [Custom intervals](/manual/config/items/item/custom_intervals).| |^|^|*History storage period*|When the checkbox is marked, the buttons will appear, allowing to set different history storage period for the item:<br>*Do not keep history* - if selected, the history will not be stored.<br>*Storage period* - if selected, an input field for specifying storage period will appear to the right. [User macros](/manual/config/macros/user_macros) and [LLD macros](/manual/config/macros/lld_macros) are supported.| |^|^|*Trend storage period*|When the checkbox is marked, the buttons will appear, allowing to set different trend storage period for the item:<br>*Do not keep trends* - if selected, the trends will not be stored.<br>*Storage period* - if selected, an input field for specifying storage period will appear to the right. [User macros](/manual/config/macros/user_macros) and [LLD macros](/manual/config/macros/lld_macros) are supported.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the item prototype, even if the tag names match.| |^|Object: *Trigger prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original trigger prototype settings:<br>*Yes* - the trigger will be added in an enabled state.<br>*No* - the trigger will be added to a discovered entity, but in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original trigger prototype settings:<br>*Yes* - the trigger will be added.<br>*No* - the trigger will not be added.| |^|^|*Severity*|When the checkbox is marked, trigger severity buttons will appear, allowing to modify trigger severity.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the trigger prototype, even if the tag names match.| |^|Object: *Graph prototype*|<|<| |^| |*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original graph prototype settings:<br>*Yes* - the graph will be added.<br>*No* - the graph will not be added.| |^|Object: *Host prototype*|<|<| |^| |*Create enabled*|When the checkbox is marked, the buttons will appear, allowing to override original host prototype settings:<br>*Yes* - the host will be created in an enabled state.<br>*No* - the host will be created in a disabled state.| |^|^|*Discover*|When the checkbox is marked, the buttons will appear, allowing to override original host prototype settings:<br>*Yes* - the host will be discovered.<br>*No* - the host will not be discovered.| |^|^|*Link templates*|When the checkbox is marked, an input field for specifying templates will appear. Start typing the template name or click on *Select* next to the field and select templates from the list in a popup window.<br>All templates linked to a host prototype will be replaced by templates from this override.| |^|^|*Tags*|When the checkbox is marked, a new block will appear, allowing to specify tag-value pairs.<br>These tags will be appended to the tags specified in the host prototype, even if the tag names match.| |^|^|*Host inventory*|When the checkbox is marked, the buttons will appear, allowing to select different inventory [mode](/manual/config/hosts/inventory) for the host prototype:<br>*Disabled* - do not populate host inventory<br>*Manual* - provide details manually<br>*Automated* - auto-fill host inventory data based on collected metrics.|
zh-cn	#### 覆盖  **覆盖** 选项卡允许设置规则来修改监控项，触发器、图形和主机原型或它们的属性以用于发现满足给定条件的对象。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_fs_e.png)  覆盖（如果有）在可重新排序的拖放列表中显示，并且按照定义的顺序执行。 配置一个新的覆盖，在 *覆盖*选项卡单击 ![](../../../assets/en/manual/config/add_link.png) 。要编辑现有覆盖，请单击覆盖名称。在弹出窗口中编辑覆盖规则详细信息。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override.png)  所有强制参数都标有红色星号。  |参数|描述| |---------|-----------| |*名称*|唯一的（根据 LLD 规则）覆盖名称。| |*如果过滤器匹配*|当下面条件满足时，下一个覆盖是否需要执行:<br>**继续覆盖** - 后续覆盖会执行。<br>**停止处理** - 前面的操作 (如果有) 和当前操作会执行, 后续覆盖会忽略。| |*过滤器*|定义了覆盖会应用到哪些已发现实体上。覆盖过滤器在自动发现规则的[过滤器](low_level_discovery#filter) 之后执行，其和自动发现规则的过滤器功能相同。| |*操作*|覆盖操作包含下列内容:<br>**条件** - 一个对象类型 (监控项原型/触发器原型/图表原型/主机原型) 和一个需要满足的条件(等于/不等于/包含/不包含/匹配/不匹配)<br>**动作** - 编辑和移除操作的链接。|  **配置一个操作**  要配置一个新操作, 点击操作面板上的 ![](../../../assets/en/manual/config/add_link.png) 。编辑现有操作, 点击操作旁边的 ![](../../../assets/en/manual/config/edit_link.png) 。点击编辑按钮会出现弹窗。  ![](../../../assets/en/manual/discovery/low_level_discovery/lld_override_op.png)  |参数|<|<|描述| |---------|-----------| |*对象*|<|<|可使用四种对象:<br>监控项原型<br>触发器原型<br>图表原型<br>主机原型| |*条件*|<|<|允许过滤执行操作的目标实体。| |<|操作|<|可用操作:<br>**等于** - 应用到此原型<br>**不等于** - 应用到所有原型, 此原型除外<br>**包含** - 如果原型名称包含此字符串，则应用<br>**不包含** - 如果原型名称不包含此字符串，则应用<br>**匹配** - 如果原型名称匹配正则表达式，则应用<br>**不匹配** - 如果原型名称不匹配正则表达式，则应用<br>| |^|模式|<|A [正则表达式](/manual/regular_expressions) 或 需要搜索的字符串。| |<|对象: *监控项原型*|<|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮, 允许覆盖原始监控项原型设置:<br>*是* - 添加监控项，并且监控项处于启用状态。<br>*否* - 添加监控项到已发现的实体，但处于禁用状态。| |^|*发现*|如果选取检查框, 会出现按钮, 允许覆盖原始监控项原型设置:<br>*是* - 添加监控项。<br>*否* - 不添加监控项。| |^|*更新间隔*|如果选取检查框, 会出现两个选项, 允许为监控项设置不同的间隔:<br>*延迟* - 监控项更新间隔。支持[用户宏](/manual/config/macros/user_macros) 和 [时间后缀](/manual/appendix/suffixes) (如 30s, 1m, 2h, 1d)。如果使用了 *自定义间隔* 则更新间隔应设置为0。<br>*自定义间隔* - 点击 ![](../../../assets/en/manual/config/add_link.png) 指定 灵活/计划的时间间隔。 更多信息请参阅 [自定义间隔](/manual/config/items/item/custom_intervals).| |^|*历史保存周期*|如果选取检查框, 会出现按钮, 允许给监控项设置不同的历史保存周期:<br>*不保存历史* - 如果选择，那么历史数据不会保存。<br>*保存周期* - 如果选择, 右侧会出现输入框，可以输入保存周期。支持[用户宏](/manual/config/macros/user_macros) 和[LLD宏](/manual/config/macros/lld_macros)。| |^|*趋势数据保存周期*|如果选取检查框, 会出现按钮, 允许给监控项设置不同的趋势数据保存周期:<br>*不保存趋势数据* - 如果选择, 趋势数据不会保存。<br>*保存周期* - 如果选择, 右侧会出现输入框。支持[用户宏](/manual/config/macros/user_macros)和[LLD宏](/manual/config/macros/lld_macros)。| |^|*标签*|如果选取检查框, 会出现一个面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到监控项原型的标签末尾。| |<|对象: *触发器原型*|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮, 允许覆盖原始触发器原型设置:<br>*是* - 添加触发器，并且处于启用状态。<br>*否* - 添加触发器到已发现的实体中，但触发器是禁用的。| |^|*发现*|如果选取检查框, 会出现按钮,允许覆盖原始触发器原型设置 :<br>*是* - 添加触发器。<br>*否* - 不会添加触发器。| |^|*严重性*|如果选取检查框, 会出现触发器严重性按钮, 允许修改触发器的严重性级别。| |^|*标签*|如果选取检查框,会出现一个新面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到监控项原型的标签末尾。| |<|对象: *图形原型*|<|<| |^|*发现*|如果选取检查框, 会出现按钮, 允许覆盖原始图形原型设置:<br>*是* - 添加图形。<br>*否* - 不添加图形。| |<|对象: *主机原型*|<|<| |^|*启用创建*|如果选取检查框, 会出现按钮,允许覆盖原始主机原型设置 :<br>*是* - 创建主机，主机处于启用状态。<br>*否* - 创建主机，主机处于禁用状态。| |^|*发现*|如果选取检查框,会出现按钮,允许覆盖原始的主机原型设置:<br>*是* - 主机将被发现。<br>*否* - 主机不会被发现。| |^|*链接模板*|如果选取检查框,会出现一个输入框，用于指定模板。 输入模板名称，或点击输入框旁边的 *选择* 然后从弹窗列表中选择模板。<br>所有链接到主机原型的模板均会被替换为此覆盖中配置的模板。| |^|*标签*|如果选取检查框,会出现一个面板, 允许指定 标签-值 的键值对。<br>即使标签名称匹配，这些标签也会追加到主机原型的标签后面。| |^|*主机资产*|如果选取检查框,会出现按钮,允许基于主机原型选择不同的资产[模式](/manual/config/hosts/inventory) :<br>*禁用* - 不添加主机资产数据。<br>*手工* - 手工输入主机资产数据。<br>*自动* - 基于收集的数据自动添加主机资产数据。|

en-us	#### Overview  Additional files or directories can be included into server/proxy/agent configuration using the `Include` parameter.
zh-cn	#### 概述  可以使用该`Include`参数将其他文件或目录包含到 server/proxy/agent 配置中。

en-us	#### Overview  Aggregate calculations are a [calculated item](/manual/config/items/itemtypes/calculated)  type allowing to collect information from several items by Zabbix server and  then calculate an aggregate, depending on the aggregate function used.  Only unsigned integer and float values (type of information) are supported for aggregate calculation  items.  Aggregate calculations do not require any agent running on the host being monitored.
zh-cn	#### 概述  聚合计算是一种 [计算监控项](/manual/config/items/itemtypes/calculated) 类型，允许 Zabbix 服务器从多个项目中收集信息，然后根据使用的聚合函数计算聚合。  聚合计算项仅支持无符号整数和浮点值（信息类型）。  聚合计算不需要在被监控的主机上运行任何agent。

en-us	#### Overview  All users in Zabbix access the Zabbix application through the web-based frontend. Each user is assigned a unique login name and a password.  All user passwords are encrypted and stored in the Zabbix database. Users cannot use their user id and password to log directly into the UNIX server unless they have also been set up accordingly to UNIX. Communication between the web server and the user browser can be protected using SSL.  With a flexible [user permission schema](/manual/config/users_and_usergroups/permissions) you can restrict and differentiate rights to:  -   access administrative Zabbix frontend functions -   perform certain actions in the frontend -   access monitored hosts in hostgroups -   use specific API methods
zh-cn	#### 概述  Zabbix 中的所有用户都通过基于 web 的方式访问 Zabbix 应用程序前端。每个用户都被分配了一个唯一的登录名和密码。  所有用户密码都经过加密并存储在 Zabbix 数据库中。用户不能使用自己的用户名和密码直接登录。除非它们也已针对 UNIX 设置相应的 UNIX 服务器。Web 服务器和用户浏览器之间的通信可以使用 SSL 保护。  具有灵活的[用户权限架构](/manual/config/users_and_usergroups/permissions) 你可以限制和区分以下权利：  - 访问管理 Zabbix 前端功能 - 在前端执行某些操作 - 访问主机组中的受监控主机 - 使用特定的 API 方法

en-us	#### Overview  An optional context can be used in [user macros](/manual/config/macros/user_macros), allowing to override the default value with a context-specific one.  The context is appended to the macro name; the syntax depends on whether the context is a static text value:      {$MACRO:"static text"}  or a regular expression:      {$MACRO:regex:"regular expression"}   Note that a macro with regular expression context can only be defined in user macro configuration. If the `regex:` prefix is used elsewhere as user macro context, like in a trigger expression, it will be treated as static context.  Context quoting is optional (see also [important notes](#important_notes)).  Macro context examples:  |Example|Description| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|User macro without context.| |`{$LOW_SPACE_LIMIT:/tmp}`|User macro with context (static string).| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|User macro with context (regular expression). Same as `{$LOW_SPACE_LIMIT:/tmp}`.| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|User macro with context (regular expression). Matches all strings prefixed with /var/log/.|
zh-cn	#### 概述  可选上下文可用于 [user宏]（/manual/config/macros/user_macros），允许覆盖具有特定于上下文的默认值。  上下文附加到宏名称；语法取决于是否上下文是一个静态文本值：      {$MACRO:"静态文本"}  或正则表达式：      {$MACRO:regex:"正则表达式"}  请注意，具有正则表达式上下文的宏只能在用户宏配置。如果 `regex:` 前缀在其他地方被用作用户宏上下文，就像在触发器表达式中一样，它将被视为静态上下文。  上下文引用是可选的（另见 [重要注释]（#important_notes））。  宏上下文示例：  |示例|说明| |-------|-----------| |`{$LOW_SPACE_LIMIT}`|没有上下文的用户宏。| |`{$LOW_SPACE_LIMIT:/tmp}`|带有上下文的用户宏（静态字符串）。| |`{$LOW_SPACE_LIMIT:regex:"^/tmp$"}`|带有上下文的用户宏（正则表达式）。与`{$LOW_SPACE_LIMIT:/tmp}`相同。| |`{$LOW_SPACE_LIMIT:regex:"^/var/log/.*$"}`|带有上下文的用户宏（正则表达式）。匹配所有以 /var/log/ 为前缀的字符串。|

en-us	#### Overview  As an alternative to setting up manually or reusing an existing server for Zabbix, users may [download](http://www.zabbix.com/download_appliance) a Zabbix appliance or a Zabbix appliance installation CD image.  Zabbix appliance and installation CD versions are based on AlmaLinux 8 (x86\_64).  Zabbix appliance installation CD can be used for instant deployment of Zabbix server (MySQL).  ::: noteimportant  You can use this Appliance to evaluate Zabbix. The Appliance is not intended for serious production use.  :::
zh-cn	#### 概述  作为手动设置或重用现有  Zabbix  服务器的替代方法，用户可以[下载](http://www.zabbix.com/download_appliance) Zabbix appliance 或 Zabbix appliance 安装 CD image。  Zabbix appliance 及 安装 CD 基于 AlmaLinux 8 (x86\_64)。  Zabbix appliance 安装 CD 可用于 Zabbix server (MySQL) 的即时部署。  ::: noteimportant 您可以使用 Appliance 来评估Zabbix。这个 Appliance 不为重要的生产用途设计。 :::

en-us	#### Overview  Assuming that we have configured some items and triggers and now are getting some events happening as a result of triggers changing state, it is time to consider some actions.  To begin with, we would not want to stare at the triggers or events list all the time. It would be much better to receive notification if something significant (such as a problem) has happened. Also, when problems occur, we would like to see that all the people concerned are informed.  That is why sending notifications is one of the primary actions offered by Zabbix. Who and when should be notified upon a certain event can be defined.  To be able to send and receive notifications from Zabbix you have to:  -   [define some media](/manual/config/notifications/media) -   [configure an action](/manual/config/notifications/action) that     sends a message to one of the defined media  Actions consist of *conditions* and *operations*. Basically, when conditions are met, operations are carried out. The two principal operations are sending a message (notification) and executing a remote command.  For discovery and autoregistration created events, some additional operations are available. Those include adding or removing a host, linking a template etc.
zh-cn	####  概述  在配置了诸多监控项和触发器，并且在触发器状态发生变化的情况下，用户已经接收到了一些告警信息，那么接下来就要考虑通过配置动作（actions）来响应事件的发生。  值得强调的是，用户不可能一直观察触发器或者事件的状态变化。更好的解决办法是，当发生明显的变化时（例如出现紧急问题）用户可以接收到系统发送的通知。当然，问题发生时，所有相关人员都可以接收到该事件通知是最好的。  可以说，事件通知是 Zabbix 首要的动作配置之一。该配置可以细致到对特定事件所要通知的对象和时间进行定义。  开启 Zabbix 事件通知的发送和接收功能，您需要做到：  -   [定义媒介](/manual/config/notifications/media) -   [配置动作](/manual/config/notifications/action) 向指定的定义媒介发送消息  标准的动作由 *条件* 和 *操作* 两个元素构成。基本上，每当设定的条件达成时，就会执行相对应的设定操作。最重要的两个操作分别为：发送消息（事件提醒）和执行远程命令。  对于发现和自动注册所创建的事件，用户可以配置一些额外的操作。这些操作包括添加或删除主机，链接一个监控模板等。

en-us	#### Overview  A template is a set of entities that can be conveniently applied to multiple hosts.  The entities may be:  -   items -   triggers -   graphs -   dashboards -   low-level discovery rules -   web scenarios  As many hosts in real life are identical or fairly similar so it naturally follows that the set of entities (items, triggers, graphs,...) you have created for one host, may be useful for many. Of course, you could copy them to each new host, but that would be a lot of manual work. Instead, with templates you can copy them to one template and then apply the template to as many hosts as needed.  When a template is linked to a host, all entities (items, triggers, graphs,...) of the template are added to the host. Templates are assigned to each individual host directly (and not to a host group).  Templates are often used to group entities for particular services or applications (like Apache, MySQL, PostgreSQL, Postfix...) and then applied to hosts running those services.  Another benefit of using templates is when something has to be changed for all the hosts. Changing something on the template level once will propagate the change to all the linked hosts.  Thus, the use of templates is an excellent way of reducing one's workload and streamlining the Zabbix configuration.  Proceed to [creating and configuring a template](/manual/config/templates/template).
zh-cn	#### 概览  模板是可以方便地应用于多个主机的一组实体。 实体可以是：  -   监控项 -   触发器 -   图表 -   仪表盘 -   低级别自动发现规则 -   web场景  由于现实生活中的许多主机是相同或类似的，所以，您为一个主机创建的一组实体（监控项，触发器，图表，...）可能对许多主机有用。当然，您可以将它们复制到每个新的主机上，但需要费很大功夫。相反，使用模板，您可以将它们复制到一个模板，然后根据需要将模板应用于尽可能多的主机。  当模板链接到主机时，模板的所有实体（监控项，触发器，图表，...）都将添加到主机。模板直接分配给每个单独的主机（而不是主机组）。  模板通常用于为特定服务或应用程序（如Apache，MySQL，PostgreSQL，Postfix ...）分组实体，然后应用于运行这些服务的主机。  使用模板的另一个好处是当所有主机都需要更改时。只需要在模板上更改某些内容将会将更改应用到所有链接的主机。  因此，使用模板是减少工作量并简化Zabbix配置的好方法。  在[创建和配置模板](/manual/config/templates/template)中继续。

en-us	#### Overview  A vertical menu in a sidebar provides access to various Zabbix frontend sections.  The menu is dark blue in the default theme.  ![](../../../assets/en/manual/introduction/vertical_menu.png){width="600"}
zh-cn	#### 概述  侧边栏的垂直菜单提供了到多个Zabbix前端组件的访问。  在默认主题，此菜单是深蓝色的。  ![](../../../assets/en/manual/introduction/vertical_menu.png){width="600"}

en-us	#### Overview  A Zabbix database must be created during the installation of Zabbix server or proxy.  This section provides instructions for creating a Zabbix database. A separate set of instructions is available for each supported database.  UTF-8 is the only encoding supported by Zabbix. It is known to work without any security flaws. Users should be aware that there are known security issues if using some of the other encodings.
zh-cn	#### 概述  在部署 Zabbix server 或 proxy 时必须要创建数据库。  本节提供创建 Zabbix 数据库的说明。 每个受支持的数据库都有对应的创建说明。  Zabbix 唯一支持的编码是 UTF-8 。使用此编码没有已知的任何安全漏洞。应注意如果使用其他的编码，则存在已知的安全问题。

en-us	### Overview  A Zabbix proxy can collect performance and availability data on behalf of the Zabbix server. This way, a proxy can take on itself some of the load of collecting data and offload the Zabbix server.  Also, using a proxy is the easiest way of implementing centralized and distributed monitoring, when all agents and proxies report to one Zabbix server and all data is collected centrally.  A Zabbix proxy can be used to:  -   Monitor remote locations -   Monitor locations having unreliable communications -   Offload the Zabbix server when monitoring thousands of devices -   Simplify the maintenance of distributed monitoring  ![](../../../assets/en/manual/proxies/proxy.png){width="500"}  The proxy requires only one TCP connection to the Zabbix server. This way it is easier to get around a firewall as you only need to configure one firewall rule.  ::: noteimportant Zabbix proxy must use a separate database. Pointing it to the Zabbix server database will break the configuration. :::  All data collected by the proxy is stored locally before transmitting it over to the server. This way no data is lost due to any temporary communication problems with the server. The *ProxyLocalBuffer* and *ProxyOfflineBuffer* parameters in the [proxy configuration file](/manual/appendix/config/zabbix_proxy) control for how long the data are kept locally.  ::: noteimportant It may happen that a proxy, which receives the latest configuration changes directly from Zabbix server database, has a more up-to-date configuration than Zabbix server whose configuration may not be updated as fast due to the value of [CacheUpdateFrequency](/manual/appendix/config/zabbix_server). As a result, proxy may start gathering data and send them to Zabbix server that ignores these data. :::  Zabbix proxy is a data collector. It does not calculate triggers, process events or send alerts. For an overview of what proxy functionality is, review the following table:  |Function|<|Supported by proxy| |--------|-|------------------| |Items|<|<| |<|*Zabbix agent checks*|**Yes**| |^|*Zabbix agent checks (active)*|**Yes** ^1^| |^|*Simple checks*|**Yes**| |^|*Trapper items*|**Yes**| |^|*SNMP checks*|**Yes**| |^|*SNMP traps*|**Yes**| |^|*IPMI checks*|**Yes**| |^|*JMX checks*|**Yes**| |^|*Log file monitoring*|**Yes**| |^|*Internal checks*|**Yes**| |^|*SSH checks*|**Yes**| |^|*Telnet checks*|**Yes**| |^|*External checks*|**Yes**| |^|*Dependent items*|**Yes**| |^|*Script items*|**Yes**| |Built-in web monitoring|<|**Yes**| |Item value preprocessing|<|**Yes**| |Network discovery|<|**Yes**| |Active agent autoregistration|<|**Yes**| |Low-level discovery|<|**Yes**| |Remote commands|<|**Yes**| |Calculating triggers|<|*No*| |Processing events|<|*No*| |Event correlation|<|*No*| |Sending alerts|<|*No*|  ::: noteclassic \[1\] To make sure that an agent asks the proxy (and not the server) for active checks, the proxy must be listed in the **ServerActive** parameter in the agent configuration file. :::
zh-cn	 #### 概览  Zabbix Proxy可以代表Zabbix server收集性能和可用性数据。 通过这种方式，proxy可以自己承担一些收集数据的负载，并减轻Zabbix Server的负担。  此外，当所有agents和proxy都向一个Zabbix server报告并且所有数据都集中收集时，使用Proxy代理是实现集中式和分布式监控的最简单方法。  Zabbix proxy 可以被使用作为:  -   监控远程位置 -   监控通信不可靠的位置 -   在监视数千个设备时卸载Zabbix服务器 -   简化分布式监控的维护  ![](../../../assets/en/manual/proxies/proxy.png){width="600"}  proxy 只需要一个到Zabbix server的TCP连接。 这样就可以更容易地绕过防火墙，因为您只需要配置一条防火墙规则。  ::: noteimportant Zabbix proxy代理必须使用单独的数据库。将其指向Zabbix server数据库将破坏配置。 :::  proxy收集的所有数据在传输到server之前都存储在本地。这种方式不会因为与server之间的任何临时通信问题而丢失数据。*ProxyLocalBuffer*和*ProxyOfflineBuffer*参数在[proxy配置文件](/manual/appendix/config/zabbix_proxy)控制数据在本地保存多长时间。  ::: noteimportant 可能会出现这样的情况:直接从Zabbix server数据库接收最新配置更改的proxy代理拥有比Zabbix server更最新的配置，而Zabbix server的配置可能因为[CacheUpdateFrequency](/manual/appendix/config/zabbix_server)的值而不能快速更新。因此，proxy代理可能会开始收集数据并将它们发送到忽略这些数据的Zabbix server。 :::  Zabbix proxy代理是一个数据收集器。 它不计算触发器、处理事件或发送警报。 有关什么是proxy代理功能的概述，请查看下表：  |功能|<|proxy支持列表| |--------|-|------------------| |Items|<|<| |<|*Zabbix agent checks*|**Yes**| |^|*Zabbix agent checks (active)*|**Yes** ^1^| |^|*Simple checks*|**Yes**| |^|*Trapper items*|**Yes**| |^|*SNMP checks*|**Yes**| |^|*SNMP traps*|**Yes**| |^|*IPMI checks*|**Yes**| |^|*JMX checks*|**Yes**| |^|*Log file monitoring*|**Yes**| |^|*Internal checks*|**Yes**| |^|*SSH checks*|**Yes**| |^|*Telnet checks*|**Yes**| |^|*External checks*|**Yes**| |^|*Dependent items*|**Yes**| |^|*Script items*|**Yes**| |Built-in web monitoring|<|**Yes**| |Item value preprocessing|<|**Yes**| |Network discovery|<|**Yes**| |Active agent autoregistration|<|**Yes**| |Low-level discovery|<|**Yes**| |Remote commands|<|**Yes**| |Calculating triggers|<|*No*| |Processing events|<|*No*| |Event correlation|<|*No*| |Sending alerts|<|*No*|  ::: 常见注意事项 \[1\] 为确保agent请求proxy(而不是server)进行活动检查，proxy代理必须被列于**ServerActive** 配置文件中的参数。 :::

en-us	#### Overview  By default, Zabbix provides a number of predefined themes. You may follow the step-by-step procedure provided here in order to create your own. Feel free to share the result of your work with Zabbix community if you created something nice.
zh-cn	#### 概述  默认情况下，Zabbix 提供了许多预定义的主题。您可以按照此处提供的分步程序来创建您自己的。如果您创建了一些不错的东西，请随时与 Zabbix 社区分享您的工作成果。

en-us	##### Overview by item type  In this screen it is easy to locate if the problem is related to one or several item types.  ![](../../../../../assets/en/manual/web_interface/queue.png){width="600"}  Each line contains an item type. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively.
zh-cn	##### 监控项类型概览  在此屏幕中，很容易找到问题是否与一种或多种监控项类型有关。  ![](../../../../../assets/en/manual/web_interface/queue.png){width="600"}  每行包含一个监控项类型。每列显示等待监控项的数量 - 分别等待 5-10 秒/10-30 秒/30-60 秒/1-5 分钟/5-10 分钟或超过 10 分钟。

en-us	##### Overview by proxy  In this screen it is easy to locate if the problem is related to one of the proxies or the server.  ![](../../../../../assets/en/manual/web_interface/queue_proxy.png){width="600"}  Each line contains a proxy, with the server last in the list. Each column shows the number of waiting items - waiting for 5-10 seconds/10-30 seconds/30-60 seconds/1-5 minutes/5-10 minutes or over 10 minutes respectively.
zh-cn	##### proxy概览  在此屏幕中，很容易找到问题是否与poxy、server之一有关。  ![](../../../../../assets/en/manual/web_interface/queue_proxy.png){width="600"}  每行包含一个proxy，server位于列表的最后。每列显示等待监控项的数量 - 分别等待 5-10 秒/10-30 秒/30-60 秒/1-5 分钟/5-10 分钟或超过 10 分钟。

en-us	#### Overview  Change of trigger status is the most frequent and most important source of events. Each time the trigger changes its state, an event is generated. The event contains details of the trigger state's change - when it happened and what the new state is.  Two types of events are created by triggers - Problem and OK.
zh-cn	#### 概述  触发器状态的变化是事件最常见和最重要的来源。每次触发器的状态改变时，都会生成一个事件。该事件包含了触发器状态变更的详细信息、发生时间以及触发器的新状态。  触发器会创建两种类型的事件：问题和正常。

en-us	#### Overview  Checking for a new item value in Zabbix is a cyclic process that is based on configured update intervals. While for many items the update intervals are quite short, there are others (including low-level discovery rules) for which the update intervals are quite long, so in real-life situations there may be a need to check for a new value quicker - to pick up changes in discoverable resources, for example. To accommodate such a necessity, it is possible to reschedule a passive check and retrieve a new value immediately.  This functionality is supported for **passive** checks only. The following item types are supported:  -   Zabbix agent (passive) -   SNMPv1/v2/v3 agent -   IPMI agent -   Simple check -   Zabbix internal -   External check -   Database monitor -   JMX agent -   SSH agent -   Telnet -   Calculated -   HTTP agent -   Script  ::: noteimportant The check must be present in the configuration cache in order to get executed; for more information see [CacheUpdateFrequency](/manual/appendix/config/zabbix_server). Before executing the check, the configuration cache is **not** updated, thus very recent changes to item/discovery rule configuration will not be picked up. Therefore, it is also not possible to check for a new value for an item/rule that is being created or has been created just now; use the *Test* option while configuring an item for that. :::
zh-cn	#### 概览  在ZABBIX中，检查一个新监控项的值是基于配置更新间隔的循环过程。虽然对于大多数监控项来说间隔非常短，但是有些监控项(包括低级别的发现规则)更新间隔会很长。因此在实际情况下，可能需要很快的检查新的值。-例如，发现资源的变化。为了满足这种需求，可以改成被动检查并立刻检索新的值。\  这个功能仅支持**被动** 检查。支持以下监控项的类型：  -   Zabbix agent (被动) -   SNMPv1/v2/v3 agent -   IPMI agent -   简单检查 -   Zabbix 内部 -   外部检查 -   数据库监控 -   JMX agent -   SSH agent -   Telnet -   计算 -   HTTP agent -   脚本  ::: noteimportant 检查必须存在于配置缓存中才能执行。有关详细信息请参阅[缓存更新频率](/zh/manual/appendix/config/zabbix_server)。\ 在执行检查前，若配置缓存**没有**更新，那么将不会检索最近更改配置的监控项/自动发现规则。同样也无法检查刚刚创建的监控项/规则的最新值，可以在配置监控项时通过*测试*选项来验证下。  :::

en-us	#### Overview  Configuring a map in Zabbix requires that you first create a map by defining its general parameters and then you start filling the actual map with elements and their links.  You can populate the map with elements that are a host, a host group, a trigger, an image, or another map.  Icons are used to represent map elements. You can define the information that will be displayed with the icons and set that recent problems are displayed in a special way. You can link the icons and define information to be displayed on the links.  You can add custom URLs to be accessible by clicking on the icons. Thus you may link a host icon to host properties or a map icon to another map.  Maps are managed in *Monitoring* → *[Maps](/manual/web_interface/frontend_sections/monitoring/maps)*, where they can be configured, managed and viewed. In the monitoring view, you can click on the icons and take advantage of the links to some scripts and URLs.  Network maps are based on vector graphics (SVG) since Zabbix 3.4.
zh-cn	#### 概述  在 Zabbix 中配置地图首先需要定义一些常规参数来创建地图，然后用元素和元素链接填充实际的地图。  您可以使用主机、主机组、触发器、图像或其他地图来填充地图。  图标用于表示地图元素。您可以定义和图标一起显示的信息并设置以特殊的方式显示最近的问题。您可以链接图标并定义要在链接上显示的信息。  您可以通过单击图标添加可访问的自定义 URL。因此您可以将主机图标链接到主机属性或将地图图标链接到另一个地图。  地图在 *监控* 中管理 →*[地图](/manual/web_interface/frontend_sections/monitoring/maps)*，其中它们可以被配置、管理和查看。在监控视图中，您可以单击图标并利用它链接某些脚本和网址。  自 Zabbix 3.4 起，网络地图基于矢量图形 (SVG)。

en-us	#### Overview  Configuring a template requires that you first create a template by defining its general parameters and then you add entities (items, triggers, graphs, etc.) to it.
zh-cn	#### 概述  配置模板需要首先通过定义一些常规参数来创建模板，然后添加实体（监控项，触发器，图表等）。

en-us	#### Overview  Custom graphs, as the name suggests, offer customization capabilities.  While simple graphs are good for viewing data of a single item, they do not offer configuration capabilities.  Thus, if you want to change graph style or the way lines are displayed or compare several items, for example, incoming and outgoing traffic in a single graph, you need a custom graph.  Custom graphs are configured manually.  They can be created for a host or several hosts or for a single template.
zh-cn	#### 概述  顾名思义，自定义图表提供自定义功能。  虽然简单的图表有利于查看单个项目的数据，但它们不支持配置功能。  因此，如果您想更改图形样式或线条的显示方式或比较几个监控项，例如，单个图表展示接收和转发的流量，您需要一个自定义图表。  自定义图表是手动配置的。  它们可以为一台主机或多台主机或单个主机创建模板。

en-us	#### Overview  Data provided in Prometheus line format can be used for low-level discovery.  See [Prometheus checks](/manual/config/items/itemtypes/prometheus) for details how Prometheus data querying is implemented in Zabbix.
zh-cn	#### 概述  Prometheus中的数据格式适用于低级别自动发现。  关于Zabbix如何执行Prometheus数据的查询，请参考 [Prometheus检查](/manual/config/items/itemtypes/prometheus)。

en-us	#### Overview  Debug mode may be used to diagnose performance problems with frontend pages.
zh-cn	#### 概述  调试模式可用于诊断前端页面的性能问题。

en-us	#### Overview  Depending on user role permissions, the *User settings* section may contain the following pages:  -   *User profile* - for customizing certain Zabbix frontend features; -   *API tokens* - for managing API tokens assigned to the current user.  The list of available pages appears upon pressing on the ![](../../../assets/en/manual/web_interface/user_profile.png) user icon near the bottom of the Zabbix menu (not available for a guest user). It is also possible to switch between pages by using a title dropdown in the top left corner.  |   |   | |---|---| |![](../../../assets/en/manual/web_interface/user_menu.png){width="300"}|![](../../../assets/en/manual/web_interface/user_selector.png){width="300"}| |Third-level menu.|Title dropdown.|
zh-cn	#### 概述  根据用户角色权限，*用户设置*部分可能包含以下页面：  - *用户配置文件* - 用于自定义某些 Zabbix 前端功能； - *API 令牌* - 用于管理分配给当前用户的 API 令牌。  按下 Zabbix 菜单底部附近的 ![](../../../assets/en/manual/web_interface/user_profile.png) 用户图标后，可用页面列表出现（对访客不可用）。 也可以使用左上角的标题下拉菜单在页面之间切换。  | · | · | |---|---| |![](../../../assets/en/manual/web_interface/user_menu.png){width="300"}|![](../../../assets/en/manual/web_interface/user_selector.png){width="300"}| |三级菜单。|标题下拉菜单。|

en-us	#### Overview  Each pre-shared key (PSK) in Zabbix actually is a pair of:  -   non-secret PSK identity string, -   secret PSK string value.  PSK identity string is a non-empty UTF-8 string. For example, "PSK ID 001 Zabbix agentd". It is a unique name by which this specific PSK is referred to by Zabbix components. Do not put sensitive information in PSK identity string - it is transmitted over the network unencrypted.  PSK value is a hard to guess string of hexadecimal digits, for example, "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9".
zh-cn	#### 概述  Zabbix中的每个预共享密钥（PSK）实际上是一对：  - 非秘密 PSK 标识字符串， - 秘密 PSK 字符串值。  PSK 标识字符串是非空 UTF-8 字符串。例如，"PSK ID 001 Zabbix agentd"。它是一个唯一的名称，Zabbix组件通过该名称引用此特定PSK。不要将敏感信息放在 PSK 标识字符串中 - 它是通过未加密的网络传输的。  PSK 值是一个难以猜测的十六进制数字字符串，例如， "e560cb0d918d26d31b4f642181f5f570ad89a390931102e5391d08327ba434e9"。

en-us	#### Overview  Event correlation allows to correlate problem events to their resolution in a manner that is very precise and flexible.  Event correlation can be defined:  -   [on trigger level](/manual/config/event_correlation/trigger) - one     trigger may be used to relate separate problems to their solution -   [globally](/manual/config/event_correlation/global) - problems can     be correlated to their solution from a different trigger/polling     method using global correlation rules
zh-cn	#### 概述  事件关联允许以非常精确灵活地方式关联问题事件和它们的解决方法。  事件关联可以被定义为：  -   [触发器级别](/manual/config/event_correlation/trigger)——不同的问题和解决方法可以关联同一个触发器 -   [全局](/manual/config/event_correlation/global)——使用全局关联规则可以通过不同的触发器轮询方法将问题和它们的解决方法关联起来

en-us	#### Overview  External check is a check executed by Zabbix server by [running a shell script](/manual/appendix/command_execution) or a binary. However, when hosts are monitored by a Zabbix proxy, the external checks are executed by the proxy.  External checks do not require any agent running on a host being monitored.  The syntax of the item key is:      script[<parameter1>,<parameter2>,...]  Where:  |ARGUMENT|DEFINITION| |--------|----------| |**script**|Name of a shell script or a binary.| |**parameter(s)**|Optional command line parameters.|  If you don't want to pass any parameters to the script you may use:      script[] or     script  Zabbix server will look in the directory defined as the location for external scripts (parameter 'ExternalScripts' in [Zabbix server configuration file](/manual/appendix/config/zabbix_server)) and execute the command. The command will be executed as the user Zabbix server runs as, so any access permissions or environment variables should be handled in a wrapper script, if necessary, and permissions on the command should allow that user to execute it. Only commands in the specified directory are available for execution.  ::: notewarning Do not overuse external checks! As each script requires starting a fork process by Zabbix server, running many scripts can decrease Zabbix performance a lot. :::
zh-cn	#### 概述  外部检查是 Zabbix server 通过[运行shell脚本](/manual/appendix/command_execution)或二进制执行的检查。但是当主机被 Zabbix proxy 接管时，外部检查则由 Zabbix proxy 执行。  外部检查不需要在被监控的主机上运行任何代理  监控项键的语法是：     script[<parameter1>,<parameter2>,...]  参数：  |字段|描述| |--------|----------| |**script**|shell 脚本或二进制文件的名称.| |**parameter(s)**|可选的命令行参数.|  如果您不想将任何参数传递给脚本,您可以使用：     script[] or    script  Zabbix Server 将查找外部脚本位置的目录([Zabbix Server配置文件](/manual/appendix/config/zabbix_server)中的“ExternalScripts”参数定义的位置)并执行该命令。该命令将以Zabbix Server服务运行的用户身份执行*script*，任何访问权限或环境变量都应该在封装在脚本中处理，该命令的权限应该只允许该用户在指定的目录下执行它。  ::: notewarning 不要过度使用外部检查！因为每个脚本都需要Zabbix Server启动一个fork出来的进程，所以运行很多脚本会大幅度的降低Zabbix的性能。 :::

en-us	#### Overview  For an easy access to Zabbix from anywhere and from any platform, the web-based interface is provided.  ::: noteclassic If using more than one frontend instance make sure that the locales and libraries (LDAP, SAML etc.) are installed and configured identically for all frontends. :::
zh-cn	#### 概述  为了可以从任何平台在任何位置轻松的访问Zabbix，我们提供了基于Web的界面。  ::: noteclassic 如果使用超过一个前端实例，需要确保语言环境和库（LDAP, SAML等等）已经安装并 在所有前端有相同的配置 :::

en-us	#### Overview  Geomap widget displays hosts as markers on a geographical map using open-source JavaScript interactive maps library Leaflet.  ::: noteclassic  Zabbix offers multiple predefined map tile service providers and an option to add a custom tile service provider or even host tiles themselves (configurable in the *Administration → General → Geographical maps* [menu section](/manual/web_interface/frontend_sections/administration/general#geographical_maps)).  :::
zh-cn	#### 概述  Geomap使用基于JavaScript的开源交互式地图库Leaflet将主机位置标记在地图上。  ::: noteclassic Zabbix内置了多种地图供应商并支持自定义地图供应商，以及自建地图（可在 *Administration → General → Geographical maps* [菜单部分](/manual/web_interface/frontend_sections/administration/general#geographical_maps)配置）。  :::

en-us	#### Overview  Geomap widget displays hosts as markers on a geographical map using open-source JavaScript interactive maps library Leaflet.  ::: noteclassic  Zabbix offers multiple predefined map tile service providers and an option to add a custom tile service provider or even host tiles themselves (configurable in the *Administration → General → Geographical maps* [menu section](/manual/web_interface/frontend_sections/administration/general#geographical_maps)).  :::  By default, the widget displays all enabled hosts that have Latitude and Longitude Inventory fields filled in the host configuration. It is possible to configure host filtering in the widget parameters.  
zh-cn	#### Overview  Geomap widget displays hosts as markers on a geographical map using open-source JavaScript interactive maps library Leaflet.  ::: noteclassic  Zabbix offers multiple predefined map tile service providers and an option to add a custom tile service provider or even host tiles themselves (configurable in the *Administration → General → Geographical maps* [menu section](/manual/web_interface/frontend_sections/administration/general#geographical_maps)).  :::  By default, the widget displays all enabled hosts that have Latitude and Longitude Inventory fields filled in the host configuration. It is possible to configure host filtering in the widget parameters.  

en-us	#### Overview  Global event correlation allows to reach out over all metrics monitored by Zabbix and create correlations.  It is possible to correlate events created by completely different triggers and apply the same operations to them all. By creating intelligent correlation rules it is actually possible to save yourself from thousands of repetitive notifications and focus on root causes of a problem!  Global event correlation is a powerful mechanism, which allows you to untie yourself from one-trigger based problem and resolution logic. So far, a single problem event was created by one trigger and we were dependent on that same trigger for the problem resolution. We could not resolve a problem created by one trigger with another trigger. But with event correlation based on event tagging, we can.  For example, a log trigger may report application problems, while a polling trigger may report the application to be up and running. Taking advantage of event tags you can tag the log trigger as *Status: Down* while tag the polling trigger as *Status: Up*. Then, in a global correlation rule you can relate these triggers and assign an appropriate operation to this correlation such as closing the old events.  In another use, global correlation can identify similar triggers and apply the same operation to them. What if we could get only one problem report per network port problem? No need to report them all. That is also possible with global event correlation.  Global event correlation is configured in **correlation rules**. A correlation rule defines how the new problem events are paired with existing problem events and what to do in case of a match (close the new event, close matched old events by generating corresponding OK events). If a problem is closed by global correlation, it is reported in the *Info* column of *Monitoring* → *Problems*.  Configuring global correlation rules is available to Super Admin level users only.  ::: noteimportant Event correlation must be configured very carefully, as it can negatively affect event processing performance or, if misconfigured, close more events than was intended (in the worst case even all problem events could be closed). :::  To configure global correlation **safely**, observe the following important tips:  -   Reduce the correlation scope. Always set a unique tag for the new     event that is paired with old events and use the *New event tag*     correlation condition; -   Add a condition based on the old event when using the *Close old     event* operation (or else all existing problems could be closed); -   Avoid using common tag names that may end up being used by different     correlation configurations; -   Keep the number of correlation rules limited to the ones you really     need.  See also: [known issues](/manual/installation/known_issues#global_event_correlation).
zh-cn	#### 概述  全局事件关联允许覆盖Zabbix监控的所有指标并创建关联性。  可以关联由完全不同的触发器创建的事件，并对它们应用相同的操作。 通过创建智能关联规则，实际上可以避免数以千计的重复通知，并专注于问题的根本原因！  全局事件关联是一种强大的机制，它可以让您从基于单个触发的问题和解决逻辑中解开自己。 到目前为止，单个问题事件是由一个触发器创建的，我们依赖于相同的问题解决触发器。 我们无法用另一个触发器解决一个触发器创建的问题。 但是基于事件标记的事件关联，我们可以。  例如，日志触发器可以报告应用程序问题，而轮询触发器可以报告应用程序启动并运行。 利用事件标记，您可以将日志触发器标记为*状态：Down*，而将轮询触发器标记为*状态：Up*。 然后，在全局关联规则中，您可以关联这些触发器并为此关联分配适当的操作，例如关闭旧事件。  在另一种用途中，全局关联可以识别类似的触发器并对它们应用相同的操作。 如果我们每个网络端口问题只能获得一个问题报告怎么办？ 无需全部报告。 通过全局事件关联也是能够实现的。  全局事件关联在**关联规则**中配置。 关联规则定义新问题事件如何与现有问题事件配对以及在匹配情况下要执行的操作（关闭新事件，通过生成相应的OK事件来关闭匹配的旧事件）。 如果问题被全局关联关闭，则会在*监控* - > *问题*的*消息*列中报告。  配置全局关联规则仅适用于Zabbix超级管理员级别用户。  ::: noteimportant 必须非常仔细地配置事件关联，因为它会对事件处理性能产生负面影响，或者如果配置错误，会关闭比预期更多的事件（在最坏的情况下，甚至可以关闭所有问题事件）。:::  要安全地配置全局关联，请遵循以下重要提示：  -   减少相关范围。     始终为与旧事件配对的新事件设置唯一标记，并使用*新事件标记*关联条件; -   使用*关闭旧事件*操作时，根据旧事件添加条件（或者可以关闭所有现有问题）; -   避免使用可能最终被不同关联配置使用的常见标记名称; -   保持关联规则的数量仅限于您真正需要的数量。  可参考: [known issues](/manual/installation/known_issues#global_event_correlation).

en-us	#### Overview  Global notifications are a way of displaying issues that are currently happening right on the screen you're at in Zabbix frontend.  Without global notifications, working in some other location than *Problems* or the *Dashboard* would not show any information regarding issues that are currently happening. Global notifications will display this information regardless of where you are.  Global notifications involve both showing a message and [playing a sound](sound).  ::: noteimportant The auto play of sounds may be disabled in recent browser versions by default. In this case, you need to change this setting manually. :::
zh-cn	#### 概述  全局通知是一种在 Zabbix 前端屏幕上显示当前正在发生的问题的方式。  如果没有全局通知，在 *问题* 或 *仪表板* 以外的其他位置工作将不会显示有关当前正在发生的问题的任何信息。 无论您身在何处，全局通知都会显示此信息。  全局通知涉及显示消息和[播放声音]（声音）。  ::: noteimportant 默认情况下，最近的浏览器版本可能会禁用声音的自动播放。 在这种情况下，您需要手动更改此设置。 :::

en-us	#### Overview  Having to use some large numbers, for example '86400' to represent the number of seconds in one day, is both difficult and error-prone. This is why you can use some appropriate unit symbols (or suffixes) to simplify Zabbix trigger expressions and item keys.  Instead of '86400' for the number of seconds you can simply enter '1d'. Suffixes function as multipliers.
zh-cn	#### 概述  当必须使用一些大数字，例如“86400”来表示一天中的秒数，既困难又容易出错。这就需要使用一些单位符号来简化 Zabbix 触发器表达式和监控项键。  可以简单地输入“1d”，而不是“86400”秒。后缀起到乘数的作用。

en-us	### Overview  High availability (HA) is typically required in critical infrastructures  that can afford virtually no downtime. So for any service that  may fail there must be a failover option in place to take over should the current service fail.  Zabbix offers a **native** high-availability solution that is easy to  set up and does not require any previous HA expertise. Native Zabbix HA  may be useful for an extra layer of protection against software/hardware  failures of Zabbix server or to have less downtime due to maintenance.  In the Zabbix high availability mode multiple Zabbix servers are run as  nodes in a cluster. While one Zabbix server in the cluster is active,  others are on standby, ready to take over if necessary.  ![](../../../../assets/en/manual/config/zabbix_ha.png)  Switching to Zabbix HA is non-committal. You may switch back to standalone  operation at any point.  See also: [Implementation details](#implementation-details)
zh-cn	### 概述  通常高可用性(HA)需要在几乎不需要停机的关键基础设施中使用。为了在服务出现任何失败故障时进行故障转移，进行接管。  Zabbix提供了一个**本地**的高可用性解决方案，方便设置，不需要任何HA专业知识也可以完成。本地Zabbix HA对于防止Zabbix server的软件/硬件故障或减少维护停机时间是有用的。  Zabbix高可用模式下，多台Zabbix server作为集群中的节点运行。 当集群中的一个Zabbix server 处于active 时，其他服务器处于standy，随时准备在必要时接管。  ![](../../../../assets/en/manual/config/zabbix_ha.png)  切换到Zabbix HA还不确定。 您可以在任何时候切换回standalone状态。  参见: [实施详细](#implementation-details)

en-us	#### Overview  History and trends are the two ways of storing collected data in Zabbix.  Whereas history keeps each collected value, trends keep averaged information on hourly basis and therefore are less resource-hungry.
zh-cn	#### 概述  历史数据（history）和趋势数据（trends）是Zabbix中存储收集到的数据的两种方式。  历史数据：每一个收集到的监控数据， 趋势数据：按小时统计计算的平均值数据。

en-us	#### Overview  Host dashboards look similar to [global dashboards](/manual/web_interface/frontend_sections/monitoring/dashboard), however, host dashboards display data about the host only. Host dashboards have no owner.  Host dashboards are configured on the [template](/manual/config/templates/template#adding_dashboards) level and then are generated for a host, once the template is linked to the host. Widgets of host dashboards can only be copied to host dashboards of the same template. Widgets from global dashboards cannot be copied onto host dashboards.  Host dashboards *cannot* be configured or directly accessed in the *Monitoring* → *[Dashboard](/manual/web_interface/frontend_sections/monitoring/dashboard)* section, which is reserved for global dashboards. The ways to access host dashboards are listed below in this section.  ![](../../../../assets/en/manual/config/visualization/host_dashboards.png){width="600"}  When viewing host dashboards you may switch between the configured dashboards using the dropdown in the upper right corner. To switch to *Monitoring→Hosts* section, click *All hosts* navigation link below the dashboard name in the upper left corner.  Widgets of the host dashboards cannot be edited.  Note that host dashboards used to be host screens before Zabbix 5.2. When importing an older template containing screens, the screen import will be ignored.
zh-cn	#### 概述  主机仪表盘与 [全局仪表盘](/manual/web_interface/frontend_sections/monitoring/dashboard)类似，仅显示主机相关的数据， 没有所有者。  主机仪表盘在链接到主机的[模板](/manual/config/templates/template#adding_dashboards) 级进行配置，然后根据主机生成仪表盘。 主机仪表盘的部件仅可以复制给相同模板的主机。全局仪表盘的部件不能拷贝到主机仪表盘。  主机仪表盘 *不能* 通过*监控* →*[仪表盘](/manual/web_interface/frontend_sections/monitoring/dashboard)*部分进行配置和访问, 这种方式是全局仪表盘的配置和访问方式。主机仪表盘的访问方式通过如下部分。  ![](../../../../assets/en/manual/config/visualization/host_dashboards.png){width="600"}  可以通过在配置仪表盘右上角的下拉菜单进行切换来查看主机仪表盘。通过*监控→主机*部分，选择左上角仪表盘名称导航链接下的*所有主机*进行切换。  主机仪表盘的小部件不可编辑。  注意，主机仪表盘在Zabbix 5.2之前是被用作主机聚合图形之中的。所以在导入早期版本的包含聚合图形的模板时，聚合图形会被忽略。

en-us	#### Overview  Host graphs can be accessed from *Monitoring → Hosts* by clicking on Graphs for the respective host.  Any [custom graph](/manual/config/visualization/graphs/custom) that has been configured for the host can be displayed, as well as any simple graph.  ![](../../../../../../assets/en/manual/web_interface/graphs.png){width="600"}  Graphs are sorted by:  -   graph name (custom graphs) -   item name (simple graphs)  Graphs for disabled hosts are also accessible.
zh-cn	#### 概述  可以通过单击相应主机的图形。从 *监控→ 主机* 访问主机图。 任意 [自定义图形](/manual/config/visualization/graphs/custom) 以及任意简单图形。 ![](../../../../../../assets/en/manual/web_interface/graphs.png){width="600"}  图表的排序方式为：  - · 图形名称（自定义图形） - · 项目名称（简单图形）  禁用主机的图表也可访问。

en-us	#### Overview  Hosts are [exported](/manual/xml_export_import) with many related objects and object relations.  Host export contains:  -   linked host groups -   host data -   template linkage -   host group linkage -   host interfaces -   directly linked items -   directly linked triggers -   directly linked graphs -   directly linked discovery rules with all prototypes -   directly linked web scenarios -   host macros -   host inventory data -   value maps
zh-cn	#### 概述  导出（exported） 的主机具有许多相关对象和对象关系。  主机导出的内容包含：  -   链接的主机组    -   主机数据 -   模板链接 -   主机组链接 -   主机接口 -   直接链接的应用集 -   直接链接的监控项 -   直接链接的触发器 -   直接链接的图形 -   直接链接的具有所有原型的发现规则 -   直接链接的web场景 -   主机宏 -   主机资产清单数据 -   值映射

en-us	#### Overview  Host [web scenario](/manual/web_monitoring) information can be accessed from *Monitoring → Hosts* by clicking on Web for the respective host.  ![](../../../../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  Data of disabled hosts is also accessible. The name of a disabled host is listed in red.  The maximum number of scenarios displayed per page depends on the *Rows per page* user profile [setting](/manual/web_interface/user_profile#configuration).  By default, only values that fall within the last 24 hours are displayed. This limit has been introduced with the aim of improving initial loading times for large pages of latest data. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration→General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.  The scenario name is link to more detailed statistics about it:  ![](../../../../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}
zh-cn	#### 概述  主机 [Web场景] (/manual/web_monitoring) 信息可以通过   单击相应主机的*监测→ 主机* 访问。  ![](../../../../../../assets/en/manual/web_interface/web_monitoring.png){width="600"}  对于处于禁用状态的主机，其WEB场景的监控数据依旧可以访问。但请注意，这类主机的名称将会是红色字体。  每页所能展示的最多场景的数量，取决于用户[设置 ](/manual/web_interface/user_profile#configuration)中的 *每页行数*。  默认情况下，仅显示过去 24 小时内的值。引入此限制的目的是缩短大页面最新数据的初始加载时间。你可以通过在 *[管理 → 常规](/manual/web_interface/frontend_sections/administration/general#gui)*菜单中更改 *最长可显示历史期限* 参数的值来延长此时间。  方案名称链接到有关它的更详细的统计信息：  ![](../../../../../../assets/en/manual/web_monitoring/scenario_details2.png){width="600"}

en-us	#### Overview  If [installed](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation) from Debian/Ubuntu packages, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java).  
zh-cn	#### 概述  如果你是通过 Debian/Ubuntu 的包[安装](/manual/installation/install_from_packages/debian_ubuntu#java_gateway_installation)，那么下列信息会帮助你配置Zabbix [Java网关](/manual/concepts/java)。

en-us	#### Overview  If [installed](/manual/installation/install_from_packages/rhel#java_gateway_installation) from RHEL packages, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java).
zh-cn	#### 概述  如果你是通过 RHEL 的包[安装](/manual/installation/install_from_packages/rhel_centos#java_gateway_installation)，那么下列信息会帮助你配置Zabbix [Java网关](/manual/concepts/java)。

en-us	#### Overview  If [installed](/manual/installation/install#installing_java_gateway) from sources, the following information will help you in setting up Zabbix [Java gateway](/manual/concepts/java).
zh-cn	#### 概述  如果你是使用源码[安装]((/manual/installation/install#installing_java_gateway))，那么下列信息会帮助你配置Zabbix [Java网关](/manual/concepts/java)。

en-us	#### Overview  If you are not satisfied with existing media types for sending alerts there is an alternative way to do that. You can create a script that will handle the notification your way.  Alert scripts are executed on Zabbix server. These scripts are located in the directory defined in the server [configuration file](/manual/appendix/config/zabbix_server) **AlertScriptsPath** variable.  Here is an example alert script:  ``` {.bash} #!/bin/bash  to=$1 subject=$2 body=$3  cat <<EOF | mail -s "$subject" "$to" $body EOF ```  ::: noteimportant Starting from version 3.4 Zabbix checks for the exit code of the executed commands and scripts. Any exit code which is different from **0** is considered as a [command execution](/manual/appendix/command_execution) error. In such case Zabbix will try to repeat failed execution. :::  Environment variables are not preserved or created for the script, so they should be handled explicitly.
zh-cn	#### 概述  如果当前的告警媒介类型无法满足您的要求，您可以创建一个自定义的脚本对告警通知进行处理。  告警脚本在Zabbix服务器上执行。这些脚本放置于服务器配置文件 [configuration file](/manual/appendix/config/zabbix_server)中定义的 **AlertScriptsPath**目录下。    以下是一个自定义告警脚本的示例:  ``` {.bash} #!/bin/bash  to=$1 subject=$2 body=$3  cat <<EOF | mail -s "$subject" "$to" $body EOF ```  ::: noteimportant 从3.4版本开始，Zabbix会检查执行的命令和脚本的退出代码。任何不为**0** 的退出代码都将被视为[command execution](/manual/appendix/command_execution) 错误. 在这种情况下，Zabbix会尝试重复执行。 ::: 环境变量不会为脚本保留或创建，因此它们应该被明确处理。

en-us	#### Overview  If you have a network to look after, you may want to have an overview of your infrastructure somewhere. For that purpose, you can create maps in Zabbix - of networks and of anything you like.  All users can create network maps. The maps can be public (available to all users) or private (available to selected users).  Proceed to [configuring a network map](/manual/config/visualization/maps/map).  
zh-cn	#### 概述  当你在维护一个网络的时候，你可能想看下整体基础设施的网络拓扑结构。 这种情况下，你可以在Zabbix中创建一个拓扑图来实现，可以是网络和任何相关节点。  所有用户都可以配置网络拓扑图. 拓扑图可以是公开的 (所有用户可见) 或者私有的 (部分用户可见)。  请参照[配置网络拓扑](/manual/config/visualization/maps/map)。

en-us	#### Overview  If you want some operations taking place as a result of events (for example, notifications sent), you need to configure actions.  Actions can be defined in response to events of all supported types:  -   Trigger actions - for events when trigger status changes from *OK*     to *PROBLEM* and back -   Service actions - for events when service status changes from *OK*     to *PROBLEM* and back -   Discovery actions - for events when network discovery takes place -   Autoregistration actions - for events when new active agents     auto-register (or host metadata changes for registered ones) -   Internal actions - for events when items become unsupported or     triggers go into an unknown state
zh-cn	#### 概述  如果您希望对产生的事件进行一些操作（例如发送通知），则需要配置动作。  可以根据所有支持类型的事件来定义动作：  -   触发器动作 - 当trigger的状态从 *OK*变为*PROBLEM*或者从  *PROBLEM*  恢复到  *OK*时 -   服务动作 - 当服务的状态从 *OK*变为*PROBLEM*或者从  *PROBLEM*  恢复到  *OK*时 -   自动发现动作 - 针对网络自动发现事件发生时 -   自动注册动作 - 当新的agents自动注册（或已注册主机元数据发生改变）时 -   内部动作 - 当监控项变成不支持状态或触发器进入未知状态时

en-us	#### Overview  If you want some operations taking place as a result of events (for example, notifications sent), you need to configure actions.  Actions can be defined in response to events of all supported types:  -   Trigger actions - for events when trigger status changes from *OK*     to *PROBLEM* and back -   Service actions - for events when service status changes from *OK*     to *PROBLEM* and back -   Discovery actions - for events when network discovery takes place -   Autoregistration actions - for events when new active agents     auto-register (or host metadata changes for registered ones) -   Internal actions - for events when items become unsupported or     triggers go into an unknown state  
zh-cn	#### 概述  如果您希望对产生的事件进行一些操作（例如发送通知），则需要配置动作。  可以根据所有支持类型的事件来定义动作：  -   触发器动作 - 当trigger的状态从 *OK*变为*PROBLEM*或者从  *PROBLEM*  恢复到  *OK*时 -   服务动作 - 当服务的状态从 *OK*变为*PROBLEM*或者从  *PROBLEM*  恢复到  *OK*时 -   自动发现动作 - 针对网络自动发现事件发生时 -   自动注册动作 - 当新的agents自动注册（或已注册主机元数据发生改变）时 -   内部动作 - 当监控项变成不支持状态或触发器进入未知状态时

en-us	#### Overview  In a similar way as [file systems](/manual/discovery/low_level_discovery#configuring_low-level_discovery) are discovered, it is possible to also discover Windows services.
zh-cn	#### 概述  与 [文件系统](/manual/discovery/low_level_discovery#configuring_low-level_discovery)自动发现相似，Windows服务同样可被Zabbix自动发现.

en-us	#### Overview  In message subjects and message text you can use macros for more efficient problem reporting.  In addition to a number of built-in macros, [user macros](/manual/config/macros/user_macros) and [expression macros](/manual/config/macros/expression_macros) are also supported. A [full list of macros](/manual/appendix/macros/supported_by_location) supported by Zabbix is available.
zh-cn	#### 概述  在消息主题和消息文本中，您可以使用宏来更有效地报告问题。  除了许多内置宏外，还支持 [用户宏](/manual/config/macros/user_macros) 和 [表达式宏](/manual/config/macros/expression_macros)。 Zabbix 支持可用的[宏的完整列表](/manual/appendix/macros/supported_by_location) 。

en-us	#### Overview  In *Monitoring → Problems* you can see what problems you currently have. Problems are those triggers that are in the "Problem" state.  ![](../../../../../assets/en/manual/web_interface/problems.png){width="600"}  |Column|Description| |--|-----------| |*Time*|Problem start time is displayed.| |*Severity*|Problem severity is displayed.<br>Problem severity is originally based on the severity of the underlying problem trigger, however, after the event has happened it can be updated using the *Update problem* [screen](/manual/acknowledges#updating_problems). Color of the problem severity is used as cell background during problem time.| |*Recovery time*|Problem resolution time is displayed.| |*Status*|Problem status is displayed:<br>**Problem** - unresolved problem<br>**Resolved** - recently resolved problem. You can hide recently resolved problems using the filter.<br>New and recently resolved problems blink for 2 minutes. Resolved problems are displayed for 5 minutes in total. Both of these values are configurable in *Administration* → *General* → *[Trigger displaying options](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*.| |*Info*|A green information icon is displayed if a problem is closed by global correlation or manually when updating the problem. Rolling a mouse over the icon will display more details:<br>![info.png](../../../../../assets/en/manual/web_interface/info.png)<br>The following icon is displayed if a suppressed problem is being shown (see *Show suppressed problems* option in the filter). Rolling a mouse over the icon will display more details:<br>![](../../../../../assets/en/manual/web_interface/info_suppressed2.png)| |*Host*|Problem host is displayed.| |*Problem*|Problem name is displayed.<br>Problem name is based on the name of the underlying problem trigger.<br>Macros in the trigger name are resolved at the time of the problem happening and the resolved values do not update any more.<br>*Note* that it is possible to append the problem name with [operational data](#operational_data_of_problems) showing some latest item values.<br>Clicking on the problem name brings up the [event menu](#event_menu).<br>Hovering on the ![](../../../../../assets/en/manual/web_interface/item_description_icon.png) icon after the problem name will bring up the trigger description (for those problems that have it).| |*Operational data*|[Operational data](#operational_data_of_problems) are displayed containing latest item values.<br>Operational data can be a combination of text and item value macros if configured on a trigger level. If no operational data is configured on a trigger level, the latest values of all items from the expression are displayed.<br>This column is only displayed if *Separately* is selected for *Show operational data* in the filter.| |*Duration*|Problem duration is displayed.<br>See also: [Negative problem duration](#negative_problem_duration)| |*Ack*|The acknowledgment status of the problem is displayed:<br>**Yes** - green text indicating that the problem is acknowledged. A problem is considered to be acknowledged if all events for it are acknowledged.<br>**No** - a red link indicating unacknowledged events.<br>If you click on the link you will be taken to the [problem update](/manual/acknowledges#updating_problems) screen where various actions can be taken on the problem, including commenting and acknowledging the problem.| |*Actions*|History of activities about the problem is displayed using symbolic icons:<br>![icon\_comment.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_comment.png) - comments have been made. The number of comments is also displayed.<br>![icon\_sev\_up1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_up1.png) - problem severity has been increased (e.g. Information → Warning)<br>![icon\_sev\_down1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_down1.png) - problem severity has been decreased (e.g. Warning → Information)<br>![icon\_severity\_back.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_severity_back.png) - problem severity has been changed, but returned to the original level (e.g. Warning → Information → Warning)<br>![icon\_actions.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions.png) - actions have been taken. The number of actions is also displayed.<br>![icon\_actions\_progress1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions_progress1.png) - actions have been taken, at least one is in progress. The number of actions is also displayed.<br>![icon\_actions\_failed.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions_failed.png) - actions have been taken, at least one has failed. The number of actions is also displayed.<br>When rolling the mouse over the icons, popups with details about the activity are displayed. See [viewing details](#Viewing_details) to learn more about icons used in the popup for actions taken.| |*Tags*|[Tags](/manual/config/tagging) are displayed (if any).<br>In addition, tags from an external ticketing system may also be displayed (see the *Process tags* option when configuring [webhooks](/manual/config/notifications/media/webhook)).|
zh-cn	#### 概述  在  *监测→ 问题*  中，你可以看到当前存在哪些问题。问题指处在 "问题" 状态下的触发器。  ![](../../../../../assets/en/manual/web_interface/problems.png){width="600"}  |列|描述| |------|-----------| |*时间*|显示问题开始时间。| |*严重性*|显示问题严重等级。<br>问题严重性最初基于基础问题触发器的严重性，但是，在事件发生后，可以使用 *问题更新*进行更新 [screen](/manual/acknowledges#updating_problems)。 在问题期间，问题严重性的颜色用作单元格背景。| |*恢复时间*|显示问题解决时间。| |*状态*|显示问题状态:<br>**问题** - 未解决的问题<br>**解决** - 最近解决的问题。您可以使用筛选器隐藏最近解决的问题。<br>新的和最近解决的问题闪烁2分钟。已解决的问题显示时间为5分钟。这两个值可以在 *管理* → *常规* → *[Trigger displaying options](/manual/web_interface/frontend_sections/administration/general#trigger_displaying_options)*中进行配置.| |*信息*|如果问题通过全局关联关闭或在更新问题时手动关闭，则会显示绿色信息图标。在图标上滚动鼠标将显示更多的细节:<br>![info.png](../../../../../assets/en/manual/web_interface/info.png)<br>如果显示被抑制的问题，则会显示以下图标 (请参阅筛选器中的 *显示被抑制的问题* 选项)。 将鼠标滚动到图标上将显示更多详细信息：<br>![](../../../../../assets/en/manual/web_interface/info_suppressed2.png)| |*主机*|显示问题主机。| |*问题*|显示问题名称。<br>问题名称基于基础问题触发器的名称。<br>触发器名称中的宏在问题发生时被解析，解析后的值不再更新。<br>*注意*可以在问题名称后面加上 [运营数据](#operational_data_of_problems) 显示一些最新的监控项值。<br>单击问题名称将显示 [事件菜单](#event_menu).<br>将鼠标悬停在问题名称后面的 ![](../../../../../assets/en/manual/web_interface/item_description_icon.png) 图标上，将会显示触发器描述(对于那些有触发器描述的问题)。| |*运行数据*|[Operational data](#operational_data_of_problems) 展示了监控项最新的值。<br>如果在触发器级别上配置，运行数据可以是文本宏和监控项值宏的组合。如果没有在触发器级别配置运行数据，则显示表达式中所有监控项的最新值。<br>仅当在过滤器中为*显示运行数据* 选择 *单独*  时才会显示此列。| |*持续时间*|显示问题持续时间。<br>参阅: [Negative problem duration](#negative_problem_duration)| |*确认*|显示问题的确认状态：<br>**是** - 绿色文本表示问题已得到确认。如果一个问题的所有事件都被确认，则认为该问题已被确认。<br>**不** - 红色链接表示未确认事件的。<br>如果您单击该链接，将跳转到 [problem update](/manual/acknowledges#updating_problems) 页面，其中可以对问题执行各种操作，包括注释和确认问题。| |*动作*|有关该问题的活动历史记录使用符号图标显示：<br>![icon\_comment.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_comment.png) - 已执行的动作。还会显示动作数。<br>![icon\_sev\_up1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_up1.png) - 问题严重性已提高 (例如：信息 → 警告)<br>![icon\_sev\_down1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_sev_down1.png) - 问题严重性已降低 (例如：警告 → 信息)<br>![icon\_severity\_back.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_severity_back.png) - 问题严重程度已更改，但恢复到原来的级别 (例如：警告→信息→警告)<br>![icon\_actions.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions.png) - 已经采取了动作。动作的数量也会显示出来。<br>![icon\_actions\_progress1.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions_progress1.png) - 已经采取了动作，至少有一次正在进行中。动作的数量也会显示出来。<br>![icon\_actions\_failed.png](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/icon_actions_failed.png) - 已经采取了动作，至少有一次失败了。动作的数量也会显示出来。<br>将鼠标滚动到图标上时，将显示包含动作详细信息的弹出窗口。参阅 [viewing details](#Viewing_details) 来了解弹出窗口中所采取的动作图标的更多信息。| |*标签*|[标签](/manual/config/tagging) 显示 (如果有)。<br>另外，可以显示来自外部标签系统的标签 (参阅 *过程标签* 选项配置 [webhooks](/manual/config/notifications/media/webhook)).|

en-us	#### Overview  In order to provide monitoring for network devices such as switches and routers, we have created two so-called models: for the network device itself (its chassis basically) and for network interface.  Since Zabbix 3.4 templates for many families of network devices are provided. All templates cover (where possible to get these items from the device):  -   Chassis fault monitoring (power supplies, fans and temperature,     overall status) -   Chassis performance monitoring (CPU and memory items) -   Chassis inventory collection (serial numbers, model name, firmware     version) -   Network interface monitoring with IF-MIB and EtherLike-MIB     (interface status, interface traffic load, duplex status for     Ethernet)  These templates are available:  -   In new installations - in *Configuration* → *Templates*; -   If you are upgrading from previous versions, you can find these     templates in the `templates` directory of the downloaded latest     Zabbix version. While in *Configuration* → *Templates* you can     import them manually from this directory.  If you are importing the new out-of-the-box templates, you may want to also update the `@Network interfaces for discovery` global regular expression to:      Result is FALSE: ^Software Loopback Interface     Result is FALSE: ^(In)?[lL]oop[bB]ack[0-9._]*$     Result is FALSE: ^NULL[0-9.]*$     Result is FALSE: ^[lL]o[0-9.]*$     Result is FALSE: ^[sS]ystem$     Result is FALSE: ^Nu[0-9.]*$  to filter out loopbacks and null interfaces on most systems.
zh-cn	 #### 概述  为了提供交换机和路由器等网络设备的监控，我们创建了两个所谓的模型：网络设备本身（基本上是它的机框）和网络接口  从Zabbix 3.4开始提供了许多网络设备系列模板。 所有模板都覆盖（尽可能从设备中获取这些监控项）：  -   机框故障监控（电源，风扇和温度，总体状态） -   机框性能监控（CPU和内存监控项） -   机框资产收集（序列号，型号名称，固件版本） -   使用IF-MIB和EtherLike-MIB进行网络接口监控（接口状态，接口流量负载，以太网的双工状态）  这些模板获取来源：  -   在新安装的Zabbix中 - 前往*配置* → *模板*; -   如果是从旧版本升级的Zabbix，你可以在下载的最新版本的Zabbix的`templates` 目录中找到模板文件。在经过手工  导入这些模板文件后，可以在*配置* → *模板*页找到模板。  如果要导入新的开箱即用模板，您可能还需要将`@Network自动发现接口`全局正则表达式更新为：      Result is FALSE: ^Software Loopback Interface     Result is FALSE: ^(In)?[lL]oop[bB]ack[0-9._]*$     Result is FALSE: ^NULL[0-9.]*$     Result is FALSE: ^[lL]o[0-9.]*$     Result is FALSE: ^[sS]ystem$     Result is FALSE: ^Nu[0-9.]*$  更新后，会过滤掉在大多数系统上环回和空接口。

en-us	#### Overview  In order to use any other language than English in Zabbix web interface, its locale should be installed on the web server. Additionally, the PHP gettext extension is required for the translations to work.
zh-cn	#### 概述  为了在Zabbix Web界面中使用英语以外的任何其他语言，其区域设置应安装在Web服务器上。此外，翻译工作还需要 PHP gettext 扩展。

en-us	#### Overview  In *Reports → Availability report* you can see what proportion of time each trigger has been in problem/ok state. The percentage of time for each state is displayed.  Thus it is easy to determine the availability situation of various elements on your system.  ![](../../../../../assets/en/manual/web_interface/availability_host.png){width="600"}  From the drop-down in the upper right corner, you can choose the selection mode - whether to display triggers by hosts or by triggers belonging to a template.  ![](../../../../../assets/en/manual/web_interface/availability_trigger.png){width="600"}  The name of the trigger is a link to the latest events of that trigger.
zh-cn	 #### 概览  在*报表→ 可用性报表*中，您可以看到每个触发器处于问题/正常状态的时间比例。显示每个状态的时间百分比。  因此，很容易确定系统中各种元素的可用性情况。  ![](../../../../../assets/en/manual/web_interface/availability_host.png){width="600"}  从右上角的下拉列表中，可以选择选择模式-是按主机显示触发器，还是按属于模板的触发器显示触发器。  ![](../../../../../assets/en/manual/web_interface/availability_trigger.png){width="600"}  触发器的名称是指向该触发器最新事件的链接。

en-us	#### Overview  In *Reports → System information* a summary of key Zabbix server and system data is displayed.  Note that in a high availability setup, it is possible to redirect the system information source (server instance) by editing the ui/conf/zabbix.conf.php file - uncomment and set $ZBX\_SERVER, $ZBX\_SERVER\_PORT to a server other than the one shown active.  With the high availability setup enabled, a separate block is displayed below the system stats with details of high availability nodes. This block is visible to Zabbix Super Admin users only.  *System information* is also available as a dashboard [widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets).
zh-cn	#### 概览  *报表→ 系统信息* 中，显示关键系统数据的摘要。   请注意，在高可用性设置中，可以通过编辑 ui/conf/zabbix.conf.php 文件 - 取消注释并将$ZBX_SERVER、$ZBX_SERVER_PORT 重定向到显示的活动服务器以外的服务器，从而重定向系统信息源（服务器实例）。   启用高可用性设置后，系统统计信息下方将显示一个单独的块，其中包含高可用性节点的详细信息。 此块仅对Zabbix超级管理员用户可见。  *系统信息* 也可做为仪表盘[部件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets)。

en-us	#### Overview  In *Reports → Triggers top 100* you can see the triggers that have changed their state most often within the period of evaluation, sorted by the number of status changes.  ![](../../../../../assets/en/manual/web_interface/triggers_top.png){width="600"}  Both host and trigger column entries are links that offer some useful options:  -   for host - links to user-defined scripts, latest data, inventory,     graphs, and dashboards for the host -   for trigger - links to latest events, the trigger configuration     form, and a simple graph  **Using filter**  You may use the filter to display triggers by host group, host, or trigger severity. Specifying a parent host group implicitly selects all nested host groups. For better search performance, data is searched with macros unresolved.  The filter is located below the *100 busiest triggers* bar. It can be opened and collapsed by clicking on the *Filter* tab on the left.  **Time period selector**  The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter.
zh-cn	 #### 概览  在*报表 → 触发器前100*中，您可以看到在评估期间最常更改其状态的触发器，并按状态更改的数量进行排序。  ![](../../../../../assets/en/manual/web_interface/triggers_top.png){width="600"}  主机和触发器列条目都提供一些有用选项的链接：  -   主机 - 链接到主机的用户定义脚本、最新数据、清单、图表和仪表盘 -   触发器 - 链接到最新事件、触发器配置表单和简单图表  **使用过滤器**  您可以使用过滤器按主机组、主机或触发器严重性显示触发器。指定父主机组会隐式选择所有嵌套的主机组。为了获得更好的搜索性能，使用未解析的宏搜索数据。  过滤器位于*100个最忙触发器*栏下方。点击左侧的*过滤器*选项卡，可以将其打开和折叠。  **时间段选择器**  [时间段选择器](/manual/config/visualization/graphs/simple#时间段选择器)允许通过单击鼠标选择经常需要的周期。通过单击过滤器旁边的时间段选项卡，可以打开时间段选择器。

en-us	#### Overview  Internal checks allow to monitor the internal processes of Zabbix. In other words, you can monitor what goes on with Zabbix server or Zabbix proxy.  Internal checks are calculated:  -   on Zabbix server - if the host is monitored by server -   on Zabbix proxy - if the host is monitored by proxy  Internal checks are processed by server or proxy regardless of host maintenance status.  To use this item, choose the **Zabbix internal** item type.  ::: notetip Internal checks are processed by Zabbix pollers. :::
zh-cn	#### 概述  内部检查可以监控 Zabbix 的内部进程。换句话说，可以监控  Zabbix server 或者 Zabbix proxy 的运行情况。  被计算的内部检查:  -   在 Zabbix server 上 - 主机是否被服务端监控 -   在 Zabbix proxy 上 - 主机是否被代理端监控  内部检查在 server或者proxy上执行，无论主机是否处于维护状态。  要使用这个监控项，请选择 **Zabbix internal**  监控项类型。  ::: notetip 内部检查是由 Zabbix 轮询进程（poller）处理。 :::

en-us	#### Overview  In the action log widget, you can display details of action operations (notifications, remote commands). It replicates information from *Administration → Audit*.
zh-cn	#### 概述  在动作记录组件，你可以显示动作操作（提示，远程命令）的细节。它复制了*管理 → 审计*的信息。

en-us	#### Overview  In the *Administration → Media types* section users can configure and maintain media type information.  Media type information contains general instructions for using a medium as delivery channel for notifications. Specific details, such as the individual e-mail addresses to send a notification to are kept with individual users.  A listing of existing media types with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/media_types.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the media type. Clicking on the name opens the media type [configuration form](/manual/config/notifications/media/email#configuration).| |*Type*|Type of the media (e-mail, SMS, etc) is displayed.| |*Status*|Media type status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.| |*Used in actions*|All actions where the media type is used directly (selected in the *Send only to* dropdown) are displayed. Clicking on the action name opens the action configuration form.| |*Details*|Detailed information of the media type is displayed.| |*Actions*|The following action is available:<br>**Test** - click to open a testing form where you can enter media type parameters (e.g. a recipient address with test subject and body) and send a test message to verify that the configured media type works. See also: [Media type testing](/manual/config/notifications/media#media_type_testing).|  To configure a new media type, click on the *Create media type* button in the top right-hand corner.  To import a media type from XML, click on the *Import* button in the top right-hand corner.
zh-cn	#### 概述  在 *管理 → 媒介类型* 部分，用户可以配置和维护媒介类型信息。  媒介类型信息包含使用媒介作为通知传递渠道的一般说明。具体细节，例如发送通知的个人电子邮件地址，由个人用户保存。  显示现有媒介类型及其详细信息的列表。  ![](../../../../../assets/en/manual/web_interface/media_types.png){width="600"}  显示数据：  |栏目|说明| |--------|------------| |*名称*|媒介类型的名称。点击名称打开媒介类型[配置表单](/manual/config/notifications/media/email#configuration)。| |*Type*|显示媒介的类型（电子邮件、SMS 等）。| |*Status*|显示媒介类型状态 - *启用* 或 *停用*。<br>单击状态可以更改它。| |*在操作中使用*|直接使用媒介类型的所有操作（在 *Send only to* 下拉列表中选择）都会显示。单击动作名称打开动作配置表单。| |*详细信息*|显示媒介类型的详细信息。| |*Actions*|以下操作可用：<br>**Test** - 点击打开一个测试表格，您可以在其中输入媒介类型参数（例如，带有测试主题和正文的收件人地址）并将测试消息发送到验证配置的媒介类型是否有效。另请参阅：[媒介类型测试](/manual/config/notifications/media#media_type_testing)。|  要配置新的媒介类型，请单击右上角的*创建媒介类型*按钮。  要从 XML 导入媒体类型，请单击右上角的 *导入* 按钮。

en-us	#### Overview  In the *Administration → Proxies* section proxies for [distributed monitoring](/manual/distributed_monitoring) can be configured in the Zabbix frontend.
zh-cn	#### 概述  在 *管理→ Proxies* 部分代理 [分布式监控](/manual/distributed_monitoring) 可以在 Zabbix 前端配置。

en-us	#### Overview  In the *Administration → Queue* section items that are waiting to be updated are displayed.  Ideally, when you open this section it should all be "green" meaning no items in the queue. If all items are updated without delay, there are none waiting. However, due to lacking server performance, connection problems or problems with agents, some items may get delayed and the information is displayed in this section. For more details, see the [Queue](/manual/config/items/queue) section.  ::: noteclassic Queue is available only if Zabbix server is running. :::  The *Administration → Queue* section contains the following pages:  -   Queue overview — displays queue by item type; -   Queue overview by proxy — displays queue by proxy; -   Queue details — displays a list of delayed items.  The list of available pages appears upon pressing on *Queue* in the *Administration* menu section. It is also possible to switch between pages by using a title dropdown in the top left corner.  |   |   | |---|---| |![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/queue_menu.png){width="300"}|![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/queue_selector.png){width="300"}| |Third-level menu.|Title dropdown.|
zh-cn	#### 概述  在 *管理 → 队列* 菜单下显示等待更新的项目。  理想情况下，当您打开此部分时，它应该全部为“绿色”，表示队列中没有项目。如果所有项目都立即更新，则没有等待。但是，由于服务器性能不足、连接问题或agent问题，某些项目可能会延迟，信息会显示在此部分中。有关详细信息，请参阅 [队列](/manual/config/items/queue) 部分。  ::: noteclassic 队列仅在 Zabbix server 运行时可用 :::  *管理 → 队列* 部分包含以下页面：  - 队列概览——按项目类型显示队列； - proxy队列概览——显示proxy队列； - 队列详细信息——显示延迟项目列表。  按下 *管理* 菜单部分中的 *队列* 后，可用页面列表出现。也可以使用左上角的标题下拉菜单在页面之间切换。  | · | · | |---|---| |![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/queue_menu.png){width="300"}|![](../../../../../assets/en/manual/web_interface/frontend_sections/administration/queue_selector.png){width="300"}| |三级菜单。|标题下拉菜单。|

en-us	#### Overview  In the *Administration → Scripts* section user-defined global scripts can be configured and maintained.  Global scripts, depending on the configured scope and also user permissions, are available for execution:  -   from the [host     menu](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu)     in various frontend locations (*Dashboard*, *Problems*, *Latest     data*, *Maps*, etc) -   from the [event     menu](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) -   can be run as an action operation  The scripts are executed on Zabbix agent, Zabbix server (proxy) or Zabbix server only. See also [Command execution](/manual/appendix/command_execution).  Both on Zabbix agent and Zabbix proxy remote scripts are disabled by default. They can be enabled by:  -   adding the `AllowKey=system.run[*]` parameter in agent     configuration; -   setting the EnableRemoteCommands parameter to '1' in proxy     configuration  A listing of existing scripts with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/scripts.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the script. Clicking on the script name opens the script [configuration form](scripts#configuring_a_global_script).| |*Scope*|Scope of the script - action operation, manual host action or manual event action. This setting determines where the script is available.| |*Used in actions*|Actions where the script is used are displayed.| |*Type*|Script type is displayed - *Webhook*, *Script*, *SSH*, *Telnet* or *IPMI* command.| |*Execute on*|It is displayed whether the script will be executed on Zabbix agent, Zabbix server (proxy) or Zabbix server only.| |*Commands*|All commands to be executed within the script are displayed.| |*User group*|The user group that the script is available to is displayed (or *All* for all user groups).| |*Host group*|The host group that the script is available for is displayed (or *All* for all host groups).| |*Host access*|The permission level for the host group is displayed - *Read* or *Write*. Only users with the required permission level will have access to executing the script.|  To configure a new script, click on the *Create script* button in the top right-hand corner.
zh-cn	#### 概述  在 *管理 → 脚本* 部分，可以配置和维护用户定义的全局脚本。  全局脚本，取决于配置的范围和用户权限，可用于执行：  - 从[主机菜单](/manual/web_interface/frontend_sections/monitoring/dashboard#host_menu) 中的各个前端位置（*仪表板*、*问题*、*最新数据*、*拓扑图*等） - 从[事件菜单](/manual/web_interface/frontend_sections/monitoring/problems#event_menu) - 可以作为动作操作运行  脚本仅在 Zabbix agent、Zabbix  server（proxy）或 Zabbix server上执行。另请参见 [命令执行](/manual/appendix/command_execution)。  默认情况下，Zabbix agent和 Zabbix proxy远程脚本都被禁用。它们可以通过以下方式启用：  - 在agent配置中添加 `AllowKey=system.run[*]` 参数； - 在proxy配置中将 EnableRemoteCommands 参数设置为“1”  将显示现有脚本及其详细信息的列表。  ![](../../../../../assets/en/manual/web_interface/scripts.png){width="600"}  显示数据：  |栏目|说明| |--------|------------| |*名称*|脚本的名称。单击脚本名称打开脚本[配置表单](scripts#configuring_a_global_script)。| |*范围*|脚本的范围 - 动作操作、手动主机动作或手动事件动作。此设置确定脚本可用的位置。| |*用于动作*|显示使用脚本的动作。| |*类型*|显示脚本类型 - *Webhook*、*Script*、*SSH*、*Telnet* 或 *IPMI* 命令。| |*执行在*|显示脚本是在Zabbix agent、Zabbix server（proxy）还是仅在Zabbix server上执行。| |*命令*|显示脚本中要执行的所有命令。| |*用户组*|显示脚本可用的用户组（或 *全部* 所有用户组）。| |*主机组*|显示脚本可用的主机组（或 *全部* 用于所有主机组）。| |*主机访问*|显示主机组的权限级别 - *读* 或 *写*。只有具有所需权限级别的用户才能执行脚本。|  要配置新脚本，请单击右上角的 *创建脚本* 按钮。

en-us	#### Overview  In the *Administration → User groups* section user groups of the system are maintained.
zh-cn	#### 概述 在 *管理 → 用户组* 菜单下维护系统的用户组。

en-us	#### Overview  In the *Administration → User roles* section roles that can be assigned to system users and specific permissions for each role are maintained.
zh-cn	#### 概述  在 *管理→ 用户角色* 部分中，可以分配给系统用户的角色和每个角色的特定权限得到维护。

en-us	#### Overview  In the *Administration → Users* section users of the system are maintained.
zh-cn	#### 概述  在 *管理 → 用户* 菜单下维护系统的用户。

en-us	#### Overview  In the classic graph widget, you can display a single custom graph or simple graph.
zh-cn	#### 概述  在经典图表组件中，你可以显示一个单一的自定义图表或简单图表。

en-us	 #### Overview  In the clock widget, you may display local, server, or specified host time.
zh-cn	#### 概述  在时钟组件，你可以显示本地、服务器、或特定的主机时钟。

en-us	#### Overview  In the *Configuration → Actions* section users can configure and maintain actions.  The actions displayed are actions assigned to the selected event source (trigger, service, discovery, autoregistration, internal actions).  Actions are grouped into subsections by event source (trigger, service, discovery, autoregistration, internal actions). The list of available subsections appears upon pressing on *Actions* in the *Configuration* menu section. It is also possible to switch between subsections by using a title dropdown in the top left corner.  |   |   | |---|---| |![](../../../../../assets/en/manual/web_interface/actions_menu.png){width="300"}|![](../../../../../assets/en/manual/web_interface/actions_selector.png){width="300"}| |Third-level menu.|Title dropdown.|  After selecting a subsection, a page with a list of existing actions with their details will be displayed.  For users without Super admin rights actions are displayed according to permission settings. That means in some cases a user without Super admin rights isn’t able to view the complete action list because of certain permission restrictions. An action is displayed to the user without Super admin rights if the following conditions are fulfilled:  -   The user has read-write access to host groups, hosts, templates, and     triggers in action conditions -   The user has read-write access to host groups, hosts, and templates     in action operations, recovery operations, and update operations -   The user has read access to user groups and users in action     operations, recovery operations, and update operations      :::noteclassic Actions for services are maintained in a similar way in the *Services->Service actions* menu section. User's access to specific service actions depends on the user role permissions set in the *Access to services* menu section. :::   ![](../../../../../assets/en/manual/web_interface/actions.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the action. Clicking on the action name opens the action [configuration form](/manual/config/notifications/action#configuring_an_action).| |*Conditions*|Action conditions are displayed.| |*[Operations](/manual/config/notifications/action/operation#configuring_an_operation)*|Action operations are displayed.<br>Since Zabbix 2.2, the operation list also displays the media type (e-mail, SMS or script) used for notification as well as the name and surname (in parentheses after the username) of a notification recipient.<br>Action operation can both be a [notification](/manual/config/notifications/action/operation/message) or a [remote command](/manual/config/notifications/action/operation/remote_command) depending on the selected type of operation.| |*Status*|Action status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.<br>See the [Escalations](/manual/config/notifications/action/escalations) section for more details as to what happens if an action is disabled during an escalation in progress.|  To configure a new action, click on the *Create action* button in the top right-hand corner.
zh-cn	#### 概述  在*配置→动作*部分，用户可以配置和维护动作。  显示的动作是分配给所选事件源的动作(触发器、服务、发现、自动注册、内部动作)。  动作按事件源(触发器、服务、发现、自动注册、内部动作)分组。可用子节的列表出现在按下*动作*在*配置*菜单部分。它也可以通过使用在左上角的标题下拉菜单在子部分之间切换。  |   |   | |---|---| |![](../../../../../assets/en/manual/web_interface/actions_menu.png){width="300"}|![](../../../../../assets/en/manual/web_interface/actions_selector.png){width="300"}| |Third-level menu.|Title dropdown.|  选择一个小节后，将显示一个包含现有动作及其详细信息列表的页面。  对于没有“超级管理员”权限的用户，根据权限设置显示动作。这意味着在某些情况下，由于某些权限限制，没有超级管理员权限的用户无法查看完整的动作列表。对于没有“超级管理员”权限的用户，当满足以下条件时，将显示动作:  —对主机组、主机、模板和运行条件中的触发器具有读写权限 —对动作、恢复动作、更新动作中的主机组、主机、模板具有读写权限 —用户对动作、恢复动作、更新动作中的用户组和用户具有读权限  :::noteclassic 在 *Services->Service actions* 菜单部分中，以类似的方式维护服务的操作。 用户对特定服务操作的访问取决于“*访问服务*”菜单部分中设置的用户角色权限。 :::  ![](../../../../../assets/en/manual/web_interface/actions.png){width="600"}  显示数据：  |列|描述| |------|-----------| |*名称*|动作名称。单击动作名称打开动作[配置表单](/manual/config/notifications/action#configuring_an_action).| |*条件*|显示动作条件| |*[动作](/manual/config/notifications/action/operation#configuring_an_operation)*|显示操作。<br>从Zabbix 2.2开始，操作列表还显示了用于通知的媒体类型(电子邮件、SMS或脚本)，以及通知接收者的姓名和姓氏(在用户名后面的括号中)。<br>根据动作类型不同，动作操作可以是[通知](/manual/config/notifications/ Action /operation/message)或[远程指令](/manual/config/notifications/ Action /operation/remote_command) |*状态*|操作状态- *启用*或*禁用*。<br>通过单击状态，您可以更改它。<br>请参阅[升级](/manual/config/notifications/action/ Escalations)小节了解更多关于在升级过程中禁用动作会发生什么情况  要配置一个新动作，请单击右上角的*新建动作*按钮。

en-us	#### Overview  In the *Configuration → Discovery* section users can configure and maintain discovery rules.  A listing of existing discovery rules with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/discovery_rules0.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the discovery rule. Clicking on the discovery rule name opens the discovery rule [configuration form](/manual/discovery/network_discovery/rule).| |*IP range*|The range of IP addresses to use for network scanning is displayed.| |*Proxy*|The proxy name is displayed, if discovery is performed by the proxy.| |*Interval*|The frequency of performing discovery displayed.| |*Checks*|The types of checks used for discovery are displayed.| |*Status*|Action status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.|  To configure a new discovery rule, click on the *Create discovery rule* button in the top right-hand corner.
zh-cn	#### 概述  在“*配置→发现*”区域，用户可以对自动发现规则进行配置和维护。  将显示现有自动发现规则的列表及其详细信息。  ![](../../../../../assets/en/manual/web_interface/discovery_rules0.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名称*|自私发现规则的名称。单击自动发现规则名称将打开自动发现规则[配置表单](/manual/discovery/network_discovery/rule).| |*IP地址范围*|显示网络扫描使用的IP地址范围| |*代理*|如果是代理执行自动发现，则显示代理名称 |*时间间隔*|自动发现频率 |*检查*|显示发现时使用的检查类型 |*状态*|操作状态- *启用*或*禁用*。<br>通过单击状态可以更改  单击右上角的“*创建自动发现规则*”按钮，可以配置新的自动发现规则。

en-us	#### Overview  In the *Configuration → Event correlation* section users can configure and maintain global correlation rules for Zabbix events.  ![](../../../../../assets/en/manual/web_interface/correlation_rules1.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the correlation rule. Clicking on the correlation rule name opens the rule [configuration form](/manual/config/event_correlation/global#configuration).| |*Conditions*|Correlation rule conditions are displayed.| |*Operations*|Correlation rule operations are displayed.| |*Status*|Correlation rule status is displayed - *Enabled* or *Disabled*.<br>By clicking on the status you can change it.|  To configure a new correlation rule, click on the *Create correlation* button in the top right-hand corner.
zh-cn	#### 概述  在“*配置→事件关联*”区域，用户可以配置和维护Zabbix事件的全局关联规则。 ![](../../../../../assets/en/manual/web_interface/correlation_rules1.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名称*|关联规则名称。单击相关规则名称将打开规则[配置表单](/manual/config/event_correlation/global#configuration) |*条件*|显示关联规则条件 |*操作*|显示关联规则操作 |*状态*|显示相关规则状态- *启用*或*禁用*。<br>通过单击状态可以更改  要配置新的关联规则，请单击右上角的“*创建关联*”按钮。

en-us	#### Overview  In the *Configuration → Host groups* section users can configure and maintain host groups. A host group can contain both templates and hosts.  A listing of existing host groups with their details is displayed. You can search and filter host groups by name.  ![](../../../../../assets/en/manual/web_interface/host_groups1.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the host group. Clicking on the group name opens the host group [configuration form](/manual/config/hosts/host#configuring_a_host_group).| |*Hosts*|Number of hosts in the group (displayed in gray). Clicking on "Hosts" will, in the whole listing of hosts, filter out those that belong to the group.| |*Templates*|Number of templates in the group (displayed in gray). Clicking on "Templates" will, in the whole listing of templates, filter out those that belong to the group.| |*Members*|Names of group members. Template names are displayed in gray, monitored host names in blue and non-monitored host names in red. Clicking on a name will open the template/host configuration form.| |*Info*|Error information (if any) regarding the host group is displayed.|
zh-cn	#### 概述  在*配置→主机组*部分中，用户可以配置和维护主机组。主机组可以既包含模板，也包含主机。  列表将显示现有主机组及其详细信息。您可以按名称搜索和过滤主机组。  ![](../../../../../assets/en/manual/web_interface/host_groups1.png){width="600"}  数据展示：  |列名|描述| |----|----| |*名称*|主机组的名字。点击主机组名称打开主机组[配置表](/manual/config/hosts/host#configuring_a_host_group).| |*主机*|主机组中的主机个数 (为灰色)。单击“主机”将呈现属于该组的主机列表。| |*模板*|主机组中的模板个数 (为灰色)。单击“模板”将呈现属于该组的模板列表。| |*成员*|组成员的名字。模板名称为灰色，已监控的主机名显示为蓝色，未监控状态的主机名显示为红色。 单击可显示template/host 配置表。| |*信息*|有关主机组的错误信息（如果有错误信息的话）|

en-us	#### Overview  In the *Configuration → Hosts* section users can configure and maintain hosts.  A listing of existing hosts with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/hosts.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the host. Clicking on the host name opens the host [configuration form](/manual/config/hosts/host#configuring_a_host).| |*Entities (Items, Triggers, Graphs, Discovery, Web)*|Clicking on the entity name will display items, triggers etc. of the host. The number of the respective entities is displayed in gray.| |*Interface*|The main interface of the host is displayed.| |*Proxy*|Proxy name is displayed, if the host is monitored by a proxy.<br>This column is only displayed if the *Monitored by* filter option is set to 'Any' or 'Proxy'.| |*Templates*|The templates linked to the host are displayed. If other templates are contained in the linked template, those are displayed in parentheses, separated by a comma. Clicking on a template name will open its configuration form.| |*Status*|Host status is displayed - *Enabled* or *Disabled*. By clicking on the status you can change it.<br>An orange wrench icon ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png) before the host status indicates that this host is in maintenance. Maintenance details are displayed when the mouse pointer is positioned over the icon.| |*Availability*|Host [availability](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability) per configured interface is displayed.<br>Icons represent only those interface types (Zabbix agent, SNMP, IPMI, JMX) that are configured. If you position the mouse on the icon, a popup list of all interfaces of this type appears with each interface details, status and errors.<br>The column is empty for hosts with no interfaces.<br>The current status of all interfaces of one type is displayed by the respective icon color:<br>**Green** - all interfaces available<br>**Yellow** - at least one interface available and at least one unavailable; others can have any value including 'unknown'<br>**Red** - no interfaces available<br>**Gray** - at least one interface unknown (none unavailable)<br>Note that active Zabbix agent items do not affect host availability.| |*Agent encryption*|Encryption status for connections to the host is displayed:<br>**None** - no encryption<br>**PSK** - using pre-shared key<br>**Cert** - using certificate<br>| |*Info*|Error information (if any) regarding the host is displayed.| |*Tags*|[Tags](/manual/config/tagging) of the host, with macros unresolved.|  To configure a new host, click on the *Create host* button in the top right-hand corner. To import a host from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner.
zh-cn	#### 概览  在“*配置→主机*”区域，用户可以对主机进行配置和维护。  显示现有主机的列表及其详细信息。 ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/hosts.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*Name*|主机名。单击主机名打开主机[配置表单](/manual/config/hosts/host#configuring_a_host).| |*实体(监控项, 触发器, 图形, 自动发现, Web)*|点击实体名称会显示主机的项目、触发器等。对应的实体数以灰色显示| |*接口*|显示主机主接口 |*代理*|如果主机通过代理监控，则显示“代理名称”。<br>仅当*监控途径* 过滤器“任意”或“代理”时，显示此字段| |*模板*|显示主机链接的模板。如果链接模板中包含其他模板，则将它们显示在圆括号中，中间用逗号分隔。单击模板名称将打开它的配置表单。| |*状态*|主机状态显示为- *启用*或*禁用*。通过单击状态，您可以更改它。<br>橙色扳手图标![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png) 在主机状态表明该主机处于维护状态之前。当鼠标停留在图标上时，显示维护详情| |*可用性*|主机 [可用性](/manual/web_interface/frontend_sections/configuration/hosts#reading_host_availability) 每个配置的接口。<br>图标仅代表已配置的接口类型(Zabbix agent、SNMP、IPMI、JMX)。如果你把鼠标放在图标上，就会弹出一个包含所有此类界面的列表，其中包含每个界面的详细信息、状态和错误。<br>对于没有接口的主机，该列为空。<br>以图标颜色表示当前所有接口的状态:<br>**绿色**-所有接口可用<br>**黄色** -至少一个接口可用，至少一个接口不可用;其他值可以是任意值，包括'unknown'<br>**红色** -没有可用的接口<br>**灰色**-至少有一个未知的接口(无不可用)<br>注意活动的Zabbix代理项不影响主机可用性| |*Agent加密*|主机连接的加密状态:<br>**无** -不加密<br>**PSK** -使用预共享密钥<br>**Cert** -使用证书<br>| |*信息*|显示主机的错误信息 | |*标签*|[标签](/manual/config/tagging)主机，未解析宏|  要配置新主机，请单击右上角的*新建主机*按钮。要从YAML、XML或JSON文件导入主机，请单击右上角的* import *按钮。

en-us	#### Overview  In the *Configuration → Maintenance* section users can configure and maintain maintenance periods for hosts.  A listing of existing maintenance periods with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/maintenance_periods1.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the maintenance period. Clicking on the maintenance period name opens the maintenance period [configuration form](/manual/maintenance#configuration).| |*Type*|The type of maintenance is displayed: *With data collection* or *No data collection*| |*Active since*|The date and time when executing maintenance periods becomes active.<br>Note: This time does not activate a maintenance period; maintenance periods need to be set separately.| |*Active till*|The date and time when executing maintenance periods stops being active.| |*State*|The state of the maintenance period:<br>**Approaching** - will become active soon<br>**Active** - is active<br>**Expired** - is not active any more| |*Description*|Description of the maintenance period is displayed.|  To configure a new maintenance period, click on the *Create maintenance period* button in the top right-hand corner.
zh-cn	#### 概述  用户可以在“*配置→维护*”中配置和维护主机的维护期。  将显示现有维护周期的列表及其详细信息。  ![](../../../../../assets/en/manual/web_interface/maintenance_periods1.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名称*|维护期名称。点击维护期名称，打开维护期[配置表](/manual/maintenance#configuration).| |*类型*|维护类型:*有数据收集*或*无数据收集*| |*开始时间*|执行维护周期的日期和时间变为活跃。<br>注:这次不激活维护周期;维护周期需要单独设置 |*活动到*|维护周期停止活动的日期和时间 |*状态*|维护期的状态:<br>**接近** -将很快变为活跃状态<br>**活跃** -已激活<br>**过期** -不再活跃| |*描述*|显示维护期的描述信息|  单击右上角的“*创建维护周期*”按钮，可以配置新的维护期。

en-us	#### Overview  In the *Configuration → Templates* section users can configure and maintain templates.  A listing of existing templates with their details is displayed.  ![](../../../../../assets/en/manual/web_interface/templates.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the template. Clicking on the template name opens the template [configuration form](/manual/config/templates/template#creating_a_template).| |*Hosts*|Number of editable hosts to which the template is linked; read-only hosts are not included.<br>Clicking on *Hosts* will open the host list with only those hosts filtered that are linked to the template.| |*Entities (Items, Triggers, Graphs, Dashboards, Discovery, Web)*|Number of the respective entities in the template (displayed in gray). Clicking on the entity name will, in the whole listing of that entity, filter out those that belong to the template.| |*Linked templates*|Templates that are linked to the template, in a nested setup where the template will inherit all entities of the linked templates.| |*Linked to templates*|The templates that the template is linked to ("children" templates that inherit all entities from this template).<br>Since Zabbix 5.0.3, this column no longer includes hosts.| |*Tags*|[Tags](/manual/config/tagging) of the template, with macros unresolved.|  To configure a new template, click on the *Create template* button in the top right-hand corner. To import a template from a YAML, XML, or JSON file, click on the *Import* button in the top right-hand corner.
zh-cn	#### 概述  在*配置 → 模板*部分，用户可以配置和维护模板。  显示现有模板及其详细信息的列表如下：  ![](../../../../../assets/en/manual/web_interface/templates.png){width="600"}  从标题栏中的右侧的下拉列表中，您可以选择是显示所有模板还是仅显示属于组的模板。 您也可以按名称搜索和过滤模板。  显示数据：  |列|描述| |---|---| |*名称*|模板名称，单击模板名称打开模板[配置表](/manual/config/templates/template#creating_a_template).| |*主机*|模板连接的可编辑的主机；不包括只读的主机。<br>点击“主机”会打开和当前模板相关联的主机列表。| |*实体（监控项，触发器，图标，仪表盘，Web）*|模板中实体的数量（以灰色显示）。 在该实体的整个列表中，单击实体名将过滤掉属于该模板的实体。| |*链接的模板*      |链接到当前模板的模板，在嵌套设置中，模板将继承所链接的模板的所有实体。| |*链接到* 模板|链接到的模板。继承了该模板所有试题的子模板<br>从Zabbix 5.0.3版本开始，这一列不在包括主机| |*标签*|模板的[标签](/manual/config/tagging) ，不支持宏解析|  点击右上角*创建模板* 按钮，即可配置一个新的模板。点击右上角*导入*按钮，即可从YAML，XML，或者JSON 文件导入模板。

en-us	#### Overview  In the data overview widget, you can display the latest data for a group of hosts.  The color of problem items is based on the problem severity color, which can be adjusted in the [problem update](/manual/acknowledges#updating_problems) screen.  By default, only values that fall within the last 24 hours are displayed. This limit has been introduced with the aim of improving initial loading times for large pages of latest data. This limit is configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max history display period* option.  Clicking on a piece of data offers links to some predefined graphs or latest values.  Note that 50 records are displayed by default (configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max number of columns and rows in overview tables* option). If more records exist than are configured to display, a message is displayed at the bottom of the table, asking to provide more specific filtering criteria. There is no pagination.
zh-cn	#### 概述  在数据概览组件，您可以显示一组主机的最新数据。  问题监控项的颜色是基于问题严重程度的，可在[问题更新](/manual/acknowledges#updating_problems)页面调整。  默认只会显示24小时内的值。此限制是为了减少大量载入最新数据的初始化时间 而推行的。此限制通过*管理* → *常用* → *[界面设置](/manual/web_interface/frontend_sections/administration/general#gui)* 中的*历史最长显示时间*选项进行配置。  点击一条数据可链接到预定义的图表或最新值。  请注意默认显示50条记录（在*管理* → *常用* → *[界面设置](/manual/web_interface/frontend_sections/administration/general#gui)* 中配置），使用*表格位中最多可展示的的组件数量*选项。 如果存在比配置的条数更多的记录，表格下放会显示一条消息，请求提供更具体的 过滤条件。不会进行分页。

en-us	#### Overview  In the graph prototype widget, you can display a grid of graphs created from either a graph prototype or an item prototype by low-level discovery.
zh-cn	#### 概述  在图形原型组件中，你可以显示一个由图形原型或监控项原型通过自动发现创建的图形网格。

en-us	 #### Overview  In the host availability widget, high-level statistics about host availability are displayed in four colored columns/lines.  |   |   | |---|---| |![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/availability_h.png)|Horizontal display (columns).| |![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/availability_v.png)|Vertical display (lines).|  Host availability in each column/line is counted as follows:  -   *Available* - hosts with all interfaces available -   *Not available* - hosts with at least one interface unavailable -   *Unknown* - hosts with at least one interface unknown (none     unavailable) -   *Total* - total of all hosts
zh-cn	 #### 概述  在主机可用性组件中，关于主机可用性的高级统计数据显示在四个彩色的列/线中。  | | | |---|---| |![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/availability_h.png)|水平显示（列）| |![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/availability_v.png)|垂直显示（行）|  每一列/行中的主机可用性的计算方法如下：  - *可用* - 所有接口都可用的主机 - *不可用* - 至少有一个接口不可用的主机 - *未知* - 至少有一个接口未知的主机（没有任何接口属于不可用状态） - *总数* - 所有主机的总数

en-us	#### Overview  In the *Inventory → Hosts* section [inventory data](/manual/config/hosts/inventory) of hosts are displayed.  You can filter the hosts by host group(s) and by any inventory field to display only the hosts you are interested in.  ![](../../../../../assets/en/manual/web_interface/inventory_filtered.png){width="600"}  To display all host inventories, select no host group in the filter, clear the comparison field in the filter and press "Filter".  While only some key inventory fields are displayed in the table, you can also view all available inventory information for that host. To do that, click on the host name in the first column.
zh-cn	#### 概览  在 *资产记录→ 主机* 将显示主机的 [资产记录信息](/manual/config/hosts/inventory) 。  您可以按主机组和任何资产字段过滤主机，来显示您感兴趣的主机。  ![](../../../../../assets/en/manual/web_interface/inventory_filtered.png){width="600"}  要显示所有主机清单，在组下拉列表中不选择任何主机组，清除过滤器中的比较字段，然后按“过滤器”。  虽然表中只显示了一些关键的资产记录字段，但您也可以查看该主机的所有可用资产信息。如果想这么查看请单击列表中第一列主机名。

en-us	#### Overview  In the *Monitoring → Discovery* section results of [network discovery](/manual/discovery/network_discovery) are shown. Discovered devices are sorted by the discovery rule.  ![](../../../../../assets/en/manual/web_interface/discovery_status0.png){width="600"}  If a device is already monitored, the host name will be listed in the *Monitored host* column, and the duration of the device being discovered or lost after previous discovery is shown in the *Uptime/Downtime* column.  After that follow the columns showing the state of individual services for each discovered device (red cells show services that are down). Service uptime or downtime is included within the cell.  ::: noteimportant Only those services that have been found on at least one device will have a column showing their state. :::
zh-cn	#### 概览  在 *监控→ 自动发现* 这部分，显示[网络发现](/manual/discovery/network_discovery) 的结果。发现的设备按发现规则排序。 ![](../../../../../assets/en/manual/web_interface/discovery_status0.png){width="600"}  如果设备已被监控，主机名将列在 *监控的主机*  列中，以及在_正常运行/停机时间_列中显示发现设备的 *持续时间/发现后的丢失时间*。  之后，请按照列显示每个发现的设备的各个服务的状态(红色单元格显示已关闭的服务)。服务正常运行时间或停机时间都包含在单元中。  ::: noteimportant 这些服务中至少有一个在设备中被发现，才会有显示其状态的列。 :::

en-us	#### Overview  In the *Monitoring → Maps* section you can configure, manage and view [network maps](/manual/config/visualization/maps).  When you open this section, you will either see the last map you accessed or a listing of all maps you have access to.  All maps can be either public or private. Public maps are available to all users, while private maps are accessible only to their owner and the users the map is shared with.
zh-cn	#### 概览  在 监测→ 拓扑图 部分，您可以配置，管理和查看[网络拓扑图](/manual/config/visualization/maps)。  当您打开此部分时，您将看到您访问的最后一张拓扑图或您可以访问的所有拓扑图的列表。 拓扑图列表可以按名称过滤。  所有拓扑图都可以是公共的或私有的。 所有用户都可以使用公共拓扑图，而私有拓扑图只能由其所有者和对其共享的用户访问。

en-us	#### Overview  In the plain text widget, you can display the latest item data in plain text.
zh-cn	#### 概述  在纯文本组件中，显示最新的纯文本监控项数据。

en-us	#### Overview  In the problem host widget, you can display high-level information about host availability.
zh-cn	#### 概述  在问题主机组件中，可以显示关于主机可用性的高级信息。

en-us	#### Overview  In the Reports → Action log section users can view details of operations (notifications, remote commands) executed within an action.  ![](../../../../../assets/en/manual/web_interface/action_log2.png){width="600"}  Displayed data:  |Column|Description| |--|--------| |*Time*|Timestamp of the operation.| |*Action*|Name of the action causing operations is displayed.| |*Type*|Operation type is displayed - *Email* or *Command*.| |*Recipient(s)*|Username, name, surname (in parentheses) and e-mail address of the notification recipient is displayed.| |*Message*|The content of the message/remote command is displayed.<br>A remote command is separated from the target host with a colon symbol: `<host>:<command>`. If the remote command is executed on Zabbix server, then the information has the following format: `Zabbix server:<command>`| |*Status*|Operation status is displayed:<br>*In progress* - action is in progress<br>For actions in progress the number of retries left is displayed - the remaining number of times the server will try to send the notification.<br>*Sent* - notification has been sent<br>*Executed* - command has been executed<br>*Not sent* - action has not been completed.| |*Info*|Error information (if any) regarding the action execution is displayed.|  **Using filter**  You may use the filter to narrow down the records by the message recipient(s). For better search performance, data is searched with macros unresolved.  The filter is located below the *Action log* bar. It can be opened and collapsed by clicking on the *Filter* tab on the left.  **Time period selector**  The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter.
zh-cn	#### 概览  在*报表 → 动作日志*部分，用户可以查看动作中执行的操作（通知、远程命令）的详细信息。  ![](../../../../../assets/en/manual/web_interface/action_log2.png){width="600"}  显示数据：  |列|描述| |------|-----------| |*时间*|操作的时间戳。| |*动作*|显示导致操作的动作名称。| |*类型*|显示的操作类型 - *邮件* 或 *命令*。| |*收件人*|显示通知收件人的用户名、姓名、姓氏（括号中）和电子邮件地址。| |*消息*|显示消息/远程命令的内容。<br>远程命令与目标主机之间用冒号分隔：`<主机>:<命令>`。如果在Zabbix服务器上执行远程命令，则信息具有如下格式：`Zabbix 服务器:<命令>`。| |*状态*|显示操作状态：<br>*进行中* - 动作在进行中<br>对于正在进行的动作，显示剩余的重试次数 - 服务器将尝试发送通知的剩余次数。<br>*已发送* - 通知已经发送<br>*已执行* - 命令已经执行<br>*未发送* - 动作尚未完成。| |*信息*|显示关于动作执行的错误信息（如果有）。|  **使用过虑器**  您可以使用过滤器按消息收件人缩小记录范围。为了获得更好的搜索性能，使用未解析的宏搜索数据。  过滤器位于*动作日志*栏下方。通过点击左侧的*过滤器*选项卡，可以将其打开和折叠。  **时间段选择器**  [时间段选择器](/manual/config/visualization/graphs/simple#时间段选择器)允许通过单击鼠标选择经常需要的周期。通过单击过滤器旁边的时间段选项卡，可以打开时间段选择器。

en-us	#### Overview  In the *Reports → Notifications* section a report on the number of notifications sent to each user is displayed.  From the dropdowns in the top right-hand corner you can choose the media type (or all), period (data for each day/week/month/year) and year for the notifications sent.  ![](../../../../../assets/en/manual/web_interface/frontend_sections/reports/notifications.png){width="600"}  Each column displays totals per one system user.
zh-cn	 #### 概览  在*报表 → 通知*部分，将显示发送给每个用户的通知数量的报告。  从右上角的下拉列表中，您可以选择发送通知的媒体类型（或全部）、周期（每天/周/月/年的数据）和年份。  ![](../../../../../assets/en/manual/web_interface/frontend_sections/reports/notifications.png){width="600"}  每列显示每个系统用户的总数。

en-us	### Overview  In the *Services → Service actions* section users can [configure](/manual/config/notifications/action) and maintain service actions.  Configured actions are displayed in the list with respect to the [user role permissions](/manual/web_interface/frontend_sections/administration/user_roles). Users will only see actions for services their user role grants access to.   Displayed data, filter and available mass editing options are the same as for other types of [actions](/manual/web_interface/frontend_sections/configuration/actions).
zh-cn	### 概述 在*Services → Service actions*中，用户可以[配置](/manual/config/notifications/action) 和维护服务。  配置的操作将显示在 [用户与权限](/manual/web_interface/frontend_sections/administration/user_roles) 相关的列表中。用户只能看到授予访问权限的服务的操作.   显示的数据，过滤器和可用的批量编辑选项与其他类型的 [动作](/manual/web_interface/frontend_sections/configuration/actions).

en-us	#### Overview  In the trigger overview widget, you can display the trigger states for a group of hosts.  -   The trigger states are displayed as colored blocks (the color of     problem triggers depends on the problem severity color, which can be     adjusted in the [problem     update](/manual/acknowledges#updating_problems) screen). Note that     recent trigger changes (within the last 2 minutes) will be displayed     as blinking blocks. -   Blue up and down arrows indicate triggers that have dependencies. On     mouseover, dependency details are revealed. -   A checkbox icon indicates acknowledged problems. All problems or     resolved problems of the trigger must be acknowledged for this icon     to be displayed.  Clicking on a trigger block provides context-dependent links to problem events of the trigger, the problem acknowledgment screen, trigger configuration, trigger URL or a simple graph/latest values list.  Note that 50 records are displayed by default (configurable in *Administration* → *General* → *[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*, using the *Max number of columns and rows in overview tables* option). If more records exist than are configured to display, a message is displayed at the bottom of the table, asking to provide more specific filtering criteria. There is no pagination. Note that this limit is applied  first, before any further filtering of data, for example, by tags.
zh-cn	#### 概述  在触发器概览组件中，你可以显示一组主机的触发状态。  - 触发器状态显示为彩色块（问题触发器的颜色取决于问题严重程度的颜色，可以通过 [问题更新](/manual/acknowledges#updating_problems) screen)调整）。注意，最近的触发器变化（2分钟内）的彩色块会呈现为闪烁状态。 - 蓝色的向上和向下箭头表示有依赖关系的触发器。鼠标移动时，会显示依赖关系的细节。 - 一个复选框图标表示已确认的问题。触发器的所有问题或已解决的问题必须被确认才能显示该图标。   点击触发器块，可以访问与该触发器的问题事件、问题确认屏幕、触发器配置、触发器URL或简单的图表/最新值列表有关的相关链接。  注意，默认情况下显示50条记录（可在*管理*→*一般*→*[GUI](/manual/web_interface/frontend_sections/administration/general#gui)*中配置，使用*表格的最大列数和行数*选项）。如果存在的记录多于配置显示的记录，则在表的底部显示一条信息，要求提供更具体的过滤标准。不会分页显示。请注意，首先应用此限制，然后再对数据进行任何进一步过滤，例如通过标签。

en-us	#### Overview  In this preprocessing step it is possible to convert CSV file data into JSON format. It's supported in:  -   items (item prototypes) -   low-level discovery rules
zh-cn	#### 概述  在预处理的步骤中，可以将CSV文件数据转换为JSON格式，支持项目如下：  -   监控项 (监控项原型) -   低级别自动发现

en-us	#### Overview  In this section the configured graph prototypes of a low-level discovery rule on the template are  displayed.   If the template is linked to the host, graph prototypes will become the basis of  creating real host [graphs](/manual/web_interface/frontend_sections/configuration/hosts/graphs)  during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/template_graph_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the graph prototype, displayed as a blue link.<br>Clicking on the name opens the graph prototype [configuration form](/manual/discovery/low_level_discovery/graph_prototypes).<br>If the graph prototype belongs to a linked template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph prototype list on the linked template level.| |*Width*|Width of the graph prototype is displayed.| |*Height*|Height of the graph prototype is displayed.| |*Type*|Type of the graph prototype is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Discover*|Discover the graph based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.|  To configure a new graph prototype, click on the *Create graph prototype* button at the top right corner.
zh-cn	#### 概述  在本段中，模板中低级发现规则的配置图形原型展示如下。  如果模板链接到主机，图形原型将成为在低级发现期间创建真实主机[图形](/manual/web_interface/frontend_sections/configuration/hosts/graphs)的基础。  ![](../../../../../../../assets/en/manual/web_interface/template_graph_prototypes.png){width="600"}  展示的数据:  |列|描述| |------|-----------| |*Name*|图形原型的名称，展示位一个蓝色链接。<br>点击名称打开图形原型 [配置格式](/manual/discovery/low_level_discovery/graph_prototypes)。<br>如果图形原型属于一个关联的模板, 模板名称显示在图形名称前面, 为灰色链接。在关联的模板层面点击模板链接将打开图形原型列表.| |*Width*|图形原型的宽度如所示。| |*Height*|图形原型的高度如所示。| |*Type*|图形原型的类型如所示- *Normal*, *Stacked*, *Pie* 或者 *Exploded*.| |*Discover*|基于这个原型发现图形:<br>**Yes** - 发现<br>**No** - 没发现。你可以通过点击'Yes'和'No' 来切换。|  要配置新的图形原型，点击右上角的 *Create graph prototype* 。

en-us	#### Overview  In this section the configured host prototypes of a low-level discovery rule on the template are  displayed.   If the template is linked to the host, host prototypes will become the basis of  creating real [hosts](/manual/web_interface/frontend_sections/configuration/hosts)  during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/template_host_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the host prototype, displayed as a blue link.<br>Clicking on the name opens the host prototype configuration form.<br>If the host prototype belongs to a linked template, the template name is displayed before the host name, as a gray link. Clicking on the template link will open the host prototype list on the linked template level.| |*Templates*|Templates of the host prototype are displayed.| |*Create enabled*|Create the host based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the host based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the host prototype are displayed.|  To configure a new host prototype, click on the *Create host prototype* button at the top right corner.
zh-cn	#### 概述  在本节中，将显示在模板上配置的低级发现规则的主机原型。  如果模板链接到主机，主机原型将成为低级发现时创建真实[主机](/manual/web_interface/frontend_sections/configuration/hosts)的基础。  ![](../../../../../../../assets/en/manual/web_interface/template_host_prototypes.png){width="600"}  显示数据：  |列|描述| |------|-----------| |*Name*|主机原型的名称，显示为蓝色链接。<br>单击名称会打开主机原型配置表单。<br>如果主机原型属于一个关联的模板,模板名称显示在主机名称前面,作为灰色链接。单击模板链接将打开链接模板级别的主机原型列表。| |*Templates*|显示主机原型的模板。| |*Create enabled*|基于此原型创建主机:<br>**Yes** - 启用<br>**No** - 禁用。 你可以通过点击来切换'Yes'和'No'| |*Discover*|基于此原型发现主机:<br>**Yes** - 发现<br>**No** - 没发现. 你可以通过点击来切换'Yes'和'No'| |*Tags*|显示主机原型的标签。|  要创建新的主机原型，点击右上方的 *Create host prototype* 按钮 。

en-us	#### Overview  In this section the configured item prototypes of a low-level discovery rule on the template are  displayed.   If the template is linked to the host, item prototypes will become the basis of  creating real host [items](/manual/web_interface/frontend_sections/configuration/hosts/items)  during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/template_item_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the item prototype, displayed as a blue link.<br>Clicking on the name opens the item prototype [configuration form](/manual/discovery/low_level_discovery/item_prototypes).<br>If the item prototype belongs to a linked template, the template name is displayed before the item name, as a gray link. Clicking on the template link will open the item prototype list on the linked template level.| |*Key*|Key of the item prototype is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days to keep item data history is displayed.| |*Trends*|How many days to keep item trends history is displayed.| |*Type*|Type of the item prototype is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Create enabled*|Create the item based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the item based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the item prototype is displayed.|  To configure a new item prototype, click on the *Create item prototype* button at the top right corner.
zh-cn	#### 概述  这部分展示的是模板上的低等级发现规则的配置项原型。  如果模板链接到主机，则监控项原型将成为在低级别发现期间创建真实主机[监控项](/manual/web_interface/frontend_sections/configuration/hosts/items)的基础。  ![](../../../../../../../assets/en/manual/web_interface/template_item_prototypes.png){width="600"}  展示的数据：  |列|描述| |------|-----------| |*Name*|项原型的名称,展示为蓝色链接.<br>点击名称打开项原型[配置格式](/manual/discovery/low_level_discovery/item_prototypes).<br>如果项原型属于一个链接模板,模板名称显示在项名称前面, 是灰色的链接。点击模板链接将打开链接模板级别的项原型列表。| |*Key*|展示项原型的键值.| |*Interval*|显示检查的频率.| |*History*|展示保存项数据历史的天数.| |*Trends*|展示保存项趋势历史的天数.| |*Type*|展示项原型的类型(Zabbix agent, SNMP agent, simple check,等等)。| |*Create enabled*|基于这个原型创建项:<br>**Yes** - 启用<br>**No** - 禁用。你可以通过点击来切换'Yes'和'No'。| |*Discover*|发现项基于这个原型:<br>**Yes** - 发现<br>**No** - 不发现。你可以通过点击来切换'Yes'和'No'。| |*Tags*|展示标签的项原型.|  点击右上方的*Create item prototype*按钮来创建新的监控项原型。

en-us	#### Overview  In this section the configured trigger prototypes of a low-level discovery rule on the template are  displayed.   If the template is linked to the host, trigger prototypes will become the basis of  creating real host [triggers](/manual/web_interface/frontend_sections/configuration/hosts/triggers)  during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/template_trigger_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the trigger prototype, displayed as a blue link.<br>Clicking on the name opens the trigger prototype [configuration form](/manual/discovery/low_level_discovery/trigger_prototypes).<br>If the trigger prototype belongs to a linked template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger prototype list on the linked template level.| |*Operational data*|Format of the operational data of the trigger is displayed, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Create enabled*|Create the trigger based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the trigger based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the trigger prototype are displayed.|  To configure a new trigger prototype, click on the *Create trigger prototype* button at the top right corner.
zh-cn	#### 概述  在本节中，模板上配置的低级发现规则的触发器原型如下。  如果模板链接到主机，触发器原型将成为在低级别发现期间创建真实主机[触发器](/manual/web_interface/frontend_sections/configuration/hosts/triggers)的基础。  ![](../../../../../../../assets/en/manual/web_interface/template_trigger_prototypes.png){width="600"}  数据如下：  |列|描述| |------|-----------| |*Name*|触发器原型的名称，展示为蓝色的链接.<br>点击名称打开触发器原型 [配置格式](/manual/discovery/low_level_discovery/trigger_prototypes).<br>如果触发器属于一个链接模板, 模板名称显示在触发器名称前面, 为灰色链接. 点击模板链接会在模板层面打开触发器原型列表.| |*Operational data*|将显示触发器的操作数据格式，其中包含将在 *Monitoring* → *Problems* 中动态解析的任意字符串和宏。| |*Create enabled*|创建触发器基于这个原型:<br>**Yes** - 启用<br>**No** - 禁用. 你可以通过点击来切换'Yes'和'No'。| |*Discover*|发现触发器基于这个原型:<br>**Yes** - 发现<br>**No** - 没发现. 你可以通过点击来切换'Yes'和'No'。| |*Tags*|展示了触发器原型的标签.|  创建新的触发器原型，点击右上方的 *Create trigger prototype* 按钮。

en-us	#### Overview  In this section the graph prototypes of a low-level discovery rule on the host are  displayed. Graph prototypes are the basis of real host [graphs](/manual/web_interface/frontend_sections/configuration/hosts/graphs)  that are created during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/host_graph_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the graph prototype, displayed as a blue link.<br>Clicking on the name opens the graph prototype [configuration form](/manual/discovery/low_level_discovery/graph_prototypes).<br>If the graph prototype belongs to a linked template, the template name is displayed before the graph name, as a gray link. Clicking on the template link will open the graph prototype list on the linked template level.| |*Width*|Width of the graph prototype is displayed.| |*Height*|Height of the graph prototype is displayed.| |*Type*|Type of the graph prototype is displayed - *Normal*, *Stacked*, *Pie* or *Exploded*.| |*Discover*|Discover the graph based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.|  To configure a new graph prototype, click on the *Create graph prototype* button at the top right corner.
zh-cn	#### 概述   本节将展示主机的低级别自动发现的图形原型。 图形原型是在低级别自动发现期间创建的实际主机[图形](/manual/web_interface/frontend_sections/configuration/hosts/graphs)的基础。  ![](../../../../../../../assets/en/manual/web_interface/host_graph_prototypes.png){width="600"}  显示数据:  |列|描述| |------|-----------| |*名字*|图形原型的名字, 用蓝色链接显示<br>点击名字打开图形原型[配置表](/manual/discovery/low_level_discovery/graph_prototypes)。<br>I如果图形原型属于链接模板，则模板名称以灰色链接的形式显示在图形名称之前。点击模板链接的名字将打开链接模板级别的图形原型列表。| |*宽度*|显示图形原型的宽度。| |*长度*|显示图形原型的长度。| |*类型*|显示图形原型的类型 - *折线图*、*堆叠面积图*、*饼图*或*分离型饼图*。| |*Discover*|发现基于此原型的图：<br>**是** - 启用discover。<br>**否** - 不启用discover。你可以通过点击在“是”和“否”之间切换。|  要配置一个新的图形原型，点击右上角的 *创建图形原型* 按钮。

en-us	#### Overview  In this section the host prototypes of a low-level discovery rule on the host are  displayed. Host prototypes are the basis of real [hosts](/manual/web_interface/frontend_sections/configuration/hosts)  that are created during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/host_host_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the host prototype, displayed as a blue link.<br>Clicking on the name opens the host prototype configuration form.<br>If the host prototype belongs to a linked template, the template name is displayed before the host name, as a gray link. Clicking on the template link will open the host prototype list on the linked template level.| |*Templates*|Templates of the host prototype are displayed.| |*Create enabled*|Create the host based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the host based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the host prototype are displayed.|  To configure a new host prototype, click on the *Create host prototype* button at the top right corner.
zh-cn	#### 概述  此区域将显示该主机上低级别自动发现规则的主机原型。主机原型是在低级别自动发现期间创建的真正 [主机](/manual/web_interface/frontend_sections/configuration/hosts) 的基础。   ![](../../../../../../../assets/en/manual/web_interface/host_host_prototypes.png){width="600"}  显示的数据:  |列|描述| |------|-----------| |*名称*|主机原型的名称，显示为蓝色链接。<br>单击名称将打开主机原型的配置表单。<br>如果主机原型属于链接模板，则在主机名前显示模板名，链接显示为灰色。点击模板链接将打开链接模板级别的主机原型列表。| |*模板*|显示主机原型的模板。| |*创建时启用*|基于此原型创建主机Create the host based on this prototype as:<br>**是** - 启用<br>**否** - 禁用。 您也可以通过单击该值，在 '是' 和 '否' 之间进行切换。| |*发现*|根据此原型发现主机:<br>**是** - 发现<br>**否** - 不发现。 您也可以通过单击该值，在 '是' 和 '否' 之间进行切换。| |*标签*|显示主机原型的标签信息。|  单击右上角的 *创建主机原型* 按钮，可以配置新的主机原型。

en-us	#### Overview  In this section the item prototypes of a low-level discovery rule on the host are  displayed. Item prototypes are the basis of real host [items](/manual/web_interface/frontend_sections/configuration/hosts/items)  that are created during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/host_item_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the item prototype, displayed as a blue link.<br>Clicking on the name opens the item prototype [configuration form](/manual/discovery/low_level_discovery/item_prototypes).<br>If the item prototype belongs to a template, the template name is displayed before the rule name, as a gray link. Clicking on the template link will open the item prototype list on the template level.| |*Key*|Key of the item prototype is displayed.| |*Interval*|Frequency of the check is displayed.| |*History*|How many days to keep item data history is displayed.| |*Trends*|How many days to keep item trends history is displayed.| |*Type*|Type of the item prototype is displayed (Zabbix agent, SNMP agent, simple check, etc).| |*Create enabled*|Create the item based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the item based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the item prototype are displayed.|  To configure a new item prototype, click on the *Create item prototype* button at the top right corner.
zh-cn	#### 概览  本节将展示主机低级别自动发现规则的监控项原型。监控项原型是主机通过低级别自动发现创建实际[监控项](/manual/web_interface/frontend_sections/configuration/hosts/items)的基础。  ![](../../../../../../../assets/en/manual/web_interface/host_item_prototypes.png){width="600"}  展示数据：  |栏|描述| |------|-----------| |*Name*|监控项原型名称，显示为蓝色链接。<br>点击名称打开监控项原型[配置](/manual/discovery/low_level_discovery/item_prototypes)。<br>如果监控项原型属于一个模板，模板名称会以灰色链接显示在规则名称之前。点击模板链接会在模板级别打开监控项原型列表。| |*Key*|监控项原型的键值。| |*Interval*|检查频率。| |*History*|监控项数据历史显示的天数。| |*Trends*|监控项趋势历史显示的天数。| |*Type*|监控项原型显示的类型（Zabbix agent，SNMP agent，简单检查等）。| |*Create enabled*|基于原型创建监控项为：<br>**Yes** - 启用<br>**No** - 禁用。可以通过点击在‘Yes’和‘No’之间切换。| |*Discover*|基于此原型发现监控项：<br>**Yes** - 自动发现<br>**No** - 不自动发现。可以通过点击在‘Yes’和‘No’之间切换。| |*Tags*|监控项原型显示的标签。|  点击右上角的*创建监控项原型*按钮配置新的监控项原型。

en-us	#### Overview  In this section the trigger prototypes of a low-level discovery rule on the host are  displayed. Trigger prototypes are the basis of real host [triggers](/manual/web_interface/frontend_sections/configuration/hosts/triggers)  that are created during low-level discovery.  ![](../../../../../../../assets/en/manual/web_interface/host_trigger_prototypes.png){width="600"}  Displayed data:  |Column|Description| |------|-----------| |*Name*|Name of the trigger prototype, displayed as a blue link.<br>Clicking on the name opens the trigger prototype [configuration form](/manual/discovery/low_level_discovery/trigger_prototypes).<br>If the trigger prototype belongs to a linked template, the template name is displayed before the trigger name, as a gray link. Clicking on the template link will open the trigger prototype list on the linked template level.| |*Operational data*|Format of the operational data of the trigger is displayed, containing arbitrary strings and macros that will resolve dynamically in *Monitoring* → *Problems*.| |*Create enabled*|Create the trigger based on this prototype as:<br>**Yes** - enabled<br>**No** - disabled. You can switch between 'Yes' and 'No' by clicking on them.| |*Discover*|Discover the trigger based on this prototype:<br>**Yes** - discover<br>**No** - do not discover. You can switch between 'Yes' and 'No' by clicking on them.| |*Tags*|Tags of the trigger prototype are displayed.|  To configure a new trigger prototype, click on the *Create trigger prototype* button at the top right corner.
zh-cn	#### 概述  本节将展示主机低级别自动发现规则的触发器原型。触发器原型是主机通过低级别自动发现创建实际[触发器](/manual/web_interface/frontend_sections/configuration/hosts/triggers)  的基础。  ![](../../../../../../../assets/en/manual/web_interface/host_trigger_prototypes.png){width="600"}  展示数据：  |栏|描述| |------|-----------| |*Name*|触发器原型名称，显示为蓝色链接。<br>点击名称打开触发器原型[配置表格](/manual/discovery/low_level_discovery/trigger_prototypes)。<br>如果触发器原型属于一个模板，模板名称会以灰色链接显示在规则名称之前。点击模板链接会在模板级别打开触发器原型列表。| |*Operational data*|所展示触发器的数据格式, 包括任意字符串和宏，会在*监控* → *问题*中动态解析。| |*Create enabled*|基于此原型发现触发器：<br>**Yes** - 启用<br>**No** - 禁用。 可以通过点击在‘Yes’和‘No’之间切换。| |*Discover*|基于此原型发现触发器：<br>**Yes** - 自动发现<br>**No** - 不自动发现。可以通过点击在‘Yes’和‘No’之间切换。| |*Tags*|触发器原型显示的标签。|  点击右上角的*创建触发器原型*按钮配置新的触发器原型。

en-us	#### Overview  In this section we will perform an SNMP [discovery](/manual/discovery/low_level_discovery) on a switch.
zh-cn	#### 概述  本章中会演示如何对交换机执行一次SNMP的 [自动发现](/manual/discovery/low_level_discovery) 。

en-us	#### Overview  In this section you can learn the meaning of some terms commonly used in Zabbix.
zh-cn	#### 概览  在本节中，您可以了解 Zabbix 中一些常用术语的含义。

en-us	### Overview  In this section you can see a high-level status of whole services that have been  configured in Zabbix, based on your infrastructure.   A service may be a hierarchy consisting if several levels of other services,  called "child" services, which are attributes to the overall status of the  service (see also an overview of the [service monitoring](/manual/it_services) functionality.)  The main categories of service status are *OK* or *Problem*, where the *Problem* status  is expressed by the corresponding problem severity name and color.  While the view mode allows to monitor services with their status and other details, you can  also configure the service hierarchy in this section (add/edit services, child services)  by switching to the edit mode.   To switch from the view to the edit mode (and back) click on the respective button  in the upper right corner:  -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/services_view_mode.png) -     view services -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/services_edit_mode.png) -     add/edit services, and child services  Note that access to editing depends on [user role](/manual/web_interface/frontend_sections/administration/user_roles) settings.
zh-cn	 ### 概述  在本节中，您可以看到基于您的基础架构在Zabbix中配置的整个服务的高级状态。  服务可以是由多个级别的其他服务组成的层次结构，称为“子”服务，这些服务是服务总体状态的属性（另请参见[服务监册](/manual/it_services) 功能概述。)  服务状态的主要类别是*正常*或*问题*，其中*问题*状态由相应的问题严重性名称和颜色表示。  虽然查看模式允许监视服务及其状态和其他详细信息，但您也可以通过切换到编辑模式[配置](/manual/it_services/service)，此部分中的服务层次结构（添加/编辑服务，子服务）。  要从查看切换到编辑模式（并返回），请点击右上角的相应按钮：  -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/services_view_mode.png) -     查看服务 -   ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/services_edit_mode.png) -     添加/编辑服务和子服务  请注意，编辑权限取决于[用户角色](/manual/web_interface/frontend_sections/administration/user_roles)设置。

en-us	#### Overview  In this section you can view the latest values  gathered by items.  Graphs are also available for the item values.  ![](../../../../../assets/en/manual/web_interface/latest_data.png){width="600"}  This section contains:  - the [filter](#using_filter) (collapsed by default) - the [subfilter](#using_subfilter) (never collapsed)  - the item list  Items are displayed with their name, time since the last check, **last value**, change amount, tags, and a link to a simple graph/history of item values.   Clicking on the item name opens the item menu with links to available graphs and the  item configuration.  Values in the *Last value* column are displayed with unit conversion and  value mapping applied. To view raw data, hover over the value.  Tags in the item list are clickable. If you click on a tag, this tag becomes enabled  in the [subfilter](#using-subfilter). The item list now displays the items corresponding to this tag and  any other previously selected tags in the subfilter. Note that once the items have  been filtered in this way, tags in the list are no longer clickable. Further modification  based on tags (e.g. remove, add another filter) must be done in the subfilter.  If an item has errors, for example, has become unsupported, an information icon will  be displayed in the *Info* column ![](../../../../../assets/en/manual/web_interface/info_icon.png).  Hover over the icon for details.  An icon with a question mark ![](../../../../../assets/en/manual/web_interface/item_description_icon.png) is displayed next to the item name for all items that have a description. Hover over this icon to see a tooltip with the item description.  If a host to which the item belongs is in maintenance, an orange wrench icon ![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png) is displayed after the host's name.  *Note*: The name of a disabled host is displayed in red. Data of disabled hosts, including graphs and item value lists, is also accessible in *Latest data*.  By default, only values that fall within the last 24 hours are displayed. This limit has been introduced with the aim of improving initial loading times for large pages of the latest data.  This time period can be extended by changing the value of  the *Max history display period* parameter in *Administration → [General]*(/manual/web_interface/frontend_sections/administration/general#gui).  ::: noteimportant For items with an update frequency of 1 day or more the change amount will never be displayed (with the default setting). Also in this case the last value will not be displayed at all if it was received more than 24 hours ago. :::
zh-cn	#### 概述  在本节中，您可以查看按项目收集的最新值。  图表也可用于展示项目值。  ![](../../../../../assets/en/manual/web_interface/latest_data.png){width="600"}  本节包含：  - [过滤器](#using_filter) (默认情况下处于折叠状态) - [子过滤器](#using_subfilter) (从不折叠)  - 项目列表  显示项目及其名称、自上次检查以来的时间、**最后一个值**、更改金额、标记以及指向项目值的简单图形/历史记录的链接。  单击项目名称将打开项目菜单，其中包含指向可用图形和项目配置的链接。  项目列表中的标签是可点击的。如果单击某个标记，则此标记将在子筛选器中启用。项目列表现在显示与此标记和子筛选器中以前选择的任何其他标记对应的项目。请注意，以这种方式筛选项目后，列表中的标记将不再可点击。基于标签的进一步修改（例如，删除，添加另一个过滤器）必须在子过滤器中完成。  将显示*最后一个值* 列中显示的值应用了单位换算和值映射。要查看原始数据，请将鼠标悬停在显示值上。  如果某个项目有错误，例如：已变得不受支持，则 *信息* ![](../../../../../assets/en/manual/web_interface/info_icon.png)列中将显示一个信息图标。将鼠标悬停在图标上可查看详细信息。  带有问号![](../../../../../assets/en/manual/web_interface/item_description_icon.png)的图标将显示在具有说明的所有项目的项目名称旁边。将鼠标悬停在此图标上，可查看包含项目描述的工具提示。  将鼠标悬停在此图标上，可查看包含项目描述的工具提示。如果项目所属的主机处于维护状态，则在主机名称后面会显示一个橙色扳手图标![](../../../../../assets/en/manual/web_interface/frontend_sections/configuration/maintenance_wrench_icon.png)  *注意*：已禁用主机的名称显示为红色。禁用主机的数据（包括图形和项目值列表）也可以在 *最新数据* 中访问。  默认情况下，只显示最近24小时内的值。引入此限制的目的是缩短大页面最新数据的初始加载时间。 在*管理 → [常规]*(/manual/web_interface/frontend_sections/administration/general#gui)中更改*最大历史记录显示周期*参数的值来延长此时间段。  :: noteimportant  对于更新频率为 1 天或以上的项目，将永远不会显示更改量（使用默认设置)。此外，在这种情况下，如果超过 24 小时前收到最后一个值，则根本不会显示该值。  :::

en-us	#### Overview  In this section you may find some details of [additional operations](/manual/config/notifications/action/operation) for discovery/autoregistration events.
zh-cn	#### 概述  在本节你将看到对发现或自动注册事件的[附加操作](/manual/config/notifications/action/operation)。

en-us	#### Overview  In this section, you will learn how to log in and set up a system user in Zabbix.
zh-cn	#### 概述  本章你会学习如何登录Zabbix，以及在Zabbix内创建一个系统用户。

en-us	#### Overview  In this section you will learn how to set up a new host.  A host in Zabbix is a networked entity (physical, virtual) that you wish to monitor. The definition of what can be a "host" in Zabbix is quite flexible. It can be a physical server, a network switch, a virtual machine or some application.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的主机。  Zabbix中的主机是一个你想要监控的网络实体（物理的，或者虚拟的）。Zabbix中，对于主机的定义非常灵活。它可以是一台物理服务器，一个网络交换机，一个虚拟机或者某些应用程序。

en-us	#### Overview  In this section, you will learn how to set up an item.  Items are the basis of gathering data in Zabbix. Without items, there is no data - because only an item defines a single metric or what kind of data to collect from a host.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的监控项。  监控项是Zabbix中采集数据的基础。没有监控项，就没有数据——因为一个主机中只有监控项定义了单一的指标或者需要获得的数据。

en-us	#### Overview  In this section you will learn how to set up a template.  Previously we learned how to set up an item, a trigger and how to get a problem notification for the host.  While all of these steps offer a great deal of flexibility in themselves, it may appear like a lot of steps to take if needed for, say, a thousand hosts. Some automation would be handy.  This is where templates come to help. Templates allow to group useful items, triggers and other entities so that those can be reused again and again by applying to hosts in a single step.  When a template is linked to a host, the host inherits all entities of the template. So, basically a pre-prepared bunch of checks can be applied very quickly.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的模板。  之前我们学习了如何创建监控项、触发器以及如何获取主机的问题通知。  虽然这些步骤提供了很大的灵活性，但仍然需要很多步骤才能完成。如果我们需要配置上千台主机，一些自动化操作会带来更多便利性。  模版功能可以实现这一点。模版允许对有用的监控项、触发器和其他对象进行分组，只需要一步就可以对监控主机应用模版，以达到重复使用的目的。  当一个模版链接到一个主机后，主机会继承这个模版中的所有对象。简单而言，一组预先定义好的检查会被快速应用到主机上。

en-us	#### Overview  In this section you will learn how to set up a trigger.  Items only collect data. To automatically evaluate incoming data we need to define triggers. A trigger contains an expression that defines a threshold of what is an acceptable level for the data.  If that level is surpassed by the incoming data, a trigger will "fire" or go into a 'Problem' state - letting us know that something has happened that may require attention. If the level is acceptable again, trigger returns to an 'Ok' state.
zh-cn	#### 概述  通过本节，你将会学习到如何创建一个新的触发器。  监控项只是用于收集数据. 如果需要自动评估收到的数据，我们需要定义触发器。触发器包含了一个表达式，这个表达式定义了数据的可接受的阈值级别。  如果收到的数据超过了这个定义好的级别，触发器将被“触发”，或者进入“问题”状态——从而引起我们的注意，让我们知道有问题发生。如果数据再次恢复到合理的范围，触发器将返回“ok”状态。

en-us	#### Overview  In this widget you can display current problems. The information in this widget is similar to *Monitoring* → *Problems*.
zh-cn	#### 概述  在这个组件中，你可以显示当前存在的问题。这个组件中的信息类似于*Monitoring* → *Problems*。

en-us	#### Overview  In this widget, you can display problems by severity. You can limit what hosts and triggers are displayed in the widget and define how the problem count is displayed.
zh-cn	#### 概述  在这个组件中，您可以按严重程度显示问题。您可以限制在组件中显示哪些主机和触发器，并定义问题计数的显示方式。

en-us	 ### Overview   In Zabbix 6.0, [service monitoring](/manual/it_services) functionality has been reworked significantly (see [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction/whatsnew600#services) for the list of changes).   This page describes how services and SLAs, defined in earlier Zabbix versions, are changed during an upgrade to Zabbix 6.0 or newer.
zh-cn	 ### 概览   在 Zabbix 6.0 中，[服务监控](/manual/it_services) 功能进行了重大修改（参见 [What's new in Zabbix 6.0.0](https://www.zabbix.com/documentation/6.0/en/manual/introduction /whatsnew600#services）以获取更改列表）。  此页面描述了在升级到 Zabbix 6.0 或更新版本期间如何更改早期 Zabbix 版本中定义的服务和 SLA。

en-us	#### Overview  Item types cover various methods of acquiring data from your system. Each item type comes with its own set of supported item keys and required parameters.  The following items types are currently offered by Zabbix:  -   [Zabbix agent checks](/manual/config/items/itemtypes/zabbix_agent) -   [SNMP agent checks](/manual/config/items/itemtypes/snmp) -   [SNMP traps](/manual/config/items/itemtypes/snmptrap) -   [IPMI checks](/manual/config/items/itemtypes/ipmi) -   [Simple checks](/manual/config/items/itemtypes/simple_checks)     -   [VMware         monitoring](/manual/config/items/itemtypes/simple_checks/vmware_keys) -   [Log file monitoring](/manual/config/items/itemtypes/log_items) -   [Calculated items](/manual/config/items/itemtypes/calculated)     -   [Aggregate         calculations](/manual/config/items/itemtypes/calculated/aggregate) -   [Zabbix internal checks](/manual/config/items/itemtypes/internal) -   [SSH checks](/manual/config/items/itemtypes/ssh_checks) -   [Telnet checks](/manual/config/items/itemtypes/telnet_checks) -   [External checks](/manual/config/items/itemtypes/external) -   [Trapper items](/manual/config/items/itemtypes/trapper) -   [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) -   [ODBC checks](/manual/config/items/itemtypes/odbc_checks) -   [Dependent items](/manual/config/items/itemtypes/dependent_items) -   [HTTP checks](/manual/config/items/itemtypes/http) -   [Prometheus checks](/manual/config/items/itemtypes/prometheus) -   [Script items](/manual/config/items/itemtypes/script)  Details for all item types are included in the subpages of this section. Even though item types offer a lot of options for data gathering, there are further options through [user parameters](/manual/config/items/userparameters) or [loadable modules](/manual/config/items/loadablemodules).  Some checks are performed by Zabbix server alone (as agent-less monitoring) while others require Zabbix agent or even Zabbix Java gateway (with JMX monitoring).  ::: noteimportant If a particular item type requires a particular interface (like an IPMI check needs an IPMI interface on the host) that interface must exist in the host definition. :::  Multiple interfaces can be set in the host definition: Zabbix agent, SNMP agent, JMX and IPMI. If an item can use more than one interface, it will search the available host interfaces (in the order: Agent→SNMP→JMX→IPMI) for the first appropriate one to be linked with.  All items that return text (character, log, text types of information) can return whitespace only as well (where applicable) setting the return value to an empty string (supported since 2.0).
zh-cn	#### 概述  监控项类型包含从系统获取数据的多种方式。 每个监控项类型都有一组自己支持的监控项key和所需的参数。  以下监控项类型由Zabbix提供：  -   [Zabbix agent 检查](/manual/config/items/itemtypes/zabbix_agent) -   [SNMP agent 检查](/manual/config/items/itemtypes/snmp) -   [SNMP traps](/manual/config/items/itemtypes/snmptrap) -   [IPMI 检查](/manual/config/items/itemtypes/ipmi) -   [简单检查](/manual/config/items/itemtypes/simple_checks)     -   [VMware         监控](/manual/config/items/itemtypes/simple_checks/vmware_keys) -   [日志文件监控](/manual/config/items/itemtypes/log_items) -   [可计算监控项](/manual/config/items/itemtypes/calculated)     -   [聚合计算](/manual/config/items/itemtypes/calculated/aggregate) -   [Zabbix 内部检查](/manual/config/items/itemtypes/internal) -   [SSH 检查](/manual/config/items/itemtypes/ssh_checks) -   [Telnet 检查](/manual/config/items/itemtypes/telnet_checks) -   [外部检查](/manual/config/items/itemtypes/external) -   [采集器监控项](/manual/config/items/itemtypes/trapper) -   [JMX 监控](/manual/config/items/itemtypes/jmx_monitoring) -   [ODBC 检查](/manual/config/items/itemtypes/odbc_checks) -   [相关监控项](/manual/config/items/itemtypes/dependent_items) -   [HTTP 检查](/manual/config/items/itemtypes/http) -   [Prometheus 检查](/manual/config/items/itemtypes/prometheus) -   [脚本监控](/manual/config/items/itemtypes/script)  所有监控项类型的详细描述都包含在本章的各个小节中。即使监控项类型提供了大量的数据收集的方式，你还可以通过 [用户参数](/manual/config/items/userparameters) or [可加载模块](/manual/config/items/loadablemodules)进一步扩展数据收集方式。  一些监控检查由Zabbix Server执行（称作无代理监控），而其它监控检查则需要Zabbix agent或者Zabbix Java网关（使用JMX监视）执行。  ::: noteimportant 如果特定的监控项类型需要特定的接口（如IPMI检查需要主机上的IPMI接口），该接口必须存在于主机定义中。 :::  可以在主机定义中设置多个接口：Zabbix agent，SNMP agent，JMX和IPMI。如果一个监控项使用多个接口，它将搜索可用的主机接口（按照以下顺序：Agent→SNMP→JMX→IPMI）直到找到连接的第一个匹配的接口。  返回文本的所有监控项（字符，日志，文本信息类型）都可以返回空格（如适用）和值设置为空的字符串。（2.0版本后支持）

en-us	#### Overview  It is possible to allow active Zabbix agent autoregistration, after which the server can start monitoring them. This way new hosts can be added for monitoring without configuring them manually on the server.  Autoregistration can happen when a previously unknown active agent asks for checks.  The feature might be very handy for automatic monitoring of new Cloud nodes. As soon as you have a new node in the Cloud Zabbix will automatically start the collection of performance and availability data of the host.  Active agent autoregistration also supports the monitoring of added hosts with passive checks. When the active agent asks for checks, providing it has the 'ListenIP' or 'ListenPort' configuration parameters defined in the configuration file, these are sent along to the server. (If multiple IP addresses are specified, the first one is sent to the server.)  Server, when adding the new autoregistered host, uses the received IP address and port to configure the agent. If no IP address value is received, the one used for the incoming connection is used. If no port value is received, 10050 is used.  It is possible to specify that the host should be autoregistered with a [DNS name](#using_dns_as_default_interface) as the default agent interface.  Autoregistration is rerun:  -   if host [metadata](#using_host_metadata) information changes:     -   due to HostMetadata changed and agent restarted     -   due to value returned by HostMetadataItem changed -   for manually created hosts with metadata missing -   if a host is manually changed to be monitored by another Zabbix     proxy -   if autoregistration for the same host comes from a new Zabbix proxy
zh-cn	 #### 概述   可以使用Zabbix agent(主动模式) 自动注册功能来添加主机，自动注册后Zabbix server就可以开始进行监控了。通过这种方式添加的主机不必再手工配置。 只要有未知的主动模式agent请求检查，就会触发自动注册。  该特性对于云上新增节点的自动监控很方便。一旦云上新增了一个节点，Zabbix就开始自动收集该节点的性能和可用性数据。  对于通过zabbix agent(被动模式)添加的主机，agent（主动模式） 自动注册同样可以监控它们。agent（主动模式）请求检查时，会将配置文件中定义的监听IP(ListenIP)或监听端口(ListenPort)参数一同发送给Zabbix server。  注册新主机时，Zabbix server使用收到的IP地址和端口信息来配置agent。如果没收到IP地址信息，则使用入站连接中的对端IP地址。如果没收到端口信息，则使用10050作为agent的端口。  可以使用[DNS名称](#using_dns_as_default_interface)作为默认agent接口来进行自动注册。  以下情况会重新执行自动注册:  -   主机 [元数据](#using_host_metadata) 信息变更:     -   由于HostMetadata信息变更并且agent重启     -   由于HostMetadataItem信息变更 -   手动添加的主机丢失元数据信息 -   已注册的主机手动迁移到另一个Zabbix proxy上 -   从一个新的Zabbix proxy收到同一台主机的自动注册信息

en-us	#### Overview  It is possible to automatically discover IPMI sensors.  To do that, you may use a combination of:  -   the `ipmi.get` IPMI item (supported since Zabbix **5.0.0**) as the     master item -   dependent low-level discovery rule and item prototypes
zh-cn	#### 概述  IPMI传感器可被自动发现.  要实现此功能, 可结合使用:  -   IPMI监控项 `ipmi.get`  (从Zabbix **5.0.0**起支持) 作为主监控项 -   依赖型的低级别自动发现规则和低级别自动发现监控项原型

en-us	#### Overview  It is possible to configure real-time exporting of trigger events, item values and trends in a newline-delimited JSON format.  Exporting is done into files, where each line of the export file is a JSON object. Value mappings are not applied.  In case of errors (data cannot be written to the export file or the export file cannot be renamed or a new one cannot be created after renaming it), the data item is dropped and never written to the export file. It is written only in the Zabbix database. Writing data to the export file is resumed when the writing problem is resolved.  For precise details on what information is exported, see the [export protocol](/manual/appendix/protocols/real_time_export) page.  Note that host/item can have no metadata (host groups, host name, item name) if the host/item was removed after the data was received, but before server exported data.
zh-cn	#### 概述 可以使用以换行符分隔的 JSON 格式，配置触发器事件、监控项值和趋势的实时导出。  导出文件的每一行都应是一个JSON对象。值映射不被应用。  如果出现错误（无法将数据写入导出文件，或者无法重命名导出文件，或者在重新创建导出文件后无法创建新文件），则会删除数据，并且永远不会将其写入导出文件。它只写在Zabbix数据库中。解决写入问题后，将恢复数据的写入。   有关导出哪些信息的确切详细信息，请参阅[export protocol](/manual/appendix/protocols/real_time_export) 。  请注意，如果主机/监控项在收到数据后被删除，但在服务器导出数据之前，则主机/监控项可以没有元数据（主机组、主机名、监控项名称）。

en-us	#### Overview  It is possible to create custom rules regarding the times when an item is checked. The two methods for that are *Flexible intervals*, which allow to redefine the default update interval, and *Scheduling*, whereby an item check can be executed at a specific time or sequence of times.
zh-cn	#### 概述  有两种方法可以创建检查监控项的时间的自定义规则。 *灵活间隔*，允许重新定义默认更新间隔；*调度*，可以在特定时间或时间序列执行监控项检查。

en-us	#### Overview  It is possible to define that an action is executed only if the event matches a defined set of conditions. Conditions are set when configuring the [action](/manual/config/notifications/action#configuring_an_action).  Condition matching is case-sensitive.
zh-cn	#### 概述  只有当事件满足了定义的条件集时，动作才会被执行。条件在配置 [action](/manual/config/notifications/action#configuring_an_action) 时进行设置。  条件匹配区分大小写。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) all interfaces configured in Zabbix frontend for a host.
zh-cn	#### 概述  在Zabbix前端页面中配置的所有主机接口都可以[自动发现](/manual/discovery/low_level_discovery)。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) all JMX MBeans or MBean attributes or to specify a pattern for the discovery of these objects.  It is mandatory to understand the difference between an MBean and MBean attributes for discovery rule configuration. An MBean is an object which can represent a device, an application, or any resource that needs to be managed.  For example, there is an MBean which represents a web server. Its attributes are connection count, thread count, request timeout, http file cache, memory usage, etc. Expressing this thought in human comprehensive language we can define a coffee machine as an MBean which has the following attributes to be monitored: water amount per cup, average consumption of water for a certain period of time, number of coffee beans required per cup, coffee beans and water refill time, etc.
zh-cn	#### 概述   可以 [自动发现](/manual/discovery/low_level_discovery) 所有 JMX MBean或MBean属性，也可以为这些对象的自动发现指定一个样式。  有必要理解自动发现规则配置中的MBean和MBean属性之间的区别。MBean是一个对象，代表一个设备、一个应用程序或任何需要管理的资源。  例如，有一个MBean，用来表示一个web服务器。其属性有连接数、线程数、请求超时时间、HTTP文件缓存大小、内存使用率等。用通俗语言来类比一下，可以把一台咖啡机定义成一个MBean，有这些属性会被监控：每杯的水量、某段时间平均消耗水量、每杯所需咖啡豆数量、咖啡豆和水的重新装填时间等。

en-us	#### Overview  It is possible to [discover](/manual/discovery/low_level_discovery#configuring_low-level_discovery) object instances of Windows performance counters. This is useful for multi-instance performance counters.
zh-cn	#### 概述  支持对Windows性能计数器的实例进行[自动发现](/manual/discovery/low_level_discovery#configuring_low-level_discovery)。 此特性对于多实例性能计数器很有用。

en-us	### Overview  It is possible to [discover](/manual/discovery/low_level_discovery) systemd units (services, by default) with Zabbix.
zh-cn	#### 概述  系统单元 (服务, 默认设置)可被Zabbix [自动发现](/manual/discovery/low_level_discovery).

en-us	#### Overview  It is possible to enhance Zabbix frontend functionality by adding 3rd party modules or by developing your own modules without the need to change the source code of Zabbix.  Note that the module code will run with the same privileges as Zabbix source code. This means:  -   3rd party modules can be harmful. You must trust the modules you are     installing; -   Errors in a 3rd party module code may crash the frontend. If this     happens, just remove the module code from the frontend. As soon as     you reload Zabbix frontend, you'll see a note saying that some     modules are absent. Go to [Module     administration](/manual/web_interface/frontend_sections/administration/general#modules)     (in *Administration* → *General* → *Modules*) and click *Scan     directory* again to remove non-existent modules from the database.
zh-cn	 #### 概述  可以通过添加第三方模块或开发自己的模块来增强Zabbix前端功能，而无需更改Zabbix的源代码。  请注意，模块代码将以与 Zabbix 源代码相同的权限运行。这意味着：  - 第三方模块可能是有害的。您必须信任您正在安装的模块; - 第三方模块代码中的错误可能会使前端崩溃。如果发生这种情况，只需从前端删除模块代码即可。重新加载Zabbix前端后，您会看到一条消息，指出某些模块不存在。转到 [Module     administration](/manual/web_interface/frontend_sections/administration/general#modules)     (在 *Administration* → *General* → *Modules*) 然后再次单击 *Scan directory* 以从数据库中删除不存在的模块。

en-us	#### Overview  It is possible to make some internal metrics of Zabbix server and proxy accessible remotely by another Zabbix instance or a third-party tool. This can be useful so that supporters/service providers can monitor their client Zabbix servers/proxies remotely or, in organizations where Zabbix is not the main monitoring tool, that Zabbix internal metrics can be monitored by a third-party system in an umbrella-monitoring setup.  Zabbix internal stats are exposed to a configurable set of addresses listed in the new 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter. Requests will be accepted only from these addresses.
zh-cn	#### 概述  可以通过另一个 Zabbix 实例或第三方工具远程访问 Zabbix 服务器和代理的一些内部指标。这可能很有用，以便支持者/服务提供商可以远程监控他们的客户端 Zabbix 服务器/代理，或者在组织中 Zabbix 不是主要的监控工具，Zabbix 内部指标可以在伞式监控设置中由第三方系统监控。  Zabbix 内部统计信息暴露给新的“StatsAllowedIP”[server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) 参数中列出的一组可配置地址。 仅接受来自这些地址的请求。

en-us	#### Overview  It is possible to store some sensitive information secretly in HashiCorp Vault KV Secrets Engine - Version 2. Secrets can be saved for:  -   user macro values -   database access credentials  Zabbix provides read-only access to the secrets in Vault, assuming that secrets are managed by someone else.
zh-cn	####概述  可以在 HashiCorp 中秘密存储一些敏感信息 Vault KV Secrets Engine - 第 2 版。可以将密钥保存为：  - 用户宏值 - 数据库访问凭据  Zabbix 提供对 Vault 中机密的只读访问权限，假设密钥由其他人管理。

en-us	#### Overview  It is very important to have Zabbix system properly tuned for maximum performance.
zh-cn	#### 概述  正确调整 Zabbix 系统以获得最佳性能非常重要。

en-us	#### Overview  JMX monitoring can be used to monitor JMX counters of a Java application.  JMX monitoring has native support in Zabbix in the form of a Zabbix daemon called "Zabbix Java gateway", introduced since Zabbix 2.0.  To retrieve the value of a particular JMX counter on a host, Zabbix server queries the Zabbix **Java gateway**, which in turn uses the [JMX management API](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/) to query the application of interest remotely.  For more details and setup see the [Zabbix Java gateway](/manual/concepts/java) section.  ::: notewarning Communication between Java gateway and the monitored JMX application should not be firewalled. :::
zh-cn	#### 概述  JMX监控端可用于监控Java应用程序的JMX计数器。  从zabbix 2.0开始，JMX监控端以Zabbix守护进程的形式运行，称为“Zabbix Java gateway”。  为了检索主机上特定JMX计数器的值，Zabbix服务器查询Zabbix **Java gateway**，网关使用[JMX管理API](http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/)远程查询指定的应用程序，将结果返回给zabbix server。  有关更多细节和设置，请参考 [Zabbix Java gateway](/manual/concepts/java)。  ::: notewarning Java gateway和JMX应用程序之间的通信应该在防火墙上放行。 :::

en-us	#### Overview  Kerberos authentication can be used in web monitoring and HTTP items in Zabbix since version 4.4.0.  This section describes an example of configuring Kerberos with Zabbix server to perform web monitoring of `www.example.com` with user 'zabbix'.
zh-cn	#### 概述  zabbix 4.4.0之后版本，Kerberos身份验证可用于Zabbix中的web监视和HTTP监控项。  这部分Kerberos配置描述Zabbix server使用'zabbix'用户对`www.example.com`进行web监控

en-us	#### Overview  Linking is a process whereby templates are applied to hosts, whereas unlinking removes the association with the template from a host.  ::: noteimportant Templates are linked directly to individual hosts and not to host groups. Simply adding a template to a host group will not link it. Host groups are used only for logical grouping of hosts and templates. :::
zh-cn	#### 概述  链接是将模板应用于主机的过程，而取消链接将从主机中删除与模板的关联。  ::: noteimportant 模板直接链接到各个主机，而不是主机组。只需将模板添加到主机组就不会链接到主机组。主机组仅用于主机和模板的逻辑分组。 :::

en-us	#### - Overview  Loadable modules offer a performance-minded option for extending Zabbix functionality.  There already are ways of extending Zabbix functionality by way of:  -   [user parameters](userparameters) (agent metrics) -   [external checks](/manual/config/items/itemtypes/external)     (agent-less monitoring) -   `system.run[]` Zabbix [agent     item](/manual/config/items/itemtypes/zabbix_agent).  They work very well, but have one major drawback, namely fork(). Zabbix has to fork a new process every time it handles a user metric, which is not good for performance. It is not a big deal normally, however it could be a serious issue when monitoring embedded systems, having a large number of monitored parameters or heavy scripts with complex logic or long startup time.  Support of loadable modules offers ways for extending Zabbix agent, server and proxy without sacrificing performance.  A loadable module is basically a shared library used by Zabbix daemon and loaded on startup. The library should contain certain functions, so that a Zabbix process may detect that the file is indeed a module it can load and work with.  Loadable modules have a number of benefits. Great performance and ability to implement any logic are very important, but perhaps the most important advantage is the ability to develop, use and share Zabbix modules. It contributes to trouble-free maintenance and helps to deliver new functionality easier and independently of the Zabbix core code base.  Module licensing and distribution in binary form is governed by the GPL license (modules are linking with Zabbix in runtime and are using Zabbix headers; currently the whole Zabbix code is licensed under GPL license). Binary compatibility is not guaranteed by Zabbix.  Module API stability is guaranteed during one Zabbix LTS (Long Term Support) [release](http://www.zabbix.com/life_cycle_and_release_policy) cycle. Stability of Zabbix API is not guaranteed (technically it is possible to call Zabbix internal functions from a module, but there is no guarantee that such modules will work).
zh-cn	#### - 概览  可加载模块提供了一个侧重性能的选项，来扩展Zabbix的功能。\  目前已经有以下的功能来扩展Zabbix功能:  -   [用户自定义变量](/zh/manual/config/items/userparameters) (Agent指标) -   [扩展检查](/zh/manual/config/items/itemtypes/external) (无Agent监控) -   `system.run[]` Zabbix     [Agent监控项](/zh/manual/config/items/itemtypes/zabbix_agent).  这些功能工作的十分优秀，但是存在一个重要的缺陷，名字叫fork()。在每次处理用户指标的时候都必须创建一个新的子进程，这样不会有优秀的性能表现。通常这并不是个大问题，然而这会在监控嵌入式系统、拥有大量监控参数或运行具有逻辑繁多或启动时间长的脚本的情况下成为一个严重的问题。\  可加载模块提供了在不额外消耗性能的情况下，扩展Zabbix Agent、Server和Proxy。\  可加载模块是基于在Zabbix守护进程启动时加载的共享库。这个库包含了一些功能，以便Zabbix可以检测到该文件确实是一个可以被加载和使用的模块。  可加载模块具有许多优点。良好的性能和容易实现逻辑的能力很重要，但最重要的能力是开发、使用和共享Zabbi模块。可加载模块有助于实现无故障维护，有助于更轻松的提供新功能并且不依赖于Zabbix核心代码库。\  二进制形式的模块的授权和分发应在GPL许可证的许可下管理（模块运行时连接到Zabbix并且使用Zabbix的头文件；目前ZABBIX的代码根据GPL许可证进行授权）。ZABBIX不保证二进制兼容性。\  在一个ZABBIX LTS(长期支持)[版本](http://www.zabbix.com/life_cycle_and_release_policy)支持周期内保证API模块的稳定性。ZABBIX API的稳定性无法保证（从技术上讲，可以从模块调用ZABBIX内部函数，但不能保证这些模块可以工作）。\

en-us	### Overview  Low-level discovery provides a way to automatically create items, triggers, and graphs for different entities on a computer. For instance, Zabbix can automatically start monitoring file systems or network interfaces on your machine, without the need to create items for each file system or network interface manually. Additionally, it is possible to configure Zabbix to remove unneeded entities automatically based on actual results of periodically performed discovery.  A user can define their own types of discovery, provided they follow a particular JSON protocol.  The general architecture of the discovery process is as follows.  First, a user creates a discovery rule in "Configuration" → "Templates" → "Discovery" column. A discovery rule consists of (1) an item that discovers the necessary entities (for instance, file systems or network interfaces) and (2) prototypes of items, triggers, and graphs that should be created based on the value of that item.  An item that discovers the necessary entities is like a regular item seen elsewhere: the server asks a Zabbix agent (or whatever the type of the item is set to) for a value of that item, the agent responds with a textual value. The difference is that the value the agent responds with should contain a list of discovered entities in a JSON format. While the details of this format are only important for implementers of custom discovery checks, it is necessary to know that the returned value contains a list of macro → value pairs. For instance, item "net.if.discovery" might return two pairs: "{\#IFNAME}" → "lo" and "{\#IFNAME}" → "eth0".  These macros are used in names, keys and other prototype fields where they are then substituted with the received values for creating real items, triggers, graphs or even hosts for each discovered entity. See the full list of [options](/manual/config/macros/lld_macros) for using LLD macros.  When the server receives a value for a discovery item, it looks at the macro → value pairs and for each pair generates real items, triggers, and graphs, based on their prototypes. In the example with "net.if.discovery" above, the server would generate one set of items, triggers, and graphs for the loopback interface "lo", and another set for interface "eth0".  Note that since **Zabbix 4.2**, the format of the JSON returned by low-level discovery rules has been changed. It is no longer expected that the JSON will contain the "data" object. Low-level discovery will now accept a normal JSON containing an array, in order to support new features such as the item value preprocessing and custom paths to low-level discovery macro values in a JSON document.  Built-in discovery keys have been updated to return an array of LLD rows at the root of JSON document. Zabbix will automatically extract a macro and value if an array field uses the {\#MACRO} syntax as a key. Any new native discovery checks will use the new syntax without the "data" elements. When processing a low-level discovery value first the root is located (array at `$.` or `$.data`).  While the "data" element has been removed from all native items related to discovery, for backward compatibility Zabbix will still accept the JSON notation with a "data" element, though its use is discouraged. If the JSON contains an object with only one "data" array element, then it will automatically extract the content of the element using JSONPath `$.data`. Low-level discovery now accepts optional user-defined LLD macros with a custom path specified in JSONPath syntax.  ::: notewarning As a result of the changes above, newer agents no longer will be able to work with an older Zabbix server. :::  See also: [Discovered entities](#discovered_entities)
zh-cn	 ### 概述  底层自动发现可以自动为主机上的不同实体创建监控项、触发器和图表。比如， Zabbix可以自动监控文件系统和网络接口，并且不需要为其手工创建监控项。另外，可以基于周期性自动发现的结果来删除无用的监控实体。  用户可以基于特定的JSON格式来自定义发现类型。  自动发现的大体流程如下：  首先，用户在 "配置" → "模板" → "自动发现" 一栏中创建发现规则。发现规则包含用来发现特定实体(如文件系统和网络接口)的(1)监控项以及监控项、触发器和图表的(2)原型。  用于自动发现的监控项与常规监控项没有大体区别：Zabbix server向agent(或者其它任何类型的监控代理)请求监控项的值，agent对其回复一个文本值。唯一区别是agent响应中包含所发现的一系列JSON数组。对自动发现检查规则有自定义的需求时才需要了解格式的细节方面，不过有必要知道返回值包含一系列 宏 → 值 的键值对。比如，监控项 "net.if.discovery" 会返回两组键值对："{\#IFNAME}" → "lo" 和 "{\#IFNAME}" → "eth0"。  当创建实际的监控项、触发器、图表以及主机时，宏会替换成接收到的值。使用底层自动发现(LLD)的宏请参考 [选项](/manual/config/macros/lld_macros) 中的全部列表。  当通过自动发现收到监控项返回值的时候，Zabbix server会查找 宏 → 值 键值对，每一对 宏 → 值 会基于原型生成监控项、触发器和图表。在上述 "net.if.discovery" 的例子中，为环回接口 "lo" 生成了一组监控项、触发器和图表，为 "eth0"接口生成了一组监控项、触发器和图表。  注意，自从**Zabbix 4.2** 开始，底层自动发现返回的JSON数组的格式变化了。JSON格式将不再包含 "data" 对象。现在底层自动发现接收一个普通的JSON数组，用于实现一些新特性，如监控项值的预处理和对于JSON文件中用于底层自动发现的宏的路径自定义。  内置的自动发现的键已经可以实现在JSON文件的根路径返回一个底层自动发现数组。如果数组使用{\#MACRO}作为键，则宏和值会自动提取。任何新版的内置的自动发现检查会使用不含 "data"元素 的新语法格式。当处理一个底层自动发现的值时，第一个步骤就是定位根目录 (数组的根目录是 `$.` 或 `$.data`)。  当"data"元素从所有跟自动发现有关的内置监控项中移除时，为了向后兼容，Zabbix会接受带有"data"元素的JSON格式，不过并不鼓励这么用。如果JSON数据包含一个对象，该对象只有一个"data"数组，则"data"数组的内容会通过JSONPath `$.data`自动提取出来。底层自动发现现在接受可选的自定义宏，可在JSONPath语法中自定义路径。  ::: notewarning 上述变更会导致新的agent不再跟旧的Zabbix server有任何关联。 :::  参阅: [发现的实体](#discovered_entities)

en-us	#### Overview  Media types are [exported](/manual/xml_export_import) with all related objects and object relations.
zh-cn	#### 概述  媒介类型是与所有相关对象和对象关系一起[导出](/manual/xml_export_import)的

en-us	#### Overview  Most Zabbix web interface pages support various HTTP GET parameters that control what will be displayed. They may be passed by specifying parameter=value pairs after the URL, separated from the URL by a question mark (?) and from each other by ampersands (&).
zh-cn	#### 概述  大多数 Zabbix Web 界面页面都支持各种 HTTP GET 参数来控制显示的内容。 它们可以通过在 URL 之后指定“参数=值“对来传递，通过问号 (?) 与 URL 隔开，并通过与号 (&) 彼此隔开。

en-us	#### Overview  Nesting is a way of one template encompassing one or more other templates.  As it makes sense to separate out entities on individual templates for various services, applications, etc., you may end up with quite a few templates all of which may need to be linked to quite a few hosts. To simplify the picture, it is possible to link some templates together in a single template.  The benefit of nesting is that you have to link only one template ("nest", parent template) to the host and the host will inherit all entities of the linked templates ("nested", child templates) automatically. For example, if we link templates T1 and T2 to template T3, we supplement T3 with entities from T1 and T2, and not vice versa. If we link template A to templates B and C, we supplement B and C with entities from A.
zh-cn	#### 概述  嵌套是一个模板包含一个或多个其他模板的一种方式。  由于在各种服务、应用程序等的各个模板上分离实体是有意义的，因此您最终可能会得到相当多的模板，所有这些模板都可能需要链接到相当多的主机。 为了简化图片，可以将一些模板链接到一个模板中。  嵌套的好处是您只需将一个模板（“嵌套”，父模板）链接到主机，主机将自动继承链接模板（“嵌套”，子模板）的所有实体。 例如，如果我们将模板 T1 和 T2 链接到模板 T3，我们就用来自 T1 和 T2 的实体补充 T3，而不是相反。 如果我们将模板 A 链接到模板 B 和 C，我们用 A 中的实体补充 B 和 C。

en-us	#### Overview  Network map [export](/manual/xml_export_import) contains:  -   all related images -   map structure - all map settings, all contained elements with their     settings, map links and map link status indicators  ::: notewarning Any host groups, hosts, triggers, other maps or other elements that may be related to the exported map are not exported. Thus, if at least one of the elements the map refers to is missing, importing it will fail. :::  Network map export/import is supported since Zabbix 1.8.2.
zh-cn	 #### 概览  网络拓扑图 [导出](/manual/xml_export_import) 包括:  -   所有相关的图片 -   拓扑图结构-所有拓扑图设置，所有包含的元素及其设置，拓扑图链接和拓扑图链接状态指示器  ::: 警告注意 不导出与导出映射相关的主机组、主机、触发器、其他映射或其他元素。因此，如果映射引用的元素中至少有一个缺失，则导入它将失败。 :::  网络拓扑图 导出/导入 支持从 Zabbix 1.8.2开始。

en-us	#### Overview  ODBC monitoring corresponds to the *Database monitor* item type in the Zabbix frontend.  ODBC is a C programming language middle-ware API for accessing database management systems (DBMS). The ODBC concept was developed by Microsoft and later ported to other platforms.  Zabbix may query any database, which is supported by ODBC. To do that, Zabbix does not directly connect to the databases, but uses the ODBC interface and drivers set up in ODBC. This function allows for more efficient monitoring of different databases for multiple purposes - for example, checking specific database queues, usage statistics and so on. Zabbix supports unixODBC, which is one of the most commonly used open source ODBC API implementations.  ::: noteimportant See also the [known issues](/manual/installation/known_issues#odbc_checks) for ODBC checks. :::
zh-cn	#### 概述  ODBC监控对应于Zabbix前端中的 *数据库监控* 监控项类型。  ODBC是C语言编写的中间件API，用于访问数据库管理系统(DBMS)。 ODBC是由Microsoft开发的，后来被移植到了其它平台。  Zabbix可以查询任何支持ODBC的数据库。实现这个目标，Zabbix不直接连接数据库，而是使用ODBC接口并在ODBC中设置的驱动程序。该功能允许出于多种目的，更加有效地监视不同的数据库。例如，检测特定的数据库队列、使用统计信息等。Zabbix支持unixODBC，是最常用的开源ODBC API实现之一。  ::: noteimportant 更多信息请查看 ODBC检查的 [已知问题](/manual/installation/known_issues#odbc_checks) 。 :::