• Products
  • Get started
  • Documentation
  • Resources

Manage internal services


Working with Internal Services

To add, view, edit, and delete Internal services owned by your own Team, access the Services tab on the Team’s Dashboard. Services your team is subscribed is also listed on the Team’s Dashboard:

Internal services

To view information about an existing Service that is owned by another Team, go to the Services:

Services

Adding and Editing Internal Services

To create an Internal Service, click the Add Service on a Team’s Dashboard via the Services tab. Define Service NameService Description, and Service Tags.

Service Limitations

  • At most 1000 services can be created for an Opsgenie team. At most 2000 services can be created for an Opsgenie account.

  • Service name cannot be longer than 512 characters.

  • Service description cannot be longer than 4096 characters.

Add service

Or you can add a service via Services page if your role allows:

Add service
Add internal service

After you have added an Internal Service to a Team, you should update the Service to add Incident Rules for Incidents and for communications with Responders and Stakeholders.

  • Incident Rules automatically generate Incidents from Alerts based on conditions that users specify.

Responder Templates

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 UsersAdmins, 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.

To add Responders to a Service

  1. Click the Responders tab in an open Service on a Team Dashboard.

  2. Add Responders:

    1. Add one or more Teams as Responders by starting to type their names under Add Team(s), and then choosing from the list.

    2. Add individual Opsgenie Users as Responders by starting to type their names under Add Responders, and then choosing from the list.

  3. Click Update.
    Notifications are based on Opsgenie’s Alert Notification Flow.

 

Add responder to service

 

Stakeholder Templates

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.

To add stakeholders to be notified about an incident

  1. 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).

    1. 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.

  2. Click Update.
    Opsgenie notifies Stakeholders according to their contact method Profile settings or any overriding Notifications Template that the organization may have set.

 

Stakeholders tab

Adding Incident Rules to Internal Services

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.

Edit incident rule
  1. To add and configure Incident Rules, click the Add Incident Rule button

  2. 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.

Incident rules

 

Rule conditions

 

Last modified on Apr 1, 2021
Cached at 3:37 PM on Apr 12, 2021 |

Additional Help

Ask the Community