Monitor Solution policies are useful for detecting when servers have health problems such as when a rogue process consumes the CPU. The CPU averaged > 85% over past 3 minutes metric rule is a predefined metric rule designed for detecting CPU problems. However the alert and the email for this metric rule give no indication of what process caused the problem and the problem may be resolved or the server may be crashed before the cause can be assessed. This article describes how to customize a monitor policy, metric rule, and metrics that will give more data and help identify the problem process. Note that the CPU usage numbers reported by monitor solution will not match those shown in Task Manager but instead correspond to CPU usage numbers shown by querying WMI with the following command: wmic path Win32_PerfFormattedData_PerfPr
1. Create a Monitor Policy
2. Create a Metric Rule
3. Create a Metric
4. Configure the Metric Evaluation
Figure 1. The configuration of the metric evaluation to trigger if any process uses over 85% of the CPU.
5. Disregard the Idle Process
Figure 2. The configuration of the metric evaluation to not trigger if the Idle process is using over 15% CPU, meaning that no other process is using that part of the CPU.
6. Add a Send Email Task
7. Add a Target