Shulou(Shulou.com)05/31 Report--

This article mainly introduces "what are the ways in which Kubernetes changes monitoring". In daily operation, I believe many people have doubts about how Kubernetes changes the way of monitoring. The editor consulted all kinds of data and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "what are the ways in which Kubernetes changes monitoring?" Next, please follow the editor to study!

Service

Kubernetes is a central brain that understands the logical and physical optimization of applications. Kubernetes is responsible for orchestrating complex container configuration tasks into your infrastructure and presenting those distributed component connections as unified services. In essence, Kubernetes creates a bridge between physical resource utilization and the logical set of pods, and services make up the applications you understand.

If you don't have a constantly up-to-date understanding of what Kubernetes does, then your monitoring system is better off tracking and alerting only to underlying resource issues. In order to understand the definition of Services and pods, your monitoring system needs to 1) dynamically fetch relevant information from Kubernetes API, 2) map logical group container sets to logical applications, and 3) continuously calculate aggregate application, service, and infrastructure metrics, allowing you to monitor your services as a whole.

Elastic expansion

With 1.2 Kubernetes, it can be expanded to more than 1000 node clusters. In addition, the system's amazing dynamic replication control can adjust additional containers in seconds as needed. Now that it closes the container, they may not be originally created, but only temporarily.

Therefore, the previous legacy alert method needs to be changed. Alerts need to be adapted in two ways. On the one hand-- as we described in the services section-- alerts need to dynamically aggregate and measure all relevant sources, no matter how old they are, to measure the overall performance of the service and pod. The second aspect-resource-level warnings, such as CPU, memory or network utilization, need to be applied to separate containers or applications as they come and go. In order to operate properly, these alert prompts need to be automatically set to the container created for Kubernetes. Alert alerts can also be applied to Pod, services, and any tags that relate to your application.

Distribution

Kubernentes Cluster federation (aka Ubernetes) makes it easier to distribute applications in multiple data centers and multiple angry providers. This significantly improves the performance of distributed applications, avoids cloud locking, and even controls costs.

On the other hand? Yes, the monitoring methods of some teams need to be changed. In particular, those who are used to using the monitoring provided by their cloud need to use a system that can monitor, alert, and troubleshoot on the cloud. Most importantly, the system can collect the same indicators fluently in the cloud to reasonably aggregate information.

Monitoring, Kubernetes, and your application environment

Services, flexible expansion, and distribution are three that can use Kubernetes1.2 to influence changes in your environment, but will have an impact on you in the future. Moving to container-driven, micro-service-oriented hybrid cloud deployment (call, really a lot of terminology) is guided by many software operational goals. In order to make a successful transition, organizations also need to rethink how they get the visualization of these new environments. Containers add a challenge here because they are black boxes; microservices add a challenge because they adjust how they think about your application; orchestration tools help flexibly expand your infrastructure, and there are some key metadata you need in this brave new world.

Oh, by the way, today Sysdig officially supports Kubernetes1.2 as you buy and use it. To keep it simple, we use Deamon to make sure that every host you create with Kubernetes is automatically instrumented through Sysdig Cloud.

At this point, the study of "what are the ways in which Kubernetes changes monitoring" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.