<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>On-Call on PlumePHP</title><link>https://plumephp.com/tags/on-call/</link><description>Recent content in On-Call on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://plumephp.com/tags/on-call/index.xml" rel="self" type="application/rss+xml"/><item><title>DevOps 事件响应体系：On-Call 轮值、MTTR 优化与事后复盘</title><link>https://plumephp.com/devops-incident-response/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://plumephp.com/devops-incident-response/</guid><description>&lt;p&gt;构建高可用线上系统，不仅需要稳健架构，更需要成熟的事件响应体系。团队能否在黄金时间内快速定位、止损、恢复，直接决定用户体验与业务损失。本文系统拆解 DevOps 事件响应六大核心模块，辅以可落地的配置代码。&lt;/p&gt;</description></item><item><title>告警设计与事件响应：降噪、分级、值班与事后复盘</title><link>https://plumephp.com/alerting-design-incident-response/</link><pubDate>Thu, 13 Aug 2026 12:10:00 +0800</pubDate><guid>https://plumephp.com/alerting-design-incident-response/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;好的告警是「不打扰」，坏的通知是「狼来了」。&lt;/strong&gt; 当 PagerDuty 每天响 50 次，团队 3 周内就会学会忽略所有告警——包括真正重要的那个。告警设计的终极目标是：每一次通知都值得被打断。&lt;/p&gt;</description></item></channel></rss>