en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Debian/Ubuntu.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x    |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x    |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x    |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x    |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x    |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x    |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x    |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x    |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::
zh-cn	#### 概述  本章节介绍如何使用由官方发布的、基于 Debian/Ubuntu 系统的Zabbix 二进制升级包，将当前应用的Zabbix **5.4**.x 版本[升级](zh/manual/installation/upgrade)到最新的 Zabbix **6.0**.x 版本。  虽然Zabbix官方并未强制要求需要及时升级 Zabbix agents（推荐升级），但在使用Zabbix 的过程中，需要保持 Zabbix server 和 proxies 保持 [相同的版本](zh/manual/appendix/compatibility)。因此，在服务器和代理服务器升级过程中，Zabbix Server 和所有的 proxies 都必须暂停进程以完成升级。在升级过程中不推荐坚持所有 Zabbix proxy 的运行，完成升级后所有的旧数据都会被摒弃。并且除非 proxy 的配置已完成同步操作，否则不会有新的数据上传。  请注意，若您在 proxy 端应用 SQLite 数据库，那么 proxy 升级之前所存储的数据将全部被清除。因为 SQLite 数据库的升级操作是不被支持的并且 SQLite 数据库文档需要被手动清除。当 proxy 第一次启动时，发现 SQLite 文档不存在，那么 proxy 会自动生成数据库文档。  6.0版本升级的时间长短取决于数据库的总体大小。  ::: 重要提示 请务必在升级前仔细阅读相关的**升级文档！** :::  提供以下升级说明:  |当前版本|阅读完整的升级说明|不同版本间重要变化| |------------|-----------------------|---------------------------------------| |5.4.x    |适用于:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|提高了最低要求的数据库版本；<br>若数据库版本不满足要求，Server/proxy 将不会启动；<br>由于架构发生变化，旧的审计日志将会被摒弃。| |5.2.x    |适用于:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|提高了对数据库最低版本的要求；<br>所有的聚合监控项将被视为单独的监控项直接删除。| |5.0.x LTS|适用于:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|PHP组件最低版本组件由 7.2.0 升到 7.2.5。| |4.4.x    |适用于:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|放弃对 IBM DB2 的支持；<br>PHP组件最低版本组件由 5.4.0 升到 7.2.5；<br>提高了对数据库最低版本的要求；<br>改变了 Zabbix PHP 文档目录。| |4.2.x    |适用于:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting 媒体类型删除。| |4.0.x LTS|适用于:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|旧版本的 Zabbix proxies 将不会再向升级过的 server 发送数据；<br>新版本的agent 不再能够与旧的 Zabbix server 一同运作。| |3.4.x    |适用于:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' 与 'zlib' 库强制应用；<br>取消对纯文本协议的支持，并且强制要求标头配置；<br>不再支持1.4版本之前的 Zabbix agents ；<br>若启用 proxy 的被动模式，那么 Server 参数是必须要配置的参数。| |3.2.x    |适用于:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite 类型的数据库不再作为 Zabbix server/frontend 的支持类型；<br>Perl Compatible Regular Expressions (PCRE) 兼容正则表达式，替换了 POSIX；<br>Zabbix server 强制要求应用 'libpcre' 与 'libevent'库；<br>为用户参数添加了退出代码检查、远程命令和不标注 'nowait' 标志的 system.run[] 监控项以及 Zabbix server 执行的脚本；<br>要求升级 Zabbix Java gateway 以支持新版本功能。| |3.0.x LTS|适用于:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|根据数据库历史表的大小，数据库升级的进程可能会很长。| |2.4.x    |适用于:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|PHP组件的最低版本要求由 5.3.0 升级到 5.4.0；<br>LogFile agent 参数必须进行配置说明| |2.2.x LTS|适用于:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|移除了基于节点的分布式监控| |2.0.x    |适用于:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|对PHP要求的最低版本从 5.1.6 升到 5.3.0；<br>为了支持 server 的正常运作，需要支持大小写识别的 MySQL 数据库；为了使 Zabbix server 正常运作，需要对 MySQL 数据库进行字符设定，需设定字符为 utf8 和 utf8\_bin 。请查阅 [数据库创建脚本](zh/manual/appendix/install/db_scripts#mysql).<br>PHP扩展更改'mysql'为现在的 'mysqli'。|  您也可以参考如下6.0版本的[安装需求](zh/manual/installation/requirements) 。  ::: 注意事项 对于正在运行中的项目，用户可以考虑在对 Zabbix 进行升级时，同时开启两路 SSH 协议登录，一路用于运行软件的升级操作，一路用于监控 server/proxy 的 log 文档。 举例如下： 运行`tail -f zabbix_server.log`或者`tail -f zabbix_proxy.log`在第二路SSH连接，方便用户通过最新的log文档对升级过程进行实时监控，发现可能存在的问题或错误。 :::

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Red Hat Enterprise Linux/CentOS.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x|For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|<| |5.2.x|For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x|For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x|For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x|For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x|For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x|For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x|For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::  
zh-cn	####概述  本章节提供了使用基于Red Hat Enterprise Linux/CentOS 系统，由官方发布的Zabbix二进制包，将Zabbix版本由**5.4**.x 成功升级到 **6.0**.x 所需的步骤[升级](/manual/installation/upgrade)  虽说 Zabbix agents非强制性进行升级版本（但推荐升级），但 Zabbix server and proxies必须是[相同主版本]。因此，在服务器代理设置中，Zabbix 服务器和所有代理都必须停止其服务并进行升级操作。在Zabbix server 升级期间保持 proxies正常运行并不会带来任何好处，因为在 proxies升级期间，它们的旧数据将被丢弃，并且在proxy配置与server同步前不会采集新数据。  请注意，若Proxy的数据库为SQLite类型，其保留的历史数据会在版本升级完成后全部被删除，因为Zabbix proxies不支持 SQLite 数据库升级并且必须手动删除 SQLite 数据库文件。当第一次启动proxy并且缺少 SQLite 数据库文件时，proxy会自动创建SQLite 数据库文件。  根据数据库大小，数据库版本升级到 6.0 可能需要很长时间。  ::: 重要事项 升级前请务必阅读相关的**升级说明！** :::  以下为提供升级Zabbix版本说明：  |升级前的版本|阅读完整的升级说明|Zabbix版本升级间最重要的变化| |------------|-----------|------------ --------------------------| |5.4.x|适用于：<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|<| |5.2.x|适用于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600) |提高了最低要求的数据库版本；<br>将聚合项作为单独的类型删除。| |5.0.x|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|所需的PHP 最低版本从 7.2.0 要求为 7.2.5。| |4.4.x|适用于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|放弃对 IBM DB2 的支持；<br >最低要求的 PHP 版本从 5.4.0 提高到 7.2.0；<br>最低要求的数据库版本提高；<br>更改了 Zabbix PHP 文件目录。| |4.2.x|适用于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|已删除 Jabber、Ez 短信媒体类型。| |4.0.x LTS|适用于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2]( https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br >Zabbix [6.0](/manual/installation/upgrade_notes_600)|旧的代理不再能够向升级的服务器报告数据；<br>新的代理不再能够与旧的 Zabbix 服务器一起工作。| |3.4.x|适用于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br> Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' 和 'zlib' 库现在强制；<br>删除对纯文本协议的支持，并且强制标头；<br>不再支持 1.4 之前版本的 Zabbix agents；<br>被动模式的proxy配置中的 Server 参数现在是强制要求的。| |3.2.x|适用于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br> Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|为 Zabbix server和前端删除了作为后端数据库的 SQLite 支持；<br>支持 Perl 兼容正则表达式 (PCRE)，而不是扩展 POSIX；<br> Zabbix 服务器强制使用“libpcre”和“libevent”库；<br>为用户参数添加了退出代码检查仪表、远程命令和不带 'nowait' 标志的 system.run\[\] 项目以及 Zabbix 服务器执行的脚本；<br>必须升级 Zabbix Java 网关以支持新功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2]( https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br >Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/安装/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|数据库升级可能会很慢，具体取决于历史表的大小。| |2.4.x|适用于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br> Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 5.3.0 提高到 5.4.0<br>LogFile ag ent 参数必须指定| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4]( https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br >Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/安装/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/文档/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/安装/upgrade_notes_600)|移除了基于节点的分布式监控| |2.0.x|适用于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240))<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br> Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.  

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Red Hat Enterprise Linux/CentOS.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x    |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x    |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x    |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x    |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x    |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x    |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x    |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x    |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::
zh-cn	#### 概述  本章节介绍如何使用由官方发布的、基于Red Hat 企业版 Linux/CentOS 系统的Zabbix二进制升级包，将当前应用的Zabbix **5.4**.x 版本[升级](zh/manual/installation/upgrade) 到最新的 Zabbix **6.0**.x 版本。  虽然Zabbix官方并未强制要求需要及时升级 Zabbix agents（推荐升级），但在使用Zabbix 的过程中，需要保持 Zabbix server 和 proxies 保持 [相同的版本](zh/manual/appendix/compatibility)。因此，在服务器和代理服务器升级过程中，Zabbix Server 和所有的 proxies 都必须暂停进程以完成升级。在升级过程中不推荐坚持所有 Zabbix proxy 的运行，完成升级后所有的旧数据都会被摒弃。并且除非 proxy 的配置已完成同步操作，不会有新的数据上传。  请注意，若您在 proxy 端应用 SQLite 数据库，那么 proxy 升级之前所存储的数据将全部被清除。因为 SQLite 数据库的升级操作是不被支持的并且 SQLite 数据库文档需要被手动清除。当 proxy 第一次启动时，发现 SQLite 文档不存在，那么 proxy 会自动生成数据库文档。  6.0版本升级的时间长短取决于数据库的总体大小。  ::: 重要提示 请务必在升级前仔细阅读相关的**升级文档！** :::  下表中列举了当前所有可参考的升级文档：  |当前版本|阅读完整的升级文档|不同版本间的重要升级内容| |----------|-----------------------|---------------------------------------| |5.4.x    |适用于：<br>Zabbix [6.0](zh/manual/installation/upgrade_notes_600)|提高了最低要求的数据库版本；<br>若数据库版本不满足要求，Server/proxy 将不会启动；<br>由于架构发生变化，旧的审计日志将会被摒弃。| |5.2.x    |适用于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](zh/manual/installation/upgrade_notes_600)|提高了对数据库最低版本的要求；<br>所有的聚合监控项将被视为单独的监控项直接删除。| |5.0.x LTS|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](zh/manual/installation/upgrade_notes_600)|PHP组件最低版本组件由 7.2.0 升到 7.2.5。| |4.4.x    |适用于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](zh/manual/installation/upgrade_notes_600)|放弃对 IBM DB2 的支持；<br>PHP组件最低版本组件由 5.4.0 升到 7.2.5；<br>提高了对数据库最低版本的要求；<br>改变了 Zabbix PHP 文档目录。| |4.2.x    |适用于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting 媒体类型删除。| |4.0.x LTS|适用于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|旧版本的 Zabbix proxies 将不会再向升级过的 server 发送数据；<br>新版本的agent 不再能够与旧的 Zabbix server 一同运作。| |3.4.x    |适用于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](zh/manual/installation/upgrade_notes_600)|'libpthread' 与 'zlib' 库强制应用；<br>取消对纯文本协议的支持，并且强制要求标头配置；<br>不再支持1.4版本之前的 Zabbix agents ；<br>若启用 proxy 的被动模式，那么 Server 参数是必须要配置的参数。| |3.2.x    |适用于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite 类型的数据库不再作为 Zabbix server/frontend 的支持类型；<br>Perl Compatible Regular Expressions (PCRE) 兼容正则表达式，替换了 POSIX；<br>Zabbix server 强制要求应用 'libpcre' 与 'libevent'库；<br>为用户参数添加了退出代码检查、远程命令和不标注 'nowait' 标志的 system.run[] 监控项以及 Zabbix server 执行的脚本；<br>要求升级 Zabbix Java gateway 以支持新版本功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|根据数据库历史表的大小，数据库升级的进程可能会很长。| |2.4.x    |适用于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|PHP组件的最低版本要求由 5.3.0 升级到 5.4.0；<br>LogFile agent 参数必须进行配置说明| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|移除了基于节点的分布式监控。| |2.0.x    |适用于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|对PHP要求的最低版本从 5.1.6 升到 5.3.0；<br>为了支持 server 的正常运作，需要支持大小写识别的 MySQL 数据库；为了使 Zabbix server 正常运作，需要对 MySQL 数据库进行字符设定，需设定字符为 utf8 和 utf8\_bin 。请查阅 [数据库创建脚本](zh/manual/appendix/install/db_scripts#mysql).<br>PHP扩展更改'mysql'为现在的 'mysqli'。|  您也可以参考如下6.0版本的[安装需求](zh/manual/installation/requirements) 。  ::: 注意事项 对于正在运行中的项目，用户可以考虑在对 Zabbix 进行升级时，同时开启两路 SSH 协议登录，一路用于运行软件的升级操作，一路用于监控 server/proxy 的 log 文档。 举例如下： 运行`tail -f zabbix_server.log`或者`tail -f zabbix_proxy.log`在第二路SSH连接，方便用户通过最新的log文档对升级过程进行实时监控，发现可能存在的问题或错误。 :::

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix packages for Red Hat Enterprise Linux.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |--|--|------| |5.4.x    |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x    |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x    |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x    |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x    |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x    |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x    |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x    |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::
zh-cn	#### 概述  本节提供使用 Red Hat Enterprise Linux 的官方 Zabbix 软件包从 Zabbix **5.4**.x 成功 [升级](/manual/installation/upgrade) 到 Zabbix **6.0**.x 所需的步骤。  虽然升级 Zabbix agent不是强制性的（但推荐），但 Zabbix 服务器和代理必须是[相同的主要版本](/manual/appendix/compatibility)。 因此，在服务器-代理设置中，必须停止和升级 Zabbix 服务器和所有代理。在服务器升级期间保持代理运行不再带来任何好处，因为在代理升级期间，它们的旧数据将被丢弃，并且不会收集新数据直到代理配置与服务器同步。  请注意，对于代理上的 SQLite 数据库，升级前来自代理的历史数据将丢失，因为不支持 SQLite 数据库升级并且必须手动删除 SQLite 数据库文件。 proxy 第一次启动时 SQLite 数据库文件丢失，proxy 会自动创建。  根据数据库大小，数据库升级到版本 6.0 可能需要很长时间。  ::: notewarning 升级前请务必阅读相关的**升级说明！** ::::  提供以下升级说明：  |升级自|阅读完整的升级说明|版本之间最重要的变化| |--|--|------| |5.4.x · |对于：<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|所需的最低数据库版本已提高；<br>如果数据库过时，服务器/代理将不会启动；<br>审计日志记录丢失 因为数据库结构改变。| |5.2.x · |对于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600 )|所需的最低数据库版本已提高；<br>将删除的监控项汇总为单独的类型。| |5.0.x LTS|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www. zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 7.2.0 升级到 7.2.5。| |4.4.x · |对于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www. zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0]( /manual/installation/upgrade_notes_600)|放弃对 IBM DB2 的支持；<br>所需的最低 PHP 版本从 5.4.0 提高到 7.2.0；<br>所需的最低数据库版本已提高；<br>更改了 Zabbix PHP 文件目录。| |4.2.x · |对于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www. zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4]( https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber、Ez Texting 媒体类型已删除。| |4.0.x LTS|对于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www. zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2]( https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br >Zabbix [6.0](/manual/installation/upgrade_notes_600)|较旧的代理不再可以向升级后的服务器报告数据；<br>较新的代理将不再能够与较旧的 Zabbix 服务器一起工作。| |3.4.x · |对于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www. zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0]( https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br >Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' 和 'zlib' 库 现在是强制性的；<br>对纯文本协议的支持被删除，标头是强制性的；<br>1.4 之前版本的 Zabbix 代理不再受支持；<br>被动代理配置中的服务器参数现在是强制性的。| |3.2.x · |对于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www. zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4]( https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br >Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/ installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite 支持作为 Zabbix 服务器/前端的后端数据库；<br>支持 Perl 兼容正则表达式 (PCRE) 而不是 POSIX 扩展；<br >'libpcre' 和 'libevent' 库对于 Zabbix 服务器是必需的；<br>为用户 p 添加了退出代码检查 参数、远程命令和 system.run\[\] 项目没有 'nowait' 标志以及 Zabbix 服务器执行的脚本；<br>Zabbix Java 网关必须升级以支持新功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www. zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2]( https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br >Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/ installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|数据库升级 可能会很慢，具体取决于历史表的大小。| |2.4.x · |对于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www. zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0]( https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br >Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/ 安装/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/ 文档/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 5.3.0 升级到 5.4.0<br>LogFile 必须指定代理参数| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www. zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4]( https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br >Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/ 安装/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/ 文档/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/ installation/upgrade_notes_600)|删除了基于节点的分布式监控| |2.0.x · |对于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www. zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2]( https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br >Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/ 安装/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/ 文档/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https:// w ww.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|所需的最低 PHP 版本从 5.1.6 升级到 5.3.0；<br>正确的服务器工作需要大小写敏感的MySQL 数据库； 字符集 utf8 和 utf8\_bin 排序规则是 Zabbix 服务器与 MySQL 数据库正常工作所必需的。 请参阅[数据库创建脚本](/manual/appendix/install/db_scripts#mysql)。<br>需要“mysqli”PHP 扩展而不是“mysql”|  您可能还想查看 6.0 的 [要求](/manual/installation/requirements)。  ::: notetip 在升级期间运行两个并行的 SSH 会话可能很方便，在一个会话中执行升级步骤并在另一个会话中监视服务器/代理日志。 例如，在第二个 SSH 会话中运行“tail -f zabbix_server.log”或“tail -f zabbix_proxy.log”，实时显示最新的日志文件条目和可能的错误。 这对于生产实例可能至关重要。 ::::

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix sources.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  ::: noteimportant It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. :::  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x|For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|<| |5.2.x|For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x|For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x|For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x|For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x|For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x|For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x|For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::  
zh-cn	#### 概述 本节提供使用 Zabbix 官方源码包从 Zabbix **5.4**.x 成功[升级](/manual/installation/upgrade)到 Zabbix **6.0**.x 所需的步骤。  虽然升级 agents 不是强制性的（但推荐），但 Server 和 Proxy 必须具有相同的[主版本](/manual/appendix/compatibility)。因此，在 Server-Proxy 这样的结构中，Zabbix Server 和所有 Proxy 都必须停止服务并进行升级。在升级期间保持 Proxy 运行没有任何用处，旧数据将被丢弃，在 Proxy 的配置信息与 Server 同步之前不会收集新数据。  ::: noteimportant 不可能再让未升级的低版本 Proxy 向高版本的 Server 端发送数据。Zabbix 从未推荐或支持这种方法，现在已正式禁用，因而 Server 将忽略来自未升级 Proxy 的数据。 :::  由于不支持 SQLite 数据库升级，SQLite 数据库文件必须手动删除，因此升级前 proxy 的历史数据将丢失。proxy 第一次启动时会缺少 SQLite 数据库文件，但 proxy 会自动创建它。  根据数据库大小，数据库升级到 6.0 版本可能需要很长时间。  ::: notewarning 在升级前请务必阅读相关**升级说明!** :::  官方提供以下升级说明：  |升级前版本|阅读完整的升级说明|版本之间最主要变更| |------------|-----------------------|---------------------------------------| |5.4.x|适用于：<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)| | |5.2.x|适用于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|要求的最低数据库版本提高；<br>聚合监控项开始作为一个单独的监控项类型。| |5.0.x|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|要求的最低 PHP 版本从 7.2.0 提高到 7.2.5。| |4.4.x|适用于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)|不再支持 IBM 的 DB2 数据库；<br>要求的最低 PHP 版本从 5.4.0 提高到 7.2.0；<br>要求的最低数据库版本提高；<br>更改了  Zabbix PHP 的文件目录。| |4.2.x|适用于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|删除了 Jabber、Ez 短信介质类型。| |4.0.x LTS|适用于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|低版本 proxy 不再可以向升级后的高版本 server 发送数据；<br>高版本的 agent 将不再适配低版本的 server。| |3.4.x|适用于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|“libpthread”和“zlib”库现在是强制性的；<br>对纯文本协议的支持被丢弃，并且头部是强制性的；<br>不再支持 1.4 之前版本的 Zabbix agent；<br>被动 proxy 配置文件中的 Server 参数现在是必需的。| |3.2.x|适用于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)| Zabbix server/前端 开始支持 SQLite 数据库作为后端存储库；<br>Perl 兼容正则表达式 (PCRE) 代替 POSIX 扩展；<br>Zabbix Server 必须使用“libpcre”和“libevent”库；<br>为用户参数、远程命令、不带有 “nowait” 标志的 system.run\[\] 监控项和 Zabbix Server 执行脚本添加了退出代码检查功能；<br>Zabbix Java 网关必须升级以支持新功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|数据库升级可能会很慢，主要取决于历史表的大小。| |2.4.x|F适用于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|要求的最低 PHP 版本从 5.3.0 提高到 5.4.0；<br>必须指定agent配置文件中的 LogFile 参数。| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|移除了基于节点的分布式监控。| |2.0.x|适用于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|要求的最低 PHP 版本从 5.1.6 提高到 5.3.0；<br>服务端正常运行需要区分大小写的 MySQL 数据库；Zabbix Server 端需要使用 utf8 和 utf8\_ 字符集才能与 MySQL 数据库适配。点击 [数据库创建脚本](/manual/appendix/install/db_scripts#mysql) 获取创建数据库和表结构的流程。<br>PHP 扩展需要'mysqli' 而不是以前的 'mysql'。|  查看关于 6.0 的其他 [配置要求](/manual/installation/requirements)。  ::: notetip 在升级期间同时运行两个并行的 SSH 会话可能会比较方便，其中一个执行升级步骤，另一个查看实时的 Server/Proxy 的日志。例如，在第二个 SSH 会话中运行 `tail -f zabbix_server.log` 或 `tail -f zabbix_proxy.log` 实时显示最新返回的日志文件记录和可能的错误。这对于生产环境可能很关键。 :::  

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **5.4**.x to Zabbix **6.0**.x using official Zabbix sources.  While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the [same major version](/manual/appendix/compatibility). Therefore, in a server-proxy setup, Zabbix server and all proxies have to be stopped and upgraded. Keeping proxies running no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.  ::: noteimportant It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies. :::  Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.  Depending on database size the database upgrade to version 6.0 may take a long time.  ::: notewarning Before the upgrade make sure to read the relevant **upgrade notes!** :::  The following upgrade notes are available:  |Upgrade from|Read full upgrade notes|Most important changes between versions| |------------|-----------------------|---------------------------------------| |5.4.x    |For:<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Server/proxy will not start if outdated database;<br>Audit log records lost because of database structure change.| |5.2.x    |For:<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required database versions upped;<br>Aggregate items removed as a separate type.| |5.0.x LTS|For:<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 7.2.0 to 7.2.5.| |4.4.x    |For:<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Support of IBM DB2 dropped;<br>Minimum required PHP version upped from 5.4.0 to 7.2.0;<br>Minimum required database versions upped;<br>Changed Zabbix PHP file directory.| |4.2.x    |For:<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Jabber, Ez Texting media types removed.| |4.0.x LTS|For:<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Older proxies no longer can report data to an upgraded server;<br>Newer agents no longer will be able to work with an older Zabbix server.| |3.4.x    |For:<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|'libpthread' and 'zlib' libraries now mandatory;<br>Support for plain text protocol dropped and header is mandatory;<br>Pre-1.4 version Zabbix agents are no longer supported;<br>The Server parameter in passive proxy configuration now mandatory.| |3.2.x    |For:<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|SQLite support as backend database dropped for Zabbix server/frontend;<br>Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;<br>'libpcre' and 'libevent' libraries mandatory for Zabbix server;<br>Exit code checks added for user parameters, remote commands and system.run\[\] items without the 'nowait' flag as well as Zabbix server executed scripts;<br>Zabbix Java gateway has to be upgraded to support new functionality.| |3.0.x LTS|For:<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Database upgrade may be slow, depending on the history table size.| |2.4.x    |For:<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.3.0 to 5.4.0<br>LogFile agent parameter must be specified| |2.2.x LTS|For:<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Node-based distributed monitoring removed| |2.0.x    |For:<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Minimum required PHP version upped from 5.1.6 to 5.3.0;<br>Case-sensitive MySQL database required for proper server work; character set utf8 and utf8\_bin collation is required for Zabbix server to work properly with MySQL database. See [database creation scripts](/manual/appendix/install/db_scripts#mysql).<br>'mysqli' PHP extension required instead of 'mysql'|  You may also want to check the [requirements](/manual/installation/requirements) for 6.0.  ::: notetip It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run `tail -f zabbix_server.log` or `tail -f zabbix_proxy.log` in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances. :::
zh-cn	#### 概述  本节提供使用官方 Zabbix 源码包从 Zabbix **5.4**.x  [升级](/manual/installation/upgrade) 到Zabbix **6.0**.x 所需的步骤。  尽管升级 Zabbix agent 不是强制性的（但推荐），但 Zabbix server 和 proxy 必须是 [相同的主版本](/manual/appendix/compatibility)。因此，在 server-proxy 架构中，Zabbix server 和所有的 proxy  都必须停止并升级。保持 proxy 运行没有任何用处，因为在 proxy 升级期间，它们的旧数据将被丢弃，并且在  proxy 配置与 server 同步之前不会收集新数据。  ::: noteimportant 使用较新的升级的 server 并让较旧但未升级的 proxy 向其发送数据不可能再成功启动。Zabbix 从未推荐或支持这种方法，现在已正式禁用，因为 server 将忽略来自未升级 proxy 的数据。 :::  请注意，proxy 如果使用 SQLite 数据库，升级前来自 proxy 的历史数据将丢失，因为不支持 SQLite 数据库表结构升级并且必须手动删除 SQLite 数据库文件。初次启动 proxy 时如果缺少 SQLite 数据库文件，proxy 会自动创建它。  根据数据库大小，数据库升级到版本 6.0 可能需要很长时间。  ::: notewarning 升级前请务必阅读相关 **升级说明！** :::  提供以下升级说明：  |从X版本升级|阅读完整的升级说明|版本之间最重要的变化| |------------|-----------------------|---------------------------------------| |5.4.x · |适用于：<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|提高了最低要求的数据库版本；<br>如果数据库版本过低，Server/proxy 将无法启动；<br>由于数据库结构更改，审计日志记录丢失。| |5.2.x · |适用于：<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|提高了最低要求的数据库版本；<br>Aggregate 监控项作为单独类型将删除。| |5.0.x LTS|适用于：<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 7.2.0 提高到 7.2.5。| |4.4.x · |适用于：<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|不再支持 IBM DB2；<br>最低要求的 PHP 版本从 5.4.0 提高到 7.2.0；<br>提高了最低要求的数据库版本；<br>更改了 Zabbix PHP 文件目录。| |4.2.x · |适用于：<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|删除了 Jabber、Ez 短信媒体类型。| |4.0.x LTS|适用于：<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|旧版本的 proxy 不再可以向升级的 server 报告数据；<br>高版本的 agent 将不再能够与较低版本的 Zabbix server 匹配。| |3.4.x · |适用于：<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|强制使用 'libpthread' 和 'zlib' 库；<br>对纯文本协议的支持被丢弃，并且头部是强制性的；<br>1.4 以前版本的 Zabbix agent 将不再支持；<br>被动 proxy 配置中的 Server 参数现在是必需的。| |3.2.x · |适用于：<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|Zabbix server/前端支持 SQLite 作为数据库;<br>支持 Perl 兼容正则表达式 (PCRE) 而不是 POSIX 扩展；<br>Zabbix server 必须使用 'libpcre' 和 'libevent' 库；<br>为不带  'nowait' 标志的用户参数、远程命令和 system.run\[\] 监控项以及 Zabbix server 执行脚本添加了退出代码检查；<br>Zabbix Java gateway 必须升级以支持新功能。| |3.0.x LTS|适用于：<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.4/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|数据库升级可能会很慢，具体取决于历史表的大小。| |2.4.x · |适用于：<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 5.3.0 升级到 5.4.0；<br>agent 配置文件的的 LogFile 参数必须指定。| |2.2.x LTS|适用于：<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|移除了基于节点的分布式监控。| |2.0.x · |适用于：<br>Zabbix [2.2](https://www.zabbix.com/documentation/2.2/manual/installation/upgrade_notes_220)<br>Zabbix [2.4](https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_240)<br>Zabbix [3.0](https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300)<br>Zabbix [3.2](https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320)<br>Zabbix [3.4](https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_340)<br>Zabbix [4.0](https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400)<br>Zabbix [4.2](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_420)<br>Zabbix [4.4](https://www.zabbix.com/documentation/4.2/manual/installation/upgrade_notes_440)<br>Zabbix [5.0](https://www.zabbix.com/documentation/5.0/manual/installation/upgrade_notes_500)<br>Zabbix [5.2](https://www.zabbix.com/documentation/5.2/manual/installation/upgrade_notes_520)<br>Zabbix [5.4](https://www.zabbix.com/documentation/5.4/manual/installation/upgrade_notes_540)<br>Zabbix [6.0](/manual/installation/upgrade_notes_600)|最低要求的 PHP 版本从 5.1.6 提高到 5.3.0；<br>server 正常工作需要区分大小写的 MySQL 数据库；Zabbix server 需要 utf8 和 utf8\_bin 字符集排序规则才能与 MySQL 数据库正常工作。请参阅 [数据库创建脚本](/manual/appendix/install/db_scripts#mysql)。<br>'mysqli' 需要 PHP 扩展而不是  'mysql'。|  你可能还想参考 6.0 的其他 [需求](/manual/installation/requirements) 。  ::: notetip 在升级期间运行两个并行 SSH 会话可能会很方便，其中一个执行升级步骤，另一个监视 server/proxy 日志。例如，在第二个 SSH 会话中运行`tail -f zabbix_server.log` 或 `tail -f zabbix_proxy.log` 实时显示最新的日志文件条目和可能的错误。这对于生产实例可能很关键。 :::

en-us	#### Overview  This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) using official RPM and DEB packages provided by Zabbix for:  -   [Red Hat Enterprise     Linux/CentOS](/manual/installation/upgrade/packages/rhel_centos) -   [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu)
zh-cn	#### 概述 本章节提供使用 Zabbix 的 RPM 和 DEB 二进制包成功升级至 Zabbix 6.0 所需的步骤[升级](/manual/installation/upgrade) ：  -   [红帽企业 Linux/CentOS](/manual/installation/upgrade/packages/rhel_centos) -   [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu)

en-us	#### Overview  This section provides upgrade information for Zabbix **6.0**:  -   using packages:     -   for [Red Hat Enterprise         Linux](/manual/installation/upgrade/packages/rhel)     -   for         [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu)  ```{=html} <!-- --> ``` -   using [sources](/manual/installation/upgrade/sources)  Direct upgrade to Zabbix 6.0.x is possible from Zabbix **5.4**.x, **5.2**.x, **5.0**.x, **4.4**.x, **4.2**.x, **4.0**.x, **3.4**.x, **3.2**.x, **3.0**.x, **2.4**.x, **2.2**.x and **2.0**.x. For upgrading from earlier versions consult Zabbix documentation for 2.0 and earlier.
zh-cn	#### 概述  本章节提供了关于升级至 Zabbix **6.0** 的信息：  - 使用二进制包安装：      - 对于 [Red Hat Enterprise    Linux/CentOS](/manual/installation/upgrade/packages/rhel_centos)      - 对于 [Debian/Ubuntu](/manual/installation/upgrade/packages/debian_ubuntu)  ```{=html} <!-- --> ``` - 使用源码包 [sources](/manual/installation/upgrade/sources)  可以从 Zabbix **5.4**.x、**5.2**.x、**5.0**.x、**4.4**.x、**4.2**.x、**4.0**.x、**3.4**.x、**3.2**.x、**3.0**.x、**2.4**.x、**2.2**.x 和 * *2.0**.x 直接升级到 Zabbix 6.0.x。 要从早期版本升级，请参阅 2.0 及更早版本的 Zabbix 文档。

en-us	#### Overview  This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using SQL queries, whose results get automatically transformed into a JSON object suitable for low-level discovery.
zh-cn	#### 概述  此类低级别[自动发现](/manual/discovery/low_level_discovery) 通过使用SQL查询实现，其结果自动转换成一个匹配低级别自动发现的JSON格式的JSON对象。

en-us	#### Overview  This widget contains shortcuts to the most needed graphs, sorted alphabetically.  The list of shortcuts is populated when you [view](/manual/web_interface/frontend_sections/monitoring/hosts/graphs) a graph and then click on its ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/button_add_fav.png) *Add to favorites* button.  All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets.
zh-cn	#### 概述  该组件包含了最常用的图表的快捷方式，按字母排序。  当你[查看](/manual/web_interface/frontend_sections/monitoring/hosts/graphs)一个图表时，点击它的![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/button_add_fav.png)*添加到收藏夹*按钮。  所有的配置参数对所有组件都是 [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的。

en-us	#### Overview  This widget contains shortcuts to the most needed maps, sorted alphabetically.  The list of shortcuts is populated when you [view](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps) a map and then click on its ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/button_add_fav.png) *Add to favorites* button.  All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets.
zh-cn	#### 概述  该组件包含了最常用的拓扑图的快捷方式，按字母排序。  当你[查看](/manual/web_interface/frontend_sections/monitoring/maps#viewing_maps)一个拓扑图时，点击它的![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/button_add_fav.png)*添加到收藏夹*按钮。  所有的配置参数对所有组件都是 [通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 的。

en-us	#### Overview  This widget displays a status summary of the active network discovery rules.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/discovery_status.png)  All configuration parameters are [common](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters)  for all widgets.
zh-cn	#### 概述  此组件显示活动的网络发现规则的状态汇总。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/discovery_status.png)  所有配置参数都是组件的[通用](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#common-parameters) 参数

en-us	#### Overview  This widget displays a status summary of the active web monitoring scenarios.
zh-cn	#### 概述  这个小部件显示Web拨测 监视场景的状态摘要。

en-us	#### Overview  This widget displays the content retrieved from the specified URL.
zh-cn	#### 概述  这个组件显示从指定的网址获取的内容。

en-us	#### Overview  This widget displays the same information as in *Reports* → *[System information](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*, however, a single dashboard widget can only display either the system stats or the high availability nodes at a time (not both).
zh-cn	#### 概述 这个组件显示的信息与*报告*→*[系统信息](/manual/web_interface/frontend_sections/reports/status_of_zabbix)*中的信息类似，但是单个仪表盘组件只能显示系统统计信息或高可用性节点（不能同时显示）。

en-us	#### Overview  This widget is useful for displaying [SLA reports](/manual/web_interface/frontend_sections/services/sla_report).  Functionally it is similar to the *Services* -> *SLA report* section.
zh-cn	#### 概览  该组件用于显示 [SLA报表](/manual/web_interface/frontend_sections/services/sla_report).  功能上类似于 *服务* -> *SLA报表* 选项。

en-us	#### Overview  This widget is useful for displaying the value of a single item  prominently.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_single.png)  Besides the value itself, additional elements can be displayed, if desired:  - time of the metric - item description - change indicator for the value  - item unit   The widget can display numeric and string values. String values are displayed on a single line and truncated, if needed. "No data" is displayed, if there is no value for the item.  Clicking on the value leads to an ad-hoc graph for numeric items or latest data for string items.  The widget and all elements in it can be visually fine-tuned using [advanced configuration](#advanced-configuration) options, allowing to create a  wide variety of visual styles:  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets.png)
zh-cn	#### 概述  此组件对于突出显示单个监控项的数值很帮助。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_single.png)  除了数值本身，如果需要，还可以显示其他元素：  - 数值统计的时间 - 监控项描述 - 数值变化的指示器 - 监控项单位  该组件可以显示数字和字符串文本。字符串值单行显示，如果需要的话会被截断。如果没有项目的值，则显示 "无数据"。  点击该值会出现数据监控项的ad-hoc图表或监控项的最新数据。  组件和其中的所有元素可以使用 [高级配置](#advanced-configuration) 选项进行视觉上的微调，允许创建各种各样的视觉风格：  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets.png)

en-us	#### Overview  This widget provides a way to create custom tables for displaying the data situation,  allowing to display *Top N*-like reports and progress-bar reports useful for capacity planning.  The maximum number of hosts that can be displayed is 100.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.png){width="527"}  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts2.png)
zh-cn	#### 概览  此小部件提供了一种创建自定义表格以显示数据情况的方法，允许显示对容量规划有用的类似*Top N*的报告和进度条报告。  最大可显示100个主机。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts.png){width="527"}  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/top_hosts2.png)

en-us	#### Overview  Though Zabbix offers a large number of webhook integrations available out-of-the-box, you may want to create your own webhooks instead. This section provides examples of custom webhook scripts (used in the *Script* parameter). See [webhook](/manual/config/notifications/media/webhook) section for description of other webhook parameters.
zh-cn	#### 概述  尽管Zabbix提供了大量现成的webhook集成，但您可能想要创建自己的webhook。本节提供了自定义webhook脚本的示例. (在 *Script* 参数中使用). 有关其他webhook参数的说明，请参见[webhook](/manual/config/notifications/media/webhook)

en-us	#### Overview  To configure a host in Zabbix frontend, do the following:  -   Go to: *Configuration → Hosts* or *Monitoring → Hosts* -   Click on *Create host* to the right (or on the host name to edit an     existing host) -   Enter parameters of the host in the form  You can also use the *Clone* and *Full clone* buttons in the form of an existing host to create a new host. Clicking on *Clone* will retain all host parameters and template linkage (keeping all entities from those templates). *Full clone* will additionally retain directly attached entities (applications, items, triggers, graphs, low-level discovery rules and web scenarios).  *Note*: When a host is cloned, it will retain all template entities as they are originally on the template. Any changes to those entities made on the existing host level (such as changed item interval, modified regular expression or added prototypes to the low-level discovery rule) will not be cloned to the new host; instead they will be as on the template.
zh-cn	#### 概述  按照以下步骤可以在 Zabbix 前端页面创建主机：  -   点击: *Configuration（配置） → Hosts（主机）* 或 *Monitoring（监测） → Hosts（主机）* -   在页面右侧点击 *Create host（创建主机）*  (点击主机名编辑一个已有的主机) -   在表单中输入主机的相关参数  你也可以在已经存在的主机上使用 *Clone（克隆）* 和 *Full clone（全克隆）* 按钮创建一台新的主机。点击 *Clone（克隆）* 将保留所有的主机参数和模板链接（保留这些模版中的所有实体），*Full clone（全克隆）* 将额外保留直接附加的实体（应用集、监控项、触发器、视图、自动发现规则和 Web 定制场景）。  *注意*: 当主机被克隆时，它将保留最初在模板上的所有模板实体。在现有主机级别上对这些实体所做的任何更改（例如更改的监控间隔、修改正则表达式或添加原型到底层发现规则）都不会复制到新主机；相反，它们将与最初模板上的保持一致。

en-us	#### Overview  To configure a network discovery rule used by Zabbix to discover hosts and services:  -   Go to *Configuration → Discovery* -   Click on *Create rule* (or on the rule name to edit an existing one) -   Edit the discovery rule attributes
zh-cn	#### 概述  配置用于发现主机和服务的网络发现规则：  -   找到 *配置→ 网络发现* -   点击 *创建规则* (或点击规则名称，编辑现有规则) -   编辑规则属性

en-us	#### Overview  To configure a trigger, do the following:  -   Go to: *Configuration* → *Hosts* -   Click on *Triggers* in the row of the host -   Click on *Create trigger* to the right (or on the trigger name to     edit an existing trigger) -   Enter parameters of the trigger in the form  See also [general information](/manual/config/triggers) on triggers and their calculation times.
zh-cn	#### 概述  配置一个触发器，按以下步骤操作：  -   进入： *配置* → *主机* -   点击主机一行的 *触发器* -   点击右上角的 *创建触发器*（或者点击触发器名称去修改一个已存在的触发器） -   在窗口中输入触发器的参数  另请参阅有关触发器及其计算时间的 [一般信息](/manual/config/triggers)。

en-us	#### Overview  To configure e-mail as the delivery channel for messages, you need to configure e-mail as the media type and assign specific addresses to users.  ::: noteclassic  Multiple notifications for single event will be grouped together on the same email thread.  :::
zh-cn	#### 概述  若要使用电子邮件作为消息发送的通道，那么您需要选择电子邮件作为媒介类型，同时为接收消息的用户指定具体的邮箱。  ::: noteclassic  同一事件的多个通知会由相同的邮件线程处理。 :::

en-us	#### Overview  To create an item in Zabbix frontend, do the following:  -   Go to: *Configuration* → *Hosts* -   Click on *Items* in the row of the host -   Click on *Create item* in the upper right corner of the screen -   Enter parameters of the item in the form  You can also create an item by opening an existing one, pressing the *Clone* button and then saving under a different name.
zh-cn	#### 概述  要在Zabbix管理页面创建一个监控项，请执行以下操作：  -   进入到: *配置* → *主机* -   在主机所在的行单击 *监控项* -   点击屏幕右上角的*创建监控项* -   在表单中输入监控项的参数  你也可以如此创建监控项：打开一个已有的监控项，按*克隆* 按钮，然后以不同的名称保存。

en-us	#### Overview  To make the calculation of trigger expressions, calculated items and some macros much faster, a value cache option is supported by the Zabbix server.  This in-memory cache can be used for accessing historical data, instead of making direct SQL calls to the database. If historical values are not present in the cache, the missing values are requested from the database and the cache updated accordingly.  To enable the value cache functionality, an optional **ValueCacheSize** parameter is supported by the Zabbix server [configuration](/manual/appendix/config/zabbix_server) file.  Two internal items are supported for monitoring the value cache: **zabbix\[vcache,buffer,<mode>\]** and **zabbix\[vcache,cache,<parameter>\]**. See more details with [internal items](/manual/config/items/itemtypes/internal).
zh-cn	#### 概览  为了更快地计算触发器表达式、计算或聚合类型监控项和一些宏。ZABBIX Server支持值缓存选项。\  这个内存缓存，可以用于访问历史数据，而不需要对数据库直接执行SQL调用。如果请求的历史值不在缓存中，则会从数据库请求缺失的数据，并相应地更新缓存。\  要启用值缓存功能，Zabbix服务器[配置](/zh/manual/appendix/config/zabbix_server)支持可选的**ValueCacheSize**参数。\  有两个内部的监控项来监控值缓存：**zabbix\[vcache，buffer，<mode>\]** 和 **zabbix\[vcache，cache，<parameter>\]**。查看更多细节，请参阅[内部监控项](/manual/config/items/itemtypes/internal)。

en-us	#### Overview  Trapper items accept incoming data instead of querying for it.  It is useful for any data you might want to "push" into Zabbix.  To use a trapper item you must:  -   have a trapper item set up in Zabbix -   send in the data into Zabbix
zh-cn	#### 概述  采集器监控项接收传入的数据，它不会去主动采集数据。  它接受任何形式的推送到zabbix server的数据。  要使用采集器监控项，你需要：  -   在Zabbix中建立一个采集器监控项 -   将数据发送到Zabbix server

en-us	#### Overview  Triggers are logical expressions that "evaluate" data gathered by items and represent the current system state.  While items are used to gather system data, it is highly impractical to follow these data all the time waiting for a condition that is alarming or deserves attention. The job of "evaluating" data can be left to trigger expressions.  Trigger expressions allow to define a threshold of what state of data is "acceptable". Therefore, should the incoming data surpass the acceptable state, a trigger is "fired" - or changes status to PROBLEM.  A trigger may have the following status:  |VALUE|DESCRIPTION| |-----|-----------| |OK|This is a normal trigger state.| |PROBLEM|Normally means that something happened. For example, the processor load is too high.|  In a basic trigger we may want to set a threshold for a five minute average of some data, for example, the CPU load. This is accomplished by defining a trigger expression where:  -   we apply the 'avg' function to the value received in the item key -   we use a five minute period for evaluation -   we set a threshold of '2'  ```{=html} <!-- --> ```     avg(host/key,5m)>2  This trigger will "fire" (become PROBLEM) if the five-minute average is over 2.  In a more complex trigger, the expression may include a **combination** of multiple functions and multiple thresholds. See also: [Trigger expression](/manual/config/triggers/expression).  Most trigger functions are evaluated based on [history](/manual/config/items/history_and_trends) data, while some trigger functions for long-term analytics, e.g. **trendavg()**, **trendcount()**, etc, use trend data.
zh-cn	#### 概述  触发器是“评估”监控项采集的数据和表示当前系统状况的逻辑表达式。  当我们使用监控项用于采集系统的数据时，一种不切合实际的情况是，我们无法始终等待一个警告或值得关注的条件。综上“评估”监控项数据的工作，我们可以留给触发器表达式。  触发器表达式允许定义一个什么状况的数据条件是“可接受”的阈值。因此，如果接收的数据超过了可接受的状态条件，则触发器会被触发 - 或将状态更改为异常。  一个触发器可以拥有下面几种状态：  |值|述| |---|---| |OK|这是一个正常的触发器状态。在旧版本的Zabbix中称为FALSE。| |PROBLEM|通常意味着发生了某些事情。例如，CPU负载较高。在旧版本的Zabbix中称为TRUE。|  在基本触发器配置中，我们可能希望为某些监控数据的五分钟平均值设置告警阈值，例如 CPU 负载。这是通过定义一个触发器表达式来完成的，其中：  - 我们将“avg”函数应用于监控项键中收到的值 - 我们使用五分钟的时间进行评估 - 我们将阈值设置为“2”  ```{=html} avg(host/key,5m)>2 ``` 如果五分钟平均值超过 2，此触发器将“触发”（成为问题PROBLEM）。  在更复杂的触发器中，表达式可能包含**组合** 具有多种功能和多种阈值。也可以看看：[Trigger expression](/manual/config/triggers/expression).    大多数触发函数的评估基于[history](/manual/config/items/history_and_trends)数据，而一些 用于长期分析的触发函数，例如**trendavg()**， **trendcount()** 等，使用趋势数据。

en-us	#### Overview  Update operations are available in actions with the following event sources:  -   *Triggers* - when problems are     [updated](/manual/acknowledges#updating_problems) by other users,     i.e. commented upon, acknowledged, severity has been changed, closed     (manually); -   *Services* - when the severity of a service has changed but the     service is still not recovered.  Both messages and remote commands are supported in update operations. While several operations can be added, escalation is not supported - all operations are assigned to a single step and therefore will be performed simultaneously.
zh-cn	#### 概述  更新操作在以下事件源中可用： - *触发器*-当问题被其他用户[更新](/manual/accounters#updateing_problems)时，即评论、确认、严重性已更改、关闭(手动)； - *服务*-当服务的严重性已更改，但服务仍未恢复时。  更新操作中同时支持消息和远程命令。虽然可以添加多个操作，但不支持升级-所有操作都分配给单个步骤，因此将同时执行。

en-us	#### Overview  User groups allow to group users both for organizational purposes and for assigning permissions to data. Permissions to monitoring data of host groups are assigned to user groups, not individual users.  It may often make sense to separate what information is available for one group of users and what - for another. This can be accomplished by grouping users and then assigning varied permissions to host groups.  A user can belong to any number of groups.
zh-cn	#### 概述 用户组允许出于组织目的和为数据分配权限的目的对用户进行分组。主机组监控数据的权限分配给用户组，而不是单个用户。  将一组用户的可用信息与另一组用户的可用信息分开通常是有意义的。这可以通过将用户分组，然后为主机组分配不同的权限来实现。  用户可以属于任意数量的组。

en-us	#### Overview  User macros are supported in Zabbix for greater flexibility, in addition to the macros [supported](/manual/appendix/macros/supported_by_location) out-of-the-box.  User macros can be defined on global, template and host level. These macros have a special syntax:      {$MACRO}  Zabbix resolves macros according to the following precedence:  1.  host level macros (checked first) 2.  macros defined for first level templates of the host (i.e.,     templates linked directly to the host), sorted by template ID 3.  macros defined for second level templates of the host, sorted by     template ID 4.  macros defined for third level templates of the host, sorted by     template ID, etc. 5.  global macros (checked last)  In other words, if a macro does not exist for a host, Zabbix will try to find it in the host templates of increasing depth. If still not found, a global macro will be used, if exists.  ::: notewarning If a macro with the **same name** exists on multiple linked templates of the same level, the macro from the template with the lowest ID will be used. Thus having macros with the same name in multiple templates is a configuration risk. :::  If Zabbix is unable to find a macro, the macro will not be resolved.  ::: noteimportant Macros (including user macros) are left unresolved in the Configuration section (for example, in the trigger list) by design to make complex configuration more transparent. :::  User macros can be used in:  -   item key parameter -   item update intervals and flexible intervals -   trigger name and description -   trigger expression parameters and constants (see     [examples](#examples)) -   many other locations - see the [full     list](/manual/appendix/macros/supported_by_location_user)
zh-cn	#### 概述  除了开箱即用的宏[supported](/manual/appendix/macros/supported_by_location)之外，Zabbix还支持用户宏，以提高灵活性。  用户宏可以在全局、模板和主机级别定义。这些宏有一种特殊的语法：      {$MACRO}  Zabbix根据以下优先级解析宏： 1.主机级宏（先选中） 2.为主机的一级模板（即直接链接到主机的模板）定义的宏，按模板ID排序 3.为主机二级模板定义的宏，按模板ID排序 4.为主机的三级模板定义的宏，按模板ID等排序。 5.全局宏（最后选中）  换句话说，如果主机不存在宏，Zabbix将尝试在深度不断增加的主机模板中找到它。如果仍然找不到，将使用全局宏（如果存在）。  ::: notewarning 如果同一级别的多个链接模板上存在具有**相同名称**的宏，则将使用ID最低的模板中的宏。因此，在多个模板中使用相同名称的宏是一种配置风险。 :::  如果Zabbix找不到宏，宏将无法解析。  ::: noteimportant 宏（包括用户宏）在配置部分（例如，在触发器列表中）被设计为不可解析，以使复杂的配置更加透明。 :::  用户宏可用于： - 项目关键参数 - 项目更新间隔和灵活间隔 - 触发器名称和描述 - 触发器表达式参数和常量(参见[示例](#示例)) - 许多其他位置-请参阅[完整列表](/manual/appendix/macros/supported_by_location_user)

en-us	#### Overview  When monitoring systems using an agent, a good practice is to obtain metrics from the host on which the agent is installed. To use the principle of least privilege, it is necessary to determine what metrics are obtained from the agent.  The table in this document allows you to select the minimum rights for guaranteed correct operation of Zabbix agent.  If a different user is selected for the agent to work, rather than 'LocalSystem', then for the operation of agent as a Windows service, the new user must have the rights "Log on as a service" from "Local Policy→User Rights Assignment" and the right to create, write and delete the Zabbix agent log file. An Active Directory user must be added to the *Performance Monitor Users* group.  ::: noteclassic When working with the rights of an agent based on the "minimum technically acceptable" group, prior provision of rights to objects for monitoring is required. :::
zh-cn	#### 概述  使用 agent 监控系统时，一种最佳实践是从安装代理的主机上获取指标。要使用最小权限原则，有必要确定哪些指标是从agent 那里获得的。  本文档中的表格允许您选择最低权限，保证 Zabbix agent 的正确运行。  如果选择了其他用户才能使 agent 工作，而不是"LocalSystem"，则要使 agent 作为Windows服务运行，新用户必须具有“本地策略→用户权限分配"中的"作为服务登录”权限分配”以及创建、写入和删除 Zabbix 代理日志文件的权利。必须将 Active Directory 用户添加到性能监视器用户组。  ::: noteclassic 基于 agent 的权限处理问题上，需要给出 "技术上可接受的最低要求 "的权限组，并且事先为监控对象提供权限。 :::

en-us	#### Overview  While a [simple graph](simple) is great for accessing data of one item and [custom graphs](custom) offer customization options, none of the two allow to quickly create a comparison graph for multiple items with little effort and no maintenance.  To address this issue, since Zabbix 2.4 it is possible to create ad-hoc graphs for several items in a very quick way.
zh-cn	#### 概览  虽然 [简单图表](../../../../../assets/en/manual/config/visualization/graphs/simple)非常适合访问单个监控项的数据，而 [自定义图表](../../../../../assets/en/manual/config/visualization/graphs/custom) 提供定制化选择，但是这两种图表都没法很轻松的快速创建多个监控项的比较图表。  为了解决这个问题，从 Zabbix 2.4 开始可以创建 ad-hoc以非常快速的方式绘制多个监控项的图表。

en-us	#### Overview  While generally problem events are resolved automatically when trigger status goes from 'Problem' to 'OK', there may be cases when it is difficult to determine if a problem has been resolved by means of a trigger expression. In such cases, the problem needs to be resolved manually.  For example, *syslog* may report that some kernel parameters need to be tuned for optimal performance. In this case the issue is reported to Linux administrators, they fix it and then close the problem manually.  Problems can be closed manually only for triggers with the *Allow manual close* option enabled.  When a problem is "manually closed", Zabbix generates a new internal task for Zabbix server. Then the *task manager* process executes this task and generates an OK event, therefore closing problem event.  A manually closed problem does not mean that the underlying trigger will never go into a 'Problem' state again. The trigger expression is re-evaluated and may result in a problem:  -   When new data arrive for any item included in the trigger expression     (note that the values discarded by a throttling preprocessing step     are not considered as received and will not cause trigger expression     to be re-evaluated); -   When time-based functions are used in the expression. Complete     time-based function list can be found on [Triggers     page](/manual/config/triggers).
zh-cn	#### 概述  通常在触发器状态由“问题”变为“OK”时，问题事件会自动解决，但在某些情况下，可能很难确定问题是否已经通过触发器表达式得到解决。在这种情况下，问题需要手动解决。  例如，*Syslog*可能会报告为了获得最佳性能需要调整一些内核参数。在这种情况下，故障会报告给Linux管理员，他们会修复故障并手动关闭。  只有触发器启用了*允许手动关闭*选项，问题才可以手动关闭。  当一个问题“手动关闭”时，Zabbix会为Zabbix服务器生成一个新的内部任务。然后*任务管理器*进程执行这个任务，并在问题事件关闭后生成一个OK事件。  手动关闭一个问题并不意味着底层的触发器再也不会进入”问题“状态。触发表达式会重新评估并可能产生一个问题，如：  -   当任何包含触发器表达式的监控项收到新数据时（请注意，节流预处理步骤丢弃的值不被视为已接收，也不会导致重新评估触发表达式）； -   当表达式中使用基于时间的函数时。所有基于时间的函数的列表可以在[触发器页面](/manual/config/triggers)找到。

en-us	#### Overview  While many things in the frontend can be configured using the frontend itself, some customisations are currently only possible by editing a definitions file.  This file is `defines.inc.php` located in /include of the Zabbix HTML document directory.
zh-cn	#### 概述  虽然可以使用前端本身配置前端中的许多东西，但目前只能通过编辑定义文件来进行一些自定义。  该文件是 `defines.inc.php`，位于 Zabbix HTML 文档目录的 /include 中。

en-us	#### Overview  While you may find the required index number (for example, of a network interface) among the SNMP OIDs, sometimes you may not completely rely on the index number always staying the same.  Index numbers may be dynamic - they may change over time and your item may stop working as a consequence.  To avoid this scenario, it is possible to define an OID which takes into account the possibility of an index number changing.  For example, if you need to retrieve the index value to append to **ifInOctets** that corresponds to the **GigabitEthernet0/1** interface on a Cisco device, use the following OID:      ifInOctets["index","ifDescr","GigabitEthernet0/1"]
zh-cn	#### 概述  虽然你可能会在SNMP OID中找到所需的索引号（例如网络接口），但有时你不能完全依赖不变的索引号。  索引号可能是动态的 -它们可能会随时间而改变，因此你的监控项可能会停止工作。  为了避免这种情况，可以定义一个考虑到索引号改变的可能性的OID。  例如，如果需要检索索引值以匹配Cisco设备上的 **GigabitEthernet0/1** 接口的 **ifInOctets** ，请使用以下OID：      ifInOctets["index","ifDescr","GigabitEthernet0/1"]

en-us	#### Overview  With calculated items it is possible to create calculations based on the values of other items.  Calculations may use both:  -   single values of individual items -   complex filters to select multiple items for aggregations (see     [aggregate     calculations](/manual/config/items/itemtypes/calculated/aggregate)     for details)  Thus, calculated items are a way of creating virtual data sources. All calculations are done by Zabbix server only. The values are periodically calculated based on the arithmetical expression used.  The resulting data is stored in the Zabbix database as for any other item; both history and trend values are stored and graphs can be generated.  ::: noteclassic If the calculation result is a float value it will be trimmed to an integer if the calculated item type of information is *Numeric (unsigned)*. :::  Calculated items share their syntax with trigger [expressions](/manual/config/triggers/expression). Comparison to strings is allowed in calculated items. Calculated items may be referenced by macros or other entities same as any other item type.  To use calculated items, choose the item type **Calculated**.
zh-cn	#### 概述  使用可计算监控项，可以根据其它监控项的值计算。  计算可以同时使用：  -   单个监控项的单一值 -   用于选择多个监控项进行聚合的复杂过滤器(有关详细信息，参阅[聚合计算](/manual/config/items/itemtypes/calculated/aggregate))  因此，可计算监控项是创建虚拟数据源的一种方式。所有计算仅由 Zabbix server 完成。这些值是根据所使用的算术表达式定期计算的。  结果数据与任何其它监控项一样存储在 Zabbix 数据库中；历史和趋势值都被存储并且可以生成图形。  ::: noteclassic 如果计算结果是浮点值，如果计算的信息项类型为*Numeric (unsigned)*，则将其修剪为整数。 :::  可计算监控项与触发器[表达式](/manual/config/triggers/expression)共享它们的语法。在可计算监控项中允许与字符串进行比较。可计算监控项可以由宏或与任何其它项类型相同的其它实体引用。  要使用可计算监控项，请选择项目类型 **Calculated**。

en-us	#### Overview  With escalations you can create custom scenarios for sending notifications or executing remote commands.  In practical terms it means that:  -   Users can be informed about new problems immediately -   Notifications can be repeated until the problem is resolved -   Sending a notification can be delayed -   Notifications can be escalated to another "higher" user group -   Remote commands can be executed immediately or when a problem is not     resolved for a lengthy period  Actions are escalated based on the **escalation step**. Each step has a duration in time.  You can define both the default duration and a custom duration of an individual step. The minimum duration of one escalation step is 60 seconds.  You can start actions, such as sending notifications or executing commands, from any step. Step one is for immediate actions. If you want to delay an action, you can assign it to a later step. For each step, several actions can be defined.  The number of escalation steps is not limited.  Escalations are defined when [configuring an operation](operation#configuring_an_operation). Escalations are supported for problem operations only, not recovery.
zh-cn	#### 概述  通过Escalations，您可以创建发送通知或执行远程命令的自定义场景。  实际应用中，这意味着：  -   用户可以立即收到新问题通知 -   通知可以重复，直到问题解决 -   发送通知可以延时 -   通知可以升级到另一个“较高”的用户组 -   可以立即执行远程命令，或者长时间不解决问题  操作会根据升级步骤进行通知升级。 每一步都有一段时间。  您可以定义默认持续时间和单个步骤的自定义持续时间。一个升级步骤的最短持续时间为60秒。  您可以从任何步骤开始执行操作，例如发送通知或执行命令。 第一步是立即采取行动。 如果要延迟操作，可以将其分配给稍后的步骤。 对于每个步骤，可以定义几个操作。  通知升级步骤的数量不受限制。  [配置操作](operation#configuring_an_operation)是即可定义Escalations. Escalations仅对问题操作支持，而不是恢复。

en-us	#### Overview  With lots of data flowing into Zabbix, it becomes much easier for the users if they can look at a visual representation of what is going on rather than only numbers.  This is where graphs come in. Graphs allow to grasp the data flow at a glance, correlate problems, discover when something started or make a presentation of when something might turn into a problem.  Zabbix provides users with:  -   built-in [simple graphs](/manual/config/visualization/graphs/simple)     of one item data -   the possibility to create more complex [customized     graphs](/manual/config/visualization/graphs/custom) -   access to a comparison of several items quickly in [ad-hoc     graphs](/manual/config/visualization/graphs/adhoc) -   modern customizable [vector     graphs](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph)
zh-cn	#### 概览  随着大量数据流入 Zabbix，如果可以以图形化查看正在发生的事情，而不仅是数字，那么对于用户来说，这将变得更加容易。。  这就是图表的用武之地。图表可以在一定程度上掌握数据流一目了然，关联问题，发现某事何时开始或者展示某事何时可能变成问题。  Zabbix 为用户提供：  - 监控项内置的[简单图形](/manual/config/visualization/graphs/simple) - 创建复杂[自定义图表](/manual/config/visualization/graphs/custom)的能力 - 在 [ad-hoc图表](/manual/config/visualization/graphs/adhoc)中快速访问多个项目的比较 - 可定制化的[矢量图表](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#graph)

en-us	#### Overview  With mass update you may change some attribute for a number of triggers at once, saving you the need to open each individual trigger for editing.
zh-cn	#### 概述  通过批量更新，您可以一次更改多个触发器的某些属性，从而无需打开每个单独的触发器进行编辑。

en-us	#### Overview  With remote commands you can define that a certain pre-defined command is automatically executed on the monitored host upon some condition.  Thus remote commands are a powerful mechanism for smart pro-active monitoring.  In the most obvious uses of the feature you can try to:  -   Automatically restart some application (web server, middleware, CRM)     if it does not respond -   Use IPMI 'reboot' command to reboot some remote server if it does     not answer requests -   Automatically free disk space (removing older files, cleaning /tmp)     if running out of disk space -   Migrate a VM from one physical box to another depending on the CPU     load -   Add new nodes to a cloud environment upon insufficient CPU (disk,     memory, whatever) resources  Configuring an action for remote commands is similar to that for sending a message, the only difference being that Zabbix will execute a command instead of sending a message.  Remote commands can be executed by Zabbix server, proxy or agent. Remote commands on Zabbix agent can be executed directly by Zabbix server or through Zabbix proxy. Both on Zabbix agent and Zabbix proxy remote commands are disabled by default. They can be enabled by:  -   adding an `AllowKey=system.run[*]` parameter in agent configuration; -   setting the EnableRemoteCommands parameter to '1' in proxy     configuration.  Remote commands executed by Zabbix server are run as described in [Command execution](/manual/appendix/command_execution) including exit code checking.  Remote commands are executed even if the target host is in maintenance.
zh-cn	#### 概述  使用远程命令，您可以预定义在某些情况下会在受监控主机上自动执行的命令。  因此远程命令是智能主动监控的强大机制。  在该功能最显而易见的用途中，你可以尝试：  -   自动重启某些没有响应的应用（web服务器、中间件、CRM）  -   使用IPMI 'reboot'命令重启某些确实无法响应的服务器。  -   磁盘空间不足时自动释放（删除旧文件、清理）      -   根据CPU负载将VM从一台物理机迁移到另一台      -   CPU（磁盘、内存或其他）资源不足时向云环境添加新节点  为远程命令配置操作与发送消息类似，唯一的区别是 Zabbix 将执行一个命令而不是发送消息。  远程命令可以由Zabbix Server、Proxy 或agent执行。Zabbix agent上的远程命令可以由Zabbix Server或通过 Proxy 执行。Zabbix agent和Zabbix Proxy上的远程命令默认都是禁用的。 它们可以通过以下方式启用：  -   在agent的配置中添加一个`AllowKey=system.run[*]` 参数；  -   在代理的配置中将`EnableRemoteCommands`参数设为‘1’。   由 Zabbix服务器执行的远程命令按照[命令执行](/manual/appendix/command_execution)所述运行，包括退出代码检查。  即使目标主机在维护状态，远程命令也会执行。

en-us	#### Overview  With Zabbix you can check several availability aspects of web sites.\  ::: noteimportant To perform web monitoring Zabbix server must be initially [configured](/manual/installation/install#from_the_sources) with cURL (libcurl) support. :::  To activate web monitoring you need to define web scenarios. A web scenario consists of one or several HTTP requests or "steps". The steps are periodically executed by Zabbix server in a pre-defined order. If a host is monitored by proxy, the steps are executed by the proxy.  Web scenarios are attached to hosts/templates in the same way as items, triggers, etc. That means that web scenarios can also be created on a template level and then applied to multiple hosts in one move.  The following information is collected in any web scenario:  -   average download speed per second for all steps of whole scenario -   number of the step that failed -   last error message  The following information is collected in any web scenario step:  -   download speed per second -   response time -   response code  For more details, see [web monitoring items](/manual/web_monitoring/items).  Data collected from executing web scenarios is kept in the database. The data is automatically used for graphs, triggers and notifications.  Zabbix can also check if a retrieved HTML page contains a pre-defined string. It can execute a simulated login and follow a path of simulated mouse clicks on the page.  Zabbix web monitoring supports both HTTP and HTTPS. When running a web scenario, Zabbix will optionally follow redirects (see option *Follow redirects* below). Maximum number of redirects is hard-coded to 10 (using cURL option [CURLOPT\_MAXREDIRS](http://curl.haxx.se/libcurl/c/CURLOPT_MAXREDIRS.html)). All cookies are preserved during the execution of a single scenario.  See also [known issues](/manual/installation/known_issues#https_checks) for web monitoring using HTTPS protocol.
zh-cn	#### 概览  可以通过 Zabbix 检查网站的几个可用性。\  ::: noteimportant 要执行 web 监控，Zabbix server 的初始 [配置](/manual/installation/install#from_the_sources) 必须支持 cURL (libcurl)。 :::  启用 Web 监控需要定义 Web 场景。Web 场景由一个或多个 HTTP 请求或 “步骤” 组成。这些步骤由 Zabbix server 以预设的顺序定期执行。如果主机由 proxy 监控，则这些步骤由 proxy 执行。  Web 场景以与监控项、触发器等相同的方式附加到主机/模板上。这意味着 Web 场景也可以在模板级别上创建，然后一次性应用于多个主机。  在任何 Web 场景中都会收集以下信息：  -   整个场景所有步骤的每秒平均下载速度 -   失败的步骤编号 -   最新的错误信息  在任何 Web 场景步骤中都会收集以下信息：  -   每秒下载速度 -   响应时间 -   响应码  更多详细信息，请参见 [web 监控项](/manual/web_monitoring/items)。  执行 Web 场景收集的数据保存在数据库中。数据自动用于图表、触发器和通知。  Zabbix 还可以检查检索到的 HTML 页面是否包含预定义的字符串。它可以执行模拟登录并遵循页面上模拟鼠标点击的路径。  Zabbix web 监控同时支持 HTTP 和 HTTPS。在运行 Web 场景时，Zabbix 将选择性地跟随重定向（请参阅下面的 *Follow redirects* 选项）。最大重定向数硬编码为 10（使用 cURL 选项[CURLOPT\_MAXREDIRS](http://curl.haxx.se/libcurl/c/CURLOPT_MAXREDIRS.html)）。在单个场景的执行过程中会保留所有 cookie。  查看使用 HTTPS 协议进行 Web 监控的 [已知问题](/manual/installation/known_issues#https_checks) 。

en-us	#### Overview  [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) is a powerful interface in Windows that can be used for retrieving various information about Windows components, services, state and software installed.  It can be used for physical disk discovery and their performance data collection, network interface discovery, Hyper-V guest discovery, monitoring Windows services and many other things in Windows OS.  This type of low-level [discovery](/manual/discovery/low_level_discovery) is done using WQL queries whose results get automatically transformed into a JSON object suitable for low-level discovery.
zh-cn	#### 概述  [WMI](https://en.wikipedia.org/wiki/Windows_Management_Instrumentation) 是一种Windows中的接口，功能强大，可用于获取各种信息，比如Windows组件、服务、状态和安装的软件。  WMI可用于物理硬盘的自动发现和相关性能数据的采集、网络接口的自动发现、Hyper-V guest的自动发现、监控Windows操作系统中的服务和其它实体。  此类低级别 [自动发现](/manual/discovery/low_level_discovery) 通过使用WQL查询实现，其结果会自动转换成一个匹配低级别自动发现的JSON格式的JSON对象。

en-us	#### Overview  You can assign some triggers to a [link](/manual/config/visualization/maps/map#linking_elements) between elements in a network map. When these triggers go into a problem state, the link can reflect that.  When you configure a link, you set the default link type and color. When you assign triggers to a link, you can assign different link types and colors with these triggers.  Should any of these triggers go into a problem state, their link style and color will be displayed on the link. So maybe your default link was a green line. Now, with the trigger in the problem state, your link may become bold red (if you have defined it so).
zh-cn	#### 概述  你可以将一些触发器[链接](/manual/config/visualization/maps/map#linking_elements)网络地图中的元素。当这些触发器进入问题状态时，该链接可以查看相关内容。  在配置链接时，可以设置默认链接类型和颜色。当你将触发器关联到链接时，你可以根据这些触发器来分配不同的链接类型和颜色。  如果这些触发器中的任何一个进入问题状态，它们的连接样式和颜色将显示在链接上。所以你的默认链接可能是一条绿线。现在，由于触发器处于问题状态，你的链接可能变为粗体红色（如果你这样定义的话）。

en-us	#### Overview  You can define maintenance periods for host groups, hosts and specific triggers/services in Zabbix.  There are two maintenance types - with data collection and with no data collection.  During a maintenance "with data collection" triggers are processed as usual and events are created when required. However, problem escalations are paused for hosts/triggers in maintenance, if the *Pause operations for suppressed problems* option is checked in action configuration. In this case, escalation steps that may include sending notifications or remote commands will be ignored for as long as the maintenance period lasts. Note that problem recovery and update operations are not suppressed during maintenance, only escalations.  For example, if escalation steps are scheduled at 0, 30 and 60 minutes after a problem start, and there is a half-hour long maintenance lasting from 10 minutes to 40 minutes after a real problem arises, steps two and three will be executed a half-hour later, or at 60 minutes and 90 minutes (providing the problem still exists). Similarly, if a problem arises during the maintenance, the escalation will start after the maintenance.  To receive problem notifications during the maintenance normally (without delay), you have to uncheck the *Pause operations for suppressed problems* option in action configuration.  ::: noteclassic If at least one host (used in the trigger expression) is not in maintenance mode, Zabbix will send a problem notification. :::  Zabbix server must be running during maintenance. Timer processes are responsible for switching host status to/from maintenance at 0 seconds of every minute. Note that when a host enters maintenance, Zabbix server timer processes will read all open problems to check if it is required to suppress those. This may have a performance impact if there are many open problems. Zabbix server will also read all open problems upon startup, even if there are no maintenances configured at the time.  A proxy will always collect data regardless of the maintenance type (including "no data" maintenance). The data is later ignored by the server if 'no data collection' is set.  When "no data" maintenance ends, triggers using nodata() function will not fire before the next check during the period they are checking.  If a log item is added while a host is in maintenance and the maintenance ends, only new logfile entries since the end of the maintenance will be gathered.  If a timestamped value is sent for a host that is in a “no data” maintenance type (e.g. using [Zabbix sender](/manpages/zabbix_sender)) then this value will be dropped however it is possible to send a timestamped value in for an expired maintenance period and it will be accepted.  ::: noteimportant To ensure predictable behavior of recurring maintenance periods (daily, weekly, monthly), it is required to use a common time zone for all parts of Zabbix. :::  If maintenance period, hosts, groups or tags are changed by the user, the changes will only take effect after configuration cache synchronization.
zh-cn	#### 概述  可以在 Zabbix 中定义主机群组、主机和特定触发器/服务的维护期。  有两种维护类型 - 有数据收集（with data collection）和没有数据收集（with no data collection）。  在“有数据收集（with data collection）”的维护期间，触发器照常处理，并在需要时创建事件。但是，如果在操作配置中选中了 *暂停操作以解决被抑制的问题（Pause operations for suppressed problems）*  选项，则会暂停维护中的主机/触发器的问题升级。在这种情况下，只要维护期持续，可能包括发送通知或远程命令的升级步骤将被忽略。请注意，维护期间不会抑制问题恢复和更新操作，只会抑制升级。  例如，如果升级步骤安排在问题开始后的 0、30 和 60 分钟，并且在真正问题出现后的 10 分钟到 40 分钟之间进行半小时的维护，则将在半小时或 60 分钟和 90 分钟（假设问题仍然存在）后执行步骤 2 和 3。同样，如果在维护过程中出现问题，则在维护后开始升级。  要在维护期间正常（无延迟）接收问题通知，您必须取消选中操作配置中的 *暂停操作以解决被抑制的问题（Pause operations for suppressed problems）* 选项。  ::: noteclassic 如果至少有一台主机（在触发器表达式中使用）未处于维护模式，Zabbix 将发送问题通知。 :::  Zabbix server 必须在维护期间运行。定时器进程负责在每分钟 0 秒将主机状态切换到维护状态或从维护状态切换。请注意，当主机进入维护时，Zabbix server 计时器进程将读取所有未解决的问题，以检查是否需要抑制这些问题。如果存在许多未解决的问题，这可能会对性能产生影响。Zabbix server 也会在启动时读取所有未解决的问题，即使当时没有配置维护。  无论维护类型如何（包括“无数据收集”维护），proxy 都将始终收集数据。如果设置了“无数据收集”，则 server 会忽略该数据。  当“无数据”维护结束时，使用 nodata() 函数的触发器在它们检查期间不会在下一次检查之前触发。  如果在主机维护和维护结束时添加日志类型监控项，则只会收集自维护结束以来的新日志文件条目。  如果为处于 “无数据收集” 维护类型的主机发送带时间戳的值（例如使用  [Zabbix sender](/manpages/zabbix_sender)），则该值将被丢弃，但是可以为过期的维护期发送带时间戳的值。  ::: noteimportant 为了确保重复维护周期（每天、每周、每月）的可预测性，Zabbix 的所有组件都需要使用同一个公共时区。 :::  如果维护周期、主机、主机群组或标签由用户更改，更改将在配置缓存同步后生效。

en-us	#### Overview  You can define the following operations for all events:  -   send a message -   execute a remote command  ::: noteimportant Zabbix server does not create alerts if access to the host is explicitly "denied" for the user defined as action operation recipient or if the user has no rights defined to the host at all. :::  For discovery and autoregistration events, there are additional operations available:  -   [add     host](/manual/config/notifications/action/operation/other#adding_host) -   remove host -   enable host -   disable host -   add to host group -   remove from host group -   link to template -   unlink from template -   set host inventory mode
zh-cn	#### 概述  你可以为所有事件定义如下这些操作：  -   发送一条消息 -   执行一条远程命令  ::: noteimportant 对用户定义的动作接受者，如果主机明确“拒绝”或者用户对主机完全没有定义的权限，Zabbix服务器不会创建告警。 :::  对于自动发现和自动注册事件，还有额外可用的操作：  -   [添加主机](/manual/config/notifications/action/operation/other#adding_host) -   移除主机 -   启用主机 -   停用主机 -   添加到主机组 -   从主机组移除 -   链接到模板 -   取消到模板的链接 -   设置主机的资产模式

en-us	#### Overview  You can differentiate user permissions in Zabbix by defining the respective user role. Then the unprivileged users need to be included in user groups that have access to host group data.
zh-cn	#### 概述  您可以通过定义 Zabbix 中的用户权限来区分相应的用户角色。然后需要将非特权用户包括有权访问主机组数据的用户组。

en-us	#### Overview  You can effectively monitor Windows performance counters using the *perf\_counter\[\]* key.  For example:      perf_counter["\Processor(0)\Interrupts/sec"]  or      perf_counter["\Processor(0)\Interrupts/sec", 10]  For more information on using this key or its English-only equivalent `perf_counter_en`, see [Windows-specific item keys](/manual/config/items/itemtypes/zabbix_agent/win_keys).  In order to get a full list of performance counters available for monitoring, you may run:      typeperf -qx  You may also use low-level discovery to discover multiple [object instances](/manual/discovery/low_level_discovery/examples/windows_perf_instances) of Windows performance counters and automate the creation of perf\_counter items for multiple instance objects.
zh-cn	#### 概览  你可以使用 *perf\_counter\[\]* 这个key有效的监控Windows性能计数器。\  例如：      perf_counter["\Processor(0)\Interrupts/sec"]  或      perf_counter["\Processor(0)\Interrupts/sec", 10]  有关使用此key的更多信息请参阅[Windows专用监控项](/zh/manual/config/items/itemtypes/zabbix_agent/win_keys)。  为了获取可用于监控的新能计数器完整列表，你可以运行：      typeperf -qx  可以通过低级别发现来发现windows性能计数器的多[对象实例](/manual/discovery/low_level_discovery/examples/windows_perf_instances),并自动创建多实例对象的性能计数器监控项。

en-us	#### Overview  You can keep the inventory of networked devices in Zabbix.  There is a special *Inventory* menu in the Zabbix frontend. However, you will not see any data there initially and it is not where you enter data. Building inventory data is done manually when configuring a host or automatically by using some automatic population options.
zh-cn	#### 概述  你可以将联网设备的资产信息保存在Zabbix里。  Zabbix管理页面有一个特殊的 *Inventory（资产记录）*菜单。 但你一开始不会看到任何数据，这里你也不能输入任何资产相关的信息。资产信息是在配置主机时人工录入建立的资产数据，或者通过使用某些自动填充选项完成的录入。

en-us	#### Overview  You can monitor the health and availability of Intelligent Platform Management Interface (IPMI) devices in Zabbix. To perform IPMI checks Zabbix server must be initially [configured](/manual/installation/install#configure_the_sources) with IPMI support.  IPMI is a standardized interface for remote "lights-out" or "out-of-band" management of computer systems. It allows to monitor hardware status directly from the so-called "out-of-band" management cards, independently from the operating system or whether the machine is powered on at all.  Zabbix IPMI monitoring works only for devices having IPMI support (HP iLO, DELL DRAC, IBM RSA, Sun SSP, etc).  Since Zabbix 3.4, a new IPMI manager process has been added to schedule IPMI checks by IPMI pollers. Now a host is always polled by only one IPMI poller at a time, reducing the number of open connections to BMC controllers. With those changes it's safe to increase the number of IPMI pollers without worrying about BMC controller overloading. The IPMI manager process is automatically started when at least one IPMI poller is started.  See also [known issues](/manual/installation/known_issues#ipmi_checks) for IPMI checks.
zh-cn	#### 概述  你可以在Zabbix中监控智能平台管理接口（IPMI）设备的运行状况和可用性。要执行IPMI检查，Zabbix服务器必须首先[配置](/zh/manual/installation/install#from_the_sources)IPMI支持。  IPMI是计算机系统的远程"关闭"或“带外”管理的标准接口。它可以独立于操作系统直接从所谓的“带外”管理卡监视硬件状态。  Zabbix IPMI监控仅适用于支持IPMI的设备(HP iLO, DELL DRAC, IBM RSA, Sun SSP, 等等).  从Zabbix 3.4开始，添加了一个新的IPMI管理器进程来安排IPMI轮询器进行IPMI检查。现在，主机始终只由一个IPMI轮询器轮询，从而减少了与BMC控制器的打开连接数。通过这些更改，可以安全地增加IPMI轮询器的数量，而无需担心BMC控制器过载。 启动至少一个IPMI轮询器时，将自动启动IPMI管理器进程。  也可以参考IPMI检查的[已知问题](/zh/manual/installation/known_issues#ipmi_checks)。

en-us	#### Overview  You may want to use SNMP monitoring on devices such as printers, network switches, routers or UPS that usually are SNMP-enabled and on which it would be impractical to attempt setting up complete operating systems and Zabbix agents.  To be able to retrieve data provided by SNMP agents on these devices, Zabbix server must be [initially configured](/manual/installation/install#configure-the-sources) with SNMP support by specifying the `--with-net-snmp` flag.  SNMP checks are performed over the UDP protocol only.  Zabbix server and proxy daemons query SNMP devices for multiple values in a single request. This affects all kinds of SNMP items (regular SNMP items, SNMP items with dynamic indexes, and SNMP low-level discovery) and should make SNMP processing much more efficient. See the [bulk processing](#internal-workings-of-bulk-processing) section for technical details on how it works internally. Bulk requests can also be disabled for devices that cannot handle them properly using the "Use bulk requests" setting for each interface.  Zabbix server and proxy daemons log lines similar to the following if they receive an incorrect SNMP response:      SNMP response from host "gateway" does not contain all of the requested variable bindings  While they do not cover all the problematic cases, they are useful for identifying individual SNMP devices for which bulk requests should be disabled.  Zabbix server/proxy will always retry at least one time after an unsuccessful query attempt: either through the SNMP library's retrying mechanism or through the internal [bulk processing](#internal-workings-of-bulk-processing) mechanism.  ::: notewarning If monitoring SNMPv3 devices, make sure that msgAuthoritativeEngineID (also known as snmpEngineID or "Engine ID") is never shared by two devices. According to [RFC 2571](http://www.ietf.org/rfc/rfc2571.txt) (section 3.1.1.1) it must be unique for each device. :::  ::: notewarning  RFC3414 requires the SNMPv3 devices to persist their engineBoots. Some devices do not do that, which results in their SNMP messages being discarded as outdated after being restarted. In such situation, SNMP cache needs to be manually cleared on a server/proxy (by using [-R snmp\_cache\_reload](/manual/concepts/server#runtime-control)) or the server/proxy needs to be restarted.  :::
zh-cn	#### 概述  您可能希望在打印机、网络交换机、路由器或 UPS 等设备上使用 SNMP 监控，这些设备通常启用 SNMP，并且在这些设备上尝试设置完整的操作系统和 Zabbix 代理是不切实际的。  为了能够在这些设备上检索 SNMP agent提供的数据，Zabbix 服务器必须 [初始配置](/manual/installation/install#configure-the-sources) 通过指定 `--with-net-snmp 支持 SNMP ` 标志。  SNMP 检查仅通过 UDP 协议执行。  Zabbix 服务器和代理守护进程在单个请求中查询 SNMP 设备的多个值。 这会影响所有类型的 SNMP 监控项（常规 SNMP 监控项、具有动态索引的 SNMP 监控项和 SNMP 底层自动发现）并且应该使 SNMP 处理更加高效。 请参阅 [bulk processing](#internal-workings-of-bulk-processing) 部分，了解有关其内部工作方式的技术细节。 使用每个接口的“使用批量请求”设置，也可以为无法正确处理批量请求的设备禁用批量请求。  如果 Zabbix 服务器和代理守护进程收到不正确的 SNMP 响应，日志行将类似于以下内容：    · 来自主机“网关”的 SNMP 响应不包含所有请求的变量绑定  虽然它们没有涵盖所有有问题的情况，但它们对于识别应该禁用批量请求的单个 SNMP 设备很有用。  Zabbix server/proxy 总是会在查询尝试失败后至少重试一次：通过 SNMP 库的重试机制或通过内部 [bulk processing](#internal-workings-of-bulk-processing) 机制。  ::: notewarning 如果监控 SNMPv3 设备，请确保 msgAuthoritativeEngineID（也称为 snmpEngineID 或“引擎 ID”）永远不会被两个设备共享。 根据 [RFC 2571](http://www.ietf.org/rfc/rfc2571.txt)（第 3.1.1.1 节），每个设备都必须是唯一的。 :::  ::: notewarning RFC3414 要求 SNMPv3 设备保留其 engineBoots。 一些设备不这样做，这导致它们的 SNMP 消息在重新启动后被丢弃为过时的。 在这种情况下，需要在服务器/代理上手动清除 SNMP 缓存（通过使用 [-R snmp\_cache\_reload](/manual/concepts/server#runtime-control)）或者需要重新启动服务器/代理 . :::

en-us	#### Overview  Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent.  This section lists parameters supported in a Zabbix agent 2 configuration file (zabbix\_agent2.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported in the beginning of     the line.
zh-cn	#### 概述  Zabbix agent 2 是新一代的 Zabbix agent 并用于替代之前的 Zabbix agent。  本节列出了Zabbix agent 2 配置文件 (zabbix\_agent2.conf) 中支持的参数。注意:  -   默认值反映的是进程默认值，而不是出厂配置文件中的值； -   Zabbix仅支持无 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark) 的UTF-8编码配置文件； -   支持注释须以 "\#" 为行首。

en-us	#### Overview  Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent. Zabbix agent 2 has been developed to:  -   reduce the number of TCP connections -   have greater check concurrency -   be easily extendible with plugins. A plugin should be able to:     -   provide trivial checks consisting of only a few simple lines of         code     -   provide complex checks consisting of long-running scripts and         standalone data gathering with periodic sending back of the data -   be a drop-in replacement for Zabbix agent (in that it supports all     the previous functionality)  Agent 2 is written in Go (with some C code of Zabbix agent reused). A configured Go environment with a currently supported [Go version](https://golang.org/doc/devel/release#policy) is required for building Zabbix agent 2.  Agent 2 does not have built-in daemonization support on Linux; it can be run as a [Windows service](/manual/appendix/install/windows_agent).  Passive checks work similarly to Zabbix agent. Active checks support scheduled/flexible intervals and check concurrency within one active server.  **Check concurrency**  Checks from different plugins can be executed concurrently. The number of concurrent checks within one plugin is limited by the plugin capacity setting. Each plugin may have a hardcoded capacity setting (100 being default) that can be lowered using the `Plugins.<Plugin name>.Capacity=N` setting in the *Plugins* configuration [parameter](#configuration_file).  See also: [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/plugins).  
zh-cn	#### Overview  Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent. Zabbix agent 2 has been developed to:  -   reduce the number of TCP connections -   have greater check concurrency -   be easily extendible with plugins. A plugin should be able to:     -   provide trivial checks consisting of only a few simple lines of         code     -   provide complex checks consisting of long-running scripts and         standalone data gathering with periodic sending back of the data -   be a drop-in replacement for Zabbix agent (in that it supports all     the previous functionality)  Agent 2 is written in Go (with some C code of Zabbix agent reused). A configured Go environment with a currently supported [Go version](https://golang.org/doc/devel/release#policy) is required for building Zabbix agent 2.  Agent 2 does not have built-in daemonization support on Linux; it can be run as a [Windows service](/manual/appendix/install/windows_agent).  Passive checks work similarly to Zabbix agent. Active checks support scheduled/flexible intervals and check concurrency within one active server.  \*\* Check concurrency \*\*  Checks from different plugins can be executed concurrently. The number of concurrent checks within one plugin is limited by the plugin capacity setting. Each plugin may have a hardcoded capacity setting (100 being default) that can be lowered using the `Plugins.<Plugin name>.Capacity=N` setting in the *Plugins* configuration [parameter](#configuration_file).  See also: [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/plugins).  

en-us	#### Overview  Zabbix agent 2 is a new generation of Zabbix agent and may be used in place of Zabbix agent. Zabbix agent 2 has been developed to:  -   reduce the number of TCP connections -   provide improved concurrency of checks -   be easily extendible with plugins. A plugin should be able to:     -   provide trivial checks consisting of only a few simple lines of         code     -   provide complex checks consisting of long-running scripts and         standalone data gathering with periodic sending back of the data -   be a drop-in replacement for Zabbix agent (in that it supports all     the previous functionality)  Agent 2 is written in Go programming language (with some C code of Zabbix agent reused). A configured Go environment with a currently supported [Go version](https://golang.org/doc/devel/release#policy) is required for building Zabbix agent 2.  Agent 2 does not have built-in daemonization support on Linux; it can be run as a [Windows service](/manual/appendix/install/windows_agent).  Passive checks work similarly to Zabbix agent. Active checks support scheduled/flexible intervals and check concurrency within one active server.   ::: noteclassic  By default, Zabbix agent 2 will schedule the first data collection for active checks at a conditionally random time within the item's update interval to prevent spikes in resource usage. To perform active checks that do not have *Scheduling* [update interval](/manual/config/items/item/custom_intervals#scheduling-interval) immediately after the agent restart, set `ForceActiveChecksOnStart` parameter (global-level) or `Plugins.<Plugin name>.System.ForceActiveChecksOnStart` (affects only specific plugin checks) in the [configuration file](/manual/appendix/config/zabbix_agent2). Plugin-level parameter, if set, will override the global parameter. Forcing active checks on start is supported since Zabbix 6.0.2.  :::   **Check concurrency**  Checks from different plugins can be executed concurrently. The number of concurrent checks within one plugin is limited by the plugin capacity setting. Each plugin may have a hardcoded capacity setting (100 being default) that can be lowered using the `Plugins.<PluginName>.System.Capacity=N` setting in the *Plugins* configuration [parameter](#configuration_file). Former name of this parameter `Plugins.<PluginName>.Capacity` is still supported, but has been deprecated in Zabbix 6.0.  See also: [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/en/plugins).
zh-cn	#### 概述  Zabbix agent 2是新一代的Zabbix agent，可以替代Zabbix agent使用。 Zabbix agent 2 已开发为：  -   减少TCP连接数量 -   提供改进的检查并发性 -   使用插件很容易扩展。一个插件应该能够:     -   提供由几行简单代码组成的简单检查     -   提供复杂的检查，包括长时间运行的脚本和独立的数据收集，并定期发回数据 -   做一个临时的替代品 Zabbix agent (因为它支持之前的所有功能)  Agent 2 是用Go 语言编写(复用了一些  Zabbix agent 中的C 语言代码).。在构建Zabbix agent 2 时，需要配置当前支持的Go环境  [Go version](https://golang.org/doc/devel/release#policy)  。  Agent 2 在Linux上没有内置的守护进程支持; 它可以作为  [Windows service](https://www.zabbix.com/documentation/devel/en/manual/appendix/install/windows_agent).  被动检查的工作类似于Zabbix agent。主动检查支持 调度/灵活间隔 同时并发检查仅使用一个active server.  ::: noteclassic 默认情况下，Zabbix agent2将在监控项更新间隔内以条件随机时间调度主动检查的第一次数据采集，避免资源使用率突增。为了在agent重启后立即做好非调度[采集间隔](/manual/config/items/item/custom_intervals#scheduling-interval) 的主动检查，设置[配置文件](/manual/appendix/config/zabbix_agent2)中ForceActiveChecksOnStart参数（全局）或者Plugins.<Plugin name>.System.ForceActiveChecksOnStart（仅影响特定插件）。插件级别参数会覆盖全局参数。从Zabbix6.0.2版本开始，支持启动agent时强制执行主动检查。  :::  **检查并发**  来自不同插件的检查可以同时执行。一个插件的并发检查次数受插件容量设置的限制。每个插件都可以有一个硬编码的容量设置(默认为100)，可以使用 `Plugins.<Plugin name>.Capacity=N`  设置  _Plugins_  配置  [parameter](https://www.zabbix.com/documentation/devel/en/manual/concepts/agent2#configuration-file).  参考:  [Plugin development guidelines](https://www.zabbix.com/documentation/guidelines/plugins).

en-us	#### Overview  Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).  The agent gathers operational information locally and reports data to Zabbix server for further processing. In case of failures (such as a hard disk running full or a crashed service process), Zabbix server can actively alert the administrators of the particular machine that reported the failure.  Zabbix agents are extremely efficient because of use of native system calls for gathering statistical information.
zh-cn	#### 概述 Zabbix agent 部署在被监控目标上，以主动监控本地资源和应用程序（硬盘、内存、处理器统计信息等）。  Zabbix agent 收集本地的操作信息并将数据报告给 Zabbix server 用于进一步处理。一旦出现异常 (例如硬盘空间已满或者有崩溃的服务进程)，Zabbix server 会主动警告管理员指定机器上的异常。  Zabbix agents 的极高效率缘于它可以利用本地系统调用来完成统计数据的采集。

en-us	#### Overview  Zabbix can be used for centralized monitoring and analysis of log files with/without log rotation support.  Notifications can be used to warn users when a log file contains certain strings or string patterns.  To monitor a log file you must have:  -   Zabbix agent running on the host -   log monitoring item set up  ::: noteimportant The size limit of a monitored log file depends on [large file support](/manual/appendix/items/large_file_support). :::
zh-cn	#### 概述  Zabbix 可用于有/无日志轮询支持的日志文件的集中监控和分析。  当日志文件包含某些字符串或字符串模式时，可以使用通知来警告用户。  要监控日志文件，必须具有如下：  -   主机上已运行Zabbix agent -   设置日志监控项  ::: noteimportant 被监控日志文件的大小限制取决于[大文件支持](/manual/appendix/items/large_file_support)。 :::

en-us	#### Overview  Zabbix can query metrics exposed in the Prometheus line format.  Two steps are required to start gathering Prometheus data:  -   an [HTTP master item](/manual/config/items/itemtypes/http) pointing     to the appropriate data endpoint, e.g.     `https://<prometheus host>/metrics` -   dependent items using a Prometheus preprocessing option to query     required data from the metrics gathered by the master item  There are two Prometheus data preprocessing options:  -   *Prometheus pattern* - used in normal items to query Prometheus data -   *Prometheus to JSON* - used in normal items and for low-level     discovery. In this case queried Prometheus data are returned in a     JSON format.
zh-cn	#### 概述  Zabbix 可以采集符合 Prometheus行协议格式的监控数据。  采集数据需要配置以下两步：  - 创建一个作为主要监控项的[HTTP监控项](/manual/config/items/itemtypes/http) 指向合适的站点批量采集数据。例如：`https://<prometheus host>/metrics` - 配置使用Prometheus 预处理选项的从属监控项，来从主要监控项中获取需要的数据  Zabbix 有两个Prometheus 预处理选项：  - *Prometheus正则匹配* - 可以应用于一般监控项中，用来从查询Prometheus行协议中提取数据 - *Prometheus转JSON* - 可以应用于一般监控项或低级别自动发现监控项。使用这个预处理步骤，将会将采集到的Prometheus 数据转化为JSON格式返回给监控项

en-us	#### Overview  Zabbix is a highly integrated network monitoring solution, offering a multiplicity of features in a single package.  **[Data gathering](/manual/config/items)**  -   availability and performance checks -   support for SNMP (both trapping and polling), IPMI, JMX, VMware     monitoring -   custom checks -   gathering desired data at custom intervals -   performed by server/proxy and by agents  **[Flexible threshold definitions](/manual/config/triggers)**  -   you can define very flexible problem thresholds, called triggers,     referencing values from the backend database  **[Highly configurable alerting](/manual/config/notifications)**  -   sending notifications can be customized for the escalation schedule,     recipient, media type -   notifications can be made meaningful and helpful using macro     variables -   automatic actions include remote commands  **[Real-time graphing](/manual/config/visualization/graphs/simple)**  -   monitored items are immediately graphed using the built-in graphing     functionality  **[Web monitoring capabilities](/manual/web_monitoring)**  -   Zabbix can follow a path of simulated mouse clicks on a web site and     check for functionality and response time  **[Extensive visualization options](/manual/config/visualization)**  -   ability to create custom graphs that can combine multiple items into     a single view -   network maps -   slideshows in a dashboard-style overview -   reports -   high-level (business) view of monitored resources  **[Historical data storage](/manual/installation/requirements#database_size)**  -   data stored in a database -   configurable history -   built-in housekeeping procedure  **[Easy configuration](/manual/config/hosts)**  -   add monitored devices as hosts -   hosts are picked up for monitoring, once in the database -   apply templates to monitored devices  **[Use of templates](/manual/config/templates)**  -   grouping checks in templates -   templates can inherit other templates  **[Network discovery](/manual/discovery)**  -   automatic discovery of network devices -   agent autoregistration -   discovery of file systems, network interfaces and SNMP OIDs  **[Fast web interface](/manual/web_interface)**  -   a web-based frontend in PHP -   accessible from anywhere -   you can click your way through -   audit log  **[Zabbix API](/manual/api)**  -   Zabbix API provides programmable interface to Zabbix for mass     manipulations, 3rd party software integration and other purposes.  **[Permissions system](/manual/config/users_and_usergroups)**  -   secure user authentication -   certain users can be limited to certain views  **[Full featured and easily extensible agent](/manual/concepts/agent)**  -   deployed on monitoring targets -   can be deployed on both Linux and Windows  **[Binary daemons](/manual/concepts/server)**  -   written in C, for performance and small memory footprint -   easily portable  **[Ready for complex environments](/manual/distributed_monitoring)**  -   remote monitoring made easy by using a Zabbix proxy
zh-cn	#### 概述  Zabbix 是一个高度集成的网络监控解决方案，在一个软件包中提供了多种功能。  **[数据收集](/manual/config/items)**  -   可用性和性能检查 -   支持 SNMP（trapping 和 polling）、IPMI、JMX、VMware监控 -   自定义检查 -   以自定义间隔收集所需数据 -   由 server/proxy 和 agents 执行  **[灵活的阈值定义](/manual/config/triggers)**  -   可以定义非常灵活的问题阈值，称为触发器，从后端数据库引用值  **[高度可配置的告警](/manual/config/notifications)**  -   可以针对升级计划、收件人、媒体类型自定义发送通知 -   使用宏可以使通知变得有意义和有用 -   自动化操作包括执行远程命令  **[实时图形](/manual/config/visualization/graphs/simple)**  -   采集到的监控项值可以使用内置的绘图功能立即绘图  **[网络监控功能](/manual/web_monitoring)**  -   Zabbix 可以跟踪网站上的模拟鼠标点击路径并检查功能和响应时间  **[广泛的可视化选项](/manual/config/visualization)**  -   创建自定义图形的能力，可以将多个监控项组合成一个聚合图形 -   网络拓扑图 -   在仪表盘中显示幻灯片 -   报表 -   受监控资源的高级（业务）视图  **[历史数据存储](/manual/installation/requirements#database_size)**  -   存储在数据库中的数据 -   可配置的历史（保留趋势） -   内置管家程序  **[建议的配置](/manual/config/hosts)**  -   将受监控的设备添加为主机 -   一旦主机被数据库添加，就会开始进行数据采集 -   将模板应用于受监控的设备  **[模板的使用](/manual/config/templates)**  -   在模板中分组检查 -   模板可以继承其他模板  **[网络发现](/manual/discovery)**  -   网络设备自动发现 -   agent 自动注册 -   发现文件系统、网络接口和 SNMP OID  **[便捷的 web 界面](/manual/web_interface)**  -   基于web的PHP前端 -   可从任何地方访问 -   可以通过你的方式点击（到任何页面） -   审计日志  **[Zabbix API](/manual/api)**  -   Zabbix API 为 Zabbix 提供可编程接口，用于大规模操作、第 3 方软件集成和其他用途。  **[权限系统](/manual/config/users_and_usergroups)**  -   安全用户认证 -   某些用户可以被限制仅访问某些视图  **[全功能且易于扩展的 agent](/manual/concepts/agent)**  -   部署在被监控目标上 -   Linux 和 Windows 操作系统都适用于  **[二进制守护进程](/manual/concepts/server)**  -   用 C 编写，用于提高性能和减少内存占用 -   轻量级、便携  **[为复杂环境做好准备](/manual/distributed_monitoring)**  -   使用 Zabbix proxy 轻松实现远程监控   

en-us	#### Overview  zabbix\_js is a command line utility that can be used for embedded script testing.  This utility will execute a user script with a string parameter and print the result. Scripts are executed using the embedded Zabbix scripting engine.  In case of compilation or execution errors zabbix\_js will print the error in stderr and exit with code 1.
zh-cn	#### 概述  zabbix\_js 是一个命令行实用程序，可用于嵌入脚本测试。  该程序可执行带有字符串参数的用户自定义脚本并打印结果。脚本的执行是由内嵌的Zabbix脚本引擎来完成的。  在编译或执行错误的情况下，zabbix\_js将在stderr中打印错误并以代码1退出。

en-us	#### Overview  Zabbix Mac OS agent can be installed from PKG installer packages available for [download](https://www.zabbix.com/download_agents#tab:44). Versions with or without encryption are available.
zh-cn	#### 概述  Zabbix Mac OS Agent 可以从 PKG 安装程序包安装。 点此 [下载](https://www.zabbix.com/download_agents#tab:44)。 加密版本和不加密版本均可以下载。

en-us	#### Overview  Zabbix offers automatic network discovery functionality that is effective and very flexible.  With network discovery properly set up you can:  -   speed up Zabbix deployment -   simplify administration -   use Zabbix in rapidly changing environments without excessive     administration  Zabbix network discovery is based on the following information:  -   IP ranges -   Availability of external services (FTP, SSH, WEB, POP3, IMAP, TCP,     etc) -   Information received from Zabbix agent (only unencrypted mode is     supported) -   Information received from SNMP agent  It does NOT provide:  -   Discovery of network topology  Network discovery basically consists of two phases: discovery and actions.
zh-cn	#### 概述  Zabbix提供高效灵活的网络自动发现功能。  网络发现的优势：  -   加快部署速度 -   简化管理 -   在快速变化的环境中避免过度管理  Zabbix网络发现依赖于以下信息：  -   IP地址范围 -   可用的外部服务 (FTP, SSH, WEB, POP3, IMAP, TCP等) -   来自Zabbix agent的信息(仅支持未加密模式) -   来自SNMP agent的信息  不支持：  -   网络拓扑发现  网络发现主要包含两个步骤：发现和动作。

en-us	#### Overview  Zabbix provides an effective and reliable way of monitoring a distributed IT infrastructure using Zabbix [proxies](/manual/distributed_monitoring/proxies).  Proxies can be used to collect data locally on behalf of a centralized Zabbix server and then report the data to the server.
zh-cn	#### 概览  Zabbix提供了一种使用Zabbix [proxies](/manual/distributed_monitoring/proxies). 监视分布式IT基础设施的有效和可靠的方法   Proxy代理可以用来代表中央Zabbix server在本地收集数据，然后将数据报告给Zabbix server。

en-us	#### Overview  Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.  Deploying a proxy is optional, but may be very beneficial to distribute the load of a single Zabbix server. If only proxies collect data, processing on the server becomes less CPU and disk I/O hungry.  A Zabbix proxy is the ideal solution for centralized monitoring of remote locations, branches and networks with no local administrators.  Zabbix proxy requires a separate database.  ::: noteimportant Note that databases supported with Zabbix proxy are SQLite, MySQL and PostgreSQL. Using Oracle is at your own risk and may contain some limitations as, for example, in [return values](/manual/discovery/low_level_discovery#overview) of low-level discovery rules. :::  See also: [Using proxies in a distributed environment](/manual/distributed_monitoring/proxies)
zh-cn	#### 概述  Zabbix proxy 是一个可以从一个或多个受监控设备采集监控数据并将信息发送到 Zabbix server 的进程，主要是代表 Zabbix server 工作。 所有收集的数据都在本地缓存，然后传输到 proxy 所属的 Zabbix server。  部署Zabbix proxy 是可选的，但可能非常有利于分担单个 Zabbix server 的负载。 如果只有代理采集数据，则 Zabbix server 上会减少 CPU 和磁盘 I/O 的开销。  Zabbix proxy 是无需本地管理员即可集中监控远程位置、分支机构和网络的理想解决方案。  Zabbix proxy 需要使用独立的数据库。  ::: noteimportant 值得注意的是，Zabbix proxy 支持 SQLite、MySQL和PostgreSQL 作为数据库。使用 Oracle 或 DB2 需要您承担一定的风险，例如，在自动发现规则中的遇到问题 [返回值](/manual/discovery/low_level_discovery#overview) 。 :::  详见：[在分布式环境中使用 Zabbix proxy](/manual/distributed_monitoring/proxies)。

en-us	#### Overview  Zabbix server is the central process of Zabbix software.  The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.  The server is the central repository in which all configuration, statistical and operational data is stored, and it is the entity in Zabbix that will actively alert administrators when problems arise in any of the monitored systems.  The functioning of a basic Zabbix server is broken into three distinct components; they are: Zabbix server, web frontend and database storage.  All of the configuration information for Zabbix is stored in the database, which both the server and the web frontend interact with. For example, when you create a new item using the web frontend (or API) it is added to the items table in the database. Then, about once a minute Zabbix server will query the items table for a list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data section.
zh-cn	#### 概述  Zabbix server 是整个 Zabbix 软件的核心程序。  Zabbix Server负责执行数据的主动轮询和被动获取，计算触发器条件，向用户发送通知。它是Zabbix Agent 和 Proxy 报告系统可用性和完整性数据的核心组件。Server自身可以通过简单服务远程检查网络服务（如Web服务器和邮件服务器）。  Zabbix Server是所有配置、统计和操作数据的中央存储中心，也是Zabbix监控系统的告警中心。在监控的系统中出现任何异常，将发出通知给管理员。  基本的 Zabbix Server 的功能分解成为三个不同的组件。他们是：Zabbix server、Web前端和数据库。  Zabbix 的所有配置信息都存储在 Server和Web前端进行交互的数据库中。例如，当你通过Web前端（或者API）新增一个监控项时，它会被添加到数据库的监控项表里。然后，Zabbix server 以每分钟一次的频率查询监控项表中的有效项，接着将它存储在 Zabbix server 中的缓存里。这就是为什么 Zabbix前端所做的任何更改需要花费两分钟左右才能显示在最新的数据段的原因。

en-us	#### Overview  Zabbix server uses a JSON- based communication protocol for receiving data from Zabbix sender with the help of [trapper item](/manual/config/items/itemtypes/trapper).  Request and response messages must begin with [header and data length](/manual/appendix/protocols/header_datalen).
zh-cn	#### 概述  Zabbix server使用基于JSON的通信协议，在[trapper item](/manual/config/items/itemtypes/trapper)的帮助下从Zabbix sender接收数据。  请求和响应消息必须以[header and data length](/manual/appendix/protocols/header_datalen)开头。

en-us	#### Overview  Zabbix strives to provide a growing list of useful out-of-the-box [templates](/manual/config/templates). Out-of-the-box templates come preconfigured and thus are a useful way for speeding up the deployment of monitoring jobs.  The 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. -   It is also possible to download the template from [Zabbix git     repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)     directly (make sure the template is compatible with your Zabbix     version).  Please use the sidebar to access information about specific template types and operation requirements.  See also:  -   [Template import](/manual/xml_export_import/templates#importing) -   [Linking a     template](/manual/config/templates/linking#linking_a_template)
zh-cn	#### 概述  Zabbix致力于提供越来越多有用的开箱即用[模板](/manual/config/templates)列表。 开箱即用的模板已预先配置，这是加速监控作业部署的有效方法。  模板获取来源：  -  在新安装的Zabbix中 - 前往*配置* → *模板*; -   如果是从旧版本升级的Zabbix，你可以在下载的最新版本的Zabbix的`templates` 目录中找到模板文件。在经过手工  导入这些模板文件后，可以在*配置* → *模板*页找到模板。 -   可以从[Zabbix git repository](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates)下载模板文件。（请确认模板文件与您的Zabbix兼容）  请使用侧边栏目录访问特定类型模板及操作须知。  参考资料:  -   [导入模板](/manual/xml_export_import/templates#importing) -   [链接模板](/manual/config/templates/linking#linking_a_template)

en-us	#### Overview  Zabbix supports a number of built-in macros which may be used in various situations. These macros are variables, identified by a specific syntax:      {MACRO}   Macros resolve to a specific value depending on the context.  Effective use of macros allows to save time and make Zabbix configuration more transparent.  In one of typical uses, a macro may be used in a template. Thus a trigger on a template may be named "Processor load is too high on {HOST.NAME}". When the template is applied to the host, such as Zabbix server, the name will resolve to "Processor load is too high on Zabbix server" when the trigger is displayed in the Monitoring section.  Macros may be used in item key parameters. A macro may be used for only a part of the parameter, for example `item.key[server_{HOST.HOST}_local]`. Double-quoting the parameter is not necessary as Zabbix will take care of any ambiguous special symbols, if present in the resolved macro.  There are other types of macros in Zabbix.  Zabbix supports the following macros:  -   `{MACRO}` - built-in macro (see [full list](/manual/appendix/macros/supported_by_location)) -   `{<macro>.<func>(<params>)}` - macro [functions](/manual/config/macros/macro_functions) -   `{$MACRO}` - [user-defined macro](/manual/config/macros/user_macros), optionally [with context](/manual/config/macros/user_macros_context) -   `{#MACRO}` - macro for [low-level discovery](/manual/config/macros/lld_macros) -   `{?EXPRESSION}` - [expression macro](/manual/config/macros/expression_macros)
zh-cn	#### 概述  Zabbix支持许多内置宏，可用于各种情况。这些宏是由特定语法标识的变量：      {MACRO}   宏根据上下文解析为特定值。  有效使用宏可以节省时间，并使Zabbix配置更加透明。  在一种典型用途中，宏可以用于模板中。因此，模板上的触发器可能被命名为“{HOST.NAME}上的处理器负载过高”。当模板应用于主机(如Zabbix服务器)时，当触发器显示在监控部分时，名称将解析为“Zabbix服务器上的处理器负载过高”。  宏可用于监控项键参数。宏只能用于参数的一部分，例如`item.key[server_{HOST.HOST}_local]`。不需要双引号引用参数，因为如果解析宏中存在任何不明确的特殊符号，Zabbix将处理这些符号。  除了内置宏之外，Zabbix还支持用户定义宏、带有上下文的用户定义宏和用于低级发现的宏。  另见： - · `{MACRO}` - 内置宏（参见 [完整列表](/manual/appendix/macros/supported_by_location)） - · `{<macro>.<func>(<params>)}` - 宏[函数](/manual/config/macros/macro_functions) - · `{$MACRO}` - [用户定义的宏](/manual/config/macros/user_macros)，可选的[上下文](/manual/config/macros/user_macros_context) - · `{#MACRO}` - 用于[底层自动发现]的宏（/manual/config/macros/lld_macros） - · `{?EXPRESSION}` - [表达式宏](/manual/config/macros/expression_macros)

en-us	#### Overview  Zabbix supports encrypted communications between Zabbix components using Transport Layer Security (TLS) protocol v.1.2 and 1.3 (depending on the crypto library). Certificate-based and pre-shared key-based encryption is supported.  Encryption can be configured for connections:  -   Between Zabbix server, Zabbix proxy, Zabbix agent, zabbix\_sender     and zabbix\_get utilities -   To Zabbix database [from Zabbix frontend and     server/proxy](/manual/appendix/install/db_encrypt)  Encryption is optional and configurable for individual components:  -   Some proxies and agents can be configured to use certificate-based     encryption with the server, while others can use pre-shared     key-based encryption, and yet others continue with unencrypted     communications (as before) -   Server (proxy) can use different encryption configurations for     different hosts  Zabbix daemon programs use one listening port for encrypted and unencrypted incoming connections. Adding an encryption does not require opening new ports on firewalls.
zh-cn	 #### 概述  Zabbix支持使用TLS协议v.1.2和1.3(取决于加密库)在Zabbix组件之间进行加密通信。支持证书加密和预共享密钥加密。  可以为连接配置加密:  -   Zabbix server，Zabbix proxy，Zabbix agent，Zabbix \_sender和Zabbix \_get工具 -   到Zabbix数据库[从zabbix前端和server/proxy](/manual/appendix/install/db_encrypt)  加密是可选和可配置的单个组件:  -   一些proxy代理和agent代理可以配置为使用服务器的基于证书的加密，而其他的可以使用基于预共享密钥的加密，而其他的则继续使用未加密的通信(与前面一样) -   Server (proxy) 可以为不同的主机使用不同的加密配置。  Zabbix守护程序为传入的加密和非加密连接使用一个侦听端口。 添加加密并不需要在防火墙上打开新的端口。

en-us	#### Overview  Zabbix supports the sending of SMS messages using a serial GSM modem connected to Zabbix server's serial port.  Make sure that:  -   The speed of the serial device (normally /dev/ttyS0 under Linux)     matches that of the GSM modem. Zabbix does not set the speed of the     serial link. It uses default settings. -   The 'zabbix' user has read/write access to the serial device. Run     the command ls –l /dev/ttyS0 to see current permissions of the     serial device. -   The GSM modem has PIN entered and it preserves it after power reset.     Alternatively you may disable PIN on the SIM card. PIN can be     entered by issuing command AT+CPIN="NNNN" (NNNN is your PIN number,     the quotes must be present) in a terminal software, such as Unix     minicom or Windows HyperTerminal.  Zabbix has been tested with these GSM modems:  -   Siemens MC35 -   Teltonika ModemCOM/G10  To configure SMS as the delivery channel for messages, you also need to configure SMS as the media type and enter the respective phone numbers for the users.
zh-cn	#### 概述  Zabbix 支持使用连接到 Zabbix server 串行口的串行 GSM 调制解调器发送短信。  请确保满足以下条件：  -   串行设备的速率（Linux下通常为 /dev/ttyS0 ）与GSM调制解调器的速度一致。Zabbix没有设置串行链路的速度。它使用默认设置。 -   'zabbix'用户对串行设备具有读/写访问权限。执行ls -l /dev/ttyS0命令来查看当前串口设备的权限。 -   GSM调制解调器已经输入了PIN码，并且在电源复位后会将其保留。或者，您可以禁用SIM卡上的PIN码。可以通过在终端软件（如Unix minicom或Windows HyperTerminal）中发出命令AT + CPIN =“NNNN” 来输入PIN码（NNNN是您的PIN码，且必须放在引号中）。  Zabbix已通过以下GSM调制解调器的测试：  -   Siemens MC35 -   Teltonika ModemCOM/G10  配置短信作为消息的传送通道时，需要将短信配置为媒介类型，并输入相应用户的电话号码。

en-us	#### Overview  Zabbix supports TimescaleDB, a PostgreSQL-based database solution of automatically partitioning data into time-based chunks to support faster performance at scale.  ::: notewarning Currently TimescaleDB is not supported by Zabbix proxy. :::  Instructions on this page can be used for creating TimescaleDB database or migrating from existing PostgreSQL tables to TimescaleDB.
zh-cn	#### 概述  Zabbix支持TimescaleDB，这是一种基于PostgreSQL的数据库解决方案，可自动将数据分为基于时间的块，以支持更快的大规模性能。  ::: notewarning 目前，Zabbix代理不支持 TimescaleDB 。 ::: 此章节会介绍创建 TimescaleDB 数据库或从现有的 PostgreSQL 表迁移到 TimescaleDB

en-us	#### Overview  Zabbix was created by Alexei Vladishev, and currently is actively developed and supported by Zabbix SIA.  Zabbix is an enterprise-class open source distributed monitoring solution.  Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers, virtual machines, applications, services, databases, websites, the cloud and more. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualization features based on the stored data. This makes Zabbix ideal for capacity planning.  Zabbix supports both polling and trapping. All Zabbix reports and statistics, as well as configuration parameters, are accessed through a web-based frontend. A web-based frontend ensures that the status of your network and the health of your servers can be assessed from any location. Properly configured, Zabbix can play an important role in monitoring IT infrastructure. This is equally true for small organizations with a few servers and for large companies with a multitude of servers.  Zabbix is free of cost. Zabbix is written and distributed under the GPL General Public License version 2. It means that its source code is freely distributed and available for the general public.  [Commercial support](http://www.zabbix.com/support.php) is available and provided by Zabbix Company and its partners around the world.  Learn more about [Zabbix features](features).  
zh-cn	#### 概述  Zabbix 是由 Alexei Vladishev 创建，目前是由 Zabbix SIA 在持续开发和提供支持。  Zabbix 是一种企业级的分布式开源监控解决方案。  Zabbix 是一款能够监控众多网络参数和服务器的健康度和完整性的软件。Zabbix 使用灵活的通知机制，允许用户为几乎任何事件配置基于邮件的警报。这样可以快速相应服务器问题。Zabbix 基于存储的数据提供出色的报告和数据可视化。这些功能使得 Zabbix 成为容量规划的理想选择。  Zabbix 支持轮询和被动捕获。所有的 Zabbix 报告、统计信息和配置参数都可以通过基于 Web 的前端页面进行访问。基于 Web 的前端页面确保您的网络状态和服务器健康状况可以从任何地方进行评估。在经过适当的配置后，Zabbix 可以在监控 IT 基础设施方面发挥重要作用。无论是对于拥有少量服务器的小型组织，还是拥有大量服务器的大型公司而言，同样适用。  Zabbix 是免费的。Zabbix 是根据 GPL 通用公共许可证的第二版编写和分发的。这意味着它的源代码是免费分发的，并且可供公共使用。  [商业支持](http://www.zabbix.com/support.php) 由 Zabbix 公司提供。  了解更多 [Zabbix 功能](features)。  

en-us	#### Overview  Zabbix web frontend can be temporarily disabled in order to prohibit access to it. This can be useful for protecting the Zabbix database from any changes initiated by users, thus protecting the integrity of database.  Zabbix database can be stopped and maintenance tasks can be performed while Zabbix frontend is in maintenance mode.  Users from defined IP addresses will be able to work with the frontend normally during maintenance mode.
zh-cn	#### 概述  可以暂时禁用 Zabbix Web 前端以禁止对其进行访问。这对于保护 Zabbix 数据库免受用户发起的任何更改非常有用，从而保护数据库的完整性。  当 Zabbix 前端处于维护模式时，可以停止 Zabbix 数据库并执行维护任务。  用户使用已定义IP 地址将能够在维护模式下正常访问前端。

en-us	#### Overview  Zabbix web service is a process that is used for communication with external web services. Currently, Zabbix web service is used for generating and sending scheduled reports with plans to add additional functionality in the future.  Zabbix server connects to the web service via HTTP(S). Zabbix web service requires Google Chrome to be installed on the same host; on some distributions the service may also work with Chromium (see [known issues](/manual/installation/known_issues#chromium_for_zabbix_web_service_on_ubuntu_20)) .  
zh-cn	#### 概述  Zabbix web service 是一个用来连接外部网站服务的进程。现在，Zabbix web service 用来收集和发送定时报告，并且计划未来添加更多功能。  Zabbix server通过HTTP(s)连接到web服务。Zabbix web service要求谷歌浏览器安装在同一台主机上；在某些发行版上，该服务也可以与Chromium一起使用（可查看 [known issues](/manual/installation/known_issues#chromium_for_zabbix_web_service_on_ubuntu_20)）。

en-us	#### Overview  Zabbix web service is a process that is used for communication with external web services.  This section lists parameters supported in Zabbix web service configuration file (zabbix\_web\_service.conf). Note that:  -   The default values reflect process defaults, not the values in the     shipped configuration files; -   Zabbix supports configuration files only in UTF-8 encoding without     [BOM](https://en.wikipedia.org/wiki/Byte_order_mark); -   Comments starting with "\#" are only supported at the beginning of     the line.
zh-cn	#### 概述  Zabbix web 服务是一个用于与外部web服务通信的进程。   本节列出了 Zabbix web service配置文件 (zabbix\_web\_service.conf)中所有支持的参数。请注意：  -   默认值表示的是进程默认值，而不是附带的配置文件中的值； -   Zabbix仅支持UTF-8编码格式的配置文件，不支持 [BOM](https://en.wikipedia.org/wiki/Byte_order_mark)； -   只支持在行首以“\#”开头来注释。

en-us	#### Overview  Zabbix Windows agent can be installed from Windows MSI installer packages (32-bit or 64-bit) available for [download](https://www.zabbix.com/download_agents#tab:44).  A 32-bit package cannot be installed on a 64-bit Windows.  All packages come with TLS support, however, configuring TLS is optional.  Both UI and command-line based installation is supported.
zh-cn	#### 概述  可以从Windows MSI安装包（32位或64位）安装Zabbix agent。[download](https://www.zabbix.com/download_agents#tab:44).  32位包不能安装在64位Windows中。  所有软件包都支持TLS，然而，配置TLS是可选的。  支持UI和命令行的安装。

en-us	### Packages  SQL scripts have been moved from the `/usr/share/doc` directory to `/usr/share` in Zabbix packages.
zh-cn	### 包  SQL 脚本已从“/usr/share/doc”目录移动到 Zabbix 包中的“/usr/share”。

en-us	#### Page menu  The page menu can be opened by clicking on the three dots ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_menu.png) next to the page name:  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/page_menu.png)  It contains the following options:  -   *Copy* - copy the page -   *Delete* - delete the page (pages can only be deleted in the     dashboard editing mode) -   *Properties* - customize the page parameters (the name and the page     display period in a slideshow)
zh-cn	#### 页面菜单  页面菜单可通过点击页面名称旁的三个点 ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/dashboard_page_menu.png) 来打开：  ![](../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/dashboard/page_menu.png)  它包含以下选项：  -   *复制* - 复制页面 -   *删除* - 删除页面（页面只能在仪表盘编辑模式删除） -   *属性* - 自定义页面参数（名称和页面在滑动显示中的显示时间范围）

en-us	#### Parameter - array  If the key parameter is an array, it is again enclosed in square brackets, where individual parameters come in line with the rules and syntax of specifying multiple parameters.  ![](../../../../../assets/en/manual/config/key_param_array.png)  ::: noteimportant Multi-level parameter arrays, e.g. `[a,[b,[c,d]],e]`, are not allowed. :::
zh-cn	#### 参数 - 数组  如果key参数是一个数组，它需要包含在方括号中，其中各个参数需要列为一行且符合多个参数的规则和语法。  ![](../../../../../assets/en/manual/config/key_param_array.png)  ::: noteimportant 多级参数数组, 例如 `[a,[b,[c,d]],e]`，是不受支持的。 :::

en-us	### Parameters  `(array)` IDs of hosts to delete.
zh-cn	 ### 参数  `(array)` 要删除主机的ID。

en-us	### Parameters  `(array)` IDs of items to clear.
zh-cn	 ### 参数  `(array)`需要删除历史数据的监控项ID。

en-us	### Parameters  `(array)` IDs of proxies to delete.
zh-cn	### 参数  `(array)` 要删除的proxy IDs。

en-us	### Parameters  `(array)` IDs of the actions to delete.
zh-cn	### 参数  `(array)` 要删除动作的 ID。

en-us	### Parameters  `(array)` IDs of the correlations to delete.
zh-cn	### 参数  `(array)` 要删除的关联 ID。

en-us	### Parameters  `(array)` IDs of the dashboards to delete.
zh-cn	### 参数  `(array)`要删除的仪表盘ID。

en-us	### Parameters  `(array)` IDs of the discovery rules to delete.
zh-cn	 ### 参数  `(array)` 要删除的发现规则的ID。

en-us	### Parameters  `(array)` IDs of the global macros to delete.
zh-cn	### 参数  `(array)` 需要删除的全局宏ID.

en-us	### Parameters  `(array)` IDs of the graph prototypes to delete.
zh-cn	 ### 参数  `(array)` 要删除的图表原型的ID。

en-us	### Parameters  `(array)` IDs of the graphs to delete.
zh-cn	### 参数  `(array)` 要删除的图表的ID。

en-us	### Parameters  `(array)` IDs of the host groups to delete.
zh-cn	 ### 参数  要删除主机组的`(数组)`ID。

en-us	### Parameters  `(array)` IDs of the host interfaces to delete.
zh-cn	### 参数  要删除主机接口的`(数组)`ID。

en-us	### Parameters  `(array)` IDs of the host macros to delete.
zh-cn	### 参数  `(array)` 需要删除主机宏的ID.

en-us	### Parameters  `(array)` IDs of the host prototypes to delete.
zh-cn	### 参数  `(array)` 要删除主机原型的ID。

en-us	### Parameters  `(array)` IDs of the icon maps to delete.
zh-cn	### 参数  `(array)` 要删除的多个图标映射的 ID。

en-us	### Parameters  `(array)` IDs of the images to delete.
zh-cn	### 参数  `(array)` 指定删除图像的 ID。

en-us	### Parameters  `(array)` IDs of the item prototypes to delete.
zh-cn	### 参数  删除可通过监控项原型的ID（数组）。

en-us	### Parameters  `(array)` IDs of the items to delete.
zh-cn	### 参数  `(array)` 删除目标监控项 ID。

en-us	### Parameters  `(array)` IDs of the LLD rules to delete.
zh-cn	### 参数  `(array)` 要删除的 LLD 规则的 ID。

en-us	### Parameters  `(array)` IDs of the maintenance periods to delete.
zh-cn	### 参数  `(array)`要删除的维护周期的IDs。

en-us	### Parameters  `(array)` IDs of the maps to delete.
zh-cn	### 参数  `(array)` 要删除的拓扑图的id列表.

en-us	### Parameters  `(array)` IDs of the media types to delete.
zh-cn	### 参数  `(array)` 要删除的媒介类型的ID。

en-us	### Parameters  `(array)` IDs of the regular expressions to delete.
zh-cn	### 参数  `(array)` 代表计划删除的正则表达式的ID号。

en-us	### Parameters  `(array)` IDs of the roles to delete.
zh-cn	### 参数  `(array)` 要删除的角色用户ID号。

en-us	### Parameters  `(array)` IDs of the scheduled reports to delete.
zh-cn	### 参数  `(array)` 将要删除的规划报告ID。

en-us	### Parameters  `(array)` IDs of the scripts to delete.
zh-cn	###  参数  `(数组)` 要删除的脚本ID。

en-us	### Parameters  `(array)` IDs of the services to delete.
zh-cn	 ### 参数  `(数组)` 要删除的服务ID。

en-us	### Parameters  `(array)` IDs of the SLAs to delete.
zh-cn	### 参数  `(array)` 要删除的SLA 的id列表

en-us	### Parameters  `(array)` IDs of the template dashboards to delete.
zh-cn	### 参数 `(array)` 需要删除的模板仪表盘ID。

en-us	### Parameters  `(array)` IDs of the templates to delete.
zh-cn	### 参数  `(array)` 要删除的模板的ID。

en-us	### Parameters  `(array)` IDs of the tokens to delete.
zh-cn	### 参数  `(array)` 要删除的令牌的 ID。

en-us	### Parameters  `(array)` IDs of the tokens to generate.
zh-cn	### 参数  `(array)` 要生成的令牌的ID。

en-us	### Parameters  `(array)` IDs of the trigger prototypes to delete.
zh-cn	### 参数  `(array)`要删除的触发器原型的 ID.

en-us	### Parameters  `(array)` IDs of the triggers to delete.
zh-cn	### 参数  `(array)` 要删除的触发器ID列表.

en-us	### Parameters  `(array)` IDs of the user groups to delete.
zh-cn	### 参数  `(array)` 需要删除的用户组ID.

en-us	### Parameters  `(array)` IDs of the value maps to delete.
zh-cn	### 参数  `(array)` 需要删除的值映射的ID。

en-us	### Parameters  `(array)` IDs of the web scenarios to delete.
zh-cn	 ### 参数  `(array)` 需要被删除的Web场景的ID。

en-us	### Parameters  `(array)` IDs of users to delete.
zh-cn	### 参数  `(array)` 要删除用户的ID.

en-us	### Parameters  `(array)` IDs of users to unblock.
zh-cn	### 参数  `(array)` 需要解锁用户的ID.

en-us	### Parameters  `(array)` The method accepts an empty array.
zh-cn	### 参数  `(array)` 该方法接受一个空的数组。

en-us	### Parameters  `(array)` The method accepts an empty array.
zh-cn	### 参数  `(array)` 此方法接受一个空数组.

en-us	#### - Parameters  Both functions use almost the same set of parameters. Use the list of [supported functions](/manual/appendix/functions) for reference.
zh-cn	#### 2 参数  这两个功能使用几乎相同的参数集。请参考 [支持的函数](/manual/appendix/functions) 列表。

en-us	#### Parameters  Foreach functions support two common parameters - item filter and time period:      foreach_function(item filter,time period)  for example:      avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)  Some functions support additional parameters.
zh-cn	#### 参数  Foreach 函数支持两个常用参数 - 监控项过滤器和时间段：      foreach_function(item filter,time period)  例如：      avg_foreach(/*/mysql.qps?[group="MySQL Servers"],5m)  一些函数支持附加参数。

en-us	### Parameters  `(object/array)` Action properties to be updated.  The `actionid` property must be defined for each action, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard action properties](object#action), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object to replace the current filter.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to replace existing operations.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to replace existing recovery operations.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to replace existing update operations.|
zh-cn	### 参数  `(object/array)` 要更新的动作属性。  必须为每个动作定义 `actionid` 属性，所有其他属性都是可选的。只会更新传递的属性，所有其他属性将保持不变。  此外，还有 [标准动作参数](object#动作)，方法接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |filter|object|动作[过滤](/manual/api/reference/action/object#动作过滤) 对象以替换当前过滤。| |operations|array|动作[操作](/manual/api/reference/action/object#动作操作) 以替换已经存在的操作。| |recovery\_operations|array|动作[恢复操作](/manual/api/reference/action/object#动作恢复操作) 以替换已经存在的恢复操作。| |update\_operations|array|动作[更新操作](/manual/api/reference/action/object#动作更新操作) 以替换已经存在的更新操作。|

en-us	### Parameters  `(object/array)` Action properties to be updated.  The `actionid` property must be defined for each action, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard action properties](object#action), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object to replace the current filter.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to replace existing operations.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to replace existing recovery operations.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to replace existing update operations.|
zh-cn	### 参数  `(object/array)` 要更新的动作属性。  必须为每个动作定义 `actionid` 属性，所有其他属性都是可选的。只会更新传递的属性，所有其他属性将保持不变。  此外，还有 [标准动作参数](object#动作)，方法接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |filter|object|动作[过滤](/manual/api/reference/action/object#动作过滤) 对象以替换当前过滤。| |operations|array|动作[操作](/manual/api/reference/action/object#动作操作) 以替换已经存在的操作。| |recovery\_operations|array|动作[恢复操作](/manual/api/reference/action/object#动作恢复操作) 以替换已经存在的恢复操作。| |update\_operations|array|动作[更新操作](/manual/api/reference/action/object#动作更新操作) 以替换已经存在的更新操作。|

en-us	### Parameters  `(object/array)` Actions to create.  Additionally to the [standard action properties](object#action), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Action [filter](/manual/api/reference/action/object#action_filter) object for the action.| |operations|array|Action [operations](/manual/api/reference/action/object#action_operation) to create for the action.| |recovery\_operations|array|Action [recovery operations](/manual/api/reference/action/object#action_recovery_operation) to create for the action.| |update\_operations|array|Action [update operations](/manual/api/reference/action/object#action_update_operation) to create for the action.|
zh-cn	 ### 参数  `(object/array)` 要创建的动作 。  此外，还有 [标准动作参数](object#动作)，方法接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |--|--|------| |filter|object|动作的动作[过滤](/manual/api/reference/action/object#动作过滤) 对象。| |operations|array|为这个动作创建的动作[操作](/manual/api/reference/action/object#动作操作) 。| |recovery\_operations|array|为这个动作创建的动作[恢复操作](/manual/api/reference/action/object#动作恢复操作)。| |update\_operations|array|为这个动作创建的动作[更新操作](/manual/api/reference/action/object#动作更新操作)。|

en-us	### Parameters  `(object/array)` A task to create.  The method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|Task type.<br><br>Possible values:<br>1 - Diagnostic information;<br>6 - Check now.| |**request**<br>(required)|object|Task request object according to the task type. Correct format of request object is described in [Task object](/manual/api/reference/task/object) section.| |proxy\_hostid|integer|Proxy about which Diagnostic information task will collect data.<br><br>Ignored for 'Check now' tasks.|  *Note* that 'Check now' tasks can be created only for the following types of items/discovery rules:  -   Zabbix agent -   SNMPv1/v2/v3 agent -   Simple check -   Internal check -   External check -   Database monitor -   HTTP agent -   IPMI agent -   SSH agent -   TELNET agent -   Calculated check -   JMX agent
zh-cn	 ### 参数  `(object/array)` 要创建的任务。  该方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |**type**<br>(必须)|integer|任务类型.<br><br>可能的值：<br>1 - 诊断信息；<br>6 - 立即检查.| |**request**<br>(必须)|object|任务请求对象取决于任务类型。 [任务对象](/manual/api/reference/task/object) 中描述了请求对象的正确格式。| |proxy\_hostid|integer|关于哪个诊断信息任务将收集数据的代理。<br><br>忽略“立即检查”任务。|  *注意* “立即检查”任务只能为以下类型的监控项/自动发现规则创建：  -   Zabbix agent -   SNMPv1/v2/v3 agent -   Simple check -   Internal check -   External check -   Database monitor -   HTTP agent -   IPMI agent -   SSH agent -   TELNET agent -   Calculated check -   JMX agent

en-us	### Parameters  `(object/array)` A task to create.  The method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|Task type.<br><br>Possible values:<br>1 - Diagnostic information;<br>6 - Check now.| |**request**<br>(required)|object|Task request object according to the task type. Correct format of request object is described in [Task object](/manual/api/reference/task/object) section.| |proxy\_hostid|integer|Proxy about which Diagnostic information task will collect data.<br><br>Ignored for 'Check now' tasks.|  *Note* that 'Check now' tasks can be created only for the following types of items/discovery rules:  -   Zabbix agent -   SNMPv1/v2/v3 agent -   Simple check -   Internal check -   External check -   Database monitor -   HTTP agent -   IPMI agent -   SSH agent -   TELNET agent -   Calculated check -   JMX agent
zh-cn	 ### 参数  `(object/array)` 要创建的任务。  该方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |**type**<br>(必须)|integer|任务类型.<br><br>可能的值：<br>1 - 诊断信息；<br>6 - 立即检查.| |**request**<br>(必须)|object|任务请求对象取决于任务类型。 [任务对象](/manual/api/reference/task/object) 中描述了请求对象的正确格式。| |proxy\_hostid|integer|关于哪个诊断信息任务将收集数据的代理。<br><br>忽略“立即检查”任务。|  *注意* “立即检查”任务只能为以下类型的监控项/自动发现规则创建：  -   Zabbix agent -   SNMPv1/v2/v3 agent -   Simple check -   Internal check -   External check -   Database monitor -   HTTP agent -   IPMI agent -   SSH agent -   TELNET agent -   Calculated check -   JMX agent

en-us	### Parameters  `(object/array)` Correlation properties to be updated.  The `correlationid` property must be defined for each correlation, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object to replace the current filter.| |operations|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to replace existing operations.|
zh-cn	 ### 参数  `(object/array)` 需要更新的关联属性。  必须为每个关联定义 `correlationid` 属性，其它的属性都是可选的。只有传递的属性会被更新，其它属性都将保持不变。  除了[标准关联属性](object#关联)以外，此方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |filter|object|替换当前过滤器的关联[过滤](/manual/api/reference/correlation/object#关联过滤) 对象。| |operations|array|替换现有操作的关联[操作](/manual/api/reference/correlation/object#关联操作)。|

en-us	### Parameters  `(object/array)` Correlation properties to be updated.  The `correlationid` property must be defined for each correlation, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |filter|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object to replace the current filter.| |operations|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to replace existing operations.|
zh-cn	 ### 参数  `(object/array)` 需要更新的关联属性。  必须为每个关联定义 `correlationid` 属性，其它的属性都是可选的。只有传递的属性会被更新，其它属性都将保持不变。  除了[标准关联属性](object#关联)以外，此方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |filter|object|替换当前过滤器的关联[过滤](/manual/api/reference/correlation/object#关联过滤) 对象。| |operations|array|替换现有操作的关联[操作](/manual/api/reference/correlation/object#关联操作)。|

en-us	### Parameters  `(object/array)` Correlations to create.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**operations**<br>(required)|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to create for the correlation.| |**filter**<br>(required)|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object for the correlation.|
zh-cn	 ### 参数  `(object/array)` 要创建的关联。  除了[标准关联属性](object#关联)以外，此方法还接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |**operations**<br>（必需）|array|创建关联的关联[操作](/manual/api/reference/correlation/object#关联操作)。| |**filter**<br>（必需）|object|关联的关联[过滤](/manual/api/reference/correlation/object#关联过滤) 对象。|

en-us	### Parameters  `(object/array)` Correlations to create.  Additionally to the [standard correlation properties](object#correlation), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**operations**<br>(required)|array|Correlation [operations](/manual/api/reference/correlation/object#correlation_operation) to create for the correlation.| |**filter**<br>(required)|object|Correlation [filter](/manual/api/reference/correlation/object#correlation_filter) object for the correlation.|
zh-cn	 ### 参数  `(object/array)` 要创建的关联。  除了[标准关联属性](object#关联)以外，此方法还接受如下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |**operations**<br>（必需）|array|创建关联的关联[操作](/manual/api/reference/correlation/object#关联操作)。| |**filter**<br>（必需）|object|关联的关联[过滤](/manual/api/reference/correlation/object#关联过滤) 对象。|

en-us	### Parameters  `(object/array)` Dashboard properties to be updated.  The `dashboardid` property must be specified for each dashboard, all other properties are optional. Only the specified properties will be updated.  Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |pages|array|Dashboard [pages](object#dashboard_page) to replace the existing dashboard pages.<br><br>Dashboard pages are updated by the `dashboard_pageid` property. New dashboard pages will be created for objects without `dashboard_pageid` property and the existing dashboard pages will be deleted if not reused. Dashboard pages will be ordered in the same order as specified. Only the specified properties of the dashboard pages will be updated. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to replace the existing elements.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to replace the existing elements.|
zh-cn	### 参数  `(object/array)` 要更新的仪表盘属性。  必须为每个仪表盘定义 `dashboardid` 属性，其它的属性都是可选的。只有指定的属性会被更新，其它属性都将保持不变。  除了[标准仪表盘属性](object#仪表盘)以外，此方法还接受如下参数：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |pages|array|更新的仪表盘[页面](object#仪表盘页面) 。<br><br>仪表盘页面由`dashboard_pageid`属性更新。将为没有`dashboard_pageid`属性的对象创建新的仪表盘页面，如果不重新使用，现有仪表盘页面将被删除。仪表盘页面的顺序将与指定的顺序相同。只会更新仪表盘页面的指定属性。“pages”属性至少需要一个仪表盘页面对象。| |users|array|更新的仪表盘[用户](object#仪表盘用户) 。| |userGroups|array|更新的仪表盘[用户组](object#仪表盘用户组)。 |

en-us	### Parameters  `(object/array)` Dashboard properties to be updated.  The `dashboardid` property must be specified for each dashboard, all other properties are optional. Only the specified properties will be updated.  Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |pages|array|Dashboard [pages](object#dashboard_page) to replace the existing dashboard pages.<br><br>Dashboard pages are updated by the `dashboard_pageid` property. New dashboard pages will be created for objects without `dashboard_pageid` property and the existing dashboard pages will be deleted if not reused. Dashboard pages will be ordered in the same order as specified. Only the specified properties of the dashboard pages will be updated. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to replace the existing elements.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to replace the existing elements.|
zh-cn	### 参数  `(object/array)` 要更新的仪表盘属性。  必须为每个仪表盘定义 `dashboardid` 属性，其它的属性都是可选的。只有指定的属性会被更新，其它属性都将保持不变。  除了[标准仪表盘属性](object#仪表盘)以外，此方法还接受如下参数：  |属性|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |pages|array|更新的仪表盘[页面](object#仪表盘页面) 。<br><br>仪表盘页面由`dashboard_pageid`属性更新。将为没有`dashboard_pageid`属性的对象创建新的仪表盘页面，如果不重新使用，现有仪表盘页面将被删除。仪表盘页面的顺序将与指定的顺序相同。只会更新仪表盘页面的指定属性。“pages”属性至少需要一个仪表盘页面对象。| |users|array|更新的仪表盘[用户](object#仪表盘用户) 。| |userGroups|array|更新的仪表盘[用户组](object#仪表盘用户组)。 |

en-us	### Parameters  `(object/array)` Dashboards to create.  Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**pages**<br>(required)|array|Dashboard [pages](object#dashboard_page) to be created for the dashboard. Dashboard pages will be ordered in the same order as specified. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to be created on the dashboard.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to be created on the dashboard.|
zh-cn	 ### 参数  `(object/array)` 要创建的仪表盘。  除了[标准仪表盘属性](object#仪表盘)，此方法还接受以下参数：  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |**pages**<br>（必需）|array|仪表盘上创建的仪表盘[页面](object#仪表盘页面) 。仪表盘页面的顺序将与指定的顺序相同。`pages`属性至少需要一个仪表盘页面对象。| |users|array|仪表盘上创建的仪表盘[用户](object#仪表盘用户) 。| |userGroups|array|仪表盘上创建的仪表盘[用户组](object#仪表盘用户组) 。|

en-us	### Parameters  `(object/array)` Dashboards to create.  Additionally to the [standard dashboard properties](object#dashboard), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**pages**<br>(required)|array|Dashboard [pages](object#dashboard_page) to be created for the dashboard. Dashboard pages will be ordered in the same order as specified. At least one dashboard page object is required for `pages` property.| |users|array|Dashboard [user](object#dashboard_user) shares to be created on the dashboard.| |userGroups|array|Dashboard [user group](object#dashboard_user_group) shares to be created on the dashboard.|
zh-cn	 ### 参数  `(object/array)` 要创建的仪表盘。  除了[标准仪表盘属性](object#仪表盘)，此方法还接受以下参数：  |参数|[类型](/manual/api/reference_commentary#数据类型)|说明| |---------|---------------------------------------------------|-----------| |**pages**<br>（必需）|array|仪表盘上创建的仪表盘[页面](object#仪表盘页面) 。仪表盘页面的顺序将与指定的顺序相同。`pages`属性至少需要一个仪表盘页面对象。| |users|array|仪表盘上创建的仪表盘[用户](object#仪表盘用户) 。| |userGroups|array|仪表盘上创建的仪表盘[用户组](object#仪表盘用户组) 。|

en-us	### Parameters  `(object/array)` Discovery rule properties to be updated.  The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.|
zh-cn	 ### 参数  `(object/array)` 要更新的发现规则属性。  必须为每个发现规则定义“druleid”属性，所有其他属性是可选的。 只有传递的属性将被更新，所有其他属性将保持不变。  除了[标准发现规则属性](object#发现规则)，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |dchecks|array|发现[checks](/manual/api/reference/dcheck/object) 以替换现有的检查。|

en-us	### Parameters  `(object/array)` Discovery rule properties to be updated.  The `druleid` property must be defined for each discovery rule, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |dchecks|array|Discovery [checks](/manual/api/reference/dcheck/object) to replace existing checks.|
zh-cn	 ### 参数  `(object/array)` 要更新的发现规则属性。  必须为每个发现规则定义“druleid”属性，所有其他属性是可选的。 只有传递的属性将被更新，所有其他属性将保持不变。  除了[标准发现规则属性](object#发现规则)，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |dchecks|array|发现[checks](/manual/api/reference/dcheck/object) 以替换现有的检查。|

en-us	### Parameters  `(object/array)` Discovery rules to create.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**dchecks**<br>(required)|array|Discovery [checks](/manual/api/reference/dcheck/object) to create for the discovery rule.|
zh-cn	 ### 参数  `(object/array)` 要创建的发现规则。  除了[标准发现规则属性](object#发现规则)，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |**dchecks**<br>（必需）|array|发现 [checks](/manual/api/reference/dcheck/object) 为发现规则创建。|

en-us	### Parameters  `(object/array)` Discovery rules to create.  Additionally to the [standard discovery rule properties](object#discovery_rule), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**dchecks**<br>(required)|array|Discovery [checks](/manual/api/reference/dcheck/object) to create for the discovery rule.|
zh-cn	 ### 参数  `(object/array)` 要创建的发现规则。  除了[标准发现规则属性](object#发现规则)，此方法接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |**dchecks**<br>（必需）|array|发现 [checks](/manual/api/reference/dcheck/object) 为发现规则创建。|

en-us	### Parameters  `(object/array)` [Global macro properties](object#global_macro) to be updated.  The `globalmacroid` property must be defined for each global macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 需要更新的 [Global macro properties](object#全局宏) .  每个全局宏必须定义 `globalmacroid` 参数, 其他参数均为可选的. 只有通过的属性才会被更新，其他属性保持不变.

en-us	### Parameters  `(object/array)` Global macros to create.  The method accepts global macros with the [standard global macro properties](object#global_macro).
zh-cn	### 参数  `(object/array)` 需要创建的全局宏.  此方法接受具有 [标准全局宏属性 ](object#global_macro)的全局宏.

en-us	### Parameters  `(object/array)` Graph properties to be updated.  The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph properties](object#graph) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	### 参数  `(object/array)` 要更新的图表属性。  必须为每个图表定义 "graphid "属性，所有其他的属性是可选的。只有传递的属性会被更新，所有其他的属性将保持不变。  除了[标准图形属性](object#图表)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|图表[监控项](/manual/api/reference/graphitem/object)来替换现有的图表监控项。如果一个图表监控项有定义`gitemid`属性，它将被更新，否则将创建一个新的图表监控项。|

en-us	### Parameters  `(object/array)` Graph properties to be updated.  The `graphid` property must be defined for each graph, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph properties](object#graph) the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	### 参数  `(object/array)` 要更新的图表属性。  必须为每个图表定义 "graphid "属性，所有其他的属性是可选的。只有传递的属性会被更新，所有其他的属性将保持不变。  除了[标准图形属性](object#图表)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|图表[监控项](/manual/api/reference/graphitem/object)来替换现有的图表监控项。如果一个图表监控项有定义`gitemid`属性，它将被更新，否则将创建一个新的图表监控项。|

en-us	### Parameters  `(object/array)` Graph prototype properties to be updated.  The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	 ### 参数  `(object/array)` 要更新的图新原型属性。  `graphid`属性必须为每个图表原型定义，所有其他属性是可选的。只有通过的属性将被更新，所有其他的将保持不变。  除了[标准图形原型属性](object#graph_prototype)，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|[图表项目](/manual/api/reference/graphitem/object)将替换现有的图表项目。如果一个图表项目定义了 `gitemid` 属性，它将会被更新，否则会创建一个新的图表项目。|

en-us	### Parameters  `(object/array)` Graph prototype properties to be updated.  The `graphid` property must be defined for each graph prototype, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |gitems|array|Graph [items](/manual/api/reference/graphitem/object) to replace existing graph items. If a graph item has the `gitemid` property defined it will be updated, otherwise a new graph item will be created.|
zh-cn	 ### 参数  `(object/array)` 要更新的图新原型属性。  `graphid`属性必须为每个图表原型定义，所有其他属性是可选的。只有通过的属性将被更新，所有其他的将保持不变。  除了[标准图形原型属性](object#graph_prototype)，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |gitems|array|[图表项目](/manual/api/reference/graphitem/object)将替换现有的图表项目。如果一个图表项目定义了 `gitemid` 属性，它将会被更新，否则会创建一个新的图表项目。|

en-us	### Parameters  `(object/array)` Graph prototypes to create.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph prototypes. Graph items can reference both items and item prototypes, but at least one item prototype must be present.|
zh-cn	 ### 参数  `(object/array)` 要创建的图表原型。  除了[标准图表属性](object#graph_prototype)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |**gitems**<br>（必选）|array|要为图表原型创建的图表[项目](/manual/api/reference/graphitem/object)。图形项目可以同时引用项目和项目原型，但至少要有一个项目原型。|

en-us	### Parameters  `(object/array)` Graph prototypes to create.  Additionally to the [standard graph prototype properties](object#graph_prototype), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph prototypes. Graph items can reference both items and item prototypes, but at least one item prototype must be present.|
zh-cn	 ### 参数  `(object/array)` 要创建的图表原型。  除了[标准图表属性](object#graph_prototype)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |**gitems**<br>（必选）|array|要为图表原型创建的图表[项目](/manual/api/reference/graphitem/object)。图形项目可以同时引用项目和项目原型，但至少要有一个项目原型。|

en-us	### Parameters  `(object/array)` Graphs to create.  Additionally to the [standard graph properties](object#graph), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph.|
zh-cn	### 参数  `(object/array)` 要创建的图表。  除了[标准图表属性](object#图表)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |**gitems**<br>（必选）|array|要为图表创建的图表[监控项](/manual/api/reference/graphitem/object)。|

en-us	### Parameters  `(object/array)` Graphs to create.  Additionally to the [standard graph properties](object#graph), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |**gitems**<br>(required)|array|Graph [items](/manual/api/reference/graphitem/object) to be created for the graph.|
zh-cn	### 参数  `(object/array)` 要创建的图表。  除了[标准图表属性](object#图表)之外，该方法还接受以下参数。  |参数|[类型](/manual/api/reference_commentary#数据类型)|描述| |---------|---------------------------------------------------|-----------| |**gitems**<br>（必选）|array|要为图表创建的图表[监控项](/manual/api/reference/graphitem/object)。|

en-us	### Parameters  `(object/array)` [Host group properties](object#host_group) to be updated.  The `groupid` property must be defined for each host group, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
zh-cn	 ### 参数  `(对象/数组)` [主机组属性](object#host_group) 将被更新。  `groupid` 属性必须为每个主机组定义，所有其他属性都是可选的。只有给定的属性将被更新，其他所有属性将保持不变。

en-us	### Parameters  `(object/array)` Host groups to create. The method accepts host groups with the [standard host group properties](object#host_group).
zh-cn	 ### 参数  创建`(对象/数组)`主机组.该方法接受具有 [标准主机组属性](object#host_group) 的主机组。

en-us	### Parameters  `(object/array)` [Host interface properties](object#host_interface) to be updated.  The `interfaceid` property must be defined for each host interface, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 要更新的[主机接口属性](object#host_interface)   必须为每个主机接口定义`interfaceid`属性，所有其他属性都是可选的。 只有给定的属性将被更新，所有其他属性将保持不变。

en-us	### Parameters  `(object/array)` Host interfaces to create. The method accepts host interfaces with the [standard host interface properties](object#host_interface).
zh-cn	### 参数  `(object/array)` 创建主机接口，该方法接受主机接口的[标准主机接口属性](object#host_interface)。

en-us	### Parameters  `(object/array)` [Host macro properties](object#host_macro) to be updated.  The `hostmacroid` property must be defined for each host macro, all other properties are optional. Only the passed properties will be updated, all others will remain unchanged.
zh-cn	### 参数  `(object/array)` 需要更新的[Host macro properties](object#主机宏) .  每个主机宏必须定义 `hostmacroid` 参数, 其他参数均为可选的. 只有通过的属性才会被更新，其他属性保持不变.

en-us	### Parameters  `(object/array)` Host macros to create.  The method accepts host macros with the [standard host macro properties](object#host_macro).
zh-cn	### 参数  `(object/array)` 要创建主机宏.  此方法接受具有 [标准主机宏属性](object#host_macro)的主机宏.

en-us	### Parameters  `(object/array)` Host properties to be updated.  The `hostid` property must be defined for each host, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.  Note, however, that updating the host technical name will also update the host's visible name (if not given or empty) by the host's technical name value.  Additionally to the [standard host properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object#host_group) to replace the current host groups the host belongs to.<br><br>The host groups must have the `groupid` property defined. All host groups that are not listed in the request will be unlinked.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces.<br><br>All interfaces that are not listed in the request will be removed.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag) to replace the current host tags.<br><br>All tags that are not listed in the request will be removed.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros.<br><br>All macros that are not listed in the request will be removed.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. All templates that are not listed in the request will be only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the host.<br><br>The templates must have the `templateid` property defined.|  ::: notetip As opposed to the Zabbix frontend, when `name` (visible host name) is the same as `host` (technical host name), updating `host` via API will not automatically update `name`. Both properties need to be updated explicitly. :::
zh-cn	 ### 参数  `(对象/数组)` 待更新的主机属性。  `hostid` 属性必须为每台主机定义，其他属性都是可选的。只有给定的属性将被更新，其他所有属性将保持不变。  但是，请注意，更新主机技术名称也将根据主机的技术名称值更新主机的可见名称(如果没有给出或为空)。  除了[标准主机属性](object#host)以外，此方法接受如下参数:  |参数|[类](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |groups|对象/数组|更换主机所属的主机[组](/manual/api/reference/hostgroup/object#host_group)。<br><br>主机组必须已定义 `groupid` 属性。所有未在请求中列出的主机组将被解除链接。| |interfaces|对象/数组|主机[接口](/manual/api/reference/hostinterface/object)用于替换当前主机接口。 <br><br>所有未在请求中列出的接口将被删除。| |tags|对象/数组|主机[标签](/manual/api/reference/host/object#host_tag)替换当前主机标签。<br><br>所有未在请求中列出的标签将被删除。| |inventory|object|主机[清单](/manual/api/reference/host/object#host_inventory)属性。| |macros|对象/数组|[用户宏](/manual/api/reference/usermacro/object)替换当前用户宏。<br><br>所有未在请求中列出的宏将被删除。| |templates|对象/数组|[模板](/manual/api/reference/template/object)替换当前链接的模板。所有未在请求中列出的模板只会被解除链接。<br><br>模板必须定义了 `templateid` 属性。| |templates\_clear|对象/数组|[模板](/manual/api/reference/template/object)取消与主机的链接并清除。<br><br>模板必须定义了 `templateid` 属性。|  ::: notetip 与Zabbix前端不同，当 `name` (可见主机名)与 `host` (技术主机名)相同时，通过API更新 `host` 不会自动更新 `name` 。这两个属性都需要显式更新。 :::

en-us	### Parameters  `(object/array)` Host properties to be updated.  The `hostid` property must be defined for each host, all other properties are optional. Only the given properties will be updated, all others will remain unchanged.  Note, however, that updating the host technical name will also update the host's visible name (if not given or empty) by the host's technical name value.  Additionally to the [standard host properties](object#host), the method accepts the following parameters.  |Parameter|[Type](/manual/api/reference_commentary#data_types)|Description| |---------|---------------------------------------------------|-----------| |groups|object/array|Host [groups](/manual/api/reference/hostgroup/object#host_group) to replace the current host groups the host belongs to.<br><br>The host groups must have the `groupid` property defined. All host groups that are not listed in the request will be unlinked.| |interfaces|object/array|Host [interfaces](/manual/api/reference/hostinterface/object) to replace the current host interfaces.<br><br>All interfaces that are not listed in the request will be removed.| |tags|object/array|Host [tags](/manual/api/reference/host/object#host_tag) to replace the current host tags.<br><br>All tags that are not listed in the request will be removed.| |inventory|object|Host [inventory](/manual/api/reference/host/object#host_inventory) properties.| |macros|object/array|[User macros](/manual/api/reference/usermacro/object) to replace the current user macros.<br><br>All macros that are not listed in the request will be removed.| |templates|object/array|[Templates](/manual/api/reference/template/object) to replace the currently linked templates. All templates that are not listed in the request will be only unlinked.<br><br>The templates must have the `templateid` property defined.| |templates\_clear|object/array|[Templates](/manual/api/reference/template/object) to unlink and clear from the host.<br><br>The templates must have the `templateid` property defined.|  ::: notetip As opposed to the Zabbix frontend, when `name` (visible host name) is the same as `host` (technical host name), updating `host` via API will not automatically update `name`. Both properties need to be updated explicitly. :::
zh-cn	 ### 参数  `(对象/数组)` 待更新的主机属性。  `hostid` 属性必须为每台主机定义，其他属性都是可选的。只有给定的属性将被更新，其他所有属性将保持不变。  但是，请注意，更新主机技术名称也将根据主机的技术名称值更新主机的可见名称(如果没有给出或为空)。  除了[标准主机属性](object#host)以外，此方法接受如下参数:  |参数|[类](/manual/api/reference_commentary#data_types)|描述| |---------|---------------------------------------------------|-----------| |groups|对象/数组|更换主机所属的主机[组](/manual/api/reference/hostgroup/object#host_group)。<br><br>主机组必须已定义 `groupid` 属性。所有未在请求中列出的主机组将被解除链接。| |interfaces|对象/数组|主机[接口](/manual/api/reference/hostinterface/object)用于替换当前主机接口。 <br><br>所有未在请求中列出的接口将被删除。| |tags|对象/数组|主机[标签](/manual/api/reference/host/object#host_tag)替换当前主机标签。<br><br>所有未在请求中列出的标签将被删除。| |inventory|object|主机[清单](/manual/api/reference/host/object#host_inventory)属性。| |macros|对象/数组|[用户宏](/manual/api/reference/usermacro/object)替换当前用户宏。<br><br>所有未在请求中列出的宏将被删除。| |templates|对象/数组|[模板](/manual/api/reference/template/object)替换当前链接的模板。所有未在请求中列出的模板只会被解除链接。<br><br>模板必须定义了 `templateid` 属性。| |templates\_clear|对象/数组|[模板](/manual/api/reference/template/object)取消与主机的链接并清除。<br><br>模板必须定义了 `templateid` 属性。|  ::: notetip 与Zabbix前端不同，当 `name` (可见主机名)与 `host` (技术主机名)相同时，通过API更新 `host` 不会自动更新 `name` 。这两个属性都需要显式更新。 :::