Request dimensional time series explicitly instead of accepting a rolled-up metric

Source facts

The Azure Monitor metrics REST API returns a rolled-up aggregate when dimension filters are omitted. A wildcard filter on a dimension requests separate series for its values; Top can limit how many series are returned and OrderBy controls their ordering. Setting resultType to metadata returns dimension values rather than metric measurements. Microsoft specifies API version 2019-07-01 or later for multidimensional values. Microsoft Learn.

Applicability

Apply this contract review to a single-resource dimensional query used by an integration or report. A successful response containing a time series does not by itself establish that the consumer received the intended per-dimension population.

DSE recommendation

Specify whether the consumer needs a rolled-up result or separate dimension series before constructing the request. Record the chosen dimension, filters and any Top limit with the report definition. Keep dimension discovery separate from measurement retrieval, and ensure a ranked subset is labeled as a subset rather than the complete breakdown.

Verification

Run controlled requests over the same resource, metric and period with the intended filter and without it. Inspect each returned series’ dimension metadata, not just the number of data points. Confirm that the consumer accepts the expected series structure and does not silently treat the aggregate as one ordinary dimension member. Check the configured result type and limits when values or series appear missing, preserving the request and sanitized response for review.

Official references

Microsoft Learn: Azure Monitor REST API walkthrough. Source reviewed September 9, 2026.