Monitor persistent memory beyond ordinary disk charts

Source facts

Microsoft says persistent memory does not produce Physical Disk performance counters, so it does not appear in the corresponding Windows Admin Center charts. It also does not produce Storport 505 data for proactive outlier detection. The UnsafeShutdownCount value totals shutdowns of underlying persistent-memory devices that may have caused data loss. Microsoft Learn.

Applicability

Confirm that the investigated device is persistent memory and identify its actual storage role. Review the documented operating-system limitations before interpreting missing chart data. Keep a missing metric, a warning state, and an unhealthy device as different observations.

DSE recommendation

Add persistent-memory-specific health queries to the storage runbook. Capture device identity, health, operational status, physical location, and unsafe-shutdown observations in a single record. Assign a hardware owner to interpret warnings alongside the vendor guidance. Avoid reinitializing an unfamiliar or unhealthy device merely to make a dashboard look normal. Preserve the initial state for investigation.

Verification

Compare the query output with the physical inventory and the relevant operational events. Verify that monitoring can detect the documented warning or unhealthy state in an approved test or reviewed incident sample. Record unavailable metrics as monitoring limitations and confirm that the escalation path reaches the correct hardware owner.

Official references

Microsoft Learn: Persistent memory health management for Storage Spaces Direct in Windows Server. Source reviewed September 8, 2026.