Site Reliability Practices
Key concepts from site reliability engineering.
The vocabulary of site reliability engineering: service-level indicators, objectives and agreements, error budgets, incident response and chaos engineering, with the metrics and routines around them such as MTTR, toil, postmortems, runbooks and the four golden signals.
Use it when
- You are setting reliability targets or writing an incident process.
- You need precise definitions that teams can share.
Watch out for
- The terms come from large-scale operations; scale them down for small teams rather than copying them whole.
- Metrics such as MTTR are averages and can hide long-tail incidents.
The data
16 rows
| Term | Description |
|---|---|
| SLI | Service Level Indicator: a measurable aspect of service level. |
| SLO | Service Level Objective: target value for an SLI over time. |
| SLA | Service Level Agreement: contractual consequences for missing SLOs. |
| Error Budget | Allowed amount of unreliability derived from the SLO. |
| Incident Response | Process for responding to and resolving service disruptions. |
| Chaos Engineering | Intentionally injecting failures to validate resilience. |
| MTTR | Mean time to recovery: the average time to restore service after a failure. |
| MTTD | Mean time to detect: the average time between a failure beginning and its detection. |
| MTBF | Mean time between failures: the average operating time between failures of a system. |
| Toil | Manual, repetitive, automatable operational work that scales with service size and adds no lasting value. |
| Blameless Postmortem | A written review of an incident that records timeline, causes and follow-ups without assigning personal blame. |
| Runbook | Documented steps for handling a known alert or operation so responders act consistently. |
| Canary Release | Releasing a change to a small share of traffic first and expanding only if metrics stay healthy. |
| Blue-Green Deployment | Running two identical environments and switching traffic from the old to the new, allowing instant rollback. |
| Four Golden Signals | Latency, traffic, errors and saturation: the four metrics Google's SRE book recommends monitoring for any service. |
| Capacity Planning | Forecasting demand and provisioning enough resources to meet objectives without large waste. |
Fields
The shape of this dataset, read from the data itself: every column, its type and a real value. Agents can use this to plan a query without fetching the whole document.
| Section | Field | Type | Example |
|---|---|---|---|
| data | term | string | SLI |
| data | description | string | Service Level Indicator: a measurable aspect of… |
Fetch the same bytes
The static files contain the same reference rows as the API, with no API rate limit. Live metadata, such as view counts, may differ. Use the API for content negotiation; use the static files for a cacheable snapshot.
curl "https://yjtoon.yunusemrevurgun.com/api/dataset/site-reliability-practices?format=toon"
const res = await fetch( "https://yjtoon.yunusemrevurgun.com/static-data/dataset/site-reliability-practices.toon" ); const toon = await res.text();
Rate limit: 120 requests per minute per IP, no key and no signup. API reference →