Create a Router

Use routers to define how Notification Center matches and delivers notifications to specific destinations.

Each router contains routing labels, routing rules, and an optional fallback connector.

Understand when to create a router

Create a router when you need to organize notification delivery by key attributes such as:

• Team: for example, SRE, Security, or DevOps
• Environment: for example, prod, staging, or dev
• Service for microservice-level routing or fine-grained separation

Routers centralize and isolate configurations so that each team or environment can manage its own delivery logic.

Understand router components

Understand routing labels matching logic

A router matches a notification when all defined labels are present in the notification request.

Router Labels	Notification Labels	Result
team:teamA, environment:prod	team:teamA, environment:prod	✅ Matched
team:teamA, environment:dev	team:teamA, environment:prod	❌ Not matched
environment:prod	team:teamA, environment:prod ,service:app1	✅ Matched
team:teamA, environment:prod	team:teamA, environment:prod ,service:app1	✅ Matched
team:teamA, environment:dev , service:app1	team:teamA, environment:prod ,service:app1	❌ Not matched

Create a router

Use these steps to create a router that matches notifications and routes them to connectors.

1. Select Integrations, then Notification Center and Routers. The Routers list displays all existing routers.
2. Select + New router.
3. In the Details section, enter a router name and description.
4. In the Routing labels section, select one or more labels that define which notifications this router should handle.
   • Example:
     • Team:sre
     • Environment:prod
     • Service:frontend
5. Based on the routing labels configured, you can see the list of matching entities in panel on the right. This helps you check which entities have the routing labels that will match the router.
6. In Fallback, select a connector to use if no routing rules match. Fallback connectors ensure notifications are still delivered, for example, to a general Slack channel or monitoring queue.
7. Select Create router to save the configuration.

The new router appears in the list and becomes available for routing rule creation.

Use a fallback connector

Use a fallback connector to handle unmatched notifications.

Fallbacks route messages to a shared channel or monitoring system when no router rules apply.

This prevents lost notifications when conditions change or new services are added.

Example router configuration

Next steps

• Routing Rules: Add rule conditions and destinations to your routers.
• Add Labels to Alerts: Ensure your alerts use routing labels that match router labels.