Sre
19 items tagged with "sre"
Best Practices13
Google Site Reliability Engineering Practices
Codified principles (error budgets, toil elimination, SLIs/SLOs) for operating large-scale services reliably.
RED & USE Monitoring Methodologies
Standard approaches for selecting golden signals (Rate-Errors-Duration / Utilisation-Saturation-Errors).
Chaos Engineering Principles
Run controlled experiments to build confidence in system resilience under turbulent conditions.
Service Level Objectives (SLOs)
A target reliability level for a service, expressed as a measurable percentage of good events over a window, used to balance reliability against feature velocity.
Error Budgets
The allowed amount of unreliability derived from an SLO (100% minus the target), spent deliberately to balance new features against reliability work.
The Four Golden Signals
Google SRE's four core metrics for monitoring a user-facing system: latency, traffic, errors, and saturation.
Symptom-Based Alerting
Alerting on user-visible symptoms (errors, latency, SLO burn) rather than internal causes, to reduce noise and page only on things that matter.
Incident Management Best Practices
A structured process for detecting, coordinating, and resolving outages with clear roles, communication, and severity levels to restore service quickly.
Blameless Postmortems
Post-incident reviews focused on systemic causes and learning rather than individual blame, producing concrete action items to prevent recurrence.
On-Call Best Practices
Sustainable on-call practices covering rotation design, escalation, actionable alerts, runbooks, and workload limits to keep services reliable without burning out engineers.
Runbook Automation
Codifying operational procedures as automated, repeatable workflows so common incident responses and maintenance tasks run reliably with less manual toil.
Capacity Planning
Forecasting future demand and provisioning resources ahead of need, combining organic growth, launches, and headroom to avoid both outages and waste.
Toil Reduction
Systematically identifying and eliminating repetitive, manual, automatable operational work so engineers can spend time on durable engineering instead.
Playbooks4
OpenTelemetry Observability Rollout Playbook
A program to instrument services with OpenTelemetry for unified traces, metrics, and logs, replacing fragmented vendor-specific monitoring.
SRE and SLO Program Playbook
A program to adopt Site Reliability Engineering with service level objectives, error budgets, and toil reduction to balance reliability and velocity.
Incident Management Program Playbook
A program to build structured incident response with clear roles, severity levels, blameless postmortems, and continuous learning.
Chaos Engineering and Resilience Program Playbook
A program to validate system resilience through controlled fault injection, hypothesis-driven experiments, and game days.
FAQs2
What is an SLO, SLI, and error budget?
An SLI (Service Level Indicator) is a measured metric of service health, such as request success rate or latency. An SLO (Service Level Objective) is ...
What is chaos engineering?
Chaos engineering is the practice of deliberately injecting failures into a system to test its resilience before real incidents expose weaknesses. Tea...