Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleShow answer

Our extension has no impact on Dynatrace HU or DEM consumption. It has an impact on Davis Data Units consumption. Creating and refreshing the topology consumes DDUs. Each problem event synchronized from Zabbix to Dynatrace consumes DDU. The extension may ingest the metric - "Number of open problems" on every Zabbix device into Dynatrace. But you may decide, whether you want to ingest problem metric data into Dynatrace, or not.

A rough estimation of the amount of DDUs consumed by metric ingest per year can be obtained through the following formula:

(525.6 * number of problems / Dynatrace problem resend time [min]) +
(525.6 * number of Zabbix hosts * number of links to Zabbix host groups per host / Refresh Zabbix Host entities in Dynatrace [min]) +
(525.6 * number of synchronized Zabbix problems)

*An option from the extension’s extension configuration is marked in bold

Are there any configuration changes needed in Zabbix?

...

Expand
titleShow answer

Of course! This monitoring consolidation concept is proven and will work with any monitoring tool.

Do you use Nagios? Please check the Dynatrace Nagios Integration.

If you use a different monitoring tool, let us know and we will be happy to look into it and discuss your options!

Who develops/maintains this integration?

Expand
titleShow answer

This integration is developed and maintained by Alanata, Master Dynatrace Partner for Slovakia and Czech republic.

We have a team with over 25 years of experience in ICT management and monitoring, and currently, we have 5 certified Dynatrace professionals and 7 certified Dynatrace associates.

If you have any Dynatrace or monitoring related questions, give it a shot and contact us, our team is ready to help you.

...