Site reliability engineering practice
Site reliability engineering for Canadian teams.
Site reliability engineering (SRE) connects production behavior to the journeys people depend on. Set clear service objectives, understand failures and use incident learning to guide engineering work. Explore the practice, compare working models and continue into the city context relevant to your team.
What this practice covers
What SRE covers
SRE applies software and systems engineering to service reliability. Begin with a journey, the behavior that matters to its users and the people responsible for it. Indicators, objectives and failure evidence provide a basis for choosing improvements and checking their effect.
What that gives your team
- A shared definition of acceptable service behavior
- Reliability priorities grounded in evidence
- Clear owners for verification and follow-up
Service indicators and objectives
Define a service-level indicator (SLI) for a user journey, then set a service-level objective (SLO) over an agreed period. Use the objective to make reliability decisions explicit.
Error budgets and change decisions
An error budget is the unreliability allowed by an SLO over its measurement period. Use budget consumption alongside incident evidence to decide when to prioritize reliability work or proceed with change.
Dependency and failure analysis
Examine how timeouts, queues, retries and upstream failures affect the complete service journey. Identify where isolation, graceful degradation or recovery checks are needed.
Operational toil and automation
Identify repetitive operational work that is manual, reactive and offers little lasting value. Consider automation or system changes where they reduce that work without hiding risk.
Incident readiness and learning
Connect usable alerts, runbooks, escalation paths and decision owners. Turn incident findings into tracked engineering work and verify whether the changes address the failure pattern.
Production change and verification
Define the expected behavior, review signals during change and agree when to stop or roll back. Verify recovery and record remaining risks before closing the work.
How it works
How SRE work moves
Move from observed service behavior to a bounded change, then verify what happened and preserve the learning.
Define the service journey.
Identify the users, dependencies and owners. Choose indicators and objectives that describe the behavior users need, including where current evidence is incomplete.
Choose and verify a change.
Use incidents, error-budget consumption and operational toil to select an improvement. Agree on review signals, acceptance checks and rollback conditions before changing production.
Learn and keep ownership clear.
Review the result against the objective. Update runbooks, record remaining risks and assign the next engineering action to an owner.
Engagement models
Choose how we work together
Choose a working model according to the responsibility you need. Consulting supports a bounded decision; other models address team contribution, implementation or ongoing operation under agreed scope. Model pages explain those boundaries without implying staffing or coverage availability.
Assessment, architecture review and technical direction for a defined reliability decision.
ExploreA model for engineering contribution inside a client-directed team, with responsibilities and availability agreed separately.
ExploreA model for scoped production response with agreed systems, activation paths and responsibility boundaries.
ExploreA model for ownership of a bounded engineering workstream, with decision rights and handback conditions defined.
ExploreA model for a defined technical outcome with implementation scope, acceptance checks and operating handoff.
ExploreA model for ongoing maintenance, troubleshooting and improvement of named systems under agreed terms.
ExploreQuestions answered
SRE questions, answered
Practical questions about service objectives, reliability work and choosing the right working model.
What does site reliability engineering cover?
SRE connects service indicators and objectives with incident readiness, dependency behavior, operational toil and production change. The scope depends on the service journey and its owners; it is broader than a monitoring installation or a single assessment.
How is the practice different from SRE consulting?
This page explains the continuing engineering practice and the working models around it. Consulting focuses on assessment, architecture review and technical direction for a bounded decision. Explore SRE consulting in Canada for that advisory context.
Does an SLO guarantee uptime?
An SLO is a target used to evaluate service behavior and guide engineering decisions. It does not itself create a contractual service-level agreement or guarantee an outcome.
Does SRE require replacing the monitoring stack?
No. Start with the signals already available and check whether they describe the user journey and its dependencies. Add or change instrumentation when the existing evidence leaves a decision unclear.
Does this page include continuous on-call coverage?
No. Coverage windows, activation, included systems, access, escalation responsibilities and response expectations require a separate scoped agreement.
Next step
Start with the service your users depend on
Describe the production journey, the reliability concern and the owners involved. Include the evidence already available and the decision or change that needs a clearer next step.