A condition describes a monitored data source and the behavior of that data source that will be considered an incident. This document will explain the types of conditions available, how to create a condition, and how to view existing conditions.
- Basic concepts and workflow
- Min/max limits (like maximum number of conditions per policy)
- REST API to list or edit alert settings
- NRQL Condition NerdGraph API to manage your NRQL conditions via NerdGraph.
If you haven't already, create your free New Relic account below to start monitoring your data today.
To create a condition:
Create a policy and you will automatically be prompted to add a condition.
From an existing policy page, select Create/add a condition.
Follow the prompts in the UI, which include:
Optional: After you finish creating a condition, copy it and add it to other policies.
Conditions that provide fields for you to input numerical values accept decimal points up to the second decimal place (hundredths). For example,
0.01 is the smallest possible value.
Here are descriptions of the different types of conditions:
You can open incidents and send notifications for response times. However, Apdex scores are almost always more meaningful and provide a better reflection of application performance. For example, average response times can be skewed by outliers, while the Apdex score gives a more accurate assessment of acceptable response time rates that your users experience.
If you want to change the default condition name, make it short and descriptive. Provide useful information for notification messages that have limited characters, such as email subject lines, online chat, etc.
- Use camel case or dotted decimal notation.
- Describe the essence of what is being breached.
To change an existing condition's name:
- Go to one.newrelic.com > All capabilities > Alerts & AI > Alert conditions > (select a condition).
- Click the ellipses menu (...) and click Edit to edit it, and then type a meaningful name for the condition.
You can't edit the product and condition type associated with a condition. Instead, you must delete the condition and create a new one with a different product and condition type.
After you save the condition, the currently selected policy lists all alert conditions that apply to it. From here you can:
- Repeat the steps to add more conditions to the policy.
- Continue the policy setup process by connecting a workflow to it.
- Change the condition's name, the entities it's scoped to, or the critical (red) and warning (yellow) thresholds.
- Copy the condition and add it other policies in the selected account.
- Rename the policy.
- Disable any conditions in the policy, or delete the policy or any of its conditions.
You may also manage your policies via the policies NerdGraph API.
The policies index lists them in alphabetical order. To view or search for existing conditions:
- Go to one.newrelic.com > All capabilities > Alerts & AI > Alert conditions (policies).
- Use the search box, sort any column, or scroll the list, then select a policy's name to see its conditions.
To view policy and condition information for a specific entity: From that entity's product UI, select Settings, then click Alert conditions.