Documentation
Table of Contents
10 What's new in Zabbix 7.2.5
Asynchronous DNS resolution
The agent poller and SNMP poller can now be configured to use the c-ares library (version 1.16.0 or newer) instead of the libevent DNS resolver. This allows for potentially faster and more flexible DNS resolution.
To enable c-ares, Zabbix must be configured with the --with-ares option.
Note that starting from c-ares 1.31.0, DNS caching is enabled by default.
Webhook integrations updated
The following out-of-the-box webhooks now support all event types and have been improved for code efficiency, maintainability, and functionality, with changes reflected in the documentation:
- Discord - script updated to use Discord API v10; hardcoded custom message format for trigger-based events removed.
- GitHub - GitHub API version parameter introduced to use a static version instead of the latest; in cases of escalation, existing issues are now updated instead of new ones being created; issue labels and adjustable prefixes in webhook parameters added.
- GLPi - message templates updated.
- Jira - trigger and service actions now support mapping of Zabbix event severities to Jira ticket priorities (via parameters
severity_information,severity_high, etc.); support for custom Jira priorities added to all autoregistration, discovery, and internal actions (via parametersjira_priority_discovery,jira_priority_autoregistration,jira_priority_internal); Jira custom fields for ticket creation added to all actions (previously only trigger); problem event messages are now sent to the Jira ticket description, and default OK event messages are now added as comments. - Jira Service Management (previously Jira Service Desk) - trigger and service actions now support mapping of Zabbix event severities to Jira ticket priorities; support for custom Jira priorities added to all autoregistration, discovery, and internal actions; Jira custom fields for ticket creation added to all actions (previously only trigger); support added for date and time, radio button, checkbox, single and multiple choice custom fields; URL custom field behavior adjusted; support for ticket labels added and issue name format updated to match the Jira media type; both private (default) and public comment options now available for escalations; in cases where event severity is updated between escalations, task priority no longer reverts to the original.
- MS Teams - message templates updated.
- OTRS CE - support added for closing incidents of resolved problems.
- PagerDuty - support added for closing incidents of resolved problems; API token moved to user media settings via
{ALERT.SENDTO}. - Slack - deprecated parameter
slack_as_userremoved; templates implemented for messages sent to Slack. - Telegram - support for reply messages added.
- Zammad - previously hardcoded user group “Users” moved to a webhook parameter; event tags no longer created by default.
SMART plugin for Zabbix agent 2 updated
The smart.disk.get item key in the SMART Zabbix agent 2 plugin now returns both raw and normalized values for SMART attributes.
Templates
For changes to existing templates and information on new templates, see Template changes.
Improved layout for “Custom on fail” option in item preprocessing
The item value preprocessing tab's "Custom on fail" options are now displayed correctly in all supported language localizations. Previously, misalignment in some translations led to configuration ambiguity when setting custom error‐handling actions for preprocessing steps. With this fix the control is rendered consistently, and after selecting the "Custom on fail" checkbox the available options are now presented as a dropdown list instead of radio buttons — providing a clearer and more compact interface.