{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "slug": "dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric", "url": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/" }, "title": "Request dimensional time series explicitly instead of accepting a rolled-up metric", "summary": "Does an Azure Monitor metrics request without dimension filters return each dimension's measurements separately?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:28:27+00:00", "modified_at": "2026-09-10T01:20:45+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 240, "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.", "primary_source": { "name": "Azure Monitor REST API walkthrough - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nThe 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.\nApplicability\nApply 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.\nDSE recommendation\nSpecify 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Azure Monitor REST API walkthrough. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nThe 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).\n\n## Applicability\n\nApply 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.\n\n## DSE recommendation\n\nSpecify 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.\n\n## Verification\n\nRun 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "url": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Request dimensional time series explicitly instead of accepting a rolled-up metric", "item": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "url": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/", "headline": "Request dimensional time series explicitly instead of accepting a rolled-up metric", "description": "Does an Azure Monitor metrics request without dimension filters return each dimension's measurements separately?", "abstract": "Does an Azure Monitor metrics request without dimension filters return each dimension's measurements separately?", "articleBody": "Source facts\nThe 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.\nApplicability\nApply 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.\nDSE recommendation\nSpecify 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.\nVerification\nRun 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.\nOfficial references\nMicrosoft Learn: Azure Monitor REST API walkthrough. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:28:27+00:00", "dateModified": "2026-09-10T01:20:45+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-209-request-dimensional-time-series-explicitly-instead-of-accepting-a-rolled-up-metric/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Request dimensional time series explicitly instead of accepting a rolled-up metric" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 240, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Azure Monitor REST API walkthrough - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/platform/rest-api-walkthrough" } } ] } }