Custom Counters with No Data
Use this page if the custom performance counters in PerformanceGuard don’t show any data for a computer. The usual cause is that the Windows performance counter configuration on that computer is damaged. To fix it, rebuild the performance counters on the computer that has no data.
-
Open an elevated Command Prompt (right-click Command Prompt and select Run as administrator).
-
Rebuild the performance counters:
Terminal window lodctr /R -
Check that the performance counter configuration is now valid and that no errors are reported:
Terminal window lodctr /Q -
List the available counters, and check that the counters your custom counters use are in the list:
Terminal window typeperf -q
The agent notices when the performance counter names change and restarts itself. If data still doesn’t appear after the next delivery interval, restart the PerformanceGuard agent service.
If a custom counter still reports no data, check the computer’s message log for the Could not create custom counter message. See Diagnose Computer Message Log.
Common performance counters
Section titled “Common performance counters”| Counter | What it measures |
|---|---|
\Processor(_Total)\% Processor Time |
Total CPU usage |
\Processor(_Total)\% User Time |
Time spent on user processes |
\Processor(_Total)\% Privileged Time |
Time spent on kernel and system processes |
\PhysicalDisk(_Total)\Disk Read Bytes/sec |
Bytes read per second |
\PhysicalDisk(_Total)\Disk Write Bytes/sec |
Bytes written per second |
\PhysicalDisk(_Total)\Avg. Disk sec/Read |
Average time per read |
\PhysicalDisk(_Total)\Avg. Disk sec/Write |
Average time per write |
\PhysicalDisk(_Total)\Disk Transfers/sec |
Total read and write operations per second |