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

> Does an Azure Monitor metrics request without dimension filters return each dimension's measurements separately?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:28:27+00:00
- Modified: 2026-09-10T01:20:45+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 2 minutes

## What you need to know

Does an Azure Monitor metrics request without dimension filters return each dimension's measurements separately?

## Potentially affected

Authorized clients querying dimensional metrics through the Azure Monitor ARM metrics REST API.

## DSE recommendation

Specify whether the consumer needs a rolled-up result or separate dimension series before constructing the request.

## Article

## 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](https://learn.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough).

## 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](https://learn.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough). Source reviewed September 9, 2026.

## Primary reference

- Name: Azure Monitor REST API walkthrough - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Request dimensional time series explicitly instead of accepting a rolled-up metric,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.