As part of Applied Intelligence, Incident Intelligence helps you correlate your incidents and reduce noise in your environment. It gives you an overview of all your incidents, their sources, and related events.
Before setting up Incident Intelligence, note that the count of incident events is a billing factor.
To enable Incident Intelligence, follow these steps. Afterwards, issues should start to appear in your issue feed.
- 1. Configure your environment (one-time).
- 2. Configure sources.
- 3. Configure destinations.
- 4. Configure pathways.
To set up an environment in Incident Intelligence, you need an administrator to select a New Relic account for it. This account should be the one your team is using.
- Who sets the environment? Only administrators, and only for accounts where they have admin privileges.
- Can administrators set more than one environment? They can set one environment per parent account and its child accounts. More than one can be set if an administrator has privileges for more than one parent account.
Incident Intelligence is a cross-account product. This means you can send in data from any New Relic account or external source to correlate events.
After setting up your environment, determine your incident sources. These are your data inputs.
You can get data from any of the following sources:
Now that you've set up your sources, you can configure your destinations. These are the data outputs where you view your incidents.
Using ServiceNow as a destination enables you to push valuable violation data into new ServiceNow incident tickets.
You can set other destinations:
For examples of destination templates, webhook formats, and JSON schema, see the Incident Intelligence destination examples.
To control when and where you want to receive notifications from your incidents, you can configure pathways.
To add a pathway:
Go to one.newrelic.com, click Alerts & AI, in the left nav under Incident Intelligence click Pathways, then click Add a pathway.
In the query builder box, select an attribute, such as
- This can be from the list of all attributes available in PagerDuty incidents and New Relic alerts violations, or you can add your own attributes.
Select a logical operator. For example,
Enter a specific value to complete the logical expression.
- To include all issues created by your sources, select Send everything. (Use this if you only use one PagerDuty service to manage all incidents.)
- To build more complex logic, use the
Select one or more of your destinations.
To edit or remove existing pathways, mouse over the pathway's name on the Pathways page.
Now that you've set up some sources and destinations for your incidents, read about how to use Incident Intelligence.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.