Challenges in Kubernetes Monitoring: Increased Complexity and Dynamic Application Scheduling

2nd chunk of `content/en/blog/_posts/2017-05-00-Kubernetes-Monitoring-Guide.md`

70c1995ded0d8f7adbe3ba25882b9c3395f5b2c307db8d990000000100000429

![](https://lh5.googleusercontent.com/tN8tzKcXWAFWF0TD9u9UkTFJakHsrdjtRx56WiF75UYwMKu8teFyr6LpLGjpuOWSr52M-l3do5r3a6VWi6VwhRWuaquCpGty8ksI585D9YuCL3t7DAcItJUwW6mlrM2jUw_jVq6A)](https://lh5.googleusercontent.com/tN8tzKcXWAFWF0TD9u9UkTFJakHsrdjtRx56WiF75UYwMKu8teFyr6LpLGjpuOWSr52M-l3do5r3a6VWi6VwhRWuaquCpGty8ksI585D9YuCL3t7DAcItJUwW6mlrM2jUw_jVq6A)
In traditional, host-centric infrastructure, we were used to monitoring only two layers: applications and the hosts running them. Now with containers in the middle and Kubernetes itself needing to be monitored, there are four different components to monitor and collect metrics from.  

**Applications are constantly moving**  
Kubernetes schedules applications dynamically based on scheduling policy, so you don’t always know where applications are running. But they still need to be monitored. That’s why using a monitoring system or tool with service discovery is a must. It will automatically adapt metric collection to moving containers so applications can be continuously monitored without interruption.

Title: Challenges in Kubernetes Monitoring: Increased Complexity and Dynamic Application Scheduling

Summary

This section discusses the challenges introduced by Kubernetes to traditional monitoring practices. It highlights the need to monitor more components (applications, containers, Kubernetes itself, and hosts) and the dynamic nature of application scheduling, which requires a monitoring system with service discovery capabilities to track moving containers.