{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "slug": "dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates", "url": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/" }, "title": "Convert Elastic SAN transaction buckets into correctly scoped average rates", "summary": "Transactions and transferred bytes need the selected interval's duration; the result is a SAN-level average, not an instantaneous per-volume peak.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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:32+00:00", "modified_at": "2026-09-10T02:01:56+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 238, "potentially_affected": "Azure Elastic SAN metric reports built from Transactions, Ingress and Egress.", "dse_recommendation": "Record aggregation, interval and SAN scope beside each calculated rate.", "primary_source": { "name": "Metrics for Azure Elastic SAN | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-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

Microsoft calculates average Elastic SAN IOPS by dividing total transactions in a time bucket by that bucket’s seconds. Average total throughput in MB/s is the sum of Ingress and Egress bytes divided by seconds and by 1,000,000. These are interval averages, not instantaneous rates.

\n

For Elastic SAN, Ingress is data written to the SAN and Egress is data read from it. Metrics are currently available at SAN level, not as volume-group or per-volume performance metrics; Microsoft recommends correlating workload, VM or operating-system monitoring. Microsoft Learn.

\n

Applicability

\n

Identify the SAN, time range, bucket duration and aggregation selected in the report. Keep read and write direction anchored to the SAN rather than the client’s interface labels.

\n

DSE recommendation

\n

DSE recommends storing the denominator and metric scope with each derived rate. Recalculate when chart granularity changes; do not keep dividing by sixty after switching away from minute buckets. Use separate workload evidence to investigate one volume instead of assigning the whole SAN’s traffic to it. Keep peaks and bucket averages distinctly labeled.

\n

Verification

\n

Reproduce a selected report point from its raw transaction or byte total and interval duration. Compare the result at another supported granularity and explain expected averaging differences. Correlate a controlled workload observation without claiming the aggregate proves a particular volume’s rate. Retain the calculation inputs so another reviewer can check both units and scope.

\n

Official references

\n

Microsoft Learn: Metrics for Azure Elastic SAN. Source retrieved September 9, 2026.

", "content_text": "Source facts\nMicrosoft calculates average Elastic SAN IOPS by dividing total transactions in a time bucket by that bucket’s seconds. Average total throughput in MB/s is the sum of Ingress and Egress bytes divided by seconds and by 1,000,000. These are interval averages, not instantaneous rates.\nFor Elastic SAN, Ingress is data written to the SAN and Egress is data read from it. Metrics are currently available at SAN level, not as volume-group or per-volume performance metrics; Microsoft recommends correlating workload, VM or operating-system monitoring. Microsoft Learn.\nApplicability\nIdentify the SAN, time range, bucket duration and aggregation selected in the report. Keep read and write direction anchored to the SAN rather than the client’s interface labels.\nDSE recommendation\nDSE recommends storing the denominator and metric scope with each derived rate. Recalculate when chart granularity changes; do not keep dividing by sixty after switching away from minute buckets. Use separate workload evidence to investigate one volume instead of assigning the whole SAN’s traffic to it. Keep peaks and bucket averages distinctly labeled.\nVerification\nReproduce a selected report point from its raw transaction or byte total and interval duration. Compare the result at another supported granularity and explain expected averaging differences. Correlate a controlled workload observation without claiming the aggregate proves a particular volume’s rate. Retain the calculation inputs so another reviewer can check both units and scope.\nOfficial references\nMicrosoft Learn: Metrics for Azure Elastic SAN. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nMicrosoft calculates average Elastic SAN IOPS by dividing total transactions in a time bucket by that bucket’s seconds. Average total throughput in MB/s is the sum of Ingress and Egress bytes divided by seconds and by 1,000,000. These are interval averages, not instantaneous rates.\n\nFor Elastic SAN, Ingress is data written to the SAN and Egress is data read from it. Metrics are currently available at SAN level, not as volume-group or per-volume performance metrics; Microsoft recommends correlating workload, VM or operating-system monitoring. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-metrics).\n\n## Applicability\n\nIdentify the SAN, time range, bucket duration and aggregation selected in the report. Keep read and write direction anchored to the SAN rather than the client’s interface labels.\n\n## DSE recommendation\n\nDSE recommends storing the denominator and metric scope with each derived rate. Recalculate when chart granularity changes; do not keep dividing by sixty after switching away from minute buckets. Use separate workload evidence to investigate one volume instead of assigning the whole SAN’s traffic to it. Keep peaks and bucket averages distinctly labeled.\n\n## Verification\n\nReproduce a selected report point from its raw transaction or byte total and interval duration. Compare the result at another supported granularity and explain expected averaging differences. Correlate a controlled workload observation without claiming the aggregate proves a particular volume’s rate. Retain the calculation inputs so another reviewer can check both units and scope.\n\n## Official references\n\n[Microsoft Learn: Metrics for Azure Elastic SAN](https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-metrics). Source retrieved 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-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "url": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Convert Elastic SAN transaction buckets into correctly scoped average rates", "item": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "url": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/", "headline": "Convert Elastic SAN transaction buckets into correctly scoped average rates", "description": "Transactions and transferred bytes need the selected interval's duration; the result is a SAN-level average, not an instantaneous per-volume peak.", "abstract": "Transactions and transferred bytes need the selected interval's duration; the result is a SAN-level average, not an instantaneous per-volume peak.", "articleBody": "Source facts\nMicrosoft calculates average Elastic SAN IOPS by dividing total transactions in a time bucket by that bucket’s seconds. Average total throughput in MB/s is the sum of Ingress and Egress bytes divided by seconds and by 1,000,000. These are interval averages, not instantaneous rates.\nFor Elastic SAN, Ingress is data written to the SAN and Egress is data read from it. Metrics are currently available at SAN level, not as volume-group or per-volume performance metrics; Microsoft recommends correlating workload, VM or operating-system monitoring. Microsoft Learn.\nApplicability\nIdentify the SAN, time range, bucket duration and aggregation selected in the report. Keep read and write direction anchored to the SAN rather than the client’s interface labels.\nDSE recommendation\nDSE recommends storing the denominator and metric scope with each derived rate. Recalculate when chart granularity changes; do not keep dividing by sixty after switching away from minute buckets. Use separate workload evidence to investigate one volume instead of assigning the whole SAN’s traffic to it. Keep peaks and bucket averages distinctly labeled.\nVerification\nReproduce a selected report point from its raw transaction or byte total and interval duration. Compare the result at another supported granularity and explain expected averaging differences. Correlate a controlled workload observation without claiming the aggregate proves a particular volume’s rate. Retain the calculation inputs so another reviewer can check both units and scope.\nOfficial references\nMicrosoft Learn: Metrics for Azure Elastic SAN. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:32+00:00", "dateModified": "2026-09-10T02:01:56+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/" }, "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-384-convert-elastic-san-transaction-buckets-into-correctly-scoped-average-rates/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Convert Elastic SAN transaction buckets into correctly scoped average rates" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 238, "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 for Azure Elastic SAN | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/elastic-san/elastic-san-metrics" } } ] } }