Table of Contents
11 What's new in Zabbix 7.0.6
TimescaleDB 2.17 support
The maximum supported version for TimescaleDB is now 2.17.X.
PostgreSQL 17 support
PostgreSQL 17 is now supported.
Asynchronous poller state calculation
Asynchronous pollers are now considered busy if they have reached the limit set by the MaxConcurrentChecksPerPoller server/proxy configuration parameter. Utilization of poller processes can be monitored with the zabbix[process,,,] internal item.
StartPreprocessors default increased
The default value of the StartPreprocessors server/proxy configuration parameter has been increased from 3 to 16. To make the best use of available resources, the number of pre-started instances of preprocessing worker threads should be set to at least match the number of available CPU cores. If preprocessing tasks are not CPU-bound and involve frequent network requests, configuring additional workers is recommended.
MSSQL instance names supported in agent 2 plugin
It is now possible to specify MSSQL instance names as part of the connection string in MSSQL agent 2 plugin items, for example:
Note that in this case no port must be specified. If port is specified, then the instance name will be ignored and the specified port will be used for connection.
Performance counter query updated in MSSQL agent 2 plugin
The performance counter query of the MSSQL agent 2 plugin has been updated, resolving issues in the data retrieval of unnamed (default) MSSQL instances.
Maximum number of rows in widgets
The maximum number of rows that can be displayed has been increased from 100 to 1000 in several dashboard widgets:
- Action log
- Item history
- Problems
- Top hosts
- Top triggers
1000 is now the value of ZBX_MAX_WIDGET_LINES parameter in frontend definitions.
Templates
For new templates and changes to existing templates, see Template changes.