Estimating Metric Consumption for Dynatrace SaaS (Extension - DPS License)

[AskMe-Solutions]

Hi everyone,

I'm currently planning to use Dynatrace SaaS with Extension (DPS License) to monitor various network and infrastructure devices in our organization. The device list includes:

• F5 R5600: 4 units

• Cisco Catalyst 9200 Switches: 172 units

• Fortinet 400E Firewalls: 2 units

• Fortinet 200F Firewalls: 2 units

• VMWare Hosts: 71 hosts

We plan to monitor them using SNMP, APIs, or vCenter integration, depending on device compatibility. We’ll be using Extension 2.0 or OneAgent remote plugins to collect metrics.

My questions are:

1. Roughly how much DPS (Davis Data Units) for metric ingest and processing should we expect to consume per year for this setup?

2. Can we customize which metrics to ingest (e.g., only CPU, Memory, Interface Traffic, Device Health, etc.) to reduce consumption?

3. Are there any formulas, tools, or best practices for estimating metric ingestion when using Dynatrace Extensions?

4. Has anyone here implemented a similar monitoring setup? If so, could you share your real-world metric consumption experience?

Any advice, recommendations, or reference architectures would be greatly appreciated. Thank you!

[Maheedhar_T · Accepted solution]

Hi @AskMe-Solutions ,
DDU consumption you can analyse from this: DDUs for metrics — Dynatrace Docs
Also licensing for hosts depends on the Rate card you get from Dynatrace. It differs if you have any discounts applied. Standard one you can find here: Host monitoring — Dynatrace Docs

and for this:
Can we customize which metrics to ingest (e.g., only CPU, Memory, Interface Traffic, Device Health, etc.) to reduce consumption?

If the metric is from hosts say host related CPU and health, they can't be controlled but anyway are included in the host licensing.
From extensions 2.0 you can control which metrics you want to ingest so yes that can help in reducing the costs.

Regards,
@Maheedhar_T