This page describes how the Metrics powered by Grail - Ingest & Process DPS capability is consumed and billed. For an overview of the capability, including its main features, see Metrics powered by Grail - Ingest & Process.
Ingested data is the number of metric data points sent to Dynatrace. A metric data point is a single measurement of a metric.
The number of included Custom Metric data points is dependent on the total monitored GiB-hours of your deployment and the OneAgent mode (Full-Stack or Infrastructure Monitoring, see built-in metrics for details. Host Monitoring also includes a number of metric data points or Custom Metrics that are deducted from your environment's total data-point consumption.
Some built-in metrics are not billed. This includes, for example, host monitoring metrics included in Full-Stack Monitoring and Infrastructure Monitoring.
Metrics are either billable or non-billable. Billable metrics consume your DPS subscription. Non-billable metrics do not consume your DPS subscription.
All metrics are billable unless otherwise noted.
Some monitoring modes include a certain amount of metric data points that can be used without consuming your DPS subscription. This is described further in the respective sections, see Host Monitoring modes overview (DPS).
The following metric keys are non-billable:
dt.* 1dt.cloud.aws.az.runningdt.cloud.azure.region.vms.initializingdt.cloud.azure.region.vms.runningdt.cloud.azure.region.vms.stoppeddt.cloud.azure.vm_scale_set.vms.initializingdt.cloud.azure.vm_scale_set.vms.runningdt.cloud.azure.vm_scale_set.vms.stoppedlegacy.containers.*legacy.dotnet.perform.*legacy.tomcat.*Metrics stored in the bucket dt_system_metrics are non-billable.
The following dt.* metric keys are billable unless otherwise noted in the list above: dt.cloud.aws.*, dt.cloud.azure.*, dt.osservice.*, dt.service.*.
The total platform usage includes every metric data point ingested by Grail.
If many data points within a given metric interval are stored as one data point in Grail, only one data point is counted for total product usage.
A single metric that is written once per minute will consume 525,600 metric data points annually:
1 metric data point × 60 min × 24 h × 365 days = 525,600 metric data points/year
Note that a single metric can have multiple dimensions. For example, if you have the same metric for 2 instances of your cloud service, you will consume 2 metric data points:
2 instances × 1 metric data point × 60 min × 24 h × 365 days = 1,051,200 metric data points/year
Metric data points are not billed based on an increase in dimensions, but rather by the increased number of metric data points. If dimensions are added, but the number of metric data points remains the same, then billable metric data points usage does not change:
Therefore, in this case, the same number of metric data points is consumed as shown in the calculation above.
The number of included Custom Metric data points is dependent on the total monitored GiB-hours of your deployment and the OneAgent mode (Full-Stack or Infrastructure Monitoring).
Not all metrics generate data points that affect billable monitoring consumption. Included (non-billable) metric data points are subtracted from the total product usage for every environment before your monitoring consumption is calculated.
For example, say that you produce 55 million billable metric data points per day which you ingest into Metrics powered by Grail. The consumption for one month (30 days) of Ingest & Process is calculated as follows:
55 million data points55 million * 30 days = 1,650 million1,650 million * (Ingest & Process price as per your rate card) = Cost