With the migration of Alerts’ notification-channels, we wanted to provide a quick review of the terminology and features users can use in New Relic Alerts and AI.
- A Destination contains unique identifiers and credentials used to create a connection to third-party notification systems. A destination contains the location where the notifications will be sent. Destinations are reusable and can be used across New Relic products.
- A Channel is a configuration object containing all the information required to send a notification event. “Destination” and “Properties” are the main building blocks of a Channel. A Channel enables users to customize their notification event data before it’s sent to your third-party destination.
- In a Workflow you can create triggers (filters) do decide when the workflow will run, can add “enrichments” (data that will be fetched from NRDB and appear in the outgoing events), and can create channels.
From the API perspective, this is the high level overview: Workflows => Channel id(s) => Destination
Why are there 3 different configurations?
We have separated configurations to configure a customized notification so we can provide connection details/ to authenticate once (Destination), but create many customized templates for your outgoing events, and connect these with the destination.
The Notifications API and configuration objects are product agnostic. Workflows is one of 3 products that use the Notifications API to send notifications events / integrate with third parties, along with ‘Error Inbox’ and others. Having a unified platform for notifications, you can, for example, set a single Slack or Jira destinations, and use them both in a Workflow and Error-Inbox configuration