See breaking changes for this version.
In some data collection scenarios, specific items can temporarily block the server/proxy history cache. This may delay writing history data to the database and slow down the system. To help manage the history cache, the following improvements have been introduced:
For long-term system stability, make sure that data collection is balanced with available resources (database performance, cache size, collection intervals, log item parameters, etc.). You can monitor Zabbix history cache using the zabbix[wcache] internal item. You can also consider increasing the size of the history cache for Zabbix server/proxy.
Host prototypes are now supported on discovered hosts, enabling Zabbix to automatically discover and monitor entities within other discovered entities (e.g., hypervisors, their virtual machines, and containers inside those virtual machines).
You can create host prototypes on discovered hosts by creating low-level discovery rules with host prototypes or by linking a template with host prototypes. Alternatively, you can link a template to the host prototype used for discovery, which will cause discovered hosts to inherit the host prototypes from the template.
If your current configuration includes host prototypes that use templates containing other host prototypes, please see Upgrade notes.
A new icmppingretry[<target>,<retries>,<backoff>,<size>,<timeout>,<options>]
simple check has been added for host accessibility monitoring by ICMP ping with the ability to modify retries.
New history functions have been added for timestamp tracking:
firstclock
- timestamp of the oldest value within the defined evaluation period;lastclock
- timestamp of the Nth most recent value within the defined evaluation period;logtimestamp
- log message timestamp of the Nth most recent log item value.New macros have been added for item-value time tracking:
Macro | Description |
---|---|
{ITEM.LASTVALUE.AGE} | The time that elapsed between the latest item value collection and macro evaluation. |
{ITEM.LASTVALUE.DATE} | The date when the latest item value was collected. |
{ITEM.LASTVALUE.TIME} | The time when the latest item value was collected. |
{ITEM.LASTVALUE.TIMESTAMP} | The timestamp when the latest item value was collected. |
{ITEM.VALUE.AGE} | The time that elapsed between the item value collection and macro evaluation. |
{ITEM.VALUE.DATE} | The date when the item value was collected. |
{ITEM.VALUE.TIME} | The time when the item value was collected. |
{ITEM.VALUE.TIMESTAMP} | The timestamp when the item value was collected. |
For better visibility of user media, user notifications now have their own menu section under User settings.
The new Notifications section contains two tabs - Media and Frontend notifications, which previously were part of the user profile section.
All users are now allowed to manage their own media by default.
However, user permissions to change media details for themselves can be granted/revoked based on their user role (see Create and edit own media option).
Additionally, Super admin user permissions to change media details for others can also be granted/revoked based on their user role (see Create and edit user media option).
It is now possible to configure map element/link labels to be displayed only when they are hovered on or selected. This setting helps to reduce visual clutter in maps with many elements close to each other.
Auto-hiding of labels can be configured for all map elements/links globally or for an individual map element/link.
It is now possible to proportionally scale background images to fit the map size.
It is now possible to bring one element in front of the other (or vice versa) by clicking on the element with the right mouse button and selecting Bring forward/Bring to front or Send backward/Send to back options.
Additionally, if map elements contain both a link between them and a highlight, the link will now appear below the highlight.
In the previous versions it was possible to adjust link style and color if some trigger went into a problem state. Now similar functionality is available based on item values.
It is possible to have link style and color adjusted if an item value:
The history syncer process title now displays detailed statistics about history syncer transactions for Zabbix server and proxy.
It is now possible to configure that vault secret macro values are retrieved by Zabbix server and Zabbix proxy independently if Resolve secret vault macros by is set to "Zabbix server and proxy".
The Plugins.*.CustomQueriesPath
parameter in Zabbix agent 2 plugin configuration files for MySQL, Oracle, and PostgreSQL, as well as Plugins.MSSQL.CustomQueriesDir
for MSSQL, now has a default value. This functionality is disabled by default and can be enabled using the newly introduced Plugins.*.CustomQueriesEnabled
parameter.
It is now easier to copy values in preprocessing test results using the added Copy to clipboard button.
Note that a similar button now replaces the Copy link for created API tokens.