--- name: monitoring-notifications title: Working with notification channels description: Configure notification channels to be notified when an alert is triggered. You manage notification channels through the *Settings* panel in the web UI. last-updated: 2025-02-27 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/monitoring?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Working with notification channels {: #notifications} Configure notification channels to be notified when an alert is triggered. You manage notification channels through the *Settings* panel in the web UI. {: shortdesc} ## Configuring a notification channel {: #notifications_create} Complete the following steps to add a notification channel: 1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch). 2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 3. Select **Notification Channels**. 4. Click **Add Notification Channel**. 5. Configure a notification channel: 1. Select the type of notification, for example, `Webhook`. 2. Enter the name of the channel. 3. Enable the *Notify when Resolved* condition to receive a notification when the alert is manually resolved by a user. 4. Enable the *Notify when Acknowledged* field to receive a notification when the alert is manually acknowledged by the user. 5. Configure the notification according to the selected notification type: * For an **Email** notification channel, add the list of recipients, separated by commas. * For a **Slack** notification channel, add the URL of the *Slack channel*. * For a **Webhook** notification channel, add the *Webhook URL*. **Note:** When an alert is triggered, the notification is sent as a POST in JSON format to your webhook endpoint. For more information, see [Configuring a Webhook channel](https://docs.sysdig.com/en/configure-a-webhook-channel.html){: external}. For example, IBM Cloud Monitoringcan be integrated with ServiceNow using a custom webhook. To learn about configuring IBM Cloud Monitoring with ServiceNow, see [Configure ServiceNow](https://docs.sysdig.com/en/configure-servicenow.html){: external}. * For a **VictorOps** notification channel, add the *API Key* and the *Routing Key*. * For an **OpsGenie** notification channel, add the *OpsGenie API key*. Notice that you must configure in OpsGenie the integration with IBM Cloud Monitoring. For more information, see [Add IBM Cloud Monitoring Integration in Opsgenie](https://docs.opsgenie.com/v1.0/docs/sysdig-cloud-integration){: external}. * For a **Microsoft Teams** notification channel, add the *Microsoft Teams* URL. * For a **PagerDuty** notification channel, first you must authorize IBM Cloud Monitoring to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Monitoring opens. Click either **Authorize Integration** or **Sign In Using Your Identity Provider** to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Monitoring notifications, then click **Finish Integration**. Select the escalation policy to use for IBM Cloud Monitoring incidents. Then, on the *Notifications* tab, confirm your PagerDuty account, your service name, and the service key. For more information, see [Add IBM Cloud Monitoring Integration in PagerDuty](https://docs.sysdig.com/en/docs/administration/administration-settings/notifications-management/set-up-notification-channels/pagerduty-notifications/){: external}. To retrieve the required permissions automatically by clicking **Auto-fetch**, first you must authorize IBM Cloud Monitoring to integrate with your account. When you select PagerDuty, a wizard to configure the integration with IBM Cloud Monitoring opens. Click either **Sign in** or **Sign In Using Your Identity Provider** to authorize PagerDuty. Choose an existing service or set up a new service for IBM Cloud Monitoring notifications, then click **Finish Integration**. Select the escalation policy to use for IBM Cloud Monitoring incidents. Then, on the *Notifications* tab, confirm your PagerDuty *Account*, *Service Key*, and *Service Name*. * For a **Teams Email** notification channel, select the name of the team to receive notifications. * For an **IBM Event Notifications** channel you must first have an [IBM Cloud Event Notifications instance configured.](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-getting-started&format=markdown) To configure the notification channel you need to specify the IBM Cloud Event Notifications instance name and specify your choice of a channel name. You will also indicate if the notification channel is enabled and when notifications should be sent, for example, when an alert is resolved. Notifications can be shared with one or all teams. Your IBM Cloud Monitoring instances can send events to IBM Cloud Event Notifications instances in the same accoount and in other accounts. [IBM Cloud Event Notifications is available in a limited number of regions](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-regions-endpoints&format=markdown). {: important} 6. Optionally, and for integrations that allow a test, enable the *Test notification* condition to receive a test notification. If you do not receive a test notification in 10 minutes, review your channel configuration. 6. Click **Save**. ## Modifying a notification channel {: #notifications_update} Complete the following steps to modify a notification channel: 1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch). 2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 3. Select **Notification Channels**. 4. Click the channel you want to edit. 5. After you make changes, click **Save**. ## Testing a notification channel {: #notifications_test} Complete the following steps to test a notification channel: 1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch). 2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 3. Select **Notification Channels**. 4. Click the channel you want to edit. 5. Enable the **Test notification** option. 6. After you make changes, click **Save**. ## Disabling a notification channel {: #notifications_disable} Complete the following steps to temporarily disable a notification channel: 1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch). 2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 3. Select **Notification Channels**. 4. For the channel you want to disable, toggle **Enabled** for the channel so it is disabled. Alerts are temporarily disabled and notifications muted. ## Deleting a notification channel {: #notifications_delete} Complete the following steps to delete a notification channel: 1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch). 2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 3. Select **Notification Channels**. 4. Identify the target channel that you want to modify and the **Actions** icon ![Actions icon](../../icons/action-menu-icon.svg "Actions"). 5. Click **Delete Channel**. 6. Confirm the deletion of the channel by clicking **Yes, delete**.