知识卡片
事件的八个生命周期阶段
事件有彼此不同的存在阶段。作者给出的典型序列是:前置条件(架构与结构性决策为故障埋下条件)、触发(某件事产生用户可见影响)、故障开始(至少部分用户、部分功能明显受影响)、检测(服务方通过自动监控或外部用户投诉得知)、排障(弄清发生了什么并设计修复办法)、缓解(找出最快且风险最低的步骤先止住最坏影响,轻则贴公告说明部分功能异常,重则彻底停用服务)、解决(修复根因、服务恢复正常)、跟进(复盘、沉淀待修项并执行)。把阶段显式列出来的价值在于:它让「现在到底在哪个阶段」成为可沟通的事实,而不是各人心里不同的猜测;也能暴露 ML 系统的特殊困难——故障常常在检测之前几周就已开始,缓解与解决有时同时发生,甚至根本不存在清晰的缓解阶段。后续三个故事都会按这套阶段逐一复盘,读者可以对照看每个阶段在 ML 场景下如何变形。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Incident Response · 查看原书依据
Life of an Incident Incidents have distinct phases of their existence. Although people of good will may differ on the specifics, incidents probably include states such as the following: Pre-incident Architectural and structural decisions that set the conditions for the outage. Trigger Something happens to create the user-facing impact.
参考来源
- 位置:《Reliable Machine Learning》第11章《Incident Response》(源文件:extracted/Reliable Machine Learning/_epub-src/OEBPS/ch11.xhtml)
- 结论依据:原文明确阐述该主题,并给出定义、实践或反例。
- 原始内容:Life of an Incident Incidents have distinct phases of their existence. Although people of good will may differ on the specifics, incidents probably include states such as the following: Pre-incident Architectural and structural decisions that set the conditions for the outage. Trigger Something happens to create the user-facing impact.