Tagged articles
Error Budget
26 articles · Page 1 of 1
This article defines software reliability per ISO/IEC 25010, distinguishes it from availability and stability, and details five operational concerns — correct user-visible results, change management, blast radius, detection/recovery speed, and failure semantics — with concrete distributed-systems patterns like idempotency, fault domains, burn-rate alerting, and fault injection.
CAP theoremError BudgetIdempotency
0 likes · 34 min read

This article uses a service release scenario to distinguish DevOps and SRE, explaining how DevOps emphasizes collaborative delivery pipelines and feedback loops while SRE focuses on service-level objectives, error budgets, and eliminating toil through software engineering, showing both perspectives can apply to the same automation.
DevOpsError BudgetSLI
0 likes · 16 min read

The article explains how a self‑healing platform improves SRE reliability by reducing MTTR, preserving error‑budget, automating high‑impact incident remediation, enforcing safety guardrails, and shifting team focus from firefighting to sustainable reliability engineering.
Error BudgetMTTRSLO
0 likes · 10 min read

This article provides a comprehensive breakdown of Google's Site Reliability Engineering (SRE) framework, covering its origins in DevOps, core principles like error budgets and SLI/SLO/SLA, key reliability metrics (MTTR, MTBF), monitoring methodologies (Golden Signals, USE, RED), incident response workflows, troubleshooting techniques, and disaster recovery architecture levels.
Error BudgetGoogle SRESLI/SLO/SLA
0 likes · 12 min read

The article explores how large organizations transform chaotic, tool‑centric observability practices into a platform capability driven by SLOs, error budgets, GitOps, and service‑mesh telemetry, using real‑world case studies to show measurable improvements in reliability, deployment speed, and team culture.
DORA metricsError BudgetSLO
0 likes · 25 min read

This guide explains the SRE framework—SLA, SLO, SLI hierarchy, golden signals, error budgets, and DORA metrics—showing how to instrument a Python app with OpenTelemetry, query Prometheus, avoid common pitfalls, and adopt a cultural and technical process that balances feature velocity with system stability.
DORAError BudgetMetrics
0 likes · 18 min read

This article traces Google Site Reliability Engineering from its 2003 inception addressing scale crises, through organizational growth, core principles, team structures, and recent security integrations, showing how SRE transformed operations into a software‑engineering discipline that drives reliable, scalable digital services.
Error BudgetGoogleOperations
0 likes · 13 min read

This guide explains how SRE teams should collaborate early in the software development lifecycle to define Service Level Indicators (SLIs), set realistic Service Level Objectives (SLOs) and Service Level Agreements (SLAs), and integrate observability signals, error budgeting, risk management, and incident handling into reliable operations.
Error BudgetIncident ManagementOperations
0 likes · 13 min read

This article explains how SRE teams should collaboratively define Service Level Indicators, Objectives, and Agreements, and then cover reliability, performance, observability signals, error budgeting, risk management, incident handling, and the engineering work needed to build robust cloud‑native platforms.
Error BudgetSLISLO
0 likes · 13 min read

The article explains how early detection and preventive measures—such as comprehensive monitoring, rate limiting, chaos testing, and proper SLOs—are essential for maintaining system stability and avoiding larger incidents, drawing on SRE principles and the incident triangle theory.
Error BudgetIncident PreventionOperations
0 likes · 4 min read

This article details how 58 Group’s cloud authentication service introduced an observability framework—optimizing logs, employing distributed tracing, defining SLO/SLA metrics, and implementing burn‑rate alerts—to improve fault detection, reduce false alarms, and achieve faster root‑cause analysis across the system.
Distributed TracingError BudgetSLO
0 likes · 16 min read

This article details Ant Group's practical implementation of Service Level Objectives (SLO) and AIOps to achieve fine‑grained operations, covering SLO fundamentals, health‑score architecture, GitOps‑based data pipelines, error‑budget alerting, AI‑driven anomaly detection, fault localization techniques, and real‑world case studies on dashboards, Kubernetes SLOs, and emergency response workflows.
AIOpsError BudgetKubernetes
0 likes · 38 min read

This guide explains how SRE teams should define service level indicators, objectives, and agreements, design reliable and observable architectures, manage error budgets, assess risks, handle incidents, and integrate development practices to improve system stability and performance.
Error BudgetSLISLO
0 likes · 15 min read

This article explains the fundamentals of Site Reliability Engineering, detailing how SRE combines development and operations to improve stability through metrics like MTBF and MTTR, the roles of SLI/SLO, the VALET selection method, and the practical use of error budgets for quantifying work and guiding alerts.
Error BudgetMTBFOperations
0 likes · 14 min read

This article outlines Bilibili's end‑to‑end SLO framework, covering metric selection, SLO definition, error‑budget calculation, alerting strategies, operational workflows, and lessons learned from real‑world deployments.
Error BudgetSLOSRE
0 likes · 28 min read


21CTONov 15, 2022 · Operations
This article explains how SRE teams should define Service Level Indicators, Objectives and Agreements, manage reliability, performance, saturation and observability, use proper metrics and tracing, handle error budgets, assess risks, and implement effective incident and project management to create robust, cloud‑native services.
Error BudgetSLASLI
0 likes · 14 min read

This article outlines the core reliability principles of the Google Cloud Architecture Framework, explaining key terms such as SLI, SLO, error budget, and SLA, and describing design and operational guidelines for defining reliability goals, building observability, ensuring high availability, creating robust processes, effective alerting, and collaborative incident management.
Error BudgetOperationsSLI
0 likes · 12 min read

Bilibili adopted Google‑SRE SLO practices—selecting SLIs, defining availability and latency targets, grading services, and tracking error budgets—but encountered costly grading inconsistencies, hidden error detection, and inaccurate business‑level metrics, leading them to realize SLOs are chiefly valuable for early alerting rather than exhaustive reporting.
Error BudgetOperationsSLO
0 likes · 21 min read

This article explains the motivations behind Site Reliability Engineering (SRE), outlines its strategic goals, defines key concepts such as SLI, SLO, SLA and error budget, introduces the four golden metrics for monitoring distributed systems, and provides practical guidance on building, operating, and continuously improving an SRE practice.
Error BudgetSLISLO
0 likes · 14 min read

This article explains Site Reliability Engineering (SRE), its core concepts such as SLI, SLO, SLA, error budgets, risk analysis, the four golden metrics, and practical steps for developing, piloting, and operating reliable services with monitoring, automation, and post‑mortem practices.
Error BudgetSLISLO
0 likes · 15 min read

This article explains Site Reliability Engineering (SRE), covering its origins, core responsibilities, key concepts such as SLI/SLO/SLA and error budgets, the four golden monitoring metrics, risk analysis, and practical guidance on building reliable services using tools like Prometheus and Grafana.
Error BudgetOperationsSLI
0 likes · 15 min read

The article traces the evolution from a rudimentary deployment workflow in a small startup to a mature, Google‑inspired Site Reliability Engineering (SRE) approach, explaining SRE definitions, team duties, error‑budget concepts, key reliability metrics (SLI/SLO/SLA), monitoring implementation with OpenTSDB, and best‑practice alerting rules.
Error BudgetSLISLO
0 likes · 7 min read

This article outlines a comprehensive SRE fault‑management framework, covering core responsibilities, stability metrics such as MTBF and MTTR, detailed pre‑, during‑, and post‑incident processes, monitoring, capacity planning, disaster‑recovery, error budgeting, organizational support, and future trends like AIOps and chaos engineering.
Error BudgetMTBFMTTR
0 likes · 30 min read

This article examines the inherent tension between operations and development, explains Google’s error‑budget and SLO approach, and shares practical DevOps, on‑call, automation, and talent strategies that help ops teams improve efficiency while maintaining product reliability.
Error BudgetOperationsRecruitment
0 likes · 9 min read

This article examines the tension between operations and development teams, explains Google's SRE error‑budget model, and shares practical reflections on engineering ops, on‑call rotation, automation, and talent development to achieve a sustainable balance between product stability and rapid innovation.
DevOpsError BudgetSRE
0 likes · 8 min read

The article explains Google’s Site Reliability Engineering (SRE) philosophy, how it empowers software engineers to automate operations, the balance between development and reliability, the concept of error budgets, and the cultural shift that turned DevOps into a core practice for large‑scale services.
DevOpsError BudgetOperations Automation
0 likes · 10 min read
