知识卡片
云原生的动态复杂性
云原生把容器、微服务等作为可伸缩的构件,服务间依赖会传播故障,实例动态变化又使短暂失败成为常态。排障必须区分起因与级联症状,并保留实例消失前的上下文;增加采集量本身不能解决依赖关系不清的问题。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- The Cloud Native Impact on Observability · 查看原书依据
Cloud native systems are commonly interlinked (e.g., via inter-service calls directly or over a service mesh), causing most failures to be cascading in nature and making it difficult to observe the exact cause versus a symptom of a failure. For example, Slack experienced a major incident caused by a cascading failure on February 22, 2022.
参考来源
- 位置:《Cloud Native Observability》第01章《The Cloud Native Impact on Observability》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Observability/_epub-src/ch01.html#challenges_of_cloud_native_observability)
- 结论依据:原文分别列出互联导致级联、动态带来暂态失败、小单元增多遥测三种挑战,支撑复杂性来自云原生优点而非单一工具不足。
- 原始内容:Cloud native systems are commonly interlinked (e.g., via inter-service calls directly or over a service mesh), causing most failures to be cascading in nature and making it difficult to observe the exact cause versus a symptom of a failure. For example, Slack experienced a major incident caused by a cascading failure on February 22, 2022.