What metrics are essential for Windows system administration?

2 Memory Usage

Memory usage measures how much of the physical and virtual memory is being used by the system and its processes. Low memory availability can lead to performance degradation, errors, or crashes. You can use the Task Manager or the Performance Monitor to view the memory usage of the system and individual processes, as well as the available bytes, pages, faults, and cache. You can also use PowerShell commands or scripts to query and report on memory metrics. You should monitor memory usage over time and compare it to the baseline and the expected demand. You should also identify and troubleshoot any processes that leak or consume excessive or abnormal memory resources.

3 Disk Usage

Disk usage measures how much of the disk space and input/output (I/O) capacity is being used by the system and its processes. High disk usage can indicate a lack of storage space, a bottleneck, or a malfunctioning process. You can use the File Explorer or the Performance Monitor to view the disk usage of the system and individual volumes, as well as the read/write bytes, latency, queue length, and errors. You can also use PowerShell commands or scripts to query and report on disk metrics. You should monitor disk usage over time and compare it to the baseline and the expected demand. You should also identify and troubleshoot any processes that generate excessive or abnormal disk activity.

4 Network Usage

Network usage measures how much of the network bandwidth and connection capacity is being used by the system and its processes. High network usage can indicate a high traffic volume, a bottleneck, or a malfunctioning process. You can use the Task Manager or the Performance Monitor to view the network usage of the system and individual interfaces, as well as the sent/received bytes, packets, errors, and drops. You can also use PowerShell commands or scripts to query and report on network metrics. You should monitor network usage over time and compare it to the baseline and the expected demand. You should also identify and troubleshoot any processes that send or receive excessive or abnormal network data.

5 Security Events

Security events measure how often and how severely the system and its processes encounter security threats, such as unauthorized access, malware, or configuration changes. High security event frequency or severity can indicate a compromised or vulnerable system. You can use the Event Viewer or the Security and Maintenance Center to view the security events of the system and individual processes, as well as the event ID, level, source, and message. You can also use PowerShell commands or scripts to query and report on security events. You should monitor security events over time and compare them to the baseline and the expected risk. You should also identify and troubleshoot any processes that cause or suffer from security issues.

6 Service Availability

Service availability measures how often and how long the system and its processes provide the expected functionality and quality to the users or clients. Low service availability can indicate a failed or degraded system. You can use the Services Manager or the Performance Monitor to view the service availability of the system and individual processes, as well as the status, start type, and dependencies. You can also use PowerShell commands or scripts to query and report on service availability. You should monitor service availability over time and compare it to the baseline and the expected SLA. You should also identify and troubleshoot any processes that stop or fail to start properly.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?