Skip to main content
Push China Mobile Cloud (ecloud) Cloud Monitor alerts to Flashduty On-call through the custom webhook address of an alarm contact. Alerts that the same rule keeps raising on the same resource map to one Flashduty alert: the alert opens when it triggers and recovers automatically when China Mobile Cloud pushes the recovery.

In Flashduty On-call

You can get the integration push URL in either of the following ways.

Use a dedicated integration

  1. In the Flashduty console, select Channel and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select China Mobile Cloud, then click Save
  4. Open the generated integration card and copy the Push URL

Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select China Mobile Cloud and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

In China Mobile Cloud

1

Create an alarm contact with a webhook address

Where: China Mobile Cloud console › Cloud Monitor › Alarm Service › Alarm Contacts › Create Alarm ContactSave the contact.China Mobile Cloud requires the webhook address to be reachable from the public internet. The Flashduty push URL meets this requirement.
2

Notify the contact from an alarm policy

Where: China Mobile Cloud console › Cloud Monitor › Alarm Service › Alarm Policies › Create Alarm Policy (or edit an existing one)Save the policy.When an alarm rule in the policy triggers or recovers, China Mobile Cloud pushes the alarm to the contact’s webhook address.
3

Trigger an alarm and confirm

  1. Make an alarm rule in the policy trigger, for example by temporarily lowering the threshold of a CPU utilization rule on a cloud server, and confirm that Flashduty receives an active alert
  2. Restore the threshold. After the monitoring data returns to normal and China Mobile Cloud pushes the recovery, confirm that the original alert recovers
Go back to Flashduty. If the integration shows a Latest event time, the setup works.

Alert key

Every push from China Mobile Cloud carries an alarm ID (alarmId). According to China Mobile Cloud, alarmId stays the same for alarms that the same rule keeps raising on the same resource. Flashduty computes the Alert Key from alarmId, so:
  • Repeated pushes and the recovery push for the same resource and alarm rule go to the same alert
  • When one alarm rule applies to several resources, each resource gets its own alert
  • Changes to the alarm level, alarm content, trigger value, or time do not change the Alert Key
Requests without alarmId are rejected.

Status and severity

The alert recovers when recover is true. Any other value is treated as a trigger. The severity comes from the alarm level (alarmLevel): A recovered alert keeps the severity it had before recovery.

Alert content and labels

The alert title combines the resource name (resourceName) and the metric name (metricName), for example ECS-45273803 CPU利用率. The alert description is the alarm content (content) pushed by China Mobile Cloud, which includes the trigger value and trigger time.

Troubleshooting

  • Flashduty receives no alerts: Confirm that the alarm policy notifies the alarm contact that has the webhook address, and that the address is complete and includes integration_key
  • Flashduty returns a parameter error: Confirm that the pushed content includes alarmId
  • The alert does not recover: China Mobile Cloud pushes a recovery when the monitoring data returns to normal and it clears the real-time alarm automatically. If an alarm that ended another way (for example, a manual clear) pushes no recovery, close the corresponding alert in Flashduty manually
  • All alerts have Warning severity: Check alarmLevel in the pushed content and see the status and severity section above
For a full description of the pushed fields, see the Cloud Monitor 告警联系人 (Alarm contacts) document in the China Mobile Cloud help center.