[英]Monitoring GKE on Stackdriver and Istio
I noticed that it is possible to have a pretty in depth view into the k8s cluster running on GKE via Stackdriver.我注意到可以通过 Stackdriver 深入了解在 GKE 上运行的 k8s 集群。 How does this differ from deploying Istio in GKE clusters?
这与在 GKE 集群中部署 Istio 有何不同? Does Istio provide more detailed information that Stackdriver is not able to do so?
Istio 是否提供了 Stackdriver 无法提供的更详细信息?
Stackdriver is used for logging/service monitoring which provides performance and diagnostics data in Kube.netes whereas Istio is a Service Mesh. Stackdriver 用于日志记录/服务监控,它在 Kube.netes 中提供性能和诊断数据,而 Istio 是一个服务网格。
Service Monitoring in an opinionated infrastructure helps monitor how end users perceive the systems thereby drill down to the infrastructure level whenever necessary.固执己见的基础架构中的服务监控有助于监控最终用户如何看待系统,从而在必要时深入到基础架构级别。
Useful Context about StackDriver from Google, with Stackdriver Service Monitoring , you get the answers to the following questions:来自 Google 的有关 StackDriver 的有用上下文,通过 Stackdriver Service Monitoring ,您可以获得以下问题的答案:
However, when it comes to Istio :然而,当谈到Istio时:
Stackdriver is the default logging solution for clusters deployed on Google Kube.netes Engine .
Stackdriver 是部署在Google Kube.netes Engine上的集群的默认日志记录解决方案。
In simple terms, Stack driver brings logging , monitoring and diagnostics and Istio , the service mesh does the actual implementation of what all should be done and how .
简单来说, Stack driver带来了日志记录、监控和诊断,而Istio服务网格负责实际执行所有应该做什么以及如何做。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.