知识卡片
自动埋点的容量代价
自动埋点使开启遥测很容易,但默认启用的大量指标未必都服务于实际问题。水平扩容后,每个实例重复发出数据,增加存储与查询负载。应检查自动采集的用途和成本,再决定保留、聚合或删除;“默认能采到”不是“必须长期保存”的理由。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Cloud Native Challenges in the Real World · 查看原书依据
A key factor contributing to this uncontrolled data growth is automatic instrumentation. Consider the example of NGINX: installing the NGINX ingress controller in a cluster is straightforward, and enabling observability data generation is as simple as activating a configuration setting. However, this ease of use comes with a downside. The activation of automatic instrumentation often results in the creation of numerous unnecessary metrics, leading
参考来源
- 位置:《Cloud Native Observability》第02章《Cloud Native Challenges in the Real World》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Observability/_epub-src/ch02.html#impact_of_uncontrolled_data_growth_on_system_perfo)
- 结论依据:原文NGINX自动启用指标加上水平扩容造成数据集膨胀和查询性能挑战,说明易启用不等于全量数据有用。
- 原始内容:A key factor contributing to this uncontrolled data growth is automatic instrumentation. Consider the example of NGINX: installing the NGINX ingress controller in a cluster is straightforward, and enabling observability data generation is as simple as activating a configuration setting. However, this ease of use comes with a downside. The activation of automatic instrumentation often results in the creation of numerous unnecessary metrics, leading