Tagged articles
SLO
67 articles · Page 1 of 1
This article details a Spring Boot-based enterprise alert center architecture covering alert ingestion, standardization, four-layer convergence (deduplication, grouping, inhibition, silencing), routing, multi-channel notification, on-call scheduling, escalation policies, and closed-loop governance with SLO integration.
Alert ConvergenceKafkaPrometheus
0 likes · 38 min read

This article details how to build a proactive fault prevention system for 10M QPS architectures by modeling risk, automating change verification, observing leading signals, continuously validating defenses, and layering independent safeguards—moving beyond reactive incident response to prevent failures before they occur.
SLOcanary deploymentcapacity planning
0 likes · 36 min read

The article explains that FDEs cannot exit after training; they must verify responsibility transfer through change, troubleshooting, recovery, and upgrade drills across four responsibility tracks, ensuring nine operational artifacts have clear owners, and defines normal vs abnormal exit criteria.
FDERunbookSLO
0 likes · 31 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

This article explains why traditional monitoring fails for AI agents and introduces AgentOps—covering observability with full traces, five key SLOs (task success rate, human escalation rate, cost per successful task), a multi-stage release pipeline with shadow and canary phases, FinOps with model routing, ROI calculation including risk costs, agent lifecycle management, and a continuous improvement flywheel turning production traces into eval datasets.
AI agentsAgentOpsFinOps
0 likes · 30 min read

The article presents a layered fault-domain strategy—physical anti-affinity, logical isolation (sharding, cluster groups, swimlanes, bulkheads), cell-based architecture, chaos-engineering validation, and quantitative governance metrics—to shrink the blast radius of a ten-million-QPS system from a fixed 100% to a controllable 1/N design parameter.
High AvailabilityKubernetesSLO
0 likes · 25 min read

This article explains how to reduce fault detection latency from minutes to seconds in 10M QPS systems by implementing layered signals, combined evidence detection, distributed judgment, event normalization, and safe automation guardrails, rather than simply increasing sampling frequency.
SLOalertingdistributed systems
0 likes · 36 min read

The article explains why fixed thresholds like 80% CPU are inadequate for large-scale systems, and introduces dynamic water level management that combines load, resource, service, and resilience signals with capacity profiling, trend prediction, and action latency to drive automated scaling, scheduling, rate limiting, and degradation in a closed loop.
10M QPSAuto ScalingSLO
0 likes · 31 min read

At massive scales of millions of QPS and hundreds of metrics, static alert thresholds become noisy and hard to maintain; the article walks through a stepwise evolution—adding sustained‑duration and multi‑condition rules, adopting dynamic baselines, leveraging anomaly detection, and applying correlation, RCA and SLO burn‑rate techniques—to transform alerts from simple threshold breaches into precise, user‑experience‑focused notifications while combating alert fatigue.
AIOpsOperationsSLO
0 likes · 18 min read

The article examines how traditional percentage‑based canary releases evolve into fine‑grained, attribute‑driven deployments with session stickiness, automated SLO gating, traffic mirroring, and service‑mesh integration, highlighting five pain points, practical solutions, and the hidden prerequisites for large‑scale systems.
IstioKubernetesSLO
0 likes · 19 min read

Capacity evaluation evolves from intuition‑based estimates to rigorous modeling by measuring per‑request costs with single‑machine benchmarks, applying USL and queueing theory, bounding effective capacity with SLOs, conducting full‑link shadow traffic tests, and continuously calibrating online water‑marks to turn high‑traffic resilience into a calculable engineering decision.
SLOUSLcapacity planning
0 likes · 19 min read

This comprehensive guide explains how Pyrra extends Sloth by providing a full SLO platform for Kubernetes, covering its architecture, four SLI types, rule generation, Web UI features, alert configuration, deployment options, Grafana integration, advanced usage, common pitfalls, and a detailed comparison to help you choose the right tool for reliable service monitoring.
KubernetesPrometheusPyrra
0 likes · 24 min read

At 10 million QPS, message backlog can silently grow for hours, turning minutes of lag into hundreds of millions of undelivered messages; this article walks through a six‑stage evolution—from manual command‑line checks to SLO‑driven predictive monitoring—detailing metrics, pitfalls, and tool choices for a robust, multi‑dimensional alert system.
KafkaSLOalerting
0 likes · 21 min read

This article explains how to build highly available services by comparing single‑datacenter, same‑city active‑active, two‑city three‑center, and global multi‑active architectures, then details health‑check mechanisms, automatic failover workflows, Prometheus‑Grafana monitoring, and SLO/SLI error‑budget management with concrete code examples.
FailoverHigh AvailabilityMulti-Active Architecture
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

The article examines the memory and latency challenges of 1750‑billion‑parameter LLM inference, introduces the xLLM framework’s Slidebatching and PD‑separation scheduling strategies, and details how these techniques achieve up to 35% system‑throughput gains and 52% SLO compliance improvements in real‑world multi‑priority workloads.
AI performanceLLMPD separation
0 likes · 15 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 presents ten essential Grafana dashboards—covering SLO burn, user‑journey funnel, infrastructure USE metrics, queue lag, database health, cache hit‑rate, CDN latency, rollout guardrails, trace topology, and a command‑center view—each explained with its purpose, panel layout, and ready‑to‑use PromQL or LogQL queries.
DashboardsGrafanaPromQL
0 likes · 13 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 article explains the differences between SLA, SLO, and SLI, shows how to express user expectations as concrete service level agreements, and introduces essential high‑availability metrics such as availability percentages, MTBF, MTTR, RPO, RTO, WRT, and MTD for reliable system design.
High AvailabilityOperationsSLA
0 likes · 9 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

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 explains the definitions and relationships of SLA, SLO, and SLI, shows how to set realistic targets, presents service‑level grading, alert‑noise reduction techniques, and practical examples to help teams prepare for large‑scale events such as the 11.11 promotion.
SLASLISLO
0 likes · 20 min read

This article explains the core concepts of SLA, SLO, and SLI, demonstrates how to set realistic service level objectives, manage alert noise, and apply practical examples—including API, MQ, and scheduled task monitoring—to improve system reliability and performance during high‑traffic events like 11.11 promotions.
SLASLISLO
0 likes · 23 min read

This article explains why Site Reliability Engineering (SRE) emerged, outlines its core responsibilities, required skill set, and how SRE teams use SLOs, monitoring, and scenario drills to improve system reliability, performance, and observability in complex production environments.
DevOpsOperationsSLO
0 likes · 12 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 article details the practical steps and architectural choices NetEase Cloud Music took to improve RPC stability in a micro‑service environment, covering service discovery, connection management, cloud‑native challenges, SLO design, log governance, degradation, rate limiting, outlier detection, thread‑pool isolation, fast‑failure handling, registry optimizations, multi‑registry support, and post‑incident knowledge‑base building.
LoggingOperationsRPC
0 likes · 14 min read

This article details Bilibili's practical SLO engineering approach, covering foundational components, SLI selection, application and business level SLIs, alerting strategies, SLO‑driven quality operations, and the GOC framework for rapid fault discovery, localization, and recovery, illustrating how reliability is systematically improved.
OperationsSLOreliability engineering
0 likes · 16 min read

This article details the challenges of RPC stability in a large‑scale microservice environment and explains the architectural redesign, SLO implementation, logging governance, exception dashboards, degradation, rate‑limiting, outlier removal, thread‑pool isolation, weak registry dependencies, and post‑incident knowledge‑base practices that together ensure reliable, high‑performance service communication.
RPCSLObackend development
0 likes · 15 min read

This article explains Site Reliability Engineering (SRE) as a collaborative methodology, outlines its stability goals measured by MTBF and MTTR, details how SLI/SLO and the VALET selection guide fault detection, and shows how error budgets quantify reliability work and drive precise alerting.
ErrorBudgetMTBFMTTR
0 likes · 14 min read

The article explains how Home Depot (THD) adopted the VALET pattern language—Volume, Availability, Latency, Error, and Ticket—to unify service‑level objectives, automate data collection, build dashboards, and improve SRE practices across its massive retail and e‑commerce infrastructure.
Home DepotOperationsSLO
0 likes · 9 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 how to define, measure, and improve microservice reliability using availability metrics, the four golden signals, RED and USE methods, and practical SLI/SLO and MTTR practices, offering concrete guidance for effective service governance.
MTTRMetricsSLI
0 likes · 19 min read

This article explains how measurement (SLI/SLO), governance (architecture refactoring, MTTx), and validation (chaos engineering, disaster drills) interrelate in microservice systems, illustrating how observability drives governance actions, governance improves metrics, and validation reinforces both through continuous testing.
SLISLOarchitecture governance
0 likes · 4 min read

The article explains why microservice governance—through measurement, targeted remediation, and verification—is crucial for maintaining system stability, reducing complexity, and improving availability in large‑scale, rapidly evolving architectures.
SLOSREgovernance
0 likes · 9 min read


DevOpsJul 27, 2023 · Operations
The article introduces the Google SRE Workbook as a practical supplement to the original SRE book, explains the five core SRE foundations—including SLO, SLI, SLA, monitoring, and real‑world case studies from Google and Kingsoft Office—while also promoting an upcoming SRE‑DevOps live session.
GoogleSLISLO
0 likes · 4 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 examines Tencent's end‑to‑end SRE quality‑operation framework built on Service Level Objectives (SLO) and On‑Call, detailing industry background, problem statements, SLO management, On‑Call benefits, product architecture, large‑scale deployment, and future plans for reliability engineering.
Quality OperationsSLOSRE
0 likes · 11 min read

The article explains why striving for perfect service availability is unnecessary, outlines the cost of high reliability, shows how to measure availability and SLOs, discusses who should set SLOs, and highlights the importance of ROI when improving reliability.
ROISLOSRE
0 likes · 8 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

This article explains how Meta built SLICK, a centralized SLO/SLI platform that improves service reliability through discoverability, long‑term insights, integrated workflows, and scalable architecture, and shares real‑world examples and lessons learned from its deployment across thousands of services.
MetaSLISLO
0 likes · 13 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

The deck outlines post‑incident stability enhancements and the adoption of Service Level Objectives after the “713” fault, detailing failure analysis, reliability upgrades, monitoring practices, and the definition and operation of SLOs to sustain system quality, illustrated through architecture diagrams and reliability metrics.
SLOreliability engineeringsite reliability
0 likes · 1 min read

In this talk, Wu Yakun from Guance Cloud explains the shortcomings of traditional operations, introduces intelligent, data‑driven approaches for the cloud‑native era, and outlines how unified data collection, observability, and SLO‑based monitoring can dramatically improve fault detection and system reliability.
Intelligent OperationsSLOdata collection
0 likes · 16 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

This guide explains how to select suitable service‑level indicators (SLIs), define customer‑centric service‑level objectives (SLOs), use error budgets, and iteratively improve reliability for various system types such as services, data processing, and storage, with practical recommendations for Google Cloud environments.
Google CloudSLISLO
0 likes · 10 min read

The article outlines Bilibili’s refined SLO framework—categorizing services into four business tiers, selecting availability, latency, and freshness SLIs, setting concrete SLO targets, and employing multi‑window error‑budget and consumption‑rate alerting strategies to improve stability and provide comprehensive quality dashboards.
MetricsSLOSite Reliability Engineering
0 likes · 18 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


DevOpsJul 25, 2022 · Operations
This article provides a comprehensive overview of Site Reliability Engineering, explaining its origins, core responsibilities across infrastructure, platform, and business layers, daily tasks such as deployment, on‑call duties, SLI/SLO management, incident post‑mortems, capacity planning, and user support, as well as career advice for aspiring SREs.
InfrastructureOncallSLI
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 what Site Reliability Engineering (SRE) is, why it was created, the challenges in hiring SREs, and breaks the role into three layers—Infrastructure, Platform, and Business—detailing their duties, deployment processes, on‑call practices, SLI/SLO management, incident post‑mortems, capacity planning, user support, and career advice.
InfrastructureOncallOperations
0 likes · 21 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

This article explains the SRE role originated by Google, outlines its core responsibilities such as automation, observability, incident response, testing, capacity planning, and SLI/SLO/SLA management, and highlights the skills and cultural practices needed for reliable service operations.
SLASLISLO
0 likes · 29 min read

This article explains the origins of Site Reliability Engineering, breaks down its three main layers—Infrastructure, Platform, and Business SRE—covers day‑one and day‑2 deployment, on‑call processes, SLI/SLO design, post‑mortems, capacity planning, user support, and offers practical advice for aspiring SREs.
InfrastructureOncallOperations
0 likes · 24 min read

This article explains the role of Site Reliability Engineering (SRE), its origins at Google, the challenges of hiring, the three-layer model of infrastructure, platform, and business SRE, and provides detailed responsibilities, on‑call practices, SLI/SLO management, capacity planning, and career advice for aspiring SREs.
InfrastructureOncallPlatform
0 likes · 23 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 explains the concepts of SLI and SLO, shows how to select appropriate indicators, introduces Google’s VALET method, and provides step‑by‑step instructions for deploying the Service Level Operator on a Kubernetes cluster with Prometheus and Grafana for full SLI/SLO monitoring and alerting.
KubernetesPrometheusSLI
0 likes · 12 min read

The article explains how Home Depot (THD) adopted the VALET model—a five‑dimensional SLO language covering Volume, Availability, Latency, Error, and Ticket—to unify communication, automate data collection, and improve reliability across its massive retail and e‑commerce infrastructure.
OperationsSLOSRE
0 likes · 9 min read

The article presents a comprehensive case study of Haodf.com's transition to a micro‑service architecture, detailing the challenges of service stability and observability, the design of a unified governance platform with log‑holographic analysis, real‑time alerts, application profiling, SLO/SLA definition, and future roadmap for capacity and reliability improvements.
LoggingPlatformSLO
0 likes · 16 min read

This article explains why Site Reliability Engineering (SRE) emerged, outlines its core responsibilities, required skill set, and how it addresses reliability challenges through decoupling, SLO‑driven monitoring, and scenario‑based drills, while highlighting key observations and focus areas for modern operations teams.
SLOSREmonitoring
0 likes · 13 min read

This article explains how focusing on three key questions during incident post‑mortems, balancing business speed with system stability, and establishing clear SLOs can turn failures into actionable improvements and better fault‑tolerance strategies.
Incident ManagementOperationsSLO
0 likes · 8 min read

This article shares key insights from the book “SRE Google Operations Unveiled,” explaining Google’s infrastructure, the role of SRE, and how Service Level Objectives (SLOs) help balance reliability, cost, and innovation in modern operations.
GoogleSLOSRE
0 likes · 9 min read


ITPUBJun 9, 2017 · Operations
This article explains the fundamentals of monitoring, distinguishes traditional OPS from SRE perspectives, defines monitoring objects and metrics, introduces quantitative thinking with SLI/SLO, and presents the USE method with a MySQL example to help engineers detect and prevent failures efficiently.
MetricsOperationsSLI
0 likes · 10 min read

The article shares personal insights from reading Google’s SRE book, explaining core SRE concepts, Google’s robust infrastructure, the role of SLOs, and how they help balance cost, reliability, and innovation in modern operations.
GoogleSLOSRE
0 likes · 8 min read

This article explains the definitions of service, SLI, SLO, and SLA, outlines how to choose and measure appropriate indicators, shares best practices for setting and improving SLOs, and shows how SLAs combine objectives with consequences to manage service reliability.
OperationsSLASLI
0 likes · 11 min read
