monitoring plugin A Docker plugin for Zabbix agent 2 is now available as part of the out-of-the-box monitoring of Docker containers (see list of supported keys). Memcached monitoring plugin A Memcached Memcached plugin for Zabbix agent 2 is now available as part of the out-of-the-box monitoring of Memcached instances (see description). MySQL monitoring plugin A MySQL plugin for Zabbix agent 2 is now available MySQL instances (see description). Agent 2 plugins update Passing a URI, username and password via plugin configuration parameters is now supported only for named sessions. As such, parameters in a format

import them manually into Zabbix. 9 What’s new in Zabbix 5.4.4 Plugins • A new Zabbix agent 2 plugin WebCertificate is now available allowing to monitor validity and expiration dates of TLS/SSL website agent 2 items smart.disk.discovery and smart.attribute.discovery items, supported for S.M.A.R.T. plugin, have been updated and now return {#DISKTYPE} macro value in the lower case. • Native support for this option only for a specific plugin by using Plugins..ForceActiveChecksOnStart (for exam- ple, Plugins.Uptime.ForceActiveChecksOnStart=1). If set, a plugin-level parameter will override the

agent and agent 2 item. See also: • Zabbix agent item keys • Zabbix agent 2 plugins • Modbus plugin documentation MQTT support Zabbix now supports receiving values of MQTT topics using the new mqtt mqtt.get[] agent 2 item. See also: • Zabbix agent 2 item keys • Zabbix agent 2 plugins • MQTT plugin documentation Digest authentication for HTTP agent Digest authentication is now supported for HTTP and Redis plugins, a Uri can now only be specified as a named session parameter. • For PostgreSQL plugin a Uri and Database name can now only be specified as a named session parameter. • For Uri parameters

RabbitMQ management plugin with Zabbix agent locally; • Template App RabbitMQ cluster by HTTP and Template App RabbitMQ node by HTTP - collect metrics by polling RabbitMQ management plugin with HTTP agent Agent 2 configuration parameters The following general configuration parameters have been moved to plugin configuration parameters: • EnableRemoteCommands → Plugins.SystemRun.EnableRemoteCommands • LogRemoteCommands MaxLinesPerSecond The internal plugin Configurator API also has been changed: another parameter has been added to the Configure() function, the format of passed plugin parameters to the Configure() function

Zabbix server or proxy. Zabbix agent 2 plugins Separate configuration files Each Zabbix agent 2 plugin now has a separate configuration file. By default, these files are located in the ./zabbix_agent2 and can be relative to the zab- bix_agent2.conf or zabbix_agent2.win.conf file location. External plugin loader Previously, plugins could only be compiled into Zabbix agent 2, which required recompiling every time you need to change the set of available plugins. Now, with the addition of the external plugin loader, plugins don’t have to be integrated into the agent 2 directly and can be added as separate

tidy or go get commands. PostgreSQL plugin loadable The PostgreSQL plugin is now loadable in Zabbix agent 2 (previously built-in). See also: PostgreSQL loadable plugin repository 14 Extended VMware monitoring performing a configuration cache reload. 15 12 What’s new in Zabbix 6.2.7 Breaking changes Loadable plugin versioning Loadable plugins for Zabbix agent 2 now use the same versioning system as Zabbix itself plugins are supported for any minor version of Zabbix 6.2. Note that source code repository for each plugin now contains a dedicated release/6.2 branch (previously, there was only master branch). MariaDB

(EnablePersistentBuffer=1). PidFile no /tmp/zabbix_agent2.pid Name of PID file. Plugins no A plugin can have one or more plugin-specific configuration parameters in the format: Plugins..= seconds) before unused plugin connections are closed. Supported for the following plugins: Ceph, Memcached, MongoDB, MySQL, Oracle, Redis, PostgreSQL. - name of the plugin. Example: Plugins Supported for: Memcached, MongoDB, MySQL, Oracle, PostgreSQL, Redis. - name of the plugin. - name of a session for using in item keys. Plugins..Sessions.

. . . . . . . . . . 1864 Create a plugin (tutorial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864 Plugin interfaces . . . . . . . . . . . . maximum supported version for TimescaleDB is now 2.10. 17 Connection options for Oracle plugin The Oracle plugin, supported for Zabbix agent 2, now allows to specify as sysdba, as sysoper, or as sysasm sysasm login option. The option can be appended either to the user item key parameter or to the plugin configu- ration parameter Plugins.Oracle.Sessions..User in the format user as sysdba (login

. . . . . . . . . . 1927 Create a plugin (tutorial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927 Plugin interfaces . . . . . . . . . . . . agent 2 has been increased from 100 to 1000. Empty values allowed Empty values are now allowed in plugin-related configuration parameters on Zabbix agent 2. Support for the old numeric type dropped The connections 30 • 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

seconds spent: 0.003534" } 3 Zabbix sender 协议 有关详细信息，请参阅Trapper items页面。 409 4 Zabbix agent 2 plugin protocol Zabbix agent 2 protocol is based on code, size and data model. Code Type Size Comments direction (i.e. from agent to plugin or from plugin to agent). For responses - ID of the corresponding request. type uint32 The request type. Log request A request sent by a plugin to write a log message message into the agent log file. direction plugin → agent response no Parameters specific to log requests: Name Type Comments severity uint32 The message severity (log level). message string The message