![]() There is a pre-made Lightstep dashboard to help you quickly visualize node-exporter monitoring. Learn more about how to Ingest Prometheus metrics using an OpenTelemetry Collector on Kubernetes. Use the Lightstep Terraform Provider to create a dashboard for the metrics. If needed, click on the metric to edit the description and how the units are displayed in Lightstep. In Lightstep, click Project settings > Metric details.įor more details see the official Kubernetes system component documentation. You can validate that metrics are reporting to Lightstep on the Metrics details page in Project settings. Validate metrics are reporting to Lightstep Once the node-exporter receiver is configured, enable it by adding it to one or more pipelines as described in the Collector configuration documentation. More details about the Prometheus scrape configuration can be found here. The OpenTelemetry repo’s README provides additional details about Prometheus receiver configuration. Receivers : prometheus : config : scrape_configs : - job_name : ' otel-node-exporter' static_configs : - targets : In the Collector configuration file, configure the Prometheus receiver to use the node-exporter Prometheus endpoint as a scrape target. In node-exporter, Prometheus metrics are on port 9100 by default.įor more details about using node-exporter with the Prometheus exporter, see the official node-exporter documentation. How you do that depends on your deployment model and whether or not the default parameters are appropriate in your case. You may need to expose node-exporter Prometheus metrics. You’ve configured the Collector to export metric data to Lightstep Observability. ![]() Enable the integration by adding it to a pipeline.Configure the Collector to use the node-exporter endpoint as a scrape target for the Prometheus receiver.Head over to the location of your Prometheus configuration file and start editing it. Now that the node exporter is running on your instance, you need to configure it as a Prometheus target so that it starts scrapping it. b Set up Node Exporter as a Prometheus Target. Configure node-exporter to use the Prometheus exporter. Note: Node Exporter exposes its metrics on port 9100.From there, the metrics are processed and exported to Lightstep Observability. The Collector uses the Prometheus Receiver to fetch metrics from the configured path. If you see the following error, it could be due to SELinux being enabled.The OpenTelemetry Collector, when configured with a Prometheus receiver, provides an integration with node-exporter to scrape Prometheus metrics. Main PID: 66608 (node_exporter ) Tasks: 6 (limit: 23494 ) Memory: 21.1MĬGroup: /system.slice/node_rviceĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =thermal_zoneĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =timeĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =timexĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =udp_queuesĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =unameĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =vmstatĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =xfsĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:115 collector =zfsĪug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =node_exporter.go:199 msg = "Listening on" address =:9100Īug 19 14:38:14 foo-instance node_exporter : level =info ts =T06:38:14.080Z caller =tls_config.go:191 msg = "TLS is disabled." http2 =false Loaded: loaded (/etc/systemd/system/node_rvice disabled vendor preset: disabled ) Active: active (running ) since Thu 14:38:14 +08 23h ago
0 Comments
Leave a Reply. |