Level=info ts=T16:24:21.762Z caller=kubernetes.go:282 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" Level=info ts=T16:24:21.759Z caller=kubernetes.go:282 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" Level=info ts=T16:24:21.757Z caller=kubernetes.go:282 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config" Level=info ts=T16:24:21.756Z caller=main.go:969 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml Level=info ts=T16:24:21.754Z caller=head.go:898 component=tsdb msg="WAL replay completed" checkpoint_replay_duration=75.316µs wal_replay_duration=451.769µs total_replay_duration=566.051µs 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: ![]() I have a Kubernetes cluster set up using kubeadm.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |