Routing is where you connect external alerting tools to Vibe and decide how incoming alerts should be handled. It lives under Settings → On-call → Routing.
For organization and team navigation, see Global and team pages.
Routing now has two main parts:
| Part | What it does |
|---|---|
| Alert sources | Named inbound connections for tools such as Grafana, Datadog, Email, HTTP, Sentry, CloudWatch, and more. A source gives you a webhook URL or email address to put in the external tool. |
| Alert routes | Reusable routing behavior. A route receives alerts from one or more sources, enriches them with attributes, and uses its Notification rule to decide who gets paged. |
<aside> ℹ️
Where it lives and who can edit it. Routing lives in the On-call group of the Settings sidebar and is visible to everyone. At Global scope, only admins can edit. In a team scope, anyone with write access to that team can edit. Everyone else sees the page read-only.
</aside>
An alert source receives the alert. The source sends the alert into one alert route. The route can add attributes, decide whether to page someone, and pass the escalation to schedules, escalation policies, and personal notification preferences.
<aside> 💡
Alert source → Alert route → Attributes → Notification rule → Escalation policy → Personal notification preferences
</aside>
Attributes are the optional step where a route adjusts an alert before deciding who to page. For example, a route can set the alert's severity from its title, or tag it with an owner that the Notification rule routes on. See Enriching alerts with attributes for examples.
On the Routing page, sources appear on the left and routes appear on the right. Connector lines show which sources send alerts to which routes.