Opsgenie Teams have 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.

About Services

Opsgenie Services has two main type: Internal and External Services. Internal 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.

External Services displays public Statuspage page information in Opsgenie. Within the External services, any public Statuspage can be easily added to know the moment an incident’s reported and set alerting rules to respond quickly.

Incidents and Incident Management workflows revolve around outages and other events that impact a Team’s Services. Because of this, the Services area of a Team Dashboard contains controls for that Service, including: Incident Rules, Incident Templates, Responders, and Stakeholders


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.