Huawei Cloud AOM alert integration

Huawei Cloud Application Operations Management (AOM) can send triggered and recovered alerts to Flashduty On-call through Simple Message Notification (SMN) or webhook data subscriptions. Both methods use the same AOM integration push URL.

Use SMN notifications for most accounts. AOM webhook data subscription is not generally available and should only be used when Huawei Cloud has enabled it for your account.

Prerequisites

You have created a Huawei Cloud AOM integration in Flashduty and obtained its HTTPS push URL.
You have created or prepared an AOM alarm rule.
To use SMN, your Huawei Cloud account can create topics, subscribe endpoints, and list topics.
The alarm rule sends notifications for both alarm triggered and alarm recovered.

Method 1: Use SMN

Create an SMN topic and subscription

Create an SMN topic

Sign in to the Huawei Cloud console and open Simple Message Notification (SMN).
Select Topic Management > Topics and click Create Topic.
Set the topic name to Flashduty and save it.

Add an HTTPS subscription

Open the Flashduty topic and click Add Subscription.
Select HTTPS as the protocol.
Enter the Flashduty AOM integration push URL as the endpoint and save the subscription.
Flashduty verifies the SMN confirmation request and automatically visits the Huawei Cloud confirmation URL. SMN starts sending alerts after the subscription status changes to Confirmed.

Configure an AOM message template

In the AOM 2.0 console, go to Alarm Center > Alarm Notifications > Message Templates. In some console versions, the path is Alarms > Alarm Action Rules > Message Templates. When creating the template, select HTTP/HTTPS as the notification method. Flashduty supports the following content formats:

HTML
JSON

HTML templates can be in Chinese or English. Add the report type as the first line so that Flashduty can reliably distinguish triggered and recovered alerts.Chinese template

上报类型：${clear_type};
通知类型：${event_type};
事件级别：${event_severity};
事件名称：${event_name_alias};
发生时间：${starts_at};
事件源：$event.metadata.resource_provider;
资源类型：$event.metadata.resource_type;
资源标识：${resources_new};
可能原因：${alarm_probableCause_zh};
附加信息：${message};
修复建议：${alarm_fix_suggestion_zh};

English template

Clear Type:${clear_type};
Alarm Name:${event_name_alias};
Alarm ID:${id};
Notification Rule:${action_rule};
Occurred:${starts_at};
Event Severity:${event_severity};
Alarm Info:${alarm_info};
Resource Identifier:${resources_new};
Suggestion:${alarm_fix_suggestion_zh};

Put each field on a separate line and keep the trailing semicolon. A resource identifier can span multiple lines. Flashduty parses its key-value pairs into labels.

After selecting JSON, keep the default JSON content generated by AOM. Flashduty parses this JSON from the message field in the outer SMN notification.The default AOM JSON contains the following core fields. Keep every field marked as required. Flashduty uses optional fields for labels or recovery detection when they have a value.

Field	Required	Purpose
`id`	No	AOM event ID; stored as the `event_id` label when present
`starts_at`	Yes	Trigger time as a Unix timestamp in milliseconds
`ends_at`	No	A value greater than 0 indicates recovery; a missing, empty, or 0 value falls back to the SMN subject
`metadata.event_name`	Yes	Alert name
`metadata.event_severity`	Yes	Alert severity
`metadata.event_type`	Yes	Event type, usually `alarm`
`metadata.resource_provider`	Yes	Event source, such as `AOM` or `CCE`
`metadata.resource_type`	Yes	Resource type
`metadata.resource_id`	Yes	Resource identifier

Do not manually add SMN envelope fields such as signature, subject, or topic_urn to the AOM JSON template. SMN generates the outer notification and its signature.

Create an alarm notification rule

Associate the SMN topic and message template

In the AOM 2.0 console, go to Alarm Center > Alarm Notifications.
Under Notification Rule Management, create an alarm notification rule.
Select the Flashduty SMN topic and the AOM message template created earlier.

Send triggered and recovered notifications

Enable notifications in the AOM alarm rule and make sure that the notification scenarios include both alarm triggered and alarm recovered.

Verify the integration

Trigger a test alert and then recover it. In Flashduty, verify that the integration’s latest event time has changed and that the alert details contain the expected severity, resource, and recovery status.

Method 2: Use an AOM webhook data subscription

AOM webhook data subscription is not generally available. If the webhook alarm subscription option is not available in your console, submit a Huawei Cloud service ticket or use SMN instead.

If Huawei Cloud has enabled this feature for your account, go to Settings > Global Settings > Data Subscription in the AOM 2.0 console. Create a webhook alarm subscription and set its destination to the same Flashduty AOM integration push URL. The webhook request must use the official AOM structured event format:

{
  "events": [
    {
      "id": "4346299651651991683",
      "starts_at": 1664001830491,
      "ends_at": 0,
      "timeout": 300000,
      "resource_group_id": "project-id",
      "metadata": {
        "event_name": "Pod memory OOM",
        "event_severity": "Major",
        "event_type": "alarm",
        "resource_provider": "CCE",
        "resource_type": "service",
        "resource_id": "clusterName=production;kind=Pod;namespace=default;name=example;uid=example-uid"
      },
      "annotations": {
        "alarm_probableCause_en_us": "The pod does not have enough memory",
        "message": "pod was OOM killed",
        "alarm_fix_suggestion_en_us": "Increase the container memory limit"
      }
    }
  ],
  "project_id": "project-id"
}

A request can contain up to 100 events. Each structured event must contain a valid id, starts_at, and all six required metadata fields.

Correlate triggered and recovered alerts

Flashduty detects recovery in the following order:

Input format	Recovery detection
SMN HTML	Read `上报类型` or `Clear Type` first; if the value is missing or unknown, inspect the SMN `subject`
SMN JSON	`ends_at > 0` indicates recovery; if it is missing, empty, or 0, inspect the SMN `subject`
Webhook data subscription	`ends_at > 0` indicates recovery

For Huawei Cloud message templates, the Chinese clear_type values are 触发 and 恢复, and the English values are generated and cleared. Flashduty uses these values first to distinguish triggered and recovered alerts.

If an SMN HTML message does not contain a recognized report type, a subject containing 恢复, _resolved, _recovered, or _clear is treated as a recovery.

The following fields must remain the same between a triggered alert and its recovery:

metadata.event_type
metadata.event_name
metadata.resource_provider
metadata.resource_type
metadata.resource_id

Flashduty generates the alert fingerprint from these fields. The id is stored as a label but does not participate in correlation, so triggered and recovered notifications may have different IDs. If two independent alerts have identical values for all five fields, Flashduty treats them as the same alert. Make sure that metadata.event_name or metadata.resource_id distinguishes alerts that must be handled separately.

Field and severity mappings

Common AOM fields are converted into Flashduty labels:

AOM field	Flashduty label
`id`	`event_id`
`metadata.event_name`	`event_name` and `check`
`metadata.event_severity`	`event_severity`
`metadata.resource_provider`	`resource_provider`
`metadata.resource_type`	`resource_type`
`metadata.resource_id`	`resource_id`, plus labels parsed from its resource key-value pairs
`policy.alarm_rule_name`	`alarm_rule_name`
`annotations.tms_tags`	`tms_tags`
`annotations.generator_url`	`generator_url`
`Notification Rule` in the English HTML template	`notification_rule`

Severity mapping:

AOM severity	Flashduty severity	Status
Critical, Major, 紧急, or 重要	Critical	Critical
Minor, Warning, 次要, or 警告	Warning	Warning
Info or 提示	Info	Info

Troubleshooting

Why does the SMN subscription remain unconfirmed?

Make sure that the endpoint is the complete HTTPS integration push URL and that its integration_key has not been changed. Flashduty only visits valid Huawei Cloud HTTPS confirmation URLs.

Why does a manually replayed SMN request fail signature verification?

The SMN signature is bound to the message body, message ID, subject, topic, timestamp, and message type. Changing any of these fields invalidates the original signature. Send a real test notification through AOM and SMN instead of modifying a historical request.

Why did the recovery not close the alert?

Make sure that the alarm rule sends recovery notifications. Add ${clear_type} to an HTML template. For SMN JSON, Flashduty first checks for an ends_at value greater than 0 and falls back to the subject when the value is missing, empty, or 0. A webhook data subscription must provide an ends_at value greater than 0. Also verify that the five correlation fields are identical in the triggered and recovered events.

What is the difference between SMN JSON and a webhook data subscription?

SMN JSON is carried in the message field of an SMN notification, whose outer object still contains a signature and subject. A webhook data subscription directly sends an {“events”:[…]} object without SMN fields. Do not combine both outer formats in one request.

Quick Start

Channels

Incident Management

Post-Mortem

Status Page

Analytics

Integration Settings

Configuration

Advanced

Integrations

Best Practices

Huawei Cloud AOM alert integration

Create an integration in Flashduty On-call

Use a dedicated integration

Use a shared integration

Prerequisites

Method 1: Use SMN

Create an SMN topic and subscription

Configure an AOM message template

Create an alarm notification rule

Method 2: Use an AOM webhook data subscription

Correlate triggered and recovered alerts

Field and severity mappings

Troubleshooting

Huawei Cloud references

​Create an integration in Flashduty On-call

​Use a dedicated integration

​Use a shared integration

​Prerequisites

​Method 1: Use SMN

​Create an SMN topic and subscription

​Configure an AOM message template

​Create an alarm notification rule

​Method 2: Use an AOM webhook data subscription

​Correlate triggered and recovered alerts

​Field and severity mappings

​Troubleshooting

​Huawei Cloud references

Create an integration in Flashduty On-call

Use a dedicated integration

Use a shared integration

Prerequisites

Method 1: Use SMN

Create an SMN topic and subscription

Configure an AOM message template

Create an alarm notification rule

Method 2: Use an AOM webhook data subscription

Correlate triggered and recovered alerts

Field and severity mappings

Troubleshooting

Huawei Cloud references