Applies to: BLAZE
Issue Summary
This article describes how to resolve cases where Health Monitoring shows '0' for all resources on the specific Windows servers. This article explains the causes of system resource display failures following Windows OS updates and provides recovery steps and addresses issues such as registry path corruption, synchronization delays in hardware driver recognition, and Windows Management Instrumentation (WMI) repository data loss. It outlines the procedures for rebuilding performance counter libraries and resyncing WMI objects to restore accurate telemetry for CPU, Memory, and Disk usage.
Resolution
Normalize resource data collection by manually re-registering corrupted performance counter reference addresses. To manually re-register:
- Click Win + R.
- Type perfmon.msc in the Run dialog.
- Click Enter.
- Check whether an error pop-up appears regarding missing counters, specifically ‘PhysicalDisk Idle Time’ or ‘PhysicalDisk Avg’.
- In the left navigation panel, select Monitoring Tools > Performance Monitor.
- Click the green plus (+) button on the top toolbar.
- Locate and add the following items:
- PhysicalDisk > % Idle Time
- PhysicalDisk > Avg. Disk sec/Read (or any specific item mentioned in the error popup)
- Navigate to the System dashboard on the Blaze Server.
- Click Refresh in the upper right corner to verify that the data values are displaying correctly.
Comments
0 comments
Article is closed for comments.