For Webex Meetings, you can create rules to get alerts for:

• Live meeting monitoring—Use this alert to find out when participants are experiencing media quality issues during meetings that are in progress. You can create up to 10 of these alerts.
• Device live meeting monitoring—Use this alert to find out when devices are experiencing media quality issues during meetings that are in progress. You can create up to 25 of these alerts.
• Historical meeting quality trend—Use this alert to find out when a percentage of participants in specific Webex sites and locations reach the media quality thresholds that are set automatically based on the past performance of meetings within the last seven days. You can create up to 10 of these alerts.
• Historical meeting quality monitoring—Similar to the history meeting quality trend alert, you can use this alert to set your own thresholds on when to receive an alert when a percentage of participants in specific Webex sites and locations reach any of the media quality thresholds. You can create up to 10 of these alerts.

For Webex Calling, you can create rules to get alerts for:

• Calling Insights—Calling insights provide you with high-level data on the quality and engagement of Webex Calling calls from users on a regular frequency, such as the percentage of poor-quality calls and a breakdown of connections used. You can create up to 10 of these alerts.

• Call Quality Drop—Use this alert to find out when the call quality at specific locations or of a user's media session drop to poor quality. You can create up to 10 of these alerts.

• Alerts for UCM Cloud—An alert is set out when there's a maintenance scheduled or an outage for Cisco Emergency Responder, Expressway, IM and Presence, Unified Communications Manager, and Unity Connection. You can create up to 10 of these alerts.

For devices, you can create rules to get alerts for:

• Offline and online events—An event is registered after a device has been offline for 10 minutes or has come back online 10 minutes ago. You can create up to 100 of these alerts.
• Issues that are detected or resolved events—You can select if you want to receive all alerts or mute the ones that you don't wish to receive. You can create up to 100 of these alerts.
• Software version expiry—An alert is sent out 14 days and 3 days before the software version expires for the device. You can create up to 10 of these alerts

See this article for more details on how to set up alerts for devices in your organization.

There are two categories of service alerts for Dedicated Instance: Maintenance alerts and Proactive alerts.

Maintenance alerts

Maintenance alerts are enabled by default. Partner or customer administrators should verify or configure the delivery channel to get notified over email and/or Webex space.

To add delivery channel information to receive maintenance alerts:

1. From the customer view in https://admin.webex.com, go to Alerts center.
2. Select Manage > All rules.
3. Click Calling-Maintenance and Outage Alerts and scroll down to Delivery Channel.
4. Select either or both of the Email or Webex spaces check boxes to receive notification on the preferred channel.

   You can add upto 30 email IDs.

   To receive notification on Webex space, you must have a Messaging license. Bot access is enabled in Apps/bots, you’re permitted to be a member of the organization room. Otherwise, you need to contact your organization administrator for a fix.

   You can select Webhooks if you have Webhooks enabled at the organizational level. For more information, see Enable webhooks for alerts in Control Hub.

   
5. Enter the Email and Webex space information and click Save to save the changes.

Whenever there's a maintenance, Control Hub automatically displays a banner including the details of the cluster, region along with the date and time on which there’s maintenance.

Proactive alerts

Partner or customer administrators can subscribe to day two or day three proactive alerts, event notifications and get the same delivered to either or both of email or spaces in the Webex App by selecting the Delivery Channel while creating the alert.

For example: Unified CM Video Conf Bridge Out of Resource Count High, Unified CM MTP Out of Resource Count High.

To create a proactive alert rule

1. From the customer view in https://admin.webex.com, go to Alerts center.
2. Select Manage > Create rule.
3. In the Summary section:
   1. Select Calling from the Service drop-down list.
   2. Select Alerts for Dedicated Instance from the Type drop-down list.
   3. Select the preferred Severity. By default the severity is High.

      • We recommend that you create rules for proactive alerts with medium or low severity.

      • You receive alerts that meet or exceed the severity you selected while creating the rule.

   4. Add Title for the new rule.
4. All the check boxes in the Rules section are selected by default. Uncheck the ones based on your preferences.
5. Select the Delivery Channel to receive the alert.

   You can select Webhooks if you have Webhooks enabled at the organizational level. For more information, see Enable webhooks for alerts in Control Hub.

6. Click Save.

   Once the rules are created, it takes a maximum of 6 hours to start receiving the notifications.

   

Certificate expiry alert:

An expiry alert is sent to UCM Cloud customers 67 days before the expiration date, and then every week until the certificate is renewed.

• Customer owned and managed certificates - A proactive alert is sent from Control Hub, and you’re responsible for renewing and managing the certificate.
• Cisco owned and managed certificates - A proactive alert is sent from Control Hub, and we’re responsible for renewing and managing the certificate.

Enhanced Survivability alert

When a Control Hub administrator activates the Enhanced Survivability Node, their email ID is automatically added to the "Calling-Enhanced Survivability Alerts" rule. If additional team members wish to receive notifications, their email addresses can be added to the alert rule, and the preferred mode of communication can be selected.

This rule sends alerts related to the Enhanced Survivability Node to the email addresses listed in the alert rule's email section.

Below are the alerts that you will receive:

1. Enhanced Survivability Node Activation Statuses

   1. Completion - Confirmation of successful activation.

   2. Precheck Errors - Notifications of errors requiring action.

   3. Action Required - Alerts for steps needing your intervention to proceed.

   For detailed instructions on the Enhanced Survivability Node Add and Activation, refer.

2. Periodic Health Check of Enhanced Survivability Node

   1. Continuous monitoring of the node's health.
   2. Alerts for issues such as service failures, firewall port changes, or db sync failures.
   3. If an issue is detected, you will be notified with details and you need to resolve it on your end. The periodic health check runs every 6 hours. If no alert is generated after the next check, the issue has been is resolved. If you cannot resolve the failures, raise a TAC support case.

Control Hub application status alarm definitions

For a list of available alarm definitions for Dedicated Instance, see Control Hub application status alarm definitions.

You can set up a webhook callback URL so that alerts show up in third-party applications. The admin can specify a webhook callback URL in Control Hub. After providing a callback URL, you can select the webhook option as an additional delivery channel in the rules for new or existing alerts. See below for steps on how to configure webhooks.

Here's an example of what the JSON element for an alert webhook looks like:

{
"orgId": "1ab23cde-4567-890f-1234-gh56ijk07l891",
"title": "title",
"summary" : "notification for a test alert",
"actionUrl" : "www.actionURL.com",
"severity" : "HIGH",
"eventType" : "created",
"resourceType": "ControlHubAlerts",
"type": "Meeting",
"subtype": "Live Meeting Monitoring",
}

You can set up a PagerDuty integration key so that alerts show up in third-party applications.