When you create a condition, you set personalized thresholds that determine what will open an incident. This document explains what thresholds are and how to set them.
What is a threshold?
For a condition, thresholds are the settings that determine what opens an incident. Depending on a policy's issue creation preference, and any workflows you may have configured, an incident may result in:
The creation of an issue
Notifications being sent
There are two types of thresholds:
Static: One value set by you.
Anomaly: An anomaly threshold uses past data to dynamically predict the data's near-future behavior. This will adjust over time as it learns the patterns of your data.
Examples of thresholds:
An application's average web response time is greater than 5 seconds for 15 minutes.
An application's error rate per minute hits 10% or higher at least once in an hour.
An application's AJAX response time deviates a certain amount from its expected behavior.
Besides a critical threshold level, you can also set thresholds for a less serious warning level.
You can set thresholds for two levels: critical and warning. At least one threshold must be set.
Threshold level
Details
Critical (red)
Optional. It will open a critical priority level incident and send notifications depending on the policy's issue creation preference setting and any workflow you may have configured. Lost signal thresholds, when triggered, also open critical priority level incidents. See below for more details.
Warning (yellow)
Optional. It will open a high priority leve incident and may send notifications depending on the policy's issue creation preference setting and any workflow you may have configured. Use a warning threshold if you want to monitor when a system behavior is concerning or noteworthy but not important enough to require a critical-level threshold.
A loss of signal is a period of time when no data is received by New Relic. This could be the result of an entity or service going offline, a problem with an agent or collector, or networking problems in a data center or the internet. You can use loss of signal detection to create a new incident when a signal stops unexpectedly. You may also want to use this to determine when an ephemeral service stops and set the action to close any open incidents that exist for this condition. Another option in the loss of signal settings is to skip opening an incident when a signal is expected to terminate. See the loss of signal documentation for more information.
Different condition types have different minimum time intervals. For example, some condition types have a minimum time interval of 5 minutes (for example, metric alert conditions), and others have a minimum time interval of 1 minute (for example, NRQL alert conditions). The same happens with the maximum time interval, where the amount is 120 minutes.
