image drawing approach. For more information see dashboard widgets. The graph widget supported before can still be used and is now renamed to Graph (classic). Time selector redesign The time period IPMI items it is now also possible to specify a search for the full name, by using a name: prefix before the value. Triggers Time triggers processed by history syncers The processing of time-based trigger sec] zabbix_server: timer #1 [updated 0 hosts, suppressed 0 events in 0.000472 sec, idle 59 sec] Before: zabbix_server: history syncer #4 [synced 35 items in 0.166198 sec, idle 5 sec] zabbix_server: timer

encryption while others through encryption): Authentication by PSK is verified by Zabbix server before adding a host. If successful, the host is added and Connections from/to host are set to ’PSK’ only that are more complex and contain several host items are listed within separate tags, as before. Frontend Default dashboard The default dashboard shipped with new installations (Global view) inherited from these unlinked templates (items, triggers, etc). By default this option is unchecked and before it is possible to mark this checkbox a warning message is displayed that all inherited entities

longer go through the preprocessing manager, the affected proxies will require more resources than before. 10 Warning: The change affects the upgrade process to Zabbix 4.2. Please see the upgrade notes failed: This was not always enough as the real problem could lie in the step before the one that failed. Therefore, now the error message is extended with a log of the executed steps in the discovery data flow, let’s compare it with the previous versions: Version LLD data flow Before Zabbix 4.2 Discovery rule → Discovery rule filter In Zabbix 4.2 Discovery rule → Preprocessing →

notifications in the message subject 7 Item value preprocessing When it comes to preprocessing item values before storing them in the database, Zabbix already had several options such as calculating delta value is used (text, macro, scenario-level variable or any combination of those). Encoding is performed before executing the step (data is saved unencoded in the database). 11.2 Flexible URL-encoding for variables chosen post variable settings in web scenario steps. For example: Version Variable syntax Result Before 3.4 {user} Variable value is passed as is. 12 Version Variable syntax Result In 3.4 {user} {user}

authentication options. It is also possible now to specify the server port other than the hardcoded 25 before. 9 See e-mail configuration for more details. 5.5 Item checking at specific times Item checking of SQL statements. As a result, the process of creating triggers takes only half of the time as before. 5.10 Multiple OID support in SNMP discovery SNMP discovery has been improved to support discovery items on the corresponding interface - they were removed or disabled (Zabbix agent active checks, as before, do not influence host availability in any way), • host is set to be monitored by proxy, a different

the item (template item, item prototype, low-level discovery rule) from the user interface even before saving and, if configured correctly, get a real value in return. Item testing is not supported for the new second parameter, e.g.: nodata(5m,strict). In this case the function will work the same as before and fire as soon as the evaluation period (five minutes, in this case) without data is past. It there is also a new option to search for graph name pattern: Top-of-the-page selection dropdowns before Zabbix 5.0. 12 Multi-select fields in the filter in the new version. • filtering by host has been

UserParameterDir is present, the agent will change its working directory to the one specified by this parameter before executing a UserParameter command. Thereby UserParameter commands can have a relative ./ prefix templates, one host tag, one host-level macro, enabled inventory and two-way encryption enabled now and before: |<| |<| |-| |<| Informative tabs allow to debug problems easier, for example, when an item has following way: • The selection fields now have modern design • Time relative to UTC is prepended before the time zone name • ’System default’ and ’System’ options now also display full details (time relative

memory usage have been improved by freeing uncompressed data as fast as possible and compressing before connection. See also protocol header information. Items • Zabbix agent 2 items proc.num, proc statistics. Hostname The system.hostname[] item can now return only shorthost (part of the hostname before the first dot) and, optionally, transform the hostname into lowercase. See Zabbix agent items for the same records twice or skipping records. Read the persistent files notes for more information before using it. VMware hypervisor discovery The vmware.hv.discovery item now also returns a {#HV.NETNAME}

events are generated. You can use the problem expression as basis (then it works the same way as before), the recovery expression as basis, or even select ’None’ in which case the trigger will always remain to them. Thus it is possible to enable/disable/delete them. Items created by low-level discovery before 3.2.0. Items created by low-level discovery in 3.2.0. 5.12 Web scenario export/import When exporting 15 • dayofmonth() • dayofweek() • now() • time() Host and item, however, must be enabled as before. 5.18 Unsupported items and unknown values in triggers/calculated items Previously any unsupported

new expression syntax is used. See the comparison below for details of the change: In Zabbix 6.0 Before Zabbix 6.0 {?avg(/host/key,1h)} Example of an expression macro in the new version. {host:key.avg(1h)} Templates section. If a template with the same name already exists, check the Delete missing option before importing to achieve a clean import. This way the items that have been excluded from the updated deleted. Supported DB versions check Zabbix server and proxy will now check the database version before launch and will not start if the version is out of the supported range. For more details, see databases