VictorOps allows you to quickly mobilize teams around an incident. While a regular incident only requires a single acknowledgement to stop paging, multi responder incidents require responses from each user or escalation policy being paged.
Cascading Escalation Policies
If an alert is sent to an escalation policy that references another escalation policy or set of escalation policies, and multi-responder is enabled, every first step in the escalation policy is required to respond if the parent escalation policy is called via manual incident or additional responder.
Using this, you may build response plays that allow you to organize multiple teams around an incident by calling on only one escalation policy.
Manual Incident – Multi Responder
You may manually send an incident to users and escalation policies, requiring an individual acknowledge per user or escalation policy.
When an incident requires multiple responders, it will not move to an acknowledged state until all required responders have acknowledged it. As an example, you will see the state of paging and progress of acknowledgement in the incident card in the below graphic.
Adding Responders to an Incident
You may require responder acknowledgement by clicking the responders icon and adding responders to a particular incident.
You will then be prompted by the following modal; here you are able to select which user or Escalation Policies to page and require individual acknowledgement. This is similar to reroute, but instead of cancelling paging via a singular Ack, each escalation policy or user must acknowledge to move an incident to an acknowledged state.
VictorOps can suggest responders who are likely able to help. VictorOps leverages historical incident information and user involvement via acknowledgement or chat to suggest these responders that may be added to an incident response. If a user is currently not on-call a red warning symbol will appear next to the user’s name.