![]() Level=info ts=T16:24:21.754Z caller=head.go:892 component=tsdb msg="WAL segment loaded" segment=0 maxSegment=0 Level=info ts=T16:24:21.753Z caller=head.go:835 component=tsdb msg="Replaying WAL, this may take a while" Level=info ts=T16:24:21.753Z caller=head.go:829 component=tsdb msg="On-disk memory mappable chunks replay completed" duration=4.15µs Level=info ts=T16:24:21.753Z caller=head.go:815 component=tsdb msg="Replaying on-disk memory mappable chunks if any" Level=info ts=T16:24:21.748Z caller=tls_config.go:191 component=web msg="TLS is disabled." http2=false Logs coming from the prometheus pod seem to have a lot of errors: kubectl logs prometheus-deployment-5d79b5f65b-tkpd2 -n monitoring ![]() When I start typing a query for a metric reported by node-exporter, it doesn't automatically show up in the query editor. I also did: kubectl port-forward prometheus-deployment-5d79b5f65b-tkpd2 8080:9090 -n monitoring and when I access the prometheus web UI > Status > Targets, I don't find node-exporters there. I can see the endpoints, as well: kubectl get endpoints -n monitoring NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES The pods seem to be running properly: kubectl get pods -namespace=monitoring -o wide I installed prometheus and node-exporter on top of it based on: Time="" level=fatal msg="listen tcp: address tcp/19100\": unknown port" source="node_exporter.I have a Kubernetes cluster set up using kubeadm. Time="" level=info msg=" - zfs" source="node_exporter.go:104" ![]() Time="" level=info msg=" - xfs" source="node_exporter.go:104" Time="" level=info msg=" - vmstat" source="node_exporter.go:104" Time="" level=info msg=" - uname" source="node_exporter.go:104" Time="" level=info msg=" - timex" source="node_exporter.go:104" the error like this: time="" level=info msg=" - time" source="node_exporter.go:104" Tried times 2(add new option to args -web.listen-address=":9100") like below: containers: Tryied times 1(modify the 9100 port to 19100): containers: the following config was what I have tried: The default port of node exporter is 9100, but the port on my local machine is already occupied, So I modify the config file serveral times to change the port. My node exporter was installed using kubernetes daemonset. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |