What we can learn from Instana Kubernetes Monitoring
Details
I recently read a blog post describing the pains of monitoring Kubernetes and the solution provided by Instana:
- It’s difficult to understand how/where K8s has deployed your environment
- It’s difficult to understand how events in Kubernetes are related to the performance and availability of your services
- It’s difficult to know when K8s itself is broken
Solution
Shows you the exact deployment, related performance, and a mapping of your containers, clusters, and pods. It also alerts you when K8s is unable to deploy components due to resource limitation or other issues. Instana screenshot showing nodes and deployments related to a cluster.
Instana collects all events generated by Kubernetes and processes them along with the data from correlated infrastructure and application components. All of this data is tracked using our Dynamic Graph which is a virtual map of every discovered application and infrastructure dependency. This allows you to navigate from application component to Kubernetes component and back right inside of the UI.
AI is applied to this dynamic data set to automatically determine if Kubernetes events are the root cause of service impact. You will finally understand the exact impact (if any) of Kubernetes generated events on your running applications and services. Instana automatically collects and correlates all K8s labels whether they are system generated or user defined. These labels are critical to mapping the monitoring data to your actual Kubernetes configurations
K8s has multiple internal services (scheduler, controller, etcd, kubelets, etc) all working together to schedule, deploy and monitor your containers. If any of those components fail you want to be alerted and fix them right away.