Troubleshoot the logs with docker-compose logs -f. If metrics do not appear after several minutes, check your work for typos, and make sure that both prometheus and node-exporter containers are running with the docker-compose ps command. You can also confirm ingestion by navigating to the billing dashboard. If you cannot see metrics in the dropdown, metrics are not being ingested. Recall that we set the job_name to node in our prometheus.yml configuration file. Use the Metrics browser to find the node_disk_io_now metric, then click on the job label and node label value. This will take you to the Explore view:Īt the top of the page, use the dropdown menu to select your Prometheus data source. In this step, you’ll query your Prometheus metrics from Grafana Cloud.Ĭlick Explore in the left-side menu to start. Step 3: Verify that metrics are being ingested You can now move on to querying these metrics from Grafana Cloud. Node-exporter | level=info ts=T21:33:36.852Z caller=tls_config.go:191 msg="TLS is disabled." http2=false Node-exporter | level=info ts=T21:33:36.852Z caller=node_exporter.go:199 msg="Listening on" address=:9100 Node-exporter | level=info ts=T21:33:36.852Z caller=node_exporter.go:115 collector=zfs Node-exporter | level=info ts=T21:33:36.852Z caller=node_exporter.go:115 collector=xfs Node-exporter | level=info ts=T21:33:36.852Z caller=node_exporter.go:115 collector=vmstat
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |