Alerts & routing
Alerts & routing in the Settings area (Platform) — route /settings/alerts-routing.
Alerts & routing lives in the Settings area of the dashboard, under Platform.
At a glance#
| Dashboard route | /settings/alerts-routing |
| Area | Settings (settings) |
| Group | Platform |
| Platforms | Available for every app platform. |
What it does#
Alerts routing decides which alerts reach which destination. It is the same routing panel that appears within Integrations, surfaced here as a page of its own because routing is a policy decision rather than a per-connection setting.
Alerts defines what is watched. This page defines who hears about it.
When to use it#
Once you have more than one alert or more than one destination. Before that there is nothing to route.
The moment it becomes necessary is when production and staging alerts start arriving in the same channel — which is the point at which people begin ignoring all of them.
Workflow#
Split by environment first
Production alerts and pre-production alerts should never share a destination. This one rule prevents most alert fatigue.
Send the severe ones somewhere that interrupts
A crash-rate breach belongs in a paging destination. A performance regression belongs in a channel someone reads during working hours. Routing everything to the same place discards that distinction.
Leave a default destination
Anything unmatched by a rule should land somewhere rather than nowhere. A silently unrouted alert is the worst outcome available.
Send a test through each route
Verify the rule and the destination together.
Permissions and prerequisites#
Requires an administrative role, and at least one connected integration to route to.
Limits and edge cases#
A rule that matches nothing is silent. Nothing warns you that a route is unused, so an alert can be configured, firing, and going nowhere.
Routing is not throttling. It decides where alerts go, not how often. A flapping alert routed correctly is still a flapping alert.
Destinations must already exist. Connect the provider first.
Editing shows the same state as Integrations — one configuration, two entry points.
Troubleshooting#
An alert fired and nobody was notified. No rule matched and there is no default. Add a catch-all.
Alerts arriving in the wrong channel. Check rule order and specificity — a broad rule placed first will match before a narrow one.
Where the data comes from#
Mounts the same routing panel as the Integrations hub, so a rule edited in either place is the same rule.
Served by
Integrations
Alerts