{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "slug": "dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history", "url": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/" }, "title": "Account for coarser samples when reviewing older S2D performance history", "summary": "How does the age of Storage Spaces Direct performance history affect its time resolution?", "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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-08T18:14:34+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 225, "potentially_affected": "Administrators interpreting retained Storage Spaces Direct performance measurements on supported releases from Windows Server 2019 onward.", "dse_recommendation": "Label every chart or report with both the object scope and time resolution.", "primary_source": { "name": "Performance history for Storage Spaces Direct", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history", "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 collects S2D performance history automatically and stores it on the cluster for up to a year. Performance history was introduced in Windows Server 2019; Windows Server 2016 does not provide it. Recent data is more detailed: the most recent hour has ten-second measurements, the day has five-minute measurements, and the week has fifteen-minute measurements. Older samples are merged using averaging or summation as appropriate. Some series are also aggregated from individual objects to parents, such as adapters to a server. Microsoft documentation.

\n

Applicability

\n

Identify the metric, object level, event time, requested timeframe, and sample granularity. Check whether the question requires a brief spike or a longer trend before relying on older retained data.

\n

DSE recommendation

\n

Label every chart or report with both the object scope and time resolution. Ask the investigator to distinguish a missing short-lived peak from a measurement that was never retained at that resolution. Preserve suitably detailed incident evidence promptly when a narrow timing question is expected.

\n

Verification

\n

Compare sample timestamps and aggregation level with the requested interval before interpreting the values. Where possible, reconcile a recent detailed period with its broader summary. Record the temporal limitation in the finding so an averaged historical value is not presented as proof that a short event did not occur.

\n

Official references

\n

Microsoft Learn: Performance history for Storage Spaces Direct. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft collects S2D performance history automatically and stores it on the cluster for up to a year. Performance history was introduced in Windows Server 2019; Windows Server 2016 does not provide it. Recent data is more detailed: the most recent hour has ten-second measurements, the day has five-minute measurements, and the week has fifteen-minute measurements. Older samples are merged using averaging or summation as appropriate. Some series are also aggregated from individual objects to parents, such as adapters to a server. Microsoft documentation.\nApplicability\nIdentify the metric, object level, event time, requested timeframe, and sample granularity. Check whether the question requires a brief spike or a longer trend before relying on older retained data.\nDSE recommendation\nLabel every chart or report with both the object scope and time resolution. Ask the investigator to distinguish a missing short-lived peak from a measurement that was never retained at that resolution. Preserve suitably detailed incident evidence promptly when a narrow timing question is expected.\nVerification\nCompare sample timestamps and aggregation level with the requested interval before interpreting the values. Where possible, reconcile a recent detailed period with its broader summary. Record the temporal limitation in the finding so an averaged historical value is not presented as proof that a short event did not occur.\nOfficial references\nMicrosoft Learn: Performance history for Storage Spaces Direct. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft collects S2D performance history automatically and stores it on the cluster for up to a year. Performance history was introduced in Windows Server 2019; Windows Server 2016 does not provide it. Recent data is more detailed: the most recent hour has ten-second measurements, the day has five-minute measurements, and the week has fifteen-minute measurements. Older samples are merged using averaging or summation as appropriate. Some series are also aggregated from individual objects to parents, such as adapters to a server. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history).\n\n## Applicability\n\nIdentify the metric, object level, event time, requested timeframe, and sample granularity. Check whether the question requires a brief spike or a longer trend before relying on older retained data.\n\n## DSE recommendation\n\nLabel every chart or report with both the object scope and time resolution. Ask the investigator to distinguish a missing short-lived peak from a measurement that was never retained at that resolution. Preserve suitably detailed incident evidence promptly when a narrow timing question is expected.\n\n## Verification\n\nCompare sample timestamps and aggregation level with the requested interval before interpreting the values. Where possible, reconcile a recent detailed period with its broader summary. Record the temporal limitation in the finding so an averaged historical value is not presented as proof that a short event did not occur.\n\n## Official references\n\n[Microsoft Learn: Performance history for Storage Spaces Direct](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history). Source reviewed September 8, 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-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "url": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Account for coarser samples when reviewing older S2D performance history", "item": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "url": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/", "headline": "Account for coarser samples when reviewing older S2D performance history", "description": "How does the age of Storage Spaces Direct performance history affect its time resolution?", "abstract": "How does the age of Storage Spaces Direct performance history affect its time resolution?", "articleBody": "Source facts\nMicrosoft collects S2D performance history automatically and stores it on the cluster for up to a year. Performance history was introduced in Windows Server 2019; Windows Server 2016 does not provide it. Recent data is more detailed: the most recent hour has ten-second measurements, the day has five-minute measurements, and the week has fifteen-minute measurements. Older samples are merged using averaging or summation as appropriate. Some series are also aggregated from individual objects to parents, such as adapters to a server. Microsoft documentation.\nApplicability\nIdentify the metric, object level, event time, requested timeframe, and sample granularity. Check whether the question requires a brief spike or a longer trend before relying on older retained data.\nDSE recommendation\nLabel every chart or report with both the object scope and time resolution. Ask the investigator to distinguish a missing short-lived peak from a measurement that was never retained at that resolution. Preserve suitably detailed incident evidence promptly when a narrow timing question is expected.\nVerification\nCompare sample timestamps and aggregation level with the requested interval before interpreting the values. Where possible, reconcile a recent detailed period with its broader summary. Record the temporal limitation in the finding so an averaged historical value is not presented as proof that a short event did not occur.\nOfficial references\nMicrosoft Learn: Performance history for Storage Spaces Direct. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:34+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/" }, "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-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/#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": "Account for coarser samples when reviewing older S2D performance history" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 225, "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": "Performance history for Storage Spaces Direct", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history" } } ] } }