# Account for coarser samples when reviewing older S2D performance history

> How does the age of Storage Spaces Direct performance history affect its time resolution?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:34+00:00
- Modified: 2026-09-08T18:26:31+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 2 minutes

## What you need to know

How does the age of Storage Spaces Direct performance history affect its time resolution?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Performance history for Storage Spaces Direct
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/performance-history
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Account for coarser samples when reviewing older S2D performance history,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-157-account-for-coarser-samples-when-reviewing-older-s2d-performance-history/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.