Configure Routing Rules
Go to Integration Center → Alert Events → Integration Details → Routing → Add Route.Configuration
| Config Item | Description |
|---|---|
| Match Condition | Filter alerts by labels, attributes, etc.; supports exact, wildcard, regex matching |
| Routing Mode | See detailed description below |
| Flow Control | Continue Matching (default): Continue matching subsequent rules after hit; Stop Matching: Don’t match further after hit |
| Default Route | Fallback rule that takes effect when no rules match |
Routing Modes
| Mode | Description | Use Case |
|---|---|---|
| Standard Routing | Manually select target channel | Alert-to-channel mapping is fixed |
| Name Mapping | Map specified label value to channel name, auto-deliver | Alerts already carry business identifier and channel name matches label value |
Operation Tips
| Feature | Description |
|---|---|
| Adjust Order | Use up/down arrows or drag rules to adjust match priority by channel |
| Insert Rule | Quickly insert new rules before/after specified rule |
| Filter Rules | Filter all rules delivering to a channel by that channel |
| Edit History | View historical configurations and quickly restore to a version |
Configuration Examples
- Route by Business Group
- Route by Alert Level
- Name Mapping Mode
Scenario: Deliver alerts from the same business group in monitoring platform to corresponding channel.
| Config Item | Value |
|---|---|
| Match Condition | Labels.group_name equals Flashduty |
| Routing Mode | Standard Routing |
| Deliver To | Flashduty |
FAQ
Routing rule not taking effect?
Routing rule not taking effect?
Check if alert event attributes/labels match the rule, and if rule configuration is correct.
Multiple rules match the same alert, delivering to the same channel?
Multiple rules match the same alert, delivering to the same channel?
Each channel will generate a corresponding incident. We recommend selecting multiple channels in the same rule to avoid duplication.
Not receiving alerts after configuring routing rules?
Not receiving alerts after configuring routing rules?
Confirm reported alerts can hit configured routing rules. We recommend configuring a default fallback route to receive unmatched alerts.
When flow control is set to 'Stop', will default route still match?
When flow control is set to 'Stop', will default route still match?
Yes. Default route is a fallback rule not subject to flow control restrictions.