Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Notification Management

Updated on 2024-11-20 GMT+08:00

Notification Management creates notification rules for users. Notification rules include incident notifications, change notifications, and issue notifications.

When an incident ticket, issue ticket, or change ticket is generated, the notification rule and the information about the incident, issue, or change are matched, then the recipients, the notification content, and notification method are obtained through parsing, and finally the notification messages are sent.

The incident and change notification templates are preset in the system. You can select a notification template as needed.

Creating a Notification Rule

Create a notification rule. After an incident, issue, or change ticket matches the corresponding rule, a notification is automatically sent.

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. On the displayed page, click Create Notification.

    Figure 1 Clicking Create Notification

  3. In the displayed dialog box, enter the notification configuration information and click OK. Table 1 described the required parameters.

    Figure 2 Setting the notification parameters
    Table 1 Notification parameters

    Parameter

    Mandatory

    Radio/Checkbox

    Description

    Name

    Yes

    /

    Notification name of a notification instance. Fuzzy search can be performed based on the notification name.

    Type

    Yes

    Radio

    Including incident notifications, change notifications, and issue notifications.

    Template

    Yes

    Checkbox

    Notification content template is system built-in. The template list varies depending on the notification type. After a template is selected, the notification template details are displayed.

    Notification Scope

    Yes

    Checkbox

    Select a service. For example, if service A is selected and service A is displayed in the incident ticket, the subscription takes effect and a notification is sent based on the subscription instance without considering other matching rules.

    Recipient

    Yes

    If Shift is selected, you can select single scenario and multiple roles. If Individual is selected, you can select multiple users.

    Objects to be notified. If Shift is selected, the notification module automatically obtains the list of personnel in the current schedule mode and sends notifications to the corresponding personnel. If Individual is selected, the notification module directly sends notifications to the corresponding users.

    Notification Rule

    /

    /

    For example, if the value of rule A is set to a, in an incident ticket, the value of rule A is a, not considering other matching rules, the subscription instance will take effect and a notification is sent based on the subscription instance. However, if the value of rule A in the incident ticket is b, the subscription instance will not take effect, and no notification is sent.

    Notification Rule - Level

    No

    Checkbox

    Level of an incident ticket. There are five levels: P1 to P5. For details about the incident ticket levels, see section Creating an Incident.

    Notification Rule - Incident Category

    No

    Checkbox

    Category of an incident ticket. Multiple values are available.

    Notification Rule - Source

    No

    Checkbox

    Source of an incident ticket. Manual creation indicates that the incident ticket is created in the incident ticket center. Transfer creation indicates that the incident ticket is generated during the transfer.

    Notification Rule - Region

    No

    Checkbox

    Region of an incident ticket. Multiple regions can be selected.

    Method

    Yes

    Checkbox

    Notification channel.

    CAUTION:

    In the shift scenario, duplicated users will be removed. However, if multiple persons use the same mobile number, multiple same notifications are sent, which is the same as the notification logic in individual scenario.

    If no rule value is set in a rule, the rule will not be matched. For example, if no value is configured for rule A, the notification instance takes effect without matching rule A, not considering other matching rules. If rule A changes, the notification instance still takes effect without matching rule A.

    After a notification is created, it is enabled by default.

Editing Notifications

Modify an existing notification instance.

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be modified and click Modify in the Operation column. Modify and save the notification by referring to the 3.

    Figure 3 Modifying notifications

Deleting a Notification

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be deleted and click Delete in the Operation column.

    Figure 4 Deleting a notification

  3. In the displayed confirmation dialog box, click OK to delete the notification. After the notification is deleted, it is not displayed in the list.

    Figure 5 Confirming the deletion

Searching for a Notification Instance

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. Enter the search criteria in the search box and press Enter.

    Figure 6 Searching for notifications
    NOTE:

    The search box supports search by notification type and notification name (fuzzy search). The search results can be displayed on multiple pages (10, 20, 50, or 100 records per page). Click the drop-down arrow on the left of each notification instance displays details.

Enabling and Disabling a Notification Instance

  1. Log in to COC.
  2. In the navigation pane on the left, choose Basic Configurations > Notification Management. Locate the notification to be enabled or disabled and click Enable or Disable in the Operation column.

    Figure 7 Enabling/Disabling a Notification

  3. The confirmation dialog box is displayed. Click OK.

    Figure 8 Confirming the enabling
    NOTE:

    The notification instance statuses include Enabled (in green) and Disabled (in red).

Other Notification Features

The following notification features are not displayed on the page:

  1. Notification deduplication

    When an incident ticket or a change ticket triggers multiple notifications, and the recipients or other factors of these notifications are the same, the notification module deduplicates the recipients, ensuring that a recipient receive only one notification when an incident or change ticket is generated.

  2. Notification Template Description

    Incident notification template: Different templates correspond to different scenarios. When an incident ticket matches a scenario, a notification can be sent. The notification templates are described as follows:

    • Incident creation: A notification needs to be sent after an incident is created.
    • Event rejection: A notification is sent after an event is rejected.
    • Incident forwarding: A notification is sent after an incident is forwarded.
    • Incident verification: A notification is sent when an incident enters the to-be-verified state after being resolved.
    • Incident completion: A notification is sent after an incident is processed and verified.
    • Incident verification failed: A notification is sent when an incident enters the to-be-verified state and fails to pass the verification.
    • Incident close after rejection: After an incident is rejected, a notification is sent after the incident is closed.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback