{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "slug": "dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry", "url": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/" }, "title": "Check locked metric-chart bounds before diagnosing missing telemetry", "summary": "Can a locked vertical axis hide valid Azure Monitor values after automatic granularity changes?", "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:27:53+00:00", "modified_at": "2026-09-10T01:20:46+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 240, "potentially_affected": "Azure Monitor metrics-explorer charts with fixed vertical-axis bounds, particularly sum, minimum or maximum aggregations.", "dse_recommendation": "Temporarily release the vertical-axis bounds and record the aggregation interval before treating a blank chart as collection failure.", "primary_source": { "name": "Troubleshooting Azure Monitor metric charts - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-troubleshoot", "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

A locked metrics-chart vertical axis can place every valid measurement outside the visible area. Microsoft cautions against combining fixed bounds with automatic granularity for sum, minimum and maximum charts: changing the browser size or screen resolution can change granularity and the resulting values, leaving the plot empty. Its troubleshooting guidance recommends resetting the bounds to check whether values are outside the displayed range. Microsoft Learn.

\n

Applicability

\n

Investigate this display condition when a previously useful chart appears blank, particularly after resizing it or opening it on another screen. Keep chart visibility separate from the underlying question of whether the resource emitted measurements.

\n

DSE recommendation

\n

Temporarily release the vertical-axis bounds and record the aggregation interval before treating a blank chart as collection failure. Compare the resource, metric and time range with the original view so the display experiment changes as little else as possible. If a fixed range is needed for operational interpretation, have the chart owner choose it deliberately alongside a documented granularity.

\n

Verification

\n

Reopen the chart with automatic bounds and inspect the actual plotted values. Compare the result at the original and changed display sizes, recording any granularity change. If measurements reappear, correct the saved view and explain the presentation issue in the investigation record. If they do not, retain that negative result and continue collection troubleshooting without claiming the axis test proved a telemetry outage or recovery.

\n

Official references

\n

Microsoft Learn: Troubleshooting metrics charts. Source reviewed September 9, 2026.

", "content_text": "Source facts\nA locked metrics-chart vertical axis can place every valid measurement outside the visible area. Microsoft cautions against combining fixed bounds with automatic granularity for sum, minimum and maximum charts: changing the browser size or screen resolution can change granularity and the resulting values, leaving the plot empty. Its troubleshooting guidance recommends resetting the bounds to check whether values are outside the displayed range. Microsoft Learn.\nApplicability\nInvestigate this display condition when a previously useful chart appears blank, particularly after resizing it or opening it on another screen. Keep chart visibility separate from the underlying question of whether the resource emitted measurements.\nDSE recommendation\nTemporarily release the vertical-axis bounds and record the aggregation interval before treating a blank chart as collection failure. Compare the resource, metric and time range with the original view so the display experiment changes as little else as possible. If a fixed range is needed for operational interpretation, have the chart owner choose it deliberately alongside a documented granularity.\nVerification\nReopen the chart with automatic bounds and inspect the actual plotted values. Compare the result at the original and changed display sizes, recording any granularity change. If measurements reappear, correct the saved view and explain the presentation issue in the investigation record. If they do not, retain that negative result and continue collection troubleshooting without claiming the axis test proved a telemetry outage or recovery.\nOfficial references\nMicrosoft Learn: Troubleshooting metrics charts. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nA locked metrics-chart vertical axis can place every valid measurement outside the visible area. Microsoft cautions against combining fixed bounds with automatic granularity for sum, minimum and maximum charts: changing the browser size or screen resolution can change granularity and the resulting values, leaving the plot empty. Its troubleshooting guidance recommends resetting the bounds to check whether values are outside the displayed range. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-troubleshoot).\n\n## Applicability\n\nInvestigate this display condition when a previously useful chart appears blank, particularly after resizing it or opening it on another screen. Keep chart visibility separate from the underlying question of whether the resource emitted measurements.\n\n## DSE recommendation\n\nTemporarily release the vertical-axis bounds and record the aggregation interval before treating a blank chart as collection failure. Compare the resource, metric and time range with the original view so the display experiment changes as little else as possible. If a fixed range is needed for operational interpretation, have the chart owner choose it deliberately alongside a documented granularity.\n\n## Verification\n\nReopen the chart with automatic bounds and inspect the actual plotted values. Compare the result at the original and changed display sizes, recording any granularity change. If measurements reappear, correct the saved view and explain the presentation issue in the investigation record. If they do not, retain that negative result and continue collection troubleshooting without claiming the axis test proved a telemetry outage or recovery.\n\n## Official references\n\n[Microsoft Learn: Troubleshooting metrics charts](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-troubleshoot). 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-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "url": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check locked metric-chart bounds before diagnosing missing telemetry", "item": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "url": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/", "headline": "Check locked metric-chart bounds before diagnosing missing telemetry", "description": "Can a locked vertical axis hide valid Azure Monitor values after automatic granularity changes?", "abstract": "Can a locked vertical axis hide valid Azure Monitor values after automatic granularity changes?", "articleBody": "Source facts\nA locked metrics-chart vertical axis can place every valid measurement outside the visible area. Microsoft cautions against combining fixed bounds with automatic granularity for sum, minimum and maximum charts: changing the browser size or screen resolution can change granularity and the resulting values, leaving the plot empty. Its troubleshooting guidance recommends resetting the bounds to check whether values are outside the displayed range. Microsoft Learn.\nApplicability\nInvestigate this display condition when a previously useful chart appears blank, particularly after resizing it or opening it on another screen. Keep chart visibility separate from the underlying question of whether the resource emitted measurements.\nDSE recommendation\nTemporarily release the vertical-axis bounds and record the aggregation interval before treating a blank chart as collection failure. Compare the resource, metric and time range with the original view so the display experiment changes as little else as possible. If a fixed range is needed for operational interpretation, have the chart owner choose it deliberately alongside a documented granularity.\nVerification\nReopen the chart with automatic bounds and inspect the actual plotted values. Compare the result at the original and changed display sizes, recording any granularity change. If measurements reappear, correct the saved view and explain the presentation issue in the investigation record. If they do not, retain that negative result and continue collection troubleshooting without claiming the axis test proved a telemetry outage or recovery.\nOfficial references\nMicrosoft Learn: Troubleshooting metrics charts. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:27:53+00:00", "dateModified": "2026-09-10T01:20:46+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/" }, "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-243-check-locked-metric-chart-bounds-before-diagnosing-missing-telemetry/#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": "Check locked metric-chart bounds before diagnosing missing telemetry" }, "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": "Troubleshooting Azure Monitor metric charts - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/metrics-troubleshoot" } } ] } }