跳转到主要内容
Generate a unique Dingtalk robot address in Flashduty, and synchronize the occurrence and recovery of alerts through Dingtalk.

Operation Steps


Create Dingtalk Alert Integration

You can obtain a Dingtalk alert integration address through either of these two methods:

Using Dedicated Integration

Choose this method when you don’t need to route alert events to different channels. It’s simpler and recommended.

Using Shared Integration

Choose this method when you need to route alerts to different channels based on the alert event’s payload information.

Customize Dingtalk Alert Integration

Dingtalk Alert Integration URL

The system will generate a unique Dingtalk alert integration URL for you. This URL is compatible with Dingtalk robot message protocol. When platforms only support Dingtalk robot channels, you can use this URL to receive corresponding messages.

Push Mode

By default, the system always creates new alerts for each message, but you can switch to these modes:
  1. Trigger or Update Alert Based on Message Title: In this mode, when receiving a new message, the system searches for open alerts based on the message title. If an alert is found, it will be updated; otherwise, a new alert will be triggered.
  2. Trigger or Close Alert Based on Rules: In this mode, when receiving a new message, the system matches messages according to your rules and triggers new alerts or closes existing alerts based on the matching results.
    • You need to fill in at least one trigger rule
    • You must set up regex extraction rules for Alert Key. The system uses this field to find historical alerts for updates or closure. If regex extraction fails, the system will use the message title to generate an Alert Key to ensure alerts won’t be lost due to configuration errors
    • You can choose whether to discard messages when none of the rules match
    Configuration example:
    • Receive all messages, close the alert when the message content contains RESOLVED, otherwise trigger a new alert
    • Extract Alert Key from message title using the rule /(.*)/.

Notes

  • Dingtalk alert integration URL only supports Text and Markdown message types; other message types cannot be received
  • When Dingtalk message type is Text, Flashduty will generate a default alert title “Dingtalk Alert”

Severity Mapping


Currently, all alerts pushed to Flashduty through the Dingtalk integration are set to Warning severity. However, you can customize the severity using the alert pipeline.