With New Relic Infrastructure, you can create alert conditions directly within the context of what you are currently monitoring with New Relic. For example, if you are monitoring a filter set and notice a problem, you do not need to recreate those criteria from New Relic Alerts.
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 entity within the filter set.
Anyone can view alert notifications tied to your account. Only Owner, Admins, or Add-on Managers can create, modify, or delete conditions.
Create alert conditions in Infrastructure
Alert conditions apply to alert policies. You can select an existing policy or create a new policy with email notifications from the Infrastructure UI. If you want to use other types of notification channels, create a new policy from within the Alerts UI.
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.
To add an Infrastructure alert condition to an Alerts policy:
Go to infrastructure.newrelic.com, then 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.
Go to infrastructure.newrelic.com > Settings > Alerts, then select [bell icon] Create alert condition.
- Type a meaningful condition name.
- Select the Alert type, or refer to the examples to decide which type to select.
Create individual filters, or copy all the filters from a filter set to identify the hosts that you want the alert condition to use.
For more information about the rules behind filters, see Filter set logic.
- 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.
Optional: Set Violation time limit for violations (this defaults to 24 hours).
- Select Create.
Create alert conditions for Infrastructure integrations
To create an alert condition for your Infrastructure integrations, use any of these options:
|UI options||Alert conditions for Infrastructure integrations|
Go to alerts.newrelic.com > Alert policies > New alert policy > Create new condition, then select Infrastructure as the product.
Go to alerts.newrelic.com > Alert policies > (select a policy), then select Add a condition.
Go to infrastructure.newrelic.com > Integrations, then select [bell icon] Create alert for any integration.
Go to insights.newrelic.com > (select an integration's dashboard). Then, beneath the integration's description, select Create alert.
Then continue with the procedures to add an alert condition to Infrastructure.
View host alert events
Anyone included in the policy's notification channels receive alert notifications directly. In addition, anyone with permissions for your New Relic account can view Infrastructure alert incidents and individual violations through the user interface.
- Go to infrastructure.newrelic.com > 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 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:
- Go to infrastructure.newrelic.com > 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 Infrastructure|
|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 a violation. Before adding or updating the link, make sure you use a valid URL.
To add, update, or delete an alert condition's runbook URL:
- Select an alert condition, and make changes to the Runbook URL link.
Save the condition.
In order to be saved, the URL must be a valid URL.
Violation time limit for violations
The violation time limit allows you to define a time period after which violations will be force-closed. By default, violation time limit is 24 hours.
To add, update, or remove an alert condition's violation time limit:
- Select an alert condition, and make changes to the violation time limit.
- To remove this limit, deselect the checkbox next to Close open violations after and select
- Save the condition.
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 condition 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.
To solve this problem, reduce the number of elements you are using in your alert condition. For example:
For more information, see Best practices for filtering in Infrastructure alerts in New Relic's Explorers Hub.