. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 11 Zabbix will automatically extract a macro and value if an array field uses the {#MACRO} syntax as a key. Any new native discovery checks will use the new syntax without the ”data” elements. When processing of experimental support of TimescaleDB, a PostgreSQL-based database solution of automatically partitioning data into time-based chunks to support faster performance at scale. A migration script is available

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 2 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 3 JSON Zabbix will cache the interface as old protocol and retry the check by sending only the plaintext item key. Zabbix get can now be run with a new option -P --protocol where ”value” is either: • auto plaintext protocol (default); • json - connect using JSON protocol key; • plaintext - connect using plaintext protocol where just the item key is sent. Enhanced item timeout configuration possibilities Timeout

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 11 easier to use • Item sets for aggregation can be specified using complex filters referencing the item key, host group and tags • The new syntax supports other expressions as parameters • Item reference is server/tick,3m)=1 {Zabbix server:tick.nodata(3m)}=1 A simple trigger expression min(min(/host/key,1h),min(/host2/key2,1h)*10,#20) Not available/supported Using other expressions as function parameters (referencing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 11 devices Low-level discovery of block devices and their type is supported using a new built-in discovery key: vfs.dev.discovery The discovery will return a JSON with the values of two macros - {#DEVNAME} and units (services, by default) is supported using a new built-in discovery key: systemd.unit.discovery Attention: This item key is only supported in Zabbix agent 2. The discovery will return a JSON with

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 11 privacy passphrases, passwords for media types; SSL key password and HTTP proxy fields used in web scenarios and HTTP items; usernames, passwords and key passphrases in remote commands. This setting shall partitions Updated macros • {ITEM.KEY.ORIG} macro is now supported in HTTP agent type and Script type items, item prototypes, and discovery rules; • {ITEM.ID} and {ITEM.KEY} macros are now supported in Script

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554 11 Specifically, the metrics of histogram type can be presented in Zabbix as multiple items with the same key names, but different parameters. However, even though such items are logically related and represent if selected item key returns data only of the specific type (for example, log[] item requires Type of information: Log). Type of information parameter is now located under the Key parameter on the primary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 JSON data[key,] - return data for the specified value name in the Windows Registry key • registry.get[key,,] - list of Windows Registry values or keys located at given key; returns type>',key,string) This is useful for cases when hash-based message authentication code (HMAC) is required for signing requests. MD5 and SHA256 hash types are supported, e. g.: • hmac('md5',key,string)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 2 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 3 JSON item ssh.run[] has been updated and now allows to pass additional SSH options as part of the item key. See SSH checks for details. Templates Template versioning To improve management and upgrade of sysdba, as sysoper, or as 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 history_bin table has been converted to hypertable on TimescaleDB to benefit from automatic partitioning on time (1 day by default) and better performance. To successfully upgrade existing installations: agent (默认值: true)。 -p --print 输出已知的监控项并退出。注意：要返回用户自定义参数 的结果， 您必须指定配置文件（如果它不在默认路径下）。 -t --test key> 测试指定的监控项并退出。注意：要返回用户自定义参数 的结果， 您必须指定配置文件（如果它不在默认路径下）。 -T --test-config 验证配置文件的合法性并退出。 -h --help Zabbix agent (默认: true). -p --print 打印已知监控项并退出。 注意: 也返回用户参数结果, 必须指定配置文件 (如果它不在默认位置)。 -t --test key> 测试指定监控项并退出。 注意: 也返回用户参数 结果, 必须指定配置文件 (如果它不在默认位置)。 -T --test-config 验证配置文件并退出。 -h --help 打印帮助信息并退出。

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 1 Virtual machine discovery key fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 11 information. This item can be used for the discovery of IPMI sensors. Item key limit raised The maximum allowed length of an item key has been raised from 256 to 2048 characters. Extended range of numeric option specifies that each line of the input file contains the following, whitespace-delimited: <key> , e.g.: Zabbix server" trap001 1429533600 748744024 43 Zabbix server" trap001