Manage notification destinations

A notification destination determines where an alert is sent once it’s triggered. Cloud Observability has built-in capability to set the following integrations destinations:

If you want alerts sent to a different app, you can use Webhooks. Cloud Observability offers several templates for popular destinations to get you started.

Once you create a notification destination, you can test it by sending a test alert.

You can also create and manage notification destinations using our Public API.

Create a ServiceNow notification destination

Centralize and manage your alerts with the ServiceNow Event Management application.

To complete the steps below, you need your ServiceNow URL and basic authentication credentials.

To create a ServiceNow destination:

  1. In Cloud Observability, click Alerts > Notification destinations.
  2. Next, click Create a destination > ServiceNow.
  3. Fill out the form in the dialog:
    • Name - The notification destination name you’ll see in Cloud Observability.
    • URL - The URL for your ServiceNow instance.
    • Username - Your ServiceNow username.
    • Password - Your ServiceNow password.
  4. Click Save to activate the notification destination and return to the Alerts page. Cloud Observability displays <Name> destination saved successfully.

To verify your ServiceNow notification destination, test it in Cloud Observability.

Create a PagerDuty notification destination

PagerDuty alerts create a new incident in PagerDuty, and the resolution of the alert in Cloud Observability resolves the PagerDuty incident.

To create a PagerDuty destination:

  1. From the navigation bar, click Alerts.
    The Alerts view shows a list of all current alerts.

  2. Click the Notification destinations tab, click Create a destination and choose PagerDuty.

    You’re redirected to PagerDuty. PagerDuty asks you to authorize Cloud Observability to trigger, acknowledge, and resolve incidents.

  3. Enter your credentials and click Authorize Integration. Select an existing service with a Cloud Observability integration or create a new PagerDuty service with an integration. Follow the prompts to configure PagerDuty.

Once configured in PagerDuty, the PagerDuty service is listed as a destination in Cloud Observability.

You can test that destination is correctly configured by sending a test alert.

Create a Slack notification destination

When you define Slack as a destination, the alert is sent to a specific channel or person in a Slack workspace. If you want all your workspace’s Slack channels to be enabled for destinations, then you can integrate Slack to provide that authorization.

The Slack message shows information about the alert with links back into Cloud Observability to begin your investigation. Alerts when the threshold is violated and notification resolutions are sent to the Slack channel.

You can also customize the Slack payload using the webhook template.

You must have Admin privileges for your Slack workspace to create a Slack destination.

To create a Slack notification destination:

  1. From the navigation bar, click Alerts.
    The Alerts view shows a list of all current alerts.

  2. Click the Notification destinations tab, click Create a destination and choose Slack.

    You’re redirected to Slack. Slack asks you to sign into the workspace you want to post the alert to.

  3. Enter your workspace name and click Continue.

    An authorization page displays asking to authorize Cloud Observability to post to your Slack Workspace.

  4. Select the channel that should receive the alert and click Install.

The channel is added as a notification destination. You can test that your destination is correctly configured by sending a test alert.

Add a Slack workspace integration

If you are using the Public API to create a notification destination, or you want to send Cloud Observability alerts to multiple Slack channels in your workspace without creating a destination per channel, you must first enable the Slack workspace integration.

To integrate your Slack workspace:

  1. In Cloud Observability, in the left-hand navigation bar, click Account Management and choose Slack integration.
  2. Scroll to the Slack integration table. In the Send alerts and warnings to Slack, click the Enable Slack button.

Be sure to select the first integration in the table. The second integration allows you to display previews when sharing Cloud Observability links in Slack.

To remove the integration, click the Revoke button.

Create a BigPanda notification destination

Alerts with a BigPanda destination result in a new incident in BigPanda. When the alert is resolved, the incident is moved to the Resolved folder in BigPanda.

To create a BigPanda destination, you’ll need a BigPanda Bearer token and App key, generated from the Integrations tab in BigPanda.

To generate the BigPanda App key and Bearer token:

  1. In BigPanda, click the Integrations tab and click New Integration. Add integration in BigPanda

  2. On the Create a New Integration page, choose REST API. REST API integration

  3. For Step 1, enter a name for the integration and click Generate App Key. Generate App key

Your App key and Bearer token are generated. You’ll need these to configure the destination in Cloud Observability. App ken and Bearer token

To create a BigPanda destination:

  1. In Cloud Observability, from the navigation bar, click Alerts.
    The Alerts view shows a list of all current alerts.

  2. Click the Notification destinations tab, click Create a destination and choose BigPanda.

  3. Enter a name for the destination and paste in the Bearer token and App key. You can add optional header content if needed. Click Save. Add BigPanda

BigPanda is listed as a destination in Cloud Observability.

You can test that destination is correctly configured by sending a test alert.

Create an Opsgenie notification destination

Alerts with an Opsgenie destination result in a new alert in Opsgenie. Opsgenie alerts are not resolved when the corresponding Cloud Observability alert resolves.

To complete the steps below, you need an Opsgenie API token.

To create an Opsgenie destination:

  1. In Cloud Observability, click Alerts > Notification destinations.
  2. Next, click Create a destination > Opsgenie.
  3. Fill out the form in the dialog:
    • Name - The notification destination name you’ll see in Cloud Observability.
    • URL - The URL for the Opsgenie alert create endpoint. This defaults to the US instance of Opsgenie, but can be configured for the EU instance of Opsgenie if needed.
    • API Key - Your Opsgenie API token.
  4. Click Save to activate the notification destination and return to the Alerts page. Cloud Observability displays <Name> destination saved successfully.

To verify your Opsgenie notification destination, test it in Lightstep.

Test a notification destination

Once you create a notification destination, you can test that it’s configured properly. Cloud Observability sends a test message without any specific alert information.

To test a notification destination:

  1. From the navigation bar, click Alerts and click the Notification destinations tab.

  2. In the list of destinations, click Test for the appropriate destination.

    Cloud Observability sends a test message.

Delete a notification destination

You can delete notification destinations from the Notification destinations tab.

To delete a notification destination:

  1. From the navigation bar, click Monitoring and click the Notification destinations tab.
  2. Click Delete for the appropriate destination.

See also

Create alerts

Create webhook notification destinations

View and manage alerts

Updated Jun 12, 2022