Core uses
Labels drive the whole alert workflow: filtering the incident list, routing alerts to channels, matching escalation rules, grouping alerts, and matching silence and inhibition rules. Label enhancement lets these steps use information the source data doesn’t provide directly.Configure label enhancement
- Go to Integration Center → Alert Events, open your integration in the list on the right, and select Label enrichment.
- Select Add for the first configuration, or Edit if rules already exist.
- Select Add label rule in the editor, configure the rule, and preview its effect. Select Save to apply the changes.
To turn off label enhancement for an integration, delete all rules and save (applies to both alert and change events). Select Add to open the editor and configure rules again.
Enhancement types

Mapping methods
When source label values vary or aren’t meaningful on their own, map them to new labels and values. When adding a mapping rule, choose Schema or API:Configuration options
Preview rules
The Preview card on the right of the editor runs your current rules, unsaved changes included, on one raw event and reports the result in two parts: a label table, and How this event was processed.- The label table lists every label after the preview: an added label is prefixed with
+, a changed label shows old value → new value, a removed label is struck through. Each change names the rule that made it (Added by rule N / Changed by rule N / Dropped by rule N), and a label a rule should have produced but didn’t is marked Not generated (Rule N did not match). - How this event was processed gives one line per rule: which labels it produced, or why it did nothing. The rule card header on the left also shows Applied / No match / Skipped / Error.
A preview covers at most 50 rules. A rule whose mapping type is API makes the preview call your mapping service for real, so it needs edit permission on the integration; without it the preview shows Previewing mapping-API rules requires edit permission and the rest of the page keeps working.
Condition fields
Label enhancement rules apply to both alert events and change events, and the fields usable in conditions are the union of the two:Flashduty validates condition fields when you save a rule. Fields outside this vocabulary make the save fail, such as typos or fields from other rule families like
incident_severity or dedup_key.Configuration examples
- Label Extraction
- Label Combination
- Mapping: Schema
- Mapping: API
Scenario: Alert events come from email integration; need to extract key information from description as labels for other scenarios, like extracting IP and trigger value from description as independent labels.


1
View Original Alert

2
Configure Extraction Rule

3
Verify Extraction Result

Mapping data management
Each account can create up to 20 mapping tables and 50 mapping services (APIs). Each mapping table holds up to 10,000 rows by default. Creating a table or uploading data fails with a limit-exceeded error once a quota is reached.
Mapping table data management
In the mapping table details page, you can manage mapping table data:
- Integrations: a label enhancement rule uses this mapping table
- Escalation rule, Schedule: a notification robot has Enable @ mentions on and uses this table as its User information mapping. Turning Enable @ mentions off keeps the selected table, which still counts as a reference
Mapping service API specification
For the request body, response format, forbidden headers, and implementation tips for your own mapping service, see Label Mapping API.Further reading
Configure Escalation Rules
Use labels to match escalation conditions
Configure Noise Reduction
Use labels as grouping dimensions
Configure Filter Conditions
Learn label matching syntax
Configure Routing Rules
Distribute alerts to different channels






