Application Monitor Thresholds
Once set, thresholds can act as trigger points. For example, if you are monitoring CPU usage, a Critical threshold set at 90% would be typical. You can use this threshold as a trigger to send an email alert to inform you of the Critical status once that threshold has been breached.
Normally, an administrator would need to monitor applications for several weeks in order to collect enough data to be used as a baseline. Once a baseline has been established, the administrator can make an educated guess how to set Warning and Critical thresholds for the component monitors.
If thresholds are set too low, the administrator would be getting alerts all the time. If set too high, problems can occur without the administrator's knowledge.
Baseline data, as well as Warning and Critical thresholds for application monitors, can be gathered and calculated automatically. The option to enter thresholds manually remains available.
By default, I/O thresholds of Windows Service Monitors are not set.
For more information, refer to the following sections:
- Inheriting Thresholds
- Adjust threshold settings and apply baseline data
- Multi-Value scripts and thresholds
- Apply baseline thresholds at the template level
- Apply baseline thresholds at the application level
- View latest baseline details