New Relic currently has two alerting systems: the legacy alerting system and New Relic Alerts. Unlike legacy alerting, New Relic Alerts allows you to catch problems faster with a single integrated solution.
By converting from legacy alerts to New Relic Alerts, you can take advantage of features like conditions for NRQL queries, dynamic baseline conditions, and advanced Java alerts and dynamic targeting for APM apps. If you have a paid subscription to any New Relic product, that account will get access to New Relic Alerts from all its other New Relic products, paid and unpaid.
If your account uses the legacy alerting system, you access your alerts directly from the APM, Browser, Plugins, Mobile or Servers UI. With New Relic Alerts, you can monitor all of your events and incidents together from alerts.newrelic.com.
Switch to New Relic Alerts
Owner or Admins
Configuration options change when you opt in to New Relic Alerts. Any alert policy configurations you have already set up will not migrate automatically.
To fully remove legacy alerting from your New Relic account:
- Create new policies and conditions in New Relic Alerts that mimic your existing policies. Refer to your legacy alerts policies and create corresponding policies to ensure that you will receive the same notifications for your existing policies. To optimally structure your alert policies, see Best practices for alert policies.
- Once the new policies and conditions have been created, as an account Administrator, go to alerts.newrelic.com > Switch to New Relic Alerts, then confirm.
Differences with New Relic Alerts
To ensure all your needs are met after switching to New Relic Alerts, see the following features that correspond to legacy alerting features:
|Legacy alerting||New Relic Alerts|
|Legacy alerts API and RSS events feed||Utilize the New Relic Alerts API. Once you have transitioned to New Relic Alerts, the legacy alerting API and RSS events feed will cease reporting data.|
|Notification levels||Specify incident preferences to influence how violations are grouped into an incident, and when notifications are sent based on those groupings.|
|Availability monitoring notifications||Re-create your availability monitoring settings with Synthetics ping monitors, and receive an alert notification whenever a monitor fails.|
|Notification groups||Rather than grouping notification channels, tailor notifications to fit your organization's needs with enhanced policies.|
|Host not reporting notifications||To send a notification when a host is unable to send metrics to New Relic, create a host not reporting condition with New Relic Infrastructure.|
|Multiple default policies||Rather than creating multiple default policies with basic alerting coverage, gain enhanced policy control with dynamic targeting. With dynamic targeting, you can leverage labels to target APM applications, and filter sets to target Infrastructure hosts.|
|Availability monitoring IP addresses||If you whitelisted availability monitoring IP addresses with legacy alerting, see the Synthetics public minion IPs for the accepted IP address list with New Relic Alerts.|
New Relic Alerts features
New Relic Alerts monitors several key features that legacy alerting is not capable of monitoring.
|Capabilities||Legacy Alerting||New Relic Alerts|
|Number of APIs||5||30|
|Number of notification channels||5||10|
|Number of alertable metrics||8||1,000+|
|Automatic policy association||Default policies||Dynamic targeting|
|Host not reporting||check||check|
|Centralized UI across products||check|
|Alert policies with any entity types (including Synthetics, Plugins, Browser, and Mobile)||check|
|Baselines metric conditions||check|