我试图在Kubernetes集群上设置Heapster/InfluxDB/Grafana。看起来Heapster正在生成数据,但没有将其发送到InfluxDB。当我查看Heapster吊舱中的eventer容器的容器日志时,日志看起来如下所示:
E1020 18:43:20.006608 52 influxdb.go:147] Failed to create infuxdb: failed to ping InfluxDB server at "monitoring-influxdb:8086" - Get http://monitoring-influxdb:8086/ping: dial tcp: lookup monitoring-influxdb on 10.254.0.10:53: read udp 172.16.23.2:43533->10.254.0.10:53: i/o timeout
I1020 18:43:30.000165 52 manager.go:95] Exporting 88 events
I1020 18:44:00.000173 52 manager.go:95] Exporting 29 events
W1020 18:44:20.000451 52 manager.go:108] Failed to events data to sink: InfluxDB Sink
E1020 18:44:20.075039 52 influxdb.go:147] Failed to create infuxdb: failed to ping InfluxDB server at "monitoring-influxdb:8086" - Get http://monitoring-influxdb:8086/ping: dial tcp: lookup monitoring-influxdb on 10.254.0.10:53: read udp 172.16.23.2:60660->10.254.0.10:53: i/o timeout
I1020 18:44:30.000211 52 manager.go:95] Exporting 26 events
I1020 18:45:00.000169 52 manager.go:95] Exporting 23 events
W1020 18:45:20.000568 52 manager.go:108] Failed to events data to sink: InfluxDB Sink
E1020 18:45:20.004656 52 influxdb.go:147] Failed to create infuxdb: failed to ping InfluxDB server at "monitoring-influxdb:8086" - Get http://monitoring-influxdb:8086/ping: dial tcp: lookup monitoring-influxdb on 10.254.0.10:53: read udp 172.16.23.2:53401->10.254.0.10:53: i/o timeout
I1020 18:45:30.000568 52 manager.go:95] Exporting 30 events
I1020 18:46:00.000188 52 manager.go:95] Exporting 26 events
W1020 18:46:20.000504 52 manager.go:108] Failed to events data to sink: InfluxDB Sink
E1020 18:46:20.074697 52 influxdb.go:147] Failed to create infuxdb: failed to ping InfluxDB server at "monitoring-influxdb:8086" - Get http://monitoring-influxdb:8086/ping: dial tcp: lookup monitoring-influxdb on 10.254.0.10:53: read udp 172.16.23.2:49101->10.254.0.10:53: i/o timeout
I1020 18:46:30.000267 52 manager.go:95] Exporting 39 events
I1020 18:46:35.052332 52 influxdb.go:199] Created database "k8s" on influxDB server at "monitoring-influxdb:8086"
I1020 18:47:00.000173 52 manager.go:95] Exporting 64 events
I1020 18:47:30.000212 52 manager.go:95] Exporting 52 events
I1020 18:48:00.000234 52 manager.go:95] Exporting 43 events
I1020 18:48:30.070486 52 manager.go:95] Exporting 52 events
I1020 18:49:00.000340 52 manager.go:95] Exporting 40 events
I1020 18:49:30.000170 52 manager.go:95] Exporting 40 events
I1020 18:50:00.000205 52 manager.go:95] Exporting 57 events
I1020 18:50:30.000211 52 manager.go:95] Exporting 94 events在此之后,只有一系列事件被导出。我的第一个问题是,Heapster是否成功地连接到InfluxDB服务,还是它只是在假定要收集一些东西的情况下将数据发送到http://monitoring-influxdb:8086?如果它连接了,为什么k8s数据库在我的InfluxDB中是空的?
我使用kubernetes/contrib/ansible中的ansible脚本部署了集群,yaml文件是从somwhere下载的(我不知道在哪里)。如果您想看一看,我将它们推上一个git存储库这里。
发布于 2017-10-23 21:18:34
确定是否正在收集数据的最简单方法(IMO)是查看进水数据库的日志。在我的环境中(从https://github.com/kubernetes/heapster/tree/master/deploy/kube-config/influxdb部署),豆荚都位于kube命名空间中:
kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
heapster-603813915-tggbr 1/1 Running 0 34d
kubernetes-dashboard-3313488171-mpn5b 1/1 Running 2 43d
monitoring-grafana-2175968514-zxgn1 1/1 Running 0 34d
monitoring-influxdb-1957622127-92r2w 1/1 Running 0 34d和原木:
kubectl logs monitoring-influxdb-1957622127-92r2w -n kube-system
httpd 10.244.1.18 -根23/Oct/2017:21:13:05 +0000 :POST /write?consistency=&db=k8s&precision=&rp=default HTTP/1.1“204 0 "-”heapster/v1.4.0“f5e74e91-b 836-11e7-84d0-000000000000 121606 httpd 10.244.1.18 -根23/Oct/2017:21:14:05 +0000”post/write?consistency=&db=k8s&precision=&rp=default HTTP/1.1“204”0“"heapster/v1.4.0”19a8a32c-b837-11e7-84d1-000000000000 137213 httpd 10.244.1.18 -根23/Oct/2017:21:15:05 +0000 "POST /write?consistency=&db=k8s&precision=&rp=default HTTP/1.1“204 0 "-”heapster/v1.4.0“3 d6eb415-b837-11e7-84d2-000000000000 125065 httpd 10.244.1.18 -根23/10/2017:21:16:05 +0000”/write?consistency=&db=k8s&precision=&rp=default HTTP/1.1“204 0”-"heapster/v1.4.0“6133e847-b 837-11e7-84d3-000000000000 128300在这种情况下,204条回应很明显是在接受数据。如果您的堆由于某种原因没有与进水数据库通信,那么答案可能也在进水数据库荚的日志中。
https://stackoverflow.com/questions/46855935
复制相似问题