Google SRE
The Site Reliability Engineering methodology and practice framework introduced by Google, which applies software engineering methods to operations, emphasizing automation, monitoring, and change management.
Core Facts
Timeline (last 90 days)
SEV-0 is the highest level in incident severity classification systems, originating from Google SRE practices and widely borrowed.
The industry often refers to ITIL's incident management practices and Google SRE's Incident Command System to build fault management processes, and the latter emphasizes designating an Incident Commander, clarifying role divisions, and the cadence of external communication.
Google SRE material on distributed scheduling points out that when a launcher may fail between launching and observing completion, recovery requires idempotent operations or a way to query the external system's state, and that a double launch is harder to undo than a skipped launch.
According to the Google SRE system, an SLI (service level indicator) is a precise quantitative measure of some aspect of a service.
P99 latency is generally a key metric for assessing the true experience of production systems; Google's SRE framework calls it tail tolerance and recommends explicitly specifying P95 or P99 latency upper bounds in SLOs.
The Incident Commander role originated from Google's SRE framework and is one of the core designs for large-scale production incident response
The error budget concept originated from Google SRE practices, quantifying reliability targets as an upper limit on allowable downtime and establishing a quantifiable trade-off framework between stability and release velocity.
MTTR是DORA四大关键指标之一，也是Google SRE体系中衡量服务可靠性的核心度量
In Google's SRE culture, the blameless post-mortem is one of the core principles, focusing on improving systems rather than holding individuals accountable.
All Facts (9)
In Google's SRE culture, the blameless post-mortem is one of the core principles, focusing on improving systems rather than holding individuals accountable.
65%UnverifiedSEV-0 is the highest level in incident severity classification systems, originating from Google SRE practices and widely borrowed.
50%UnverifiedThe industry often refers to ITIL's incident management practices and Google SRE's Incident Command System to build fault management processes, and the latter emphasizes designating an Incident Commander, clarifying role divisions, and the cadence of external communication.
50%UnverifiedGoogle SRE material on distributed scheduling points out that when a launcher may fail between launching and observing completion, recovery requires idempotent operations or a way to query the external system's state, and that a double launch is harder to undo than a skipped launch.
50%UnverifiedAccording to the Google SRE system, an SLI (service level indicator) is a precise quantitative measure of some aspect of a service.
50%UnverifiedP99 latency is generally a key metric for assessing the true experience of production systems; Google's SRE framework calls it tail tolerance and recommends explicitly specifying P95 or P99 latency upper bounds in SLOs.
50%UnverifiedThe Incident Commander role originated from Google's SRE framework and is one of the core designs for large-scale production incident response
50%UnverifiedThe error budget concept originated from Google SRE practices, quantifying reliability targets as an upper limit on allowable downtime and establishing a quantifiable trade-off framework between stability and release velocity.
50%UnverifiedMTTR是DORA四大关键指标之一，也是Google SRE体系中衡量服务可靠性的核心度量
50%