The OpenTelemetry Collector, when configured with a Prometheus receiver, provides an integration with node-exporter to scrape Prometheus metrics. The Collector uses the Prometheus Receiver to fetch metrics from the configured path. From there, the metrics are processed and exported to Cloud Observability.
To complete the integration, you will:
You’ve configured the Collector to export metric data to Cloud Observability.
You may need to expose node-exporter Prometheus metrics. How you do that depends on your deployment model and whether or not the default parameters are appropriate in your case. In node-exporter, Prometheus metrics are on port 9100 by default.
For more details about using node-exporter with the Prometheus exporter, see the official node-exporter documentation.
In the Collector configuration file, configure the Prometheus receiver to use the node-exporter Prometheus endpoint as a scrape target.
1
2
3
4
5
6
7
receivers:
prometheus:
config:
scrape_configs:
- job_name: 'otel-node-exporter'
static_configs:
- targets: ['node-exporter.kube-system.svc.cluster.local']
The OpenTelemetry repo’s README provides additional details about Prometheus receiver configuration.
More details about the Prometheus scrape configuration can be found here.
Once the node-exporter receiver is configured, enable it by adding it to one or more pipelines as described in the Collector configuration documentation.
You can validate that metrics are reporting to Cloud Observability on the Metrics details page in Settings.
In Cloud Observability, click Settings > Metric details.
Search for node-exporter metric names.
For more details see the official Kubernetes system component documentation.
If needed, click on the metric to edit the description and how the units are displayed in Cloud Observability.
Use the Cloud Observability Terraform Provider to create a dashboard for the metrics.
Learn more about how to Ingest Prometheus metrics using an OpenTelemetry Collector on Kubernetes.
There is a pre-made Cloud Observability dashboard to help you quickly visualize node-exporter monitoring.
Updated Dec 1, 2022