The features described here are early access. You won't be able to use these features if you're not part of the early access program.
Destinations are where we send notifications about your New Relic One data. A destination is a unique identifier for a third-party system that you use.
Destination settings contain the connection details to integrate with third-party systems and can be used across a variety of tools in New Relic One.
The supported destination platforms include:
- Atlassian Jira
For more on these and other destinations, see notification integrations.
It's also possible to configure destinations using the
aiNotifications NerdGraph API.
Destination settings require specific capabilities:
- To access your settings: you need
- To modify or delete your settings: you need
- Go to one.newrelic.com, click Alerts & AI, and in the left nav under Enrich and Respond, click Destinations. The destinations table shows information about the existing destinations and allows users to enable, disable, and modify.
- To add a destination, click the appropriate platform tile. To modify destination settings, click the destination row in the destinations table.
one.newrelic.com > Alerts & AI > Destinations.
Destinations have a 'status' value that indicates if we encountered issues while processing and sending events to them (see the destinations table in the above image). Some errors, like Authentication or Authorization issues, require an update to the destination's connection details. After the update, the destination status value will be changed to "Default".
To view past notification events details, go to the Destination menu, and click the Notifications log tab.
Notifications log enable you to view the history and status of all your past notifications. Here you can view the status of any notification along with related error details and destination ticket numbers.
Filter your destination logs by destination type, sent by, and status.