Alerts and applied intelligence transition guide

Over the course of several months during 2022 and 2023, new functionalities in New Relic One will replace alerting functionalities reaching end of life (EOL). We are providing these early notices so you can plan accordingly and make a smooth transition.

If you have questions or comments about anything in this EOL transition guide, don't hesitate to:

Reach out to your New Relic account representative.
Use the reply thread in our Explorers Hub post.

What's changed

Starting in late 2021, we've reorganized the navigation UI for alerts and applied intelligence. Although the alerts and applied intelligence navigation has changed pretty dramatically, all the features you use are still there.

Instead of grouping things by features, we've reorganized the navigation into categories that clarify your alerts and applied intelligence workflow. For example, the Analyze category is the place where you can go to see all the recent activity for violations, issues, incidents, and anomalies.

We're slowly rolling out this update to all of our users over the next months.

The new UI includes these new categories.

Analyze

Use the analyze features to scan for critical problems affecting your systems, via alerts violations, issues, incidents, and anomalies.

The overview page shows your most recent open, closed, and muted violations.

The Issues & activity page shows your most recent issues, incidents, and anomalies.

Detect

Use the detect features to define the conditions in your system you want to be notified about, as well as configuring how anomalies are detected.

The alert conditions (policies) page lists the policies where your conditions are created and organized. Create new policies here.

The anomaly detection page lists your expanded anomaly detection configurations. An anomaly is a behavioral trend that doesn't match the historical data for your system. You can add or edit the configurations here.

Correlate

Use the correlate features to define your data sources and review and configure the logic grouping your incidents together.

The sources page shows the data input sources you've chosen to analyze and be notified about. You can add new sources or configure existing ones. Sources include New Relic sources, such as alerts conditions and detected anomalies, as well as third-party sources like AWS Cloudwatch Alarms and PagerDuty.

The decisions page shows your correlated incidents. You can review, edit, and add decisions.

Enrich & notify

Use the enrich and notify features to add additional metadata to your notifications, schedule when you don't want to be notified, and configure where your notifications get sent.

Use the muting rules page to temporarily stop your alerts violation notifications.

Use workflows to add more data to your alerts notifications.

Use destinations to configure where your applied intelligence notifications get sent.

Use pathways to configure where your correlated issues get sent.

Use incident workflows to automate common problems and actions related to your alerts policies.

Use incident destinations to add and configure third-party services for your incidents.

Settings

Use the settings page to review and manage your current incident intelligence usage.

Alerts (classic)

Alerts (classic) lets you manage events, incidents, and notification channels with the UI you're used to using.

Use the events and incidents pages to review alerts violations and other events.

Use the channels page for a list of your alerts notification channels and to create new channels.

What's changing

Here is a summary of what we plan to EOL in 2022 and 2023, why this is happening, and what will replace the current experience for alerts and applied intelligence.

Reason for EOL: Outlier conditions don't provide efficient cluster identification and analysis capabilities.

Replacement: Use NRQL baselines to watch for anomalies in your cluster or to group similar signals. This method is an improvement over outlier conditions, since it will alert you to exactly which member of the group is misbehaving. You may be able to meet the same need as your old outlier conditions by using a faceted baseline condition.

Learn more:

Reason for EOL: The current alerting setup process is rigid and cannot be customized. It also requires restrictive policy-based alert conditions that focus on incident creation.

Replacement: Workflows and destinations, a new way to manage issue-driven notifications, will replace current notification channel options. This solution is more flexible, and it enables notifications for all severity levels.

Learn more:

Additional documentation will be provided for the new workflow.
Explorers Hub

Reason for EOL: Currently NRQL alert conditions are one type of alert condition we offer. But our many types of alert conditions have resulted in a complex user experience, and the lack of alignment has prevented advances in detection capabilities.

Replacement: This is being replaced by NRQL alert conditions with increased functionality. You can start preparing for this transition now by using NRQL alert conditions instead of other types.

Learn more:

Additional documentation will be provided.
Explorers Hub

Alerts and applied intelligence transition guide

What's changed

An overview of alerts and applied intelligence navigation changes

Analyze

Detect

Correlate

Enrich & notify

Settings

Alerts (classic)

What's changing

March 2022: NRQL baselines to replace outlier NRQL alert condition types.

2nd half of 2022: Native experience in New Relic One to replace classic incident response workflow.

1st half of 2023: Workflows and destinations to replace notification channels and relationship to policies.

2nd half of 2023: NRQL conditions to replace all non-NRQL alert condition types.