Notification channels: Control where to send alerts
You can use alerts to set up notification channels, and attach those channels to policies. Your selected channels provide fast and consistent ways for the right personnel to be notified about incidents. For example, notifications allow you to include charts about the incident to provide context and share them with your team.
Alerts offers several notification channels, including webhooks, Slack rooms, email, and more. You'll be notified by your notification channels when incidents are opened, acknowledged, or closed. This document explains the available notification channels and how to set them up.
We're replacing notification channels with more powerful workflows. Existing notifications will be automatically migrated to workflows that provide more options, flexibility, and control and you can enrich notifications with additional data.
Learn about workflows
View notification channels
To see all notification channels in your account: Go to one.newrelic.com > Alerts & AI > Channels.
Add or remove notification channels
To set up a new notification channel:
On the Notification channels, click New notification channel.
We automatically add every individual and their email address on the selected account to the User notification channel and you can select them there. You don't need to add existing New Relic accounts to the Email channel.
To add an email channel for other users, follow these guidelines:
In general, use the Email notification channel to identify user emails or email aliases that are not already on the selected account. For example, if you have a firstname.lastname@example.org email alias for your DevOps team, add the email alias to the Email channel. Otherwise, use the User notification channel to select specific users on your DevOps team.
For easier maintenance, add a single non-user email address or alias to a single alert notification channel. If you want to use the email channel for more than one email, create an email group or alias outside your account. These email addresses can be the same as or different from email addresses already on your account.
A meaningful name for the OpsGenie notification channel (maximum 64 characters).
API key (required)
The API key generated from your OpsGenie integration used to authenticate API requests.
List of team names that are responsible for the alert. OpsGenie runs team escalation policies to calculate which users will receive notifications.
A comma-separated list of labels attached to the alert.
To overwrite the OpsGenie Quiet Hours setting for urgent alerts, add an OverwriteQuietHours tag.
One or more names of users, groups, on-call schedules, escalation policies, etc., that OpsGenie uses to calculate where to send notifications.
You must have an existing PagerDuty account in order to provide the following information:
Service name (required)
The name of your service integrating with PagerDuty for notifications.
Integration key (required)
The unique service identifier used by PagerDuty's Integration API to trigger, acknowledge, and resolve incidents for the service.
Before adding Slack notifications, you must create a unique webhook integration using Slack's New Relic integration. If you want web, transaction, server, and mobile alerts to be posted in separate channels, you must set up separate integrations for each one.
Channel name (required)
A meaningful name for the Slack notification channel (maximum 64 characters); for example, Network Ops Center.
Copy and paste the New Relic webhook integration URL that you've set up with Slack. For example:
Be sure to include https:// in the URL. Do not use http://.
Team channel (optional)
If used, include # before the name of the Slack channel where alert notifications are sent; for example, #NOC.
After September 30, 2022, we're discontinuing support for several capabilities, including VictorOps notifications. For more details, including how you can easily prepare for this transition, see our Support Forum post.
You must have an existing VictorOps account in order to provide the following required information:
Channel name (required)
A meaningful name for this notification channel (maximum 64 characters). For example, if the VictorOps Route key is for your Technical Support team, you could name this channel Tech Support - VictorOps.
VictorOps generates a unique key for each account. It maps the VictorOps account to its associated integrations.
Route key (optional)
This key maps the alert or incident to a specific team.
Webhooks are HTTP POST messages containing JSON documents delivered to a destination URL. When an incident is opened, acknowledged, or closed, our webhook feature sends a message to your URL with any relevant information, such as a description of the event and a link back to New Relic. You also have the option to customize the payload in the POST message for further integration into your system.
If your endpoint does not acknowledge the POST request within 10 seconds, the alerts UI may indicate a failed notification event for the related incident.
Before adding webhook notifications, you must have an endpoint set up to respond with a status code between 200 and 206 after receiving the following required information:
Channel name (required)
A meaningful name for the webhook (maximum 64 characters).
Base url (required)
The endpoint that will receive the POST message and trigger customized behaviors in your system.
If you want to include a port number in the webhook URL, make sure the port is available for requests. Otherwise the webhook will not work.
Basic auth (optional)
To require basic authentication for the webhook, select Add basic auth, and provide the user name and password to authenticate the webhook.
Custom headers (optional)
To include headers with webhooks, select Add custom headers, and provide the name and value for each header.
Use custom payload (optional)
To use the default values, leave blank. To view and edit the default values, select Add custom payload.
Specify the message format: JSON (default) or Form.
After September 30, 2022, we're discontinuing support for several capabilities, including xMatters notifications. For more details, including how you can easily prepare for this transition, see our Support Forum post.
You must have an existing xMatters account in order to provide the following information:
Channel name (required)
Name your channel so you can identify it easily when associating it with a policy.
Integration url (required)
The unique integration url provided by xMatters pointing to your xMatters account.
Receive mobile push notifications
In order to receive mobile push notifications, your device must be registered and listed in (account) > User preferences. If the device is not listed in User preferences, log out of the app, log back in, and check again to see if it is listed.
To receive mobile push notifications:
Log in to your New Relic account via the mobile app at least once to ensure the device is registered. If you haven't already, create your free New Relic account below to start monitoring your data today.