Reliability Engineering & Tools
4 entriesPrinciples and the tools that put them into practice.
AI-assisted Operations
3 entriesUsing AI for incident response and root cause analysis.
Incidents & Resilience
5 entriesResponding to failure and testing for it.
Learn SRE
1 entriesFree canonical references.
SRE Books, Conferences & Communities
5 entriesCore SRE reading and events.
Related Pages
19 entriesNeighbouring directories.
Frequently Asked Questions
What is site reliability engineering?
SRE applies software engineering to operations: teams define service level objectives, automate toil and use error budgets to balance reliability against feature velocity.
What is an SLO?
A service level objective is a target for a service level indicator such as availability or latency, for example 99.9% of requests succeeding over 30 days.
What is an error budget?
It is the allowed amount of unreliability implied by the SLO; when it is spent, teams slow feature releases to focus on reliability.
How does SRE differ from DevOps?
DevOps is a culture and set of practices for delivery; SRE is a specific implementation focused on reliability targets, automation and incident discipline.
Where do AI tools help?
AI SRE tools correlate alerts, summarise incidents and suggest root causes; see the AI SRE pages.
What is SRE?
Site reliability engineering applies software engineering to operations, using SLOs, error budgets, automation and blameless postmortems. Google's SRE book is the foundation.
Where do SREs learn and meet?
SREcon, SRE Weekly and incident-learning communities.
Which additional references does this page add?
The section 'SRE Books, Conferences & Communities' lists Google SRE Book, Google SRE Workbook, SREcon (USENIX), SRE Weekly, OpenSLO.
Which links may need a manual click?
Links were rechecked in October 2026. This page links mainly to related directories on this site, including the new SLO & Error Budgeting Tools, AIOps Platforms and Top AI SRE Tools pages.