Transition from legacy alerting to New Relic Alerts

Legacy alerting reached end of life on May 15, 2018. You will no longer receive alert notifications from the legacy alerting system. You must transition to New Relic Alerts in order to continue using alert features.

The enhanced differences with New Relic Alerts allow you to prevent or catch problems faster with a single integrated solution. By converting from legacy alerts to New Relic Alerts, you can take advantage of features such as:

If you have a paid subscription to any New Relic product, that account will have access to New Relic Alerts for all products, paid and unpaid.

Legacy alerting end-of-life (EOL)

On May 15, 2018, legacy alerting reached end of life, and New Relic customers no longer have access to the legacy alerting UI and APIs. In addition, all evaluation of policies and conditions has stopped.

To continue receiving alerts from New Relic, follow the transition procedures to switch to New Relic Alerts. For more information:

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. In addition, the REST APIs for legacy alerting will no longer be available after you switch to New Relic Alerts. For more information, see New Relic's Explorers Hub about using the REST API.

To fully remove legacy alerting from your New Relic account, complete these steps before May 15, 2018:

  1. Use the legacy REST APIs as needed to gather information about your legacy policies, conditions, notification channels, affected users, etc.
  2. 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.
  3. Once the new policies and conditions have been created, as an account Administrator, go to > Switch to New Relic Alerts, then confirm.

If you did not complete these transition procedures before May 15, 2018, contact Support at

Differences with New Relic Alerts

To ensure all your alerting needs are met after switching to New Relic Alerts, review these features, which correspond to legacy alerting features:

Legacy alerting New Relic Alerts
Legacy alerts API and RSS events feed Use 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.
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 notifications To access information about your legacy availability monitoring settings, use New Relic APM's Availability report page. Re-create your availability monitoring settings with Synthetics ping monitors, and receive an alert notification whenever a monitor fails.
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
Alert policies check icon check icon
Host not reporting check icon check icon
Centralized UI across products check icon
Alert policies with any entity types (including Synthetics, Plugins, Browser, and Mobile) check icon
NRQL alerts check icon
Baseline metric conditions check icon

For more help

If you have questions or comments, visit New Relic’s Explorers Hub transition page, or contact Support at

Recommendations for learning more: