Opsgenie Teams have new areas for Incident Response functions: Services. By defining these services in Opsgenie, you can quickly communicate with all parties when a service is impacted by an incident. Because most of the Incident Response automation features rely on Service definitions and control, Incident Response setup begins with creating and updating Services on the Team Dashboard for the Team that controls a Service.
Services are specific systems, tools, or products that IT responders are responsible for, and Stakeholders are interested in. Some examples of a Service which may be owned by a Team are a Public Web Site, Order Processing, Mobile Apps, Customer Portal, and Backup Services.
Incidents and Incident Management workflows revolve around outages and other events that impact a Team’s Services. Because of this, the new Services area of a Team Dashboard contains controls for that Service, including: Incident Rules, Incident Templates, Responders, and Stakeholders:
To add, view, edit, and delete Services owned by your own Team, access the Services tab on the Team’s Dashboard:
To view information about an existing Service that is owned by another Team, go to the new Services List — if the Team made its Service visible to the organization (and if your Opsgenie User Role allows):
To create a Service, you click the + Add Service on a Team’s Dashboard via the Services tab. Define a Service by entering (and saving) Service Name, Service Description, and visibility (private to the Team or visible to the organization).
After you have added a Service to a Team, you should update the Service to add Incident Rules and Templates for Incidents and for communications with Responders and Stakeholders.
- Templates save time filling out forms for manually-created alerts, as well as setting up different Incident workflows and communications for varying types of scenarios involving a Service.
- Incident Rules automatically generate Incidents from Alerts based on conditions that users specify.
You can create and add Templates to design both Incidents and communications for Responders and Stakeholders who need to be involved with an Incident impacting a Service. See Incident Template Creation .
- By default, Incident Rules and Templates apply to the same Responders and Stakeholders you identify in Services. You can change these Responders and Stakeholders when you create Incidents.
Other teams or individuals may need to be involved in resolving an Incident. You can add other Opsgenie users to a Service as Responders in order to notify them (by separate Alert) and give them the ability to view Incidents.
- Owner Teams - In the context of an Incident, the Team that owns an impacted Service (the Owner Team) receives the main Incident notification. It is also the only Responder that can acknowledge an Alert.
- Other Teams: In the context of an Incident, Teams that are added to an Incident as Responders, receive a Subalert notification (for the Incident). Subalerts created for Responder teams are shown under the Alerts Dashboard as normal Alerts. Subalerts contain links to the impacted Service’s Service Status page. They allow access to the same collaboration tools for the related Incident.
- Individuals: In the context of an Incident, individual Responders can be added as Responders — from a list of Users, Admins, and Owners.
When you want to provide additional experts with access to Incident and Alert information and permission to take actions on Incidents involving a Service, you can follow the directions below to add Responders.
- Click the Responders tab in an open Service on a Team Dashboard.
- Add Responders:
- Add one or more Teams as Responders by starting to type their names under Add Team(s), and then choosing from the list.
- Add individual Opsgenie Users as Responders by starting to type their names under Add Responders, and then choosing from the list.
- Click Update.
Notifications are based on Opsgenie’s Alert Notification Flow.
Opsgenie can automatically notify Stakeholders from across your organization about an Incident involving a Service (through a variety of communication channels). Just follow the Instructions below to add Stakeholders to be notified.
- Either add individual Opsgenie users as Stakeholders or configure Opsgenie Rules to select types of Stakeholders whose user profiles match specific conditions.
Start typing to add an individual Stakeholder or choose the Rule Configuration for Opsgenie to use, and then click + Add new type (to begin entering conditions that Opsgenie will match against user data).
- When Match all conditions is entered with multiple conditions, Opsgenie selects only users who match all the conditions.
For example: if the conditions include State is Virginia and City is Falls Church, then Opsgenie will only look for users in Falls Church, Virginia — and only send Stakeholder notifications to those users.
- Click Update.
Opsgenie notifies Stakeholders according to their contact method Profile settings or any overriding Notifications Template that the organization may have set.
Incident Rules allow for customization for how Incidents are automatically created. More than one Incident Rule is able to be applied to any Service, and Incident Rules can contain multiple conditions.
When you create an Incident Rule, set the conditions that filter incoming Alert data from integrated sources — and create an Incident if incoming alert data matches the conditions that are set:
- Match all alerts:
Opsgenie creates an Incident when it receives incoming alerts from any source.
- Match one or more conditions below:
Opsgenie creates an Incident if incoming alert data matches any condition specified.
- Match all conditions below:
Opsgenie creates an Incident only if incoming alert data matches all the conditions specified. If any of them fail, Opsgenie doesn't perform the action.
- To add and configure Incident Rules, click the Add Incident Rule button
- Enter information in the fields, just as an Alert Rule is created.
When conditions are specified:
1. Select a field to examine. 2. Select a condition, such as equals or contains. 3. Enter any value to compare with alert information.