Skip to main content
Changelog
  • New Integrations: Alibaba CloudMonitor 2.0 Notification Policies and BlueKing ITSM

    Two new integrations: one brings Alibaba CloudMonitor 2.0 alerts in, the other sends incidents into the BlueKing ITSM ticket workflow.

    Alibaba CloudMonitor 2.0 Notification Policy Edition

    Alerts that leave Alibaba Cloud through CloudMonitor 2.0 → Alert center → Notification policy → Custom webhook now arrive through this integration. A notification policy groups related events into one Alibaba Cloud issue, and one notification becomes one Flashduty alert event keyed by incidentId (the alert key). Child events in events[] add to the description and labels instead of being split into separate alerts, and later notifications with the same incidentId reuse the same key. Use this integration whenever the notification goes out through that policy, even if the event came from ECS, Prometheus, or APM.

    It supports Alibaba Cloud's system default webhook template only. Both the Chinese and English templates must keep their default content; custom templates and added, removed, or renamed fields are not supported. If you have already edited the template, choose Restore default in the Alibaba Cloud template editor and save. CloudMonitor 1.0 metric callbacks, cloud product system event callbacks, and direct ARMS or Prometheus callbacks keep using their own integrations.

    BlueKing ITSM synchronization

    The BlueKing ITSM integration creates BlueKing tickets from Flashduty incidents and synchronizes a linked ticket's workflow node or completion state back to the incident. There are three directions: two-way (create tickets manually or automatically, state flows back), Flashduty to BlueKing only (tickets are created, but no incident is acknowledged or closed from them), and BlueKing to Flashduty only (no ticket is created; link an existing ticket number).

    State synchronization applies to linked incidents only and never imports other BlueKing tickets as new incidents. Acknowledging, closing, or editing fields in Flashduty does not stand in for BlueKing approval and does not rewrite fields on a created ticket. Before you set it up, prepare your BlueKing application's app_code and app_secret, a BlueKing username with permission on the target service and its tickets, and the matching ESB / API gateway resource permissions for the application.

    Get started

    Go to Flashduty console → Integrations: pick Alibaba CloudMonitor 2.0 Notification Policy Edition under alert integrations, and BlueKing ITSM under webhooks.

    Product docs: Alibaba CloudMonitor 2.0 Notification Policy Edition, BlueKing ITSM synchronization.