Skip to main content

Why dynamic dispatch

In enterprise operations, you often manage thousands of monitored objects (hosts, services, databases, and so on), and the responsible responders change frequently as the organization evolves. Maintaining separate escalation rules for each object is both costly and error-prone. Dynamic dispatch solves this problem: you configure one escalation rule as a “template”, and Flashduty replaces or appends notification targets based on labels on the alert. When responders change, you update the label data, not the escalation rule.

How it works

The core flow of dynamic dispatch consists of three steps:
1

Alert enters the channel

After being ingested through an integration, the alert enters a channel and matches a configured escalation rule.
2

System reads dynamic labels

The system detects that the alert carries a specific label (for example, layer_person_reset_0_emails=bob@corp.com or layer_person_append_0_emails=bob@corp.com) and automatically replaces or appends notification targets in level 1 of the escalation rule.
3

Dispatch based on the adjusted rule

The system dispatches notifications according to the updated escalation rule. After dispatch completes, these control labels are automatically removed to keep the alert details page clean.

Configure a template escalation rule first

Dynamic dispatch depends on an existing escalation rule in the channel. Configure one in the target channel in advance as a “template”. See Escalation rules.
  • The notification targets in the template can be any value (for example, a default team). During dispatch, the dynamic labels replace or append them. Targets can be responders, teams, or chat bots
  • Other settings (notification methods, timeout, escalation levels, and so on) stay unchanged and work normally
  • For the full label parameter reference, see Dynamic dispatch

How to generate dynamic labels

The key to dynamic dispatch is ensuring alerts carry the correct labels. The following two approaches can achieve this — choose whichever fits your situation.
This guide uses the reset replacement mode as an example. To keep the original targets in the template escalation rule while adding responders, teams, or group bots, use the append mode. For the complete parameter reference, see Dynamic dispatch.

Approach 1: Add labels directly in the monitoring system

If you have configuration access to your monitoring system and it supports custom labels (for example, Prometheus, Nightingale, Zabbix), add the label to your alert rules:
  • Label key: layer_person_reset_0_emails
  • Label value: bob@corp.com
This approach requires minimal configuration and works well when responders rarely change. However, you’ll need to update the alert rules in your monitoring system whenever personnel changes occur.

Approach 2: Auto-generate with label mapping

Use label mapping if you can’t change the monitoring configuration. It also fits when you want to manage the “monitored object → responder” mapping centrally, for example by syncing it from a CMDB. This approach creates a mapping table that automatically “translates” existing basic labels in alerts (such as host) into dynamic dispatch labels, without modifying the monitoring system.
1

Prepare mapping data

Compile the mapping between monitored objects and responders. For small datasets, you can enter data manually on the page; for large datasets, prepare a CSV file.
The target column name in the CSV must use the dynamic dispatch parameter name (for example, layer_person_reset_0_emails).
You can source this data from anywhere — CMDB, configuration management platforms, operations systems, or Excel spreadsheets — as long as it follows the format above.
2

Create a mapping table

Import the data into the system to create a reusable mapping “dictionary”.
  1. Go to Configuration → Mappings → Schema.
  2. Click Create.
  3. Enter data:
    • Upload file: Upload a CSV file for bulk operations.
    • Manual input: Add entries one by one on the page for small-scale maintenance.
  4. After saving, you’ll have a mapping table ready to be referenced by integrations.
To keep the mapping in sync with external systems in real time, use the Flashduty API to update the mapping table automatically, achieving fully unattended configuration sync.
3

Configure label enhancement rules

Reference the mapping table in your alert integration so the system automatically populates dynamic labels during alert ingestion.
  1. Go to Integration Center → Alert Events, open the integration you want to use (for example, a Zabbix integration) in the list on the right, then go to Label enrichment.
  2. Click Add label rule and choose Mapping labels as the rule type. The Mapping labels rule type requires the Pro plan or above.
  3. Select mapping table: Choose the mapping table created in the previous step.
  4. Configure mapping:
    • Source label: Select host.
    • Target label: Select layer_person_reset_0_emails.
Once configured, the system will automatically look up the host value in the mapping table during alert ingestion and generate the corresponding dynamic dispatch label.

Verify the result

After completing the configuration, trigger a test alert to verify:
  1. Check the dispatch process: In Incident Details → Timeline, you’ll see a log entry similar to: “Based on dynamic labels, responders have been reset to bob@corp.com”.
  2. Check alert labels: On the alert details page, you will not see layer_person_reset_xxx labels — these control directives are automatically cleaned up after taking effect.

Further reading

Dynamic dispatch

View the full dynamic label parameter reference and push examples

Label enhancement

Learn how to auto-generate new labels based on existing ones