Monitoring and alarm of kubernetes

This article introduces how to Kubernetes The cluster monitors and configures alarms .

Kubernetes Monitoring of

Deployed with the cluster TiDB Monitoring only focuses on TiDB Operation of its components , It does not include the container resources 、 The host machine 、Kubernetes Components and TiDB Operator And so on . Monitoring of these components or resources , Need to be in the whole Kubernetes The cluster dimension deploys the monitoring system to realize .

Host monitoring

The monitoring of the host and its resources is the same as the traditional server physical resource monitoring .

If you already have a monitoring system for physical servers in your existing infrastructure , Just use the conventional method to Kubernetes Add the host to the existing monitoring system ; If there is no monitoring system available , Or we hope to deploy an independent monitoring system for monitoring Kubernetes The host of the host , You can also use any monitoring system you are familiar with .

The newly deployed monitoring system can run on an independent server 、 Run directly on Kubernetes The host of the host , Or run on Kubernetes Within cluster , There are some differences between different deployment methods except in installation configuration and resource utilization , There is no significant difference in use .

Common open source monitoring systems that can be used to monitor server resources are ：

• CollectD
• Nagios
• Prometheus & node_exporter
• Zabbix

Some cloud service providers or special performance monitoring service providers also have their own free or paid monitoring solutions to choose .

We recommend that  Prometheus Operator  stay Kubernetes Deployment within the cluster is based on  Node Exporter  and Prometheus Host computer monitoring system , This scheme can be compatible and used for Kubernetes Monitoring of its own components .

Kubernetes Component monitoring

Yes Kubernetes For component monitoring, please refer to Official documents The solution provided , You can also use other compatible Kubernetes The monitoring system of .

Some cloud service providers may provide their own Kubernetes Component monitoring scheme , Some specialized performance monitoring service providers also have their own Kubernetes The integration scheme can be selected .

because TiDB Operator It actually runs on Kubernetes In the container , Select any to override the pair Kubernetes The monitoring system that monitors the container status and resources can cover TiDB Operator Monitoring of , There is no need to deploy additional monitoring components .

We recommend that  Prometheus Operator  Based on the deployment  Node Exporter  and Prometheus Host computer monitoring system , This scheme can also be compatible and used for monitoring the host resources .

Kubernetes The alarm

If you use Prometheus Operator Deploy for Kubernetes Host and service monitoring , Some alarm rules will be configured by default , And will deploy one AlertManager service , Please refer to  kube-prometheus  Explanation .

If you use other tools or services Kubernetes Host computers and services are monitored , Please refer to the corresponding information of the tool or service provider .