Skip to main content
Plan requirement: Basic label enhancement requires an On-call Standard or higher subscription. Advanced label enhancement (such as API mapping) requires a Pro or higher subscription. Learn more

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

  1. Go to Integration Center → Alert Events, open your integration in the list on the right, and select Label enrichment.
  2. Select Add for the first configuration, or Edit if rules already exist.
  3. 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

Label 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

Multiple rules execute sequentially from top to bottom. Flashduty skips a rule that doesn’t match and generates no label for it.

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.
The event source switches between Recent events and Custom. Recent events picks one of the raw events the integration received (each integration keeps its latest 20 events for 7 days, at most one every 10 seconds); when the event you want isn’t in the list, switch to Custom and paste an event JSON. The preview runs exactly what the editor holds; in Recent events mode edited lines are highlighted and you can revert them. A mapping rule also shows the row it matched in the mapping table inside the rule, with the match column marked (match column); the labels it generated are green and summed up as Found 1 row for this raw event; adds …. Sample values in the regex and template editors come from the same event. When a rule does nothing, the preview names the reason: 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

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

Original alert
2

Configure Extraction Rule

Extraction rule configuration
3

Verify Extraction Result

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:
Mapping table data management
A mapping table that is still referenced cannot be deleted. The delete is refused with Delete failed, resource is in use., and the objects still referencing it are listed by type; select one to open its configuration:
  • 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
Remove these references first (switch to another table, clear the mapping table selection, or delete the robot), then delete the mapping table.
For frequently changing mapping relationships (like data synced from a CMDB), we recommend using API mapping, or use Flashduty API for automated mapping table updates.

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