SLO/OpenSearch on K8s Platform
Status: draft
Organizational
Service
(Varies) Any OpenSearch cluster hosted on the OpenSearch on K8s platform .
Teams
| Term | Definition |
|---|---|
| Platform owner | The team that owns OpenSearch on Kubernetes (currently Data Platform SRE) |
| Application owner | The team or person who owns an application which uses OpenSearch on Kubernetes as a backing store. |
Architectural
Environmental dependencies
dse-k8s clusters in eqiad and codfw datacenters
Service dependencies
Same
Client-facing
Clients
The "application owners" as defined above.
Request Classes
What are the request classes, and how is a request classified? If your service has only one request class, delete this section.
Service Level Indicators (SLIs)
What are the service level indicators? Copy a selection from the instructions, filling in the blanks.
Operational
Monitoring
How is the service monitored?
Documented here
Troubleshooting
How complex is the service to troubleshoot?
Deployment
How is the service deployed?
Service Level Objectives
Realistic targets
What are the realistic targets for each SLI? Why?
Lower than 95%, because the platform owner (DPE SRE) is not staffed outside of business hours.
Ideal targets
What are the ideal targets for each SLI? Why?
95%, because the platform owner (DPE SRE) is not staffed outside of business hours.
Reconciliation
Reconcile the realistic vs. ideal targets, documenting any decisions made along the way.
Once the SLO is final, consider collapsing the above three sections.
What are the agreed-upon SLOs, for each SLI and each request class?
Each SLO should be defined in Pyrra; include links here.