Configure routing rules
Go to Integration Center → Alert Events, open your integration in the list on the right, then select Routes → Edit → Add route. After configuring the rules, select Save to apply the full set of routing rules.Configuration
Matching methods
Match Condition values are always strings, and the format decides the matching method. The condition editor lists the five supported forms directly under the input:
For the complete syntax and examples, see Configure filter conditions.
Routing modes

Operation tips
Edit history
Routing rules support viewing edit history, helping you track configuration changes and quickly roll back when needed. Click the Edit History button on the routing configuration page to open a dialog (history version list on the left, diff comparison area on the right). History records are grouped by date, and each record includes the version number, operator, and modification time. The currently active version is labeled Current Version. You can perform the following actions: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.
FAQ
Routing rule not taking effect?
Routing rule not taking effect?
Use Route Preview with real alerts to see which rule and channel each alert reaches. If no rule matches, check that a default route is configured.
Multiple rules match the same alert, delivering to the same channel?
Multiple rules match the same alert, delivering to the same channel?
Target channels are deduplicated for each event. If multiple rules match the same channel, it receives the event once. Different channels receive the event separately.
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?
The default route is independent of Continue Matching or Stop Matching:
- If no rule resolves a target channel, the event goes to the default route. This includes a name mapping rule that matches but finds no corresponding channel.
- If some mapped names have no matching channel, or the 100-name limit is exceeded, both the resolved channels and the default route receive the event.
- Otherwise, once a rule resolves a target channel, the default route is not used.
Further reading
Integrate Alerts
Learn the difference between dedicated and shared integrations
Configure Filter Conditions
Learn condition matching syntax
Configure Label Enhancement
Dynamically generate or modify alert labels
Configure Alert Processing
Cleanse and transform alert data at source
