Alert routing gives you the ability to assign specific types of alerts to specific groups. The objective is to ensure that only those team members that can address an issue are alerted to it.
Routing Keys’ settings can be found by Navigating to Settings >> Alert Behavior >> Route Keys.
When an alert is delivered to VictorOps, your routing rules determine whether an incident is created, and to which team alerts and incidents will be routed. When an incident is routed to a particular escalation policy, that escalation policy determines who to notify, and who to escalate to if the incident stays unacknowledged.
All types of alerts have a routing key assigned to them by your administrator. This key is what is used to map the alert to a team. To find the routing key for an alert, click on an open incident for the alert (or look in the alert’s details) in the VO mobile or web app. You will see the routing key in the list of key/values.
- Each team should have one routing key that is not shared with any other teams. Keeping the naming of the routing keys identical or at least similar to the team name will also reduce confusion.
- Keep the names of routing keys simple. They are case sensitive, making all key names entirely lowercase and intuitively named will obviously indicate which team or teams the key associates with.
- A well-made set of routing keys will make filtering the timeline a breeze. A filtered timeline is the easiest way to hone in on exclusively the events that are important to you.
Note: Due to a previous issue, Admins were able to save routing keys containing currently invalid characters (such as spaces). As a best practice, we recommend ensuring that all existing routing keys only possess letters, numbers, hyphens, and underscores, and changing the routing key if any other characters are found.