Kubernetes & Docker監控之最後一章,前三篇以下:
一、kubernetes+docker監控之簡介node
二、 kubernetes+docker監控之Docker監控——cadvisorsql
三、 Docker監控——Cadvisor+InfluxDB+Grafana搭建過程docker
docker pull index.tenxcloud.com/google_containers/heapster:v1.1.0shell |
docker run -d index.tenxcloud.com/google_containers/heapster:v1.1.0 "--source=kubernetes:http://192.168.16.100:8080?inClusterConfig=false&kubeletHttps=true&kubeletPort=10250&useServiceAccount=true&auth=" "--sink=influxdb:http://192.168.16.234:8086"數據庫 |
參數說明:api
--source :指定kube-apiserver,這裏使用https,須要注意下google --sink :指定influxdb,heapster自動建立數據庫【k8s】spa inClusterConfig :Use kube config in service accounts associated with heapster's.net namesapce. (default: true)3d kubeletPort :kubelet port to use (default: 10255) kubeletHttps : whether to use https to connect to kubelets (default: false) apiVersion : API version to use to talk to Kubernetes. Defaults to the version in kubeConfig. insecure :whether to trust kubernetes certificates (default: false) auth :client auth file to use. Set auth if the service accounts are not usable. useServiceAccount :whether to use the service account token if one is mounted at /var/run/secrets/kubernetes.io/serviceaccount/token (default: false) |
heapster容器,啓動過程:
[root@localhost kube-1.2]# docker run -d index.tenxcloud.com/google_containers/heapster:v1.1.0 "--source=kubernetes:http://192.168.16.100:8080?inClusterConfig=false&kubeletHttps=true&kubeletPort=10250&useServiceAccount=true&auth=" "--sink=influxdb:http://192.168.16.234:8086" b86aaaaa88ccf648120611254bfeb0078a8b9dd853d4b5a2d6a0abb97743bf1d
[root@localhost kube-1.2]# docker logs b86aaaaa8 I0714 07:05:18.116787 1 heapster.go:65] /heapster --source=kubernetes:http://192.168.16.100:8080?inClusterConfig=false&kubeletHttps=true&kubeletPort=10250&useServiceAccount=true&auth= --sink=influxdb:http://192.168.16.234:8086 I0714 07:05:18.117158 1 heapster.go:66] Heapster version 1.1.0 I0714 07:05:18.239220 1 configs.go:60] Using Kubernetes client with master "http://192.168.16.100:8080" and version "v1" I0714 07:05:18.239270 1 configs.go:61] Using kubelet port 10250 I0714 07:05:31.255132 1 influxdb.go:223] created influxdb sink with options: host:192.168.16.234:8086 user:root db:k8s I0714 07:05:31.255170 1 heapster.go:92] Starting with InfluxDB Sink I0714 07:05:31.255177 1 heapster.go:92] Starting with Metric Sink I0714 07:05:31.271159 1 heapster.go:171] Starting heapster on port 8082 I0714 07:06:05.000403 1 manager.go:79] Scraping metrics start: 2016-07-14 07:05:00 +0000 UTC, end: 2016-07-14 07:06:00 +0000 UTC E0714 07:06:05.000504 1 kubelet.go:270] No nodes received from APIserver. I0714 07:06:05.000520 1 manager.go:152] ScrapeMetrics: time: 5.756µs size: 0 I0714 07:06:05.365486 1 influxdb.go:201] Created database "k8s" on influxDB server at "192.168.16.234:8086" [root@localhost kube-1.2]# [root@localhost kube-1.2]# docker ps |grep heapster b86aaaaa88cc index.tenxcloud.com/google_containers/heapster:v1.1.0 "/heapster --source=k" 2 minutes ago Up 2 minutes furious_mahavira [root@localhost kube-1.2]# |
看到influxdb已經有k8s的數據庫和表了,剩下的就是grafana搜索和顯示了
[root@localhost kube-1.2]# influx Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring. Connected to http://localhost:8086 version 0.9.6 InfluxDB shell 0.9.6 > > > show databases name: databases --------------- name _internal cadvisor k8s > > use k8s Using database k8s > > SHOW MEASUREMENTS name: measurements ------------------ name cpu/node_reservation cpu/node_utilization cpu/usage cpu/usage_rate filesystem/limit filesystem/usage memory/major_page_faults memory/major_page_faults_rate memory/node_reservation memory/node_utilization memory/page_faults memory/page_faults_rate memory/usage memory/working_set network/rx network/rx_errors network/rx_errors_rate network/rx_rate network/tx network/tx_errors network/tx_errors_rate network/tx_rate uptime |
請參考以前Cadvisor+InfluxDB+Grafana的內容,http://my.oschina.net/fufangchun/blog/718382
請參考以前Cadvisor+InfluxDB+Grafana的內容,http://my.oschina.net/fufangchun/blog/718382
Ⅰ、配置influxdb數據源:
Ⅱ、新建展現頁:
展現頁,用來區分不一樣的influxdb數據源
Ⅲ、新建數據項:
根據特定的條件(sql),從influxdb查詢相關的數據,並展現。
Grafana會自動顯示k8s庫的字段,能夠根據需求進行選擇,每一個where後面,加上:【pod_name =~ /^\.*/】,按照pod名稱分類
SELECT last(value) FROM k8s."default"."network/tx" WHERE pod_name =~ /^\.*/ AND time > now() - 30m GROUP BY time(10s), pod_name |
Ⅳ、完整的grafana展現:
這裏上傳可能看不清,能夠去百度盤下載,我這裏是有些數據是分別作了,按照pod和namespace進行分組的,有多租戶的狀況,比較實用,能夠根據狀況,自行定義。
百度盤地址: http://pan.baidu.com/s/1qXQIqPA
Kubernetes & Docker監控 ,至此完結,歡迎分享討論!!!