New Relic Alerts gives you the ability to be notified when incidents are opened, acknowledged, or closed. This document explains the available notification channels and how to set them up.
This document is about notifications for New Relic Alerts. For general information about unsubscribing from other New Relic emails, including marketing emails, weekly reports, and announcements, see Unsubscribe from New Relic emails.
Owner, Admins, or add-on managers
You can set up several different channel types and one or more channels for any alert policy from the user interface. You can also use custom payload webhooks to control how the notification is delivered.
To create a notification channel in New Relic Alerts:
- From alerts.newrelic.com, select Notification channels.
- Select New notification channel.
- From Channel details, select the type of channel.
- Enter the required information for your selected channel type.
- Select Create channel.
- Optional: Select Envelope Message Icon Send a test notification.
- Add the notification channel to one or more alert policies.
The Alert policies page includes the option to add notification channels directly to the selected policy.
Instructions for specific notification channels
We support these types of destinations as notification channels for alerts. The user interface also lists the available notification channel types.
For your convenience, we automatically load all users and their email addresses for the selected account. If your account has one or more sub-accounts, the notification channel includes only users for the master account or sub-account you have currently selected.
Use the User notification channel to select existing account team members and admins. To view the Users list or to add users to alert policies: From alerts.newrelic.com, select Alerts > Notification channels > Users.
A user channel also sends push notifications to any of the user's registered mobile devices. A device is registered if the user has logged into New Relic using the mobile app on the device.
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 do not need to add existing account users to the Email channel.
To add an email channel for other users, follow these guidelines:
Field Description Email (required)
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
email@example.com 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.
Users can unsubscribe from general (non-alerts-related) emails, but they cannot unsubscribe from alert email notifications. Instead, the account Owner, Admin, or add-on manager must remove users from the policy's email notification channel.
Include JSON attachment (optional) To include a JSON attachment with the email notification, select this checkbox.
You must have an existing OpsGenie account integrated with New Relic in order to provide the following information:
Field Description Channel name (required) 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. Teams (optional) List of team names that are responsible for the alert. OpsGenie runs team escalation policies to calculate which users will receive notifications. Tags (optional)
A comma-separated list of labels attached to the alert.
To overwrite the OpsGenie
Quiet Hourssetting for urgent alerts, add an
Recipients (optional) One or more names of users, groups, on-call schedules, escalation policies, etc. that OpsGenie uses to calculate where to send alert notifications.
You must have an existing PagerDuty account in order to provide the following information:
Field Description 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 in Slack 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.
Field Description Channel name (required) A meaningful name for the Slack notification channel (maximum 64 characters); for example,
Network Ops Center.
Copy and paste your New Relic webhook integration URL that you have previously set up with Slack. For example:
Be sure to include
https://in the URL. Do not use
Team channel (optional) If used, include
#before the name of the Slack channel where alert notifications are sent; for example,
You must have an existing VictorOps account in order to provide the following required information:
Field Description 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.
Key (required) 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 the specified 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 accept the following required information:
Field Description 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.
(for custom payloads only)
Your customized POST message code. This field includes:
- A list of variables you can use
- Syntax highlighting, based on payload type
(for custom payloads only)
Specify the message format: JSON (default) or Form.
You must have an existing xMatters account in order to provide the following information:
Field Description 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.
Before adding Campfire notifications, you must have an existing Campfire account to provide the following required information:
Field Description Channel name (required) A meaningful name for the Campfire notification channel (maximum 64 characters). Subdomain (required)
This information is company-specific. It appears in your browser's address bar when you log into Campfire and join a chat room. In the following example, the Subdomain is
Token (required) Code that authenticates New Relic Alerts to your Campfire account. Room (required) The name of the room where you want to send notifications.
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.
- Add the user channel to the alert policy.
- Switch push notifications On for the device.
Acknowledge alert notifications
Anyone in your account can acknowledge alert notifications through the user interface or through their email notification.