Instead, you can immediately select your filter set, and tailor the alert condition directly from the chart you are viewing. This helps you proactively manage and monitor the alerting system for your environment. Any alert violations will be created per host within the filter set.
Anyone can view alerts tied to your New Relic Infrastructure account. Only Owner, Admins, or Add-on Managers can create, modify, or delete conditions.
Create alert conditions in New Relic Infrastructure
To add a New Relic Infrastructure alert condition to a New Relic Alerts policy:
From infrastructure.newrelic.com, select any of these Infrastructure pages: Hosts, Processes, Network, or Storage. Mouse over the chart you want to alert on, select the ellipses [ellipses icon] icon, and then select Create alert.
From infrastructure.newrelic.com, select Settings > Alerts, then select [bell icon] Create alert condition.
- Type a meaningful condition name.
- Select the Alert type, or refer to the examples for additional help with which type to select.
- Apply filter sets to identify the set of hosts (and any additional options for interfaces, processes, etc. as applicable) that you want the alert condition to apply to.
For best results, use attributes or partial strings to filter on hosts. Manually selecting hosts is not advised. For more about this, see Alert condition query limitations.
- Define the Critical (required) and Warning (optional, if available) thresholds for triggering the alert notification.
- Optional: To create the condition criteria proactively but not receive alert notifications at this time, turn off the Enabled checkbox option.
Select an existing policy for the new condition.
Select the option to create a new policy and identify the email for alert notifications.
Optional: Add a runbook url.
- Select Create.
Alert conditions apply to alert policies. You can select an existing policy or create a new policy with email notifications from the New Relic Infrastructure UI. If you want to use other types of notification channels, create a New Relic Alerts policy.
The Infrastructure REST API has a limit of 3,700 alert conditions, including both active and disabled conditions. The API, whether used directly or via the UI, will reject all requests to add any additional alert conditions beyond the 3,700 alert condition limit.
Create alert conditions for Infrastructure integrations
To create an alert condition for your New Relic Infrastructure integrations, use any one of these options:
- From New Relic Alerts: Select Alert policies > New alert policy > Create new condition and select Infrastructure as the product. You can also do this by clicking on a pre-existing policy and selecting Add a condition.
- From New Relic Infrastructure: Select the Integrations page, then select [bell icon] Create alert for any integration.
- From New Relic Insights: To create an alert condition while viewing your integration data on your dashboard, select Create alert beneath the integration description.
Then continue with the procedures to add an alert condition to Infrastructure.
View host alert events
Anyone included in the policy's notification channel receives alert notifications directly. In addition, anyone with permissions for your New Relic account can view New Relic Infrastructure alert incidents and individual violations through the user interface.
- From infrastructure.newrelic.com, select Events.
- To change the hosts or time frame, use the search window, Filter set, or Time functions.
- From the Events list, select the alert violation.
- To view detailed information in New Relic Alerts about the selected violation, select the link.
Update or delete host alert information
Owner, Admins, or add-on managers
To edit, disable (or re-enable), or delete host alert information:
- From infrastructure.newrelic.com, select Settings > Alerts.
- Optional: Use the search window or Select all checkbox to locate one or more alert conditions.
- Select any of the available functions to [pencil icon] edit, disable, enable, or [trash can icon] delete the selected conditions.
Use New Relic Alerts to monitor your entire infrastructure
New Relic Alerts provides a single, coordinated alerting tool across all of your New Relic products. This allows you to manage alert policies and conditions that focus on the metrics for entities that you care about the most, such as Docker containers, JVMs, and more.
|Alert features||Features in New Relic Infrastructure|
|Alert policy conditions|
|Information on alerts|
View, add, change, disable, or delete:
Add host conditions to an existing policy: Use the Infrastructure UI.
To view, add, change, or delete available notification options:
Add or edit a runbook URL
The alert condition creation process includes an option for setting a URL for runbook instructions. This lets you link to information or standard procedures for handling an alert condition violation.
To add, update, or delete an alert condition's runbook URL:
- Select an alert condition and make changes to the runbook URL.
Save the condition. In order to be saved, the URL must be a valid URL.
Alert conditions that generate too-long NRQL queries
Alert conditions created in Infrastructure rely on behind-the-scenes NRQL queries, and NRQL queries have a 4096-character limit. This means that if your alert generates a very complex NRQL query that filters on many elements (for example, including many hosts, or many tags), it will exceed this limit and display an error message saying that the condition failed.
The solution to this problem is to reduce the number of elements you are using in your alert condition. For example, if you entered a large number of hosts that caused the condition to fail, you could reduce the number of hosts. Other solutions include:
- Reform your alert condition to target specific attributes that apply to the entities you're trying to target.
- Create custom attributes for the entities you want to target, and use those attributes in your alert condition.
- Use substrings to target hosts. For example: instead of targeting
prod-host-03, just target all hosts with
prod-host-0in the name.
For more about this issue, see Best practices for filtering in Infrastructure alerts on the Explorer's Hub.