Skip to main content
Dynamic assignment lets an alert carry responder information when it is pushed. Flashduty uses it to replace or append the assignment targets and group bots at each level of the matched escalation rule, so On-call works with your own responder system.

Use cases

Alert responders are maintained in the source monitoring system and change frequently; you want them synced to Flashduty On-call promptly. Typical cases:
  • Task system: each task has a primary and a secondary responder. When a task fails, notify the primary responder first; if the alert is not resolved after 30 minutes, escalate to the secondary responder.
  • Host monitoring: each host carries a responder tag, and host alerts notify the matching responder.
  • Policy-to-group notification: each monitoring policy maps to a fixed notification group. After moving to Flashduty, alerts still go to the mapped group.

Implementation

When pushing an alert, add specific labels (or the same-named query parameters on the push URL) to adjust assignment targets in Flashduty On-call. Parameter values can contain multiple emails, team names, or bot tokens separated by ,. Dynamic assignment supports two modes:
N in a parameter name is the level number (a single digit, 0–9), starting from 0. For example, layer_person_reset_0_emails points to escalation rule level 1, and layer_person_append_1_emails points to escalation rule level 2.

Responder and team parameters

Group bot parameters

When an incident is triggered, Flashduty matches existing escalation rules. After matching an escalation rule, it assigns or escalates according to the levels in that rule. If these parameters are set, the system automatically replaces or appends assignment targets and group chat channels.In the matched escalation rule, everything remains unchanged except for the assignment targets and group chat targets, so the rule acts as a template escalation rule.
reset has higher priority than append. Responders and teams share the same responder group dimension: if any layer_person_reset_* parameter is set for a level, layer_person_append_* parameters for that level are not merged. Group bots are evaluated by bot type. For example, if both layer_webhook_reset_0_wecoms and layer_webhook_append_0_wecoms are set, level 1 uses the WeCom bot from reset; appending Feishu/Lark or Dingtalk bots at the same level still takes effect.

Push example

Step 1: Set up template escalation rule

Configure an escalation rule for the channel. In the example below, the channel has one assignment level with a team as the responder. It also posts to a WeCom group chat whose token ends in 5b96.
Template Escalation Rule Configuration

Template Escalation Rule Configuration Example

Step 2: Set alert labels

Using custom alert event integration as an example, push a sample alert to the target channel:
  • Set layer_person_reset_0_emails label to replace level 1 responders with alice and bob
  • Set layer_webhook_reset_0_wecoms label to replace level 1 WeCom group chat token with the token of another WeCom group bot
  • Set layer_person_append_0_emails label to append carol to level 1
  • Set layer_webhook_append_0_feishus label to append one Feishu/Lark group bot to level 1

Step 3: View incident assignment timeline

As shown below, the target incident is triggered and assigned normally. The incident responders and target group chats are replaced or appended according to the dynamic labels.
Dynamic Assignment Result Display

Dynamic Assignment Result

FAQ

1

Option 1: Manually Add Labels

If your system supports manually adding labels, such as Prometheus or Nightingale, we recommend adding specific labels directly in the alert policy.
2

Option 2: Use Label Enhancement

Your system may already have related labels in a different format or naming. For example, hosts have team labels, and you need each team’s responder. Use label enhancement to generate responder labels from the team labels.For details, see Configure Label Enhancement.

Label Enhancement

Automatically generate new labels based on existing labels

Escalation Rules

Learn how to configure escalation rules