. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104 8 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . decreased from 365 days to 1 day. • Maximum error message length has been increased from 128 to 2048 symbols for trigger and alert errors. This should reduce the possibility of error message being trimmed ’zabbix’ for Zabbix server and ’zabbix_proxy’ for Zabbix proxy. PHP_TZ Web-interface Timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is ’Europe/Riga’

5.10.1 Unified date and time format Date and time format has been unified across Zabbix frontend according to the ISO 8601 standard of YYYY-MM-DD hh:mm:ss. The new format is implemented everywhere except configuration file are now validated to be proper Zabbix item keys. These keys now also support colon symbols in their parameters. A new configuration parameter (User) has been introduced for daemons which messages in Zabbix 2.4.0. Additionally, maximum message length has been increased from 128 to 2048 symbols. This should reduce the possibility of error message being trimmed. ** Database related changes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330 8 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . trends Real-time export of trigger events, item values and trends in a newline- delimited JSON format is possible by specifying the new ExportDir parameter in server configuration. Another new parameter Both general map description and individual element description is available, in the following format: • for map description:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233 8 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expected format change in low-level discovery In order to support preprocessing of low-level discovery result and custom paths to low-level discovery (LLD) macro values in a JSON document, the format of JSON Prometheus integration offers the ability to monitor any object that exposes metrics in Prometheus line format, including Kubernetes, Docker, GitLab, Ceph, Collectd, etcd, InfluxDB, InfluxDB Telegraf and others

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349 9 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . preprocessing options CSV to JSON conversion It is now possible to convert CSV file data into JSON format. 12 See also: CSV to JSON preprocessing Custom error handling Custom error handling is now also webhooks, media types can now be exported and imported. The export files support the new human-readable format (see below) implemented for host/template export. Human-readable export files of hosts/templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688 8 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . notes Export to YAML Zabbix configuration elements now can also be exported and imported in the YAML format, which is easy to read and edit. Custom handling for item errors Custom handling for item errors persistent storage on agent 2 for active items. Plugins Plugins may have their own parameters, in the format Plugins..=. A common plugin parameter is Capacity, setting the limit

Differential • I → Incremental In Monitoring → Latest data, displayed values are shortened to 20 symbols. If value mapping is used, this shortening is not applied to the mapped value, but only to the raw information more informative, now a name and surname is also displayed, in the ’alias (name surname)’ format. The name and surname are taken from the respective (now optional) user configuration fields. Name • Improved formatting of a trapper response to values sent by Zabbix sender. The new info field format is ”processed: ; failed: ; total: ; seconds spent: ”. • Maximum length of an alert

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518 8 Unit symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . As such, parameters in a format Plugins..Uri, Plugins..User, Plugins..Password are no longer supported. Named session parameters in a format Plugins..Sessions parameter or to the plugin configu- ration parameter Plugins.Oracle.Sessions..User in the format user as sysdba (login option is case-insensitive; must not contain a trailing space). 38 What’s

QUEUE_DETAIL_ITEM_COUNT definition parameter now may be edited to retrieve more than default 500 values. Format of the counter displayed in Detail view of Administration → Queue has been enhanced by exposing the ’zabbix’ for Zabbix server and ’zabbix_proxy’ for Zabbix proxy. PHP_TZ Web-interface Timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is ’Europe/Riga’ discarded. All cases of discarded LLD data are listed in the Zabbix server log file in the following format: cannot process discovery rule "host:key": another value is being processed SMTP authentication

previously supported. In the new version flexible intervals have been supplemented with a new Scheduling format where item checking can be defined for specific time points. In the example above item checking support discovery of multiple OIDs. The discovery SNMP OID now is specified by using the following format: discovery[{#MACRO1}, oid1, {#MACRO2}, oid2, ...] The discovered OIDs are grouped by their indexes information set to integer (”Numeric (unsigned)”), and thus be graphed. 5.12.3 Miscellaneous • ISO date format of yyyy-mm-dd hh:mm:ss used Several improvements focus on better readability of labels in graphs