知识卡片

普通读书笔记卡 · 4598

诊断需区分网格与工作负载

理解等级:高级

引入网格后出现错误,可能来自应用、配置或代理,需结合请求头、错误标记及诊断工具定位。把所有失败都归咎于新基础设施会妨碍学习,也不能据此证明网格本身没有缺陷。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 采用结论 · 查看原书依据

      Inspect service request headers with your service mesh and annotate when requests fail to help you identify whether the failure is in your workloads or the service mesh. Show immediate value. Observability signals are a great way of doing so, and Linkerd makes this simple: $ linkerd stat deploy --from web NAMESPACE NAME MESHED SUCCESS RPS LATENCY_P50 _P95 _P99 emojivoto emoji 1/1 100.00% 2.0rps 1ms 2ms 2ms emojivoto voting 1/1

    参考来源

    - 位置:《The Enterprise Path to Service Mesh Architectures, 2nd Edition》第05章《采用结论》(来源项目book-sources;源文件:extracted/The Enterprise Path to Service Mesh Architectures, 2nd Edition/_epub-src/OEBPS/ch05.xhtml) - 结论依据:原文在此说明该机制、范围或取舍;本卡保留其历史语境,不将预测、产品状态或命令作为当前已核验事实。 - 原始内容:Inspect service request headers with your service mesh and annotate when requests fail to help you identify whether the failure is in your workloads or the service mesh. Show immediate value. Observability signals are a great way of doing so, and Linkerd makes this simple: $ linkerd stat deploy --from web NAMESPACE NAME MESHED SUCCESS RPS LATENCY_P50 _P95 _P99 emojivoto emoji 1/1 100.00% 2.0rps 1ms 2ms 2ms emojivoto voting 1/1