2.1.0
Fixed bug with a custom CA certificate
2.0.0
Initial release
Extension Framework 2.0
ActiveGate Extensions module must be >= 1.285
1.31
changes in Zabbix User API from Zabbix version 5.4
1.30
Migration to v2 API only (new token required during upgrade from the previous version)
Problem title prefix configuration
1.29
Starting with Dynatrace ActiveGate version 1.231, the Extension Framework upgraded from Python 3.6 to Python 3.8
1.28
Works with Dynatrace ActiveGate version lower than 1.231
Fix for SSL certificate check when connecting to Zabbix
Mapping of Zabbix problems to Dynatrace entities is performed by problem tags, not trigger/host tags.
1.27
Additional Zabbix severities
Added all Zabbix severities for mapping problemsEvent suppression
Added suppression level in severity mapping to allow ignoring Zabbix problems by severity. For ignoring specific severities, for example, Information, set the severity mapping to Suppress in the Extension UI.Rest API is the default option for sending events to Dynatrace.
This allows disabling of problem merging and sending events to specific Dynatrace entities.Allow or Disable Davis problems merge.
Set tofalse
to force creating a new problem in Dynatrace for each Zabbix problem.Option to send events to any Dynatrace entity
By adding a tag to Zabbix Host or Trigger extension allows sending the Zabbix problem, the extension can send problem opening events to any Dynatrace entity specified by the tag value. This is useful for example if Zabbix monitors entities such as databases or services which are also monitored by Dynatrace. If this tag is present on the trigger or host, problems will be sent to Dynatrace entities by the tag value. Zabbix tag value may contain a single Dynatrace entity ID or Dynatrace entitySelector. Zabbix tag name can be specified in the extension configuration.
1.20
New license model implemented
Fixed handling of unsupported item keys