Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Server & Application Monitor (SAM) > Server & Application Monitor (SAM) Getting Started Guide > Thresholds > How thresholds work

How thresholds work

Table of contents
No headers

Alerts are triggered when a monitored value exceeds a threshold. Orion comes with predefined static thresholds for most statistics, but you can override these thresholds and customize them on a per-object basis.

Orion provides two threshold levels: critical and warning. A value that crosses a warning threshold appears yellow, and a critical threshold appears red.

If you want to change the predefined value for a threshold, you use a static threshold or a dynamic baseline threshold.

  • Static threshold. a constant value that you 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 for a statistic are 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 for a specific device.

Baselines are calculated once, after data has been collected for a week. You can recalculate baselines on demand.

Last modified
16:28, 8 May 2017