Tagged articles
on-call
20 articles · Page 1 of 1
This article explains monitoring systems through MTTF/MTTR availability math, three telemetry signals (metrics, logs, traces), Google's four golden signals, cardinality pitfalls, structured logging, trace sampling strategies, wide events, dashboard best practices, symptom-based alerting, synthetic testing, RUM, predictive monitoring, on-call organization, and AI-assisted observability levels.
AI observabilityMTTFMTTR
0 likes · 15 min read

This article establishes a four-tier alert classification framework and provides concrete PromQL queries for user-facing errors, latency percentiles, saturation signals, and resource risks, showing how to route only actionable alerts via Alertmanager while demoting noisy host metrics to dashboards.
AlertmanagerPromQLPrometheus
0 likes · 35 min read

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 evolve ad-hoc incident response into a standing war room mechanism for 10M QPS systems, covering six key roles, a full lifecycle with trigger/exit criteria, fixed 10-minute decision cadences, reversible mitigation constraints, evidence-linked tooling, and a three-phase rollout with drills and templates to build organizational muscle memory.
10M QPShigh-scale systemsincident command
0 likes · 28 min read

This article details a comprehensive framework for transforming ad-hoc incident response into a structured, repeatable process for high-concurrency systems, covering incident state machines, role definitions, severity grading, first 15-minute checklists, timeline management, automation, blameless postmortems, and evolutionary stages from visibility to organizational learning.
Operationsautomationblameless culture
0 likes · 30 min read

The article examines why a single‑level alerting approach fails at massive scale, outlines the five practical limitations it creates, and presents a step‑by‑step framework—classification matrix, routed channels, SLA timers, escalation policies, and on‑call discipline—to allocate limited human attention to the most business‑critical incidents.
OperationsSLAalert tiering
0 likes · 18 min read

This article presents a complete SRE on‑call handbook that defines alert severity levels, provides concrete Prometheus Alertmanager configurations, outlines a step‑by‑step response flow, details war‑room roles, escalation paths, handoff checklists, post‑mortem procedures, and dozens of ready‑to‑use templates to reduce MTTR and improve reliability.
OperationsRunbookSRE
0 likes · 27 min read

This handbook presents a complete, two‑year‑tested SRE on‑call process that defines alert severity tiers, response requirements, escalation paths, War‑Room roles, handoff schedules, post‑mortem procedures, and provides ready‑to‑use configuration snippets, checklists and templates to reduce MTTR and repeat incidents.
OperationsRunbookSRE
0 likes · 26 min read

This article shares a software engineer’s eight‑year journey, detailing concrete habits like weekly work logs, on‑call participation, cautious tech adoption, internal team rotation, writing, and interview preparation, offering actionable advice for junior and mid‑level developers seeking rapid career advancement.
Interview PreparationTechnical Writingcareer development
0 likes · 24 min read

This article compiles diverse Zhihu comments on the reality of 24 × 7 on‑call duties, contrasting exaggerated myths with practical team‑based solutions, global shift models, backup strategies, and actionable tips for improving operations without sacrificing personal life.
SREon-callteamwork
0 likes · 7 min read

A collection of Zhihu answers reveals how large tech firms use multi‑timezone teams for 24/7 on‑call coverage, while smaller companies rely on rotation, backup, and automation to keep operations manageable, showing that constant availability need not be a nightmare.
24x7incident managementon-call
0 likes · 8 min read

This article examines the challenges of traditional on‑call duty systems for operations teams, proposes an SRE‑inspired rotation model that involves developers, defines concrete KPI targets, and describes how automation and chat‑bot tools can streamline incident response and reduce internal friction.
KPIOperationsSRE
0 likes · 12 min read

This article explores how Tencent builds and practices its SRE quality operation system, focusing on On‑Call incident management, standardized channels, alert handling, data quality models, and the resulting improvements in reliability, MTTR reduction, and data‑driven decision making.
OperationsSREobservability
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

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 how Google SRE limits weekly alerts to ten, compares it with typical Chinese internet operations teams, and provides practical strategies—including on‑call scheduling, alert escalation, automation, dashboard optimization, and team management—to dramatically reduce alert volume and improve incident response.
OperationsSREalert management
0 likes · 15 min read

This article shares concrete SRE‑inspired techniques—duty‑roster scheduling, tiered alert handling, automation safeguards, dashboard focus on top‑3 alerts, time‑based filtering, and systematic code review—to dramatically reduce daily alarm volume while keeping on‑call teams motivated and effective.
SREalert optimizationincident management
0 likes · 15 min read

This article offers eight practical operations‑team strategies—inspection, monitoring alerts, capacity planning, network restrictions, risk pre‑plans, data backup, on‑call mechanisms, and staying connected—to ensure system stability and enjoy the Golden Week holiday without incidents.
HolidayOperationsbackup
0 likes · 4 min read

This article shares practical insights from Google SRE on on‑call duty, covering why on‑call is needed, common challenges, effective scheduling, evaluation methods, and actionable tips to improve team resilience and reduce stress for operations engineers.
OperationsSREincident management
0 likes · 9 min read

This article outlines a systematic approach to onboarding and training new Site Reliability Engineers, covering trust building, readiness assessment, diverse learning methods, structured curricula, on‑call milestones, project‑focused work, reverse‑engineering skills, statistical thinking, and improvisation techniques to develop high‑performing SRE teams.
OperationsSREon-call
0 likes · 17 min read
