這個案例的核心責任是提供「觀測不該跟系統共命運（跟被觀測系統一起在同一波壓力下失效）」的權威根據。

觀察

Google SRE Book「Monitoring Distributed Systems」章明文：「the elements of your monitoring system that direct to a pager need to be very simple and robust」；「Your monitoring system is as important as any other service you run」；「Like all software systems, monitoring can become so complex that it’s fragile, complicated to change, and a maintenance burden」、因此「design your monitoring system with an eye toward simplicity」、「The rules that catch real incidents most often should be as simple, predictable, and reliable as possible」；並主張「maintaining distinct systems with clear, simple, loosely coupled points of integration is a better strategy」。

判讀

觀測系統若跟被觀測系統一樣複雜、依賴一樣多，它會在同樣的壓力下一起變 fragile。故意把「叫醒人類」那條路徑做到最簡、最少 moving parts，本質是把觀測的失效域跟生產失效域切開。要注意引用邊界：SRE Book 沒有「monitoring 必須比它監控的系統依賴更少 / 不共享失效域」的字面原句 —— 可直引的是「simple and robust」「fragile」「loosely coupled」，「共命運 / shared fate」是從這些原句推導的框架、正文標明推導、不假託為 SRE Book 直引。

對應大綱

觀測共命運章「失效模式」段（總論、權威錨點）。

引用源

• Monitoring Distributed Systems（Google SRE Book） — 一手官方全文。已 WebFetch 驗證（兩次交叉確認原句）。

二手來源與狀態標注

「共命運 / 不共享失效域」為從 simple/robust/fragile/loosely-coupled 推導的框架、非 SRE Book 明文。