New Relic AIOps Incident Intelligence Product Evolution:

Incident Intelligence is evolving.

We are introducing a new product menu to streamline the journey of detection and incident response.

Note that all new features are extending the legacy classic features and products (e.g. Alerts, Proactive Detection, Incident intelligence and Incident Workflows (Beta)).

The configuration and menu items of legacy products are still available, and can be found by the following mapping:

  • Alert Policies - is now under DETECT
  • Alert Events, Incidents, Notification Channels - is at the bottom of the menu under ALERTS (Classic)
  • Alert Muting Rules - is under ENRICH & NOTIFY
  • Proactive detection configuration - is under DETECT

Let’s Align on Terminology

Exciting and long-expected features are coming:

Intelligent Correlation:

Group your incidents together before notifications are sent to reduce noise and increase context. Rather than receiving many separate notifications about the same issue, receive one more actionable message by connecting your alert policies to Decisions for intelligent event correlation.

Decisions come ready to work with out of the box logic to reduce noise, and you can create your own in using our flexible Decision builder, by using the Correlation Assistant or by reviewing and activating Suggested Decisions that are generated from patterns automatically observed in your data.

Learn more about using Decisions here


The new Workflows allow one to filter and tunnel the relevant issues to the right destination. A great example of filtering is the ability to get notified on WARNING incidents.

Enrichment allows for adding more data layers to any notification. Want to attach a sum of errors related to an issue based on an NRQL query? Now you can.

We know that each organization and sometimes each team is different. Workflows allows you to customize the notification message to best meet your needs and leverage the power of data from New Relic. Test your workflow configuration using real data and receive a real formatted notification at your destination/s

New destination capabilities:

The new notification platform (not replacing the old notification channels, which are available as before) supports:

  • Flexible Webhook configuration
  • 2-way customizable integration with JIRA
  • 2-way customizable integration with ServiceNow’s ITSM
  • Slack integration

What to expect next?

  • Correlations: Topology based correlation to help your correlation setup

  • New destinations on the new notification platform:

    • Email
    • PagerDuty
    • AWS EventBridge
    • MS Teams
    • And more
  • Workflows:

    • Configure triggering event. Decide if you want to get notified for every event or just a specific set of events (e.g. notify me only on issue creation).
    • Conditional filters
    • Dynamic filters
    • And more

And of course our small disclaimer: The planned features may vary based on user type and product rollout schedule.


… And is called “Anomaly Detection”

How can I send incident data to destination aws eventbridge as in this doc link

What are all the alerting sources that I can integrate OOTB?

Hi there, this is a deprecated product (Connect).
You can send data to AWS EventBridge through a webhook.
We are working on a new dedicated EventBridge integration that should be available in early 2022, and perhaps before

1 Like

New Relic Detection (Alerts and Anomalies)

Hi @sbrenner ,

You said “You can send data to AWS EventBridge through a webhook”.

My questions are :

  1. Do we need to make any pre-configuration of our AWS account / IAM role to allow New Relic to send data to our EventBridge ?

  2. The doc in shows a sample webhook setting of :



“type”: “awseventbridge”,

“endpoint”: “<your eventbridge endpoint>”



What value for “endpoint” should we enter ? The ARN for our EventBridge rule ?

In addition to my questions (posted a few minutes ago), what “Base Url” should I specify for the Webhook if I wanted to send an alert to AWS EventBridge ?

for 1, we are working on templates to the new product to be leveraged to send data to AWS EventBridge through Webhook.
For 2 - this is an old blog, for a deprecated product (Connect)

Do we have an ETA on the Eventbridge destination?

This topic was automatically closed after 365 days. New replies are no longer allowed.