英文:
OTEL Collector deployment on a Kubernetes cluster
问题
我们计划在Kubernetes上实施OTEL，但似乎在涉及K8s时找不到正确的答案。
问题是，我是否需要/应该在每个节点上安装收集器代理，还是只需为整个集群安装一个运算符。
对于OTEL和K8s，最佳方法是什么？
英文:
We are planning to implement OTEL with Kubernetes and I can't seem to find the correct answer when it comes to k8s.
The question is, do I need/should have the collector agent on each node or just have an Operator for the whole cluster.
What is the best method for OTEL and K8s?
答案1
得分: 1
你可以将一个收集器部署为一个 DaemonSet，这样不仅可以收集来自 Pod 的指标，还可以根据你想要收集的指标，潜在地收集 kubelet 和其他节点本地进程的指标。
另外，如果你有其他远程监控解决方案，并且它们可以读取/接受来自收集器的指标，那么你可以将一个 sidecar 容器部署到你想要监视的特定命名空间。
英文:
You could deploy a collector as a DaemonSet, which could allow you to not only collect metrics from pods, but also potentially the kubelet and other node-local processes, depending on what metrics you want to gather.
Otherwise, if you have other remote monitoring solutions, and they can read/accept metrics from a collector, then you can deploy a sidecar container into specific namespaces that you want to monitor.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论