Set thresholds in SAM
Thresholds are markers that indicate certain levels were reached. The Orion Platform includes predefined thresholds for most statistics, such as Disk Usage and Response statistics for all monitored nodes, that you can override, as described in Thresholds in the Orion Platform. Many SAM templates, application monitors, and component monitors include predefined thresholds that you can adjust.
In the Orion Web Console, the color of a statistic indicates if reached either of two threshold levels: critical or warning. A value that crosses a warning threshold appears yellow, and a critical threshold appears red.
If thresholds are set too low, you'll receive frequent alerts. If set too high, problems can occur without your knowledge.
You can customize thresholds by setting a static value or letting the Orion Platform calculate baseline values.
- Static threshold. A constant value set for your threshold. For example, the warning threshold for response time might be 500 ms, and the critical value might be 1000 ms. You should be familiar with the performance of that object to know what a reasonable value for a static threshold is.
- Dynamic baseline threshold. Data is collected for a week, and then used to calculate mean and standard deviation. The warning and critical threshold values are defined as 2 and 3 standard deviations above the mean, respectively. For example, if the mean value for packet loss for a specific node is 0%, the warning threshold for packet loss would be 3% (+2 standard deviations) and the critical threshold would be 4% (+3 standard deviations). Dynamic baseline thresholds are the most accurate way to define thresholds, and can be recalculated on demand.
To learn more about thresholds, see:
- Manage thresholds in SAM (SAM Administrator Guide)
- Thresholds in the Orion Platform (Orion Platform Administrator Guide)
- Baseline thresholds (THWACK)
- Use MIN/MAX Average Statistic charts to set thresholds based on 95th percentile data for component monitors (SolarWinds Success Center)