Account for coarser samples when reviewing older S2D performance history

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.

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. Source reviewed September 8, 2026.