Understand application monitor thresholds
Thresholds are markers that indicate certain levels have been reached. Many component monitors used in SAM application monitors have thresholds that can be adjusted and set to act as trigger points. For example, if monitoring CPU usage, a Critical threshold set at 90% would be typical. You can use this threshold as a trigger for SAM to send you an email alert when a Critical status threshold is breached.
In general, you need to monitor applications for several weeks to collect enough data to use as a baseline. After you establish a baseline, you can make an educated guess about how to set Warning and Critical thresholds for component monitors.
If thresholds are set too low, you'll receive frequent alerts. If set too high, problems can occur without your knowledge.
Baseline data, as well as Warning and Critical thresholds for application monitors, can also be gathered and calculated automatically, as described in Adjust threshold settings and apply baseline data. The option to enter thresholds manually remains available.
By default, I/O thresholds of Windows Service Monitors are not set.
For more information, see:
- Thresholds in the Orion Platform (Orion Platform Administrator Guide)
- Inheriting thresholds in SAM
- Multi-Value scripts and thresholds
- Apply baseline thresholds at the template level
- Apply baseline thresholds at the application level
- Use Min/Max Average Statistic charts to set thresholds based on 95th percentile data (Success Center)
- View latest baseline details
- Baseline thresholds (THWACK)
If an application is slow, you can use performance thresholds and baselines in SAM to identify the current problem and isolate it to an infrastructure, application, or database issue.
Did you know you can use SolarWinds Database Performance Analyzer (DPA) to identify specific queries that contribute to an issue? With DPA, you can use histogram analysis to find the offending query and dissect it with response-time analysis.