By adding a tag to a Zabbix problem you can send problem opening events to any Dynatrace entity. This is useful for example if Zabbix monitors entities such as databases or services which are also monitored by Dynatrace. By utilizing this extension functionality, you will have the proper mapping of events between Zabbix host entities and your existing Dynatrace entities.

Enabling the mapping

1. Configure the name of the Zabbix tag in the extension configuration in the option Zabbix tag for Dynatrace entities. This tag will be evaluated by the extension and its value will be used for mapping when Zabbix problems are synchronized. For example, use the name DT_Entity

2. Save the extension configuration in Dynatrace UI

3. Add this tag in Zabbix configuration to the desired templates or triggers. The value of the tag must be a valid entity selector.

   1. Dynatrace entitySelector, such as type("SERVICE"),tag("MyTag")The entity selector may evaluate to any entity type or list of entities.

Mapping process

When a problem is opened in Zabbix, the extension:

1. Iterates through the tags of the Zabbix problem.

2. For each problem tag with the key specified in the extension configuration option, the extension considers the value as a Dynatrace entity selector

3. Extension sends a Dynatrace event with an entity selector from the tag.

Configuration example

This example illustrates how to configure Zabbix to send events to Dynatrace entities using Zabbix templates. In this case database services.

Add the configured Zabbix tag to the desired template as shown in the figure. You can use any existing templates.

In this case, we are using the Dynatrace entitySelector to send any future Zabbix problems generated from triggers in this template to the corresponding database service in Dynatrace using Zabbix macro {HOST.NAME}.

Open

 

Ensure the template is linked to your Zabbix hosts. In this case, it’s the Zabbix host named ttrss representing the database.

Open