{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "slug": "dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports", "url": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/" }, "title": "Interpret the 100 marker for new metrics in usage-change reports", "summary": "Does a 100 value in a metrics usage change column always mean an existing metric doubled?", "format": { "slug": "explainer", "name": "Explainer" }, "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:25:43+00:00", "modified_at": "2026-09-10T02:01:56+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 240, "potentially_affected": "Azure Monitor workspaces using Metrics usage insights in supported public-preview regions.", "dse_recommendation": "Separate newly appearing metrics from growth of existing metrics before ranking changes by percentage.", "primary_source": { "name": "Metrics usage insights in Azure Monitor (Preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-usage-insights", "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

Metrics usage insights is a region-limited public preview. Its Ingestion Volume Change view compares the first and last days of the selected period. When a metric’s initial value is zero, the percentage-change columns display 100 to mark a new metric; when both endpoint values are zero, the percentage is blank. The displayed 100 therefore has a special documented meaning for that case. Microsoft Learn.

\n

Applicability

\n

Use this interpretation for the preview’s comparison table, after confirming regional availability. Record the selected start and end dates, metric name, and dimensions. Do not transfer this display convention to an unrelated metric chart or an independently calculated percentage.

\n

DSE recommendation

\n

Separate newly appearing metrics from growth of existing metrics before ranking changes by percentage. Review the initial and final counts alongside the display column. Ask the monitoring owner whether a new metric was expected from an instrumentation or collection change. Keep an unexplained disappearance or zero-value case visible rather than forcing every row into the same growth narrative.

\n

Verification

\n

Inspect examples of an established metric, a newly appearing metric, and a row with zero at both endpoints. Compare the underlying values with the documented display behavior. Preserve the comparison dates and dimensions with any investigation handoff. If the intended question concerns activity between those endpoints, perform a separate timeline review rather than presenting the two-day comparison as evidence of the entire intervening pattern.

\n

Official references

\n

Microsoft Learn: Metrics usage insights (Preview). Source reviewed September 9, 2026.

", "content_text": "Source facts\nMetrics usage insights is a region-limited public preview. Its Ingestion Volume Change view compares the first and last days of the selected period. When a metric’s initial value is zero, the percentage-change columns display 100 to mark a new metric; when both endpoint values are zero, the percentage is blank. The displayed 100 therefore has a special documented meaning for that case. Microsoft Learn.\nApplicability\nUse this interpretation for the preview’s comparison table, after confirming regional availability. Record the selected start and end dates, metric name, and dimensions. Do not transfer this display convention to an unrelated metric chart or an independently calculated percentage.\nDSE recommendation\nSeparate newly appearing metrics from growth of existing metrics before ranking changes by percentage. Review the initial and final counts alongside the display column. Ask the monitoring owner whether a new metric was expected from an instrumentation or collection change. Keep an unexplained disappearance or zero-value case visible rather than forcing every row into the same growth narrative.\nVerification\nInspect examples of an established metric, a newly appearing metric, and a row with zero at both endpoints. Compare the underlying values with the documented display behavior. Preserve the comparison dates and dimensions with any investigation handoff. If the intended question concerns activity between those endpoints, perform a separate timeline review rather than presenting the two-day comparison as evidence of the entire intervening pattern.\nOfficial references\nMicrosoft Learn: Metrics usage insights (Preview). Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nMetrics usage insights is a region-limited public preview. Its Ingestion Volume Change view compares the first and last days of the selected period. When a metric’s initial value is zero, the percentage-change columns display 100 to mark a new metric; when both endpoint values are zero, the percentage is blank. The displayed 100 therefore has a special documented meaning for that case. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-usage-insights).\n\n## Applicability\n\nUse this interpretation for the preview’s comparison table, after confirming regional availability. Record the selected start and end dates, metric name, and dimensions. Do not transfer this display convention to an unrelated metric chart or an independently calculated percentage.\n\n## DSE recommendation\n\nSeparate newly appearing metrics from growth of existing metrics before ranking changes by percentage. Review the initial and final counts alongside the display column. Ask the monitoring owner whether a new metric was expected from an instrumentation or collection change. Keep an unexplained disappearance or zero-value case visible rather than forcing every row into the same growth narrative.\n\n## Verification\n\nInspect examples of an established metric, a newly appearing metric, and a row with zero at both endpoints. Compare the underlying values with the documented display behavior. Preserve the comparison dates and dimensions with any investigation handoff. If the intended question concerns activity between those endpoints, perform a separate timeline review rather than presenting the two-day comparison as evidence of the entire intervening pattern.\n\n## Official references\n\n[Microsoft Learn: Metrics usage insights (Preview)](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-usage-insights). 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-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "url": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Interpret the 100 marker for new metrics in usage-change reports", "item": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "url": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/", "headline": "Interpret the 100 marker for new metrics in usage-change reports", "description": "Does a 100 value in a metrics usage change column always mean an existing metric doubled?", "abstract": "Does a 100 value in a metrics usage change column always mean an existing metric doubled?", "articleBody": "Source facts\nMetrics usage insights is a region-limited public preview. Its Ingestion Volume Change view compares the first and last days of the selected period. When a metric’s initial value is zero, the percentage-change columns display 100 to mark a new metric; when both endpoint values are zero, the percentage is blank. The displayed 100 therefore has a special documented meaning for that case. Microsoft Learn.\nApplicability\nUse this interpretation for the preview’s comparison table, after confirming regional availability. Record the selected start and end dates, metric name, and dimensions. Do not transfer this display convention to an unrelated metric chart or an independently calculated percentage.\nDSE recommendation\nSeparate newly appearing metrics from growth of existing metrics before ranking changes by percentage. Review the initial and final counts alongside the display column. Ask the monitoring owner whether a new metric was expected from an instrumentation or collection change. Keep an unexplained disappearance or zero-value case visible rather than forcing every row into the same growth narrative.\nVerification\nInspect examples of an established metric, a newly appearing metric, and a row with zero at both endpoints. Compare the underlying values with the documented display behavior. Preserve the comparison dates and dimensions with any investigation handoff. If the intended question concerns activity between those endpoints, perform a separate timeline review rather than presenting the two-day comparison as evidence of the entire intervening pattern.\nOfficial references\nMicrosoft Learn: Metrics usage insights (Preview). Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:25:43+00:00", "dateModified": "2026-09-10T02:01:56+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/" }, "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-373-interpret-the-100-marker-for-new-metrics-in-usage-change-reports/#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": "Interpret the 100 marker for new metrics in usage-change reports" }, "articleSection": [ "IT" ], "keywords": [ "IT", "Explainer", "Information priority" ], "genre": "Explainer", "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": "Metrics usage insights in Azure Monitor (Preview) - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-usage-insights" } } ] } }