SR Ops user guide
The SR Ops guide will help you become skilled at creating and administering teams, services, and integrations.
User process in SR Ops
| Step | Description | See this |
|---|---|---|
Set up an SR Ops team |
Set up a team and define services for the team. Teams are responsible for the issues that occur in the associated services. | Set up an SR Ops team |
Set up on-call schedule and escalation policies |
Create an on-call schedule for your team to ensure to ensure that dedicated support team members are available to resolve issues as they arise. You can set up an escalation policy for your team so that at least one team member is engaged in incident response. | Create an on-call schedule for your team |
Create services and configure service relationships |
Use a map canvas to add, configure, and arrange services. You can add child services that depend on parent services. | Create services and configure relationships between them |
Establish SLO & error budget for services |
Establish you goal on how well your service should operate. Also specify the maximum amount of time that a technical system can fail without contractual consequences. | Create a reliability indicator |
Integrate service with an APM tool |
Set up the integration with an Event Management Application Performance Management (APM) tool — the push connector that sends alerts to SR Ops. | Integrate with an APM tool |
|
Set up alert rules |
Alerting rules allow you to define alert conditions. Set up alert rules for each APM tool to define the conditions when the APM tool should send notifications to SR Ops. | Specific integrations in SR Ops |
Register change |
Create a change request to propose an alteration in a supported configuration item (CI). | Create a change request from a service |