Determine which teams, services, and escalation policies an incoming alert is routed to with Alert Routes.
Routing incoming alerts ensures that the appropriate responders are paged to begin investigating any potential issues and events from your monitoring tools.
Rootly has two ways to route alerts to a team, service, or escalation policy:
This guide will help you configure your routing logic inside of Rootly using Alert Routes.
Create an Alert Route by navigating to Alerts > Routes and select New Route. An Alert Route includes the following information:
Once you’ve configured all the details on your Alert Route, make sure to Save and enable the route to begin routing your Alerts.
Use the Owning Team field to assign ownership over the Alert Route.
The Owning Team’s Team Admin will be granted create, update, and delete permissions for the Alert Route.
Note: Team Admins are only able to create Alert Routes assigned to their team. They will also only be able to route alerts from Alert Sources owned by their team.
Use Conditions to set rules for when an Alert from the Alert Source is eligible for being routed to the Destination.
For example, if your organization is using a single webhook for your monitoring tool, add a Condition to only route an Alert to a specific Team if the payload indicates that Team’s product area is impacted.
As you update your Conditions, the right-hand Alert Preview window will update to reflect the Alerts that fulfill the Condition criteria.
If an Alert Route doesn’t have any conditions, all Alerts from the Alert Source are eligible to be routed by the Alert Route.
Quickly build your Conditions by using the right-hand Alert Preview window. Click into each Alert to see the payloads, and select the field values to prefill the JSONPath for that field.
When an Alert is routed to a team or service, that team or service’s escalation policy will be fired.
We recommend routing to a team or service rather than directly to an Escalation Policy for easier measurement of your team’s on-call performances.
When an Alert from your monitoring tools is sent to Rootly, we do the following:
Note: An Alert will only be routed through a single Alert Route. We evaluate the Routing rules from oldest to newest, and will route using the first rule that matches the Alert.
The Alert’s timeline will include an event indicating which Alert Route the Alert was routed through.