{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "slug": "dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics", "url": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/" }, "title": "Check the disk controller before interpreting missing Azure latency metrics", "summary": "Does an absent Azure disk-latency series mean an NVMe-backed workload has no latency?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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:31:02+00:00", "modified_at": "2026-09-10T00:35:07+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 246, "potentially_affected": "Azure VM operators interpreting disk performance metrics for SCSI and NVMe controllers.", "dse_recommendation": "Check metric availability for the actual controller before treating a missing series as a healthy result.", "primary_source": { "name": "Disk metrics - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-metrics", "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

Azure’s OS Disk Latency and Data Disk Latency metrics are preview measurements available for SCSI-attached disks, not disks attached through an NVMe controller. The documented temporary-disk latency, queue-depth, read and write metrics are also unavailable for NVMe temporary storage. Disk performance metrics do not record individual create, read, update or delete operations inside a managed disk. Microsoft Learn.

\n

Applicability

\n

Use this check while reviewing a monitoring gap after choosing or changing a VM’s storage controller. Separate an unsupported measurement from an observed value of zero, and do not describe aggregate performance monitoring as a file-operation audit.

\n

DSE recommendation

\n

Check metric availability for the actual controller before treating a missing series as a healthy result. Have the monitoring owner record the controller, disk role and precise requested metric before investigating collection failure. Identify a supported measurement path for the workload’s performance question and a separately authorized audit approach if individual data access is the concern. Keep unavailable signals visibly unresolved instead of filling their chart gaps with assumed healthy values.

\n

Verification

\n

On a controlled VM, confirm the actual disk/controller configuration and inspect which series are emitted. Compare supported observations with the application’s measured behavior during the same interval. Document any excluded metric so a later dashboard consumer knows why it is absent. Do not use a successful VM start or a populated neighboring chart as evidence that an unsupported latency metric has become available.

\n

Official references

\n

Microsoft Learn: Disk performance metrics. Source reviewed September 9, 2026.

", "content_text": "Source facts\nAzure’s OS Disk Latency and Data Disk Latency metrics are preview measurements available for SCSI-attached disks, not disks attached through an NVMe controller. The documented temporary-disk latency, queue-depth, read and write metrics are also unavailable for NVMe temporary storage. Disk performance metrics do not record individual create, read, update or delete operations inside a managed disk. Microsoft Learn.\nApplicability\nUse this check while reviewing a monitoring gap after choosing or changing a VM’s storage controller. Separate an unsupported measurement from an observed value of zero, and do not describe aggregate performance monitoring as a file-operation audit.\nDSE recommendation\nCheck metric availability for the actual controller before treating a missing series as a healthy result. Have the monitoring owner record the controller, disk role and precise requested metric before investigating collection failure. Identify a supported measurement path for the workload’s performance question and a separately authorized audit approach if individual data access is the concern. Keep unavailable signals visibly unresolved instead of filling their chart gaps with assumed healthy values.\nVerification\nOn a controlled VM, confirm the actual disk/controller configuration and inspect which series are emitted. Compare supported observations with the application’s measured behavior during the same interval. Document any excluded metric so a later dashboard consumer knows why it is absent. Do not use a successful VM start or a populated neighboring chart as evidence that an unsupported latency metric has become available.\nOfficial references\nMicrosoft Learn: Disk performance metrics. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nAzure’s OS Disk Latency and Data Disk Latency metrics are preview measurements available for SCSI-attached disks, not disks attached through an NVMe controller. The documented temporary-disk latency, queue-depth, read and write metrics are also unavailable for NVMe temporary storage. Disk performance metrics do not record individual create, read, update or delete operations inside a managed disk. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-metrics).\n\n## Applicability\n\nUse this check while reviewing a monitoring gap after choosing or changing a VM’s storage controller. Separate an unsupported measurement from an observed value of zero, and do not describe aggregate performance monitoring as a file-operation audit.\n\n## DSE recommendation\n\nCheck metric availability for the actual controller before treating a missing series as a healthy result. Have the monitoring owner record the controller, disk role and precise requested metric before investigating collection failure. Identify a supported measurement path for the workload’s performance question and a separately authorized audit approach if individual data access is the concern. Keep unavailable signals visibly unresolved instead of filling their chart gaps with assumed healthy values.\n\n## Verification\n\nOn a controlled VM, confirm the actual disk/controller configuration and inspect which series are emitted. Compare supported observations with the application’s measured behavior during the same interval. Document any excluded metric so a later dashboard consumer knows why it is absent. Do not use a successful VM start or a populated neighboring chart as evidence that an unsupported latency metric has become available.\n\n## Official references\n\n[Microsoft Learn: Disk performance metrics](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-metrics). 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-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "url": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check the disk controller before interpreting missing Azure latency metrics", "item": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "url": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/", "headline": "Check the disk controller before interpreting missing Azure latency metrics", "description": "Does an absent Azure disk-latency series mean an NVMe-backed workload has no latency?", "abstract": "Does an absent Azure disk-latency series mean an NVMe-backed workload has no latency?", "articleBody": "Source facts\nAzure’s OS Disk Latency and Data Disk Latency metrics are preview measurements available for SCSI-attached disks, not disks attached through an NVMe controller. The documented temporary-disk latency, queue-depth, read and write metrics are also unavailable for NVMe temporary storage. Disk performance metrics do not record individual create, read, update or delete operations inside a managed disk. Microsoft Learn.\nApplicability\nUse this check while reviewing a monitoring gap after choosing or changing a VM’s storage controller. Separate an unsupported measurement from an observed value of zero, and do not describe aggregate performance monitoring as a file-operation audit.\nDSE recommendation\nCheck metric availability for the actual controller before treating a missing series as a healthy result. Have the monitoring owner record the controller, disk role and precise requested metric before investigating collection failure. Identify a supported measurement path for the workload’s performance question and a separately authorized audit approach if individual data access is the concern. Keep unavailable signals visibly unresolved instead of filling their chart gaps with assumed healthy values.\nVerification\nOn a controlled VM, confirm the actual disk/controller configuration and inspect which series are emitted. Compare supported observations with the application’s measured behavior during the same interval. Document any excluded metric so a later dashboard consumer knows why it is absent. Do not use a successful VM start or a populated neighboring chart as evidence that an unsupported latency metric has become available.\nOfficial references\nMicrosoft Learn: Disk performance metrics. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:31:02+00:00", "dateModified": "2026-09-10T00:35:07+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/" }, "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-054-check-the-disk-controller-before-interpreting-missing-azure-latency-metrics/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check the disk controller before interpreting missing Azure latency metrics" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 246, "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": "Disk metrics - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-metrics" } } ] } }