Skip to main content
Sync alert events from Alibaba Cloud DataWorks Intelligent Monitoring (Operation Center) to Flashduty On-call through a custom webhook.

​
In Flashduty On-call

You can obtain an integration push URL in either of the following two ways.

​
Use an exclusive integration

Choose this option when you do not need to route alert events to different collaboration spaces. It is simpler.
  1. Go to the Flashduty console, select Collaboration Spaces, and open a space’s detail page
  2. Select the Integrated Data tab, click Add integration, and open the add-integration page
  3. Select the Alibaba Cloud DataWorks Operation Center integration and click Save to generate a card
  4. Click the card to view the push URL, copy it for later use, and you are done

​
Use a shared integration

Choose this option when you need to route alerts to different collaboration spaces based on the alert payload.
  1. Go to the Flashduty console and select Integration Center → Alert Events to open the integration selection page
  2. Select the Alibaba Cloud DataWorks Operation Center integration:
    • Integration name: define a name for this integration
  3. Configure the default route and select the corresponding collaboration space (after creation, you can go to Routing to configure more routing rules)
  4. Click Save, then copy the newly generated push URL on the current page for later use

​
In Alibaba Cloud DataWorks

1

Open a monitoring rule in DataWorks Operation Center

Where: DataWorks console › Data Development and O&M › Operation Center › Monitoring and Alerting › Rule ManagementOpen an existing rule, or create a new one. Custom webhooks are supported only on DataWorks Enterprise Edition; custom monitoring rules apply only to automatically scheduled periodic instances.
2

Enable WebHook in the rule and enter the push URL

Where: Rule Management › your rule › Alarm BehaviorSave the rule. Alerts triggered by this rule are pushed to Flashduty in real time.
3

Send a test message and confirm

Where: Rule Management › your rule › Alarm Behavior › Send test messageAfter entering the URL, click Send test message to verify connectivity (the official docs do not confirm this button for custom webhooks; check your console). The test message only verifies the push URL; Flashduty returns success without creating an alert event.To see the first event, trigger the rule for real. Go back to Flashduty. If the integration shows a Latest event time, the setup works.

​
Supported alert types

DataWorks Intelligent Monitoring wraps every custom webhook message in a message field, distinguished by message.title. This integration supports the following three alert families:The connectivity test message (message.content) is used only to verify the push URL and never creates an alert event.

​
Status and severity

Mapping from custom alert remind_type to Flashduty severity:Mapping from baseline alert status:Mapping from event alert event_type:

​
Alert key and alert merging

DataWorks Intelligent Monitoring webhooks are one-shot events: the official protocol defines alert notifications only, with no recovery or update semantics, and it provides no vendor-level deduplication ID or fingerprint field. Therefore this integration never automatically recovers (closes) any alert; every event is delivered in a triggered state.Every webhook delivery receives a fresh random UUID as its Alert Key, so each push creates an independent alert event and repeated triggers are not merged automatically. To reduce noise, configure alert grouping or convergence policies in Flashduty.

​
Field label mapping

Key fields from the push message are preserved as labels on the alert event and can be used for routing, silencing, and template rendering:Empty-valued fields do not produce labels. The alert title comes from the family’s name field: remind_name for custom alerts, baseline_name for baseline alerts, and task_name for event alerts.

​
FAQ

Why are alerts never automatically recovered?The DataWorks Intelligent Monitoring webhook protocol defines no resolve message; it is a one-shot notification with no recovery semantics. To close an alert, handle it manually in the Flashduty console or configure alert convergence policies for the rule.Why is no alert visible after sending a test message?The DataWorks connectivity test message (message.content) only verifies that the push URL is reachable. Flashduty returns success without creating an alert event. Trigger a real rule to verify the end-to-end flow.