When you create a condition, you set thresholds that determine what will open a violation. This document explains what thresholds are and how to set them.
- The creation of an incident.
- Notifications being sent.
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 baseline behavior.
Besides a mandatory critical threshold level, you can also set thresholds for a less serious warning level, which doesn't generate an incident or send a notification.
Thresholds are set during the process of creating a condition:
Set thresholds for a new condition
Set thresholds as part of the process of creating a condition.
View and update thresholds for existing conditions
To view a condition’s thresholds: find that condition in the UI. To update thresholds, select a condition’s thresholds and make changes.
To learn more about specific alert condition types (like baseline and NRQL), see Types of conditions.
Details about other functionality and rules:
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.