SLIs, SLOs, error budgets, and other core site reliability engineering concepts.
35 cards · basic cards · AI-written, checked twice. Edit anything.
- What does SLI stand for?
- Service Level Indicator
- What does SLO stand for?
- Service Level Objective
- What does SLA stand for?
- Service Level Agreement
- What is an error budget?
- The amount of downtime or failed requests allowed within an SLO period before violating the objective
- What is availability?
- The percentage of time a service is operational and responding to requests
- What is latency?
- The time delay between a user request and the system response
- What does MTTR stand for?
- Mean Time To Recovery
- What does MTTF stand for?
- Mean Time To Failure
- What is toil?
- Repetitive, manual operational work that does not add long-term value to the service
- What is on-call?
- Being available to respond to incidents and production issues outside normal business hours
- What is a postmortem?
- A structured analysis after an incident to identify root causes and prevent recurrence
- What is blameless culture?
- An organizational approach focused on understanding systems and processes rather than assigning individual blame for incidents
- What is a runbook?
- A documented guide with step-by-step procedures for handling a specific operational task or incident type
- What is incident severity?
- A classification level that indicates the impact and urgency of an incident
- What is chaos engineering?
- Testing system resilience by intentionally introducing failures in a controlled, non-production environment