简体   繁体   English

在哪里进行Kubernetes监控的最佳实践在哪里?

[英]Where is the best practice place to put kubernetes monitoring?

Is it best practice to place monitoring tools like Prometheus and Grafana inside a Kubernetes cluster or outside a Kubernetes cluster? 将Prometheus和Grafana之类的监视工具放置在Kubernetes集群内部还是Kubernetes集群外部是最佳实践?

I can see the case for either. 我可以看到任何一种情况。 It seems very easy to place it inside the cluster. 将其放置在群集中似乎很容易。 But that seems less robust. 但这似乎不那么可靠。

It seems people do this typically, likely they are running everything in their environment or app under K8S. 人们似乎通常会这样做,很可能是他们在K8S下在其环境或应用程序中运行所有内容。 In a bigger picture view if you have use cases outside of one specific app it likely makes sense to run this on another architecture. 从更大的角度来看,如果您在一个特定应用程序之外有用例,则可以在另一种架构上运行它。 The reason why is that Prometheus doesn't support clustering. 原因是Prometheus不支持群集。 You can write to two instances, but there is not really an HA plan for this product. 您可以写入两个实例,但实际上没有针对该产品的HA计划。 To me, that's a major problem for a monitoring technology. 对我来说,这是监视技术的主要问题。

Most organizations who use this tool heavily end up not meeting use cases which APM (transaction tracing and diagnostics) can do. 使用此工具的大多数组织最终都无法满足APM(事务跟踪和诊断)可以使用的用例。 Additionally, you'll need to deploy an ELK/Splunk type stack, so it gets very complex. 另外,您将需要部署ELK / Splunk类型的堆栈,因此它变得非常复杂。 They also find it difficult to manage and often will look towards a Datadog, SingalFx, Sysdig, or another system which can do more and is fully managed. 他们还发现管理起来很困难,经常会去找Datadog,SingalFx,Sysdig或其他可以做得更多并且受到完全管理的系统。 Naturally, most of what I have said here has cost, so if you do not have a budget then you'll have to spend your time (time=money) doing all the work. 自然,我在这里所说的大部分内容都是有成本的,因此,如果您没有预算,那么您将不得不花费时间(时间=金钱)来完成所有工作。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM