Azure Monitor metrics

  • Latest Dynatrace
  • Explanation
  • Published Oct 31, 2025
  • Preview

The Dynatrace Azure Cloud Platform Monitoring is ultimately designed to allow the ingestion of any Azure Monitor metric from any Azure service (a service which sends metrics to a Azure Monitor).

Our metric ingest strategy allows you to quickly onboard with our recommended set of services and metrics. At the same time customization using advanced settings is possible while onboarding or post onboarding.

Our metric strategy is a gradual product improvement which is planned to be completed at the General Availability.

During the Preview period we plan to gradually add new features.

Metric ingest methods

The Dynatrace Azure Cloud Platform Monitoring was designed to support the following Azure Monitor metrics ingest method:

  • Poll-based : The Dynatrace SaaS metric poller calls the Azure Monitor getBatch and ListMetricDefinitions APIs to validate, poll, and persist metrics.

    The metric poller is scheduled every 5 minutes, evaluating a 5-minute window with 5 minute delay. Meaning that a metric poller job which started at 9:00 AM will evaluate the data-points for 8:50 AM-8:55 AM (5 minute delay + a 5-minute window). The evaluation delay is necessary as Azure Monitor is an eventually consistent metrics API, Azure Monitor takes few minutes (late aggregations) to make the latest data-points available.

Metrics observability options

Our metric observability options consists of the following key elements.

Recommended services represent a logical group of Dynatrace opinionated native Azure Services, and their corresponding recommended metrics.

When onboarding an Azure subscription following the Recommend path, the recommended services are enabled by default.

See the current list of recommended Azure services supported in Preview
  • Azure API Management Service
  • Azure Cache for Redis
  • Azure Managed Redis
  • Azure IoT Hub
  • Azure Cosmos DB Account (GlobalDocumentDB)
  • Azure Cosmos DB Account (MongoDB)
  • Azure Application Gateway
  • Azure Standard Load Balancer
  • Azure Gateway Load Balancer
  • Azure SQL Database (vCore)
  • Azure SQL Database (DTU)
  • Azure SQL Database—Hyperscale
  • Azure Storage Account
  • Azure Storage Blob Services
  • Azure Storage File Services
  • Azure Storage Queue Services
  • Azure Storage Table Services
  • Azure Virtual Machines
  • Azure Virtual Machine Scalesets
  • Azure Event Hubs Namespace
  • Azure Service Bus Standard Namespace
  • Azure Service Bus Premium Namespace
  • Azure Web App
  • Azure Function App
  • Azure Logic Apps (Standard)
  • Azure Logic Apps (Consumption)
  • Azure Container
  • Microsoft Foundry
  • Azure OpenAI

The recommended services list is constantly evaluated based on customer feedback and Azure innovation; Dynatrace may change the list to reflect user feedback and/or to keep up with the Azure innovation. Any changes are designed not to introduce breaking changes for exiting Azure connections.

Metric collection sets

A metric collection set is a group of metrics assigned to a supported Azure service. Once assigned, all metrics in this collection set are scheduled for polling.

Only a single metric collection set can be assigned to a service at any given time (1:1).

Metric collection set types

  • Recommended: A customer-immutable list of opinionated Dynatrace recommended metrics (per cloud service). An optimal starting point.

  • Recommended+Custom: Cherry-pick specific metrics from the Recommended set as well as from a larger set of Dynatrace curated metrics.

  • Auto-discovery: All metrics for a specific Azure service are auto-discovered and marked for polling. This option has the potential to generate elevated Azure Monitor and Dynatrace costs.

To view the most updated list of metrics that the Recommended metric collection set ingests (per Azure service):

  1. Go to Dynatrace Hub Hub.
  2. In search, type preview, then select the Azure Cloud Monitoring (Preview) tile.
  3. Scroll down, and in the Feature Sets section, search metrics using this pattern: [Azure Resource Type]_essential, for example microsoft_apimanagement.service_essential.

All metrics across each metric collection set are designed to support our signals-in-context principle, where they are linked to their respective Dynatrace entity. This enables the following use cases:

  • Clouds Clouds metrics in-context view (view the metrics related to the Azure resource).
  • Enrichment of those metrics with cloud extended metadata as attributes (azure.subscription.id, azure.region, azure.tag, azure.tag.[TagKeyName]:value), allowing advanced filtering use cases.

Advanced metrics ingest use cases

Ingest any Azure Monitor metrics

In addition to the predefined metric collection sets, you can configure Dynatrace to collect any Azure Monitor native platform metric. This enables monitoring of:

  • Metrics not included in the standard collection sets
  • Metrics from Azure services not yet fully supported by Dynatrace

To use this feature, you must provide precise details about the Azure resource type and metric definition. Incorrect values will result in failed metric collection.

When configuring a custom metric, you specify the following:

FieldRequiredDescription
TypeYesThe Azure resource type (for example, Microsoft.Compute/virtualMachines). This must match the resource provider namespace and type exactly as defined in Azure.
KindsNoComma-separated list of resource kinds to filter (for example, Standard,Premium). Leave empty to include all kinds.
SKU nameNoFilter by specific SKU name if the resource type supports SKUs.
SuffixNoResource type suffix for specialized resource variants.
NameYesThe metric name as defined in Azure Monitor (for example, Percentage CPU). Must match the exact metric name from Azure Monitor.
DimensionsNoComma-separated list of dimensions to include in metric collection. Use dimensions to split metrics by specific attributes.
Time grainYesThe aggregation interval for the metric (for example, PT1M for 1 minute, PT5M for 5 minutes).
StatisticsYesThe aggregation type to apply (for example, Average, Sum, Minimum, Maximum, Count).

To find the correct metric names, resource types, and available dimensions, refer to the Azure Resource Graph and the Azure Monitor supported metrics documentation.

Limitations

  • During Preview, our Azure services and metrics list will increment in stages.
  • Azure Monitor Metric Streaming is not currently planned.
  • Telemetry signals enrichment with metadata such as Azure tags is only possible for signals which were successfully linked to an entity (Azure Resource).
  • The maximum number of user provided Azure tags for enrichment is 20.
  • The maximum number of tag-based filtering is up to 5 for include and 5 for exclude.
Related tags
Infrastructure Observability