Notification channels: Control where to send alerts

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.

Create channels

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 New Relic Alerts user interface. You can also use custom payload webhooks to control how the alert is delivered.

Alerts_Notification_Channels_Index.png
Alerts > Notification channels: The Notification channels index lists existing notification channels. From here you can create and test new notification channels, search for and sort existing channels, update and add policies to them, or delete channels.

To create a notification channel in New Relic Alerts:

  1. From alerts.newrelic.com, select Notification channels.
  2. Select New notification channel.
  3. From Channel details, select the type of channel.
  4. Enter the required information for your selected channel type.
  5. Select Create channel.
  6. Optional: Select Envelope Message Icon Send a test notification.
  7. 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.

Alerts v3: Notification channels
Alerts > Notification channels: After you create a new channel, you can test it or add alert policies to it.

Instructions for specific notification channels

New Relic Alerts supports these types of destinations as notification channels for alerts. New Relic's user interface also lists the available notification channel types.

User

For your convenience, New Relic Alerts automatically loads all users and their email addresses for the selected account. If your New Relic 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.

Email

New Relic Alerts automatically adds 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 New Relic account. For example, if you have a dev-ops@company.com 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 New Relic account. These email addresses can be the same as or different from New Relic account email addresses.

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.
HipChat Cloud

Before adding HipChat notifications to New Relic, you must have an existing HipChat Cloud account 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 Hipchat Room name is 123456, you could identify the Channel name as Network Ops Center HipChat.
v1 Admin token (required) Code that grants New Relic Alerts access to your HipChat Cloud account. You can either use an admin token with access methods to all API methods, or you can use a notification token that has permissions to the target room. The admin token must be from the v1 API.
Room name (required) The name of the HipChat room where New Relic Alerts sends the alert notifications.
OpsGenie

You must have an existing OpsGenie account integrated with New Relic in order to provide the following information to New Relic Alerts:

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 Hours setting for urgent alerts, add an OverwriteQuietHours tag.

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.
PagerDuty

You must have an existing PagerDuty account in order to provide the following information to New Relic Alerts:

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.
Slack

Before adding Slack notifications to New Relic Alerts, 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.
URL (required)

Copy and paste your New Relic webhook integration URL that you have previously set up with Slack. For example:

https://hooks.slack.com/services/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

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.
VictorOps

You must have an existing VictorOps account in order to provide the following required information to New Relic Alerts:

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.
Webhook

Webhooks are HTTP POST messages containing JSON documents delivered to a destination URL. When an incident is opened, acknowledged, or closed, New Relic's 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 in New Relic Alerts, 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.

Payload

(for custom payloads only)

Your customized POST message code. This field includes:

  • A list of New Relic Alerts variables you can use
  • Syntax highlighting, based on payload type

Payload type

(for custom payloads only)

Specify the message format: JSON (default) or Form.
xMatters

You must have an existing xMatters account in order to provide the following information to New Relic Alerts:

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.
Campfire

Before adding Campfire notifications to New Relic, 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 newrelic:

http://newrelic.campfirenow.com/room/123
Token (required) Code that authenticates New Relic Alerts to your Campfire account.
Room (required) The name of the room where you want New Relic Alerts 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:

  1. Log in to your New Relic account via the mobile app at least once to ensure the device is registered.
  2. Add the user channel to the alert policy.
  3. Switch push notifications On for the device.
screen-user-notification-channel.png
alerts.newrelic.com > Alert policies > (selected policy) > Notification channels > Add notification channels > User: To receive push notifications on your mobile device, select your username from the list.

Acknowledge alert notifications

Anyone in your account can acknowledge alert notifications through the New Relic Alerts user interface or through their email notification. The ability to acknowledge alert notifications from other channels (ack back) is a planned enhancement for a future release.

Add your company's notification product

To request your company's product to be added to the supported channels for New Relic Alerts, fill out New Relic's new partner application.

For more help

Recommendations for learning more: