This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect metrics from Node Exporter. This document shows you how to do the following:
- Set up Node Exporter to report metrics.
- Configure a PodMonitoring resource for Managed Service for Prometheus to collect the exported metrics.
- Access a dashboard in Cloud Monitoring to view the metrics.
- Configure alerting rules to monitor the metrics.
These instructions apply only if you are using managed collection with Managed Service for Prometheus. If you are using self-deployed collection, then see the source repository for Node Exporter for installation information.
These instructions are provided as an example and are expected to work in most Kubernetes environments. If you are having trouble installing an application or exporter due to restrictive security or organizational policies, then we recommend you consult open-source documentation for support.
Prerequisites
To collect metrics from Node Exporter by using Managed Service for Prometheus and managed collection, your deployment must meet the following requirements:
- Your cluster must be running Google Kubernetes Engine version 1.21.4-gke.300 or later.
- You must be running Managed Service for Prometheus with managed collection enabled. For more information, see Get started with managed collection.
- To use dashboards available in Cloud Monitoring for the
integration, you must use
node_exporter
version 1.3.1 or later.For more information about available dashboards, see Install dashboards.
Install Node Exporter
You can use the following configuration to install Node Exporter:
To apply configuration changes from a local file, run the following command:
kubectl apply -f FILE_NAME
You can also use Terraform to manage your configurations.
Define rules and alerts
You can use the following Rules
configuration to define
alerts on your metrics:
To apply configuration changes from a local file, run the following command:
kubectl apply -f FILE_NAME
You can also use Terraform to manage your configurations.
For more information about applying rules to your cluster, see Managed rule evaluation and alerting.
ThisRules
configuration was adapted from the rules and alerts contributed
to the
kube-prometheus
repository.
Verify the configuration
You can use Metrics Explorer to verify that you correctly configured the exporter. It might take one or two minutes for Cloud Monitoring to ingest your metrics.
To verify the metrics are ingested, do the following:
-
In the Google Cloud console, go to the leaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
- In the toolbar of the query-builder pane, select the button whose name is either code MQL or code PromQL.
- Verify that PromQL is selected in the Language toggle. The language toggle is in the same toolbar that lets you format your query.
- Enter and run the following query:
up{job="node-exporter", cluster="CLUSTER_NAME", namespace="gmp-public"}
Install dashboards
Cloud Monitoring provides a library of sample dashboards for integrations. The sample library includes "Prometheus" dashboards, which you can install to view your data in the Google Cloud console.
Note that the Kubernetes Cluster Prometheus Overview dashboard requires Kube State Metrics to be installed. The Kubernetes Pod Prometheus Overview dashboard requires Kube State Metrics and Kubelet/cAdvisor to be installed.
To install a dashboard from the sample library, do the following:
-
In the Google Cloud console, go to the Dashboards page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
- Select the Sample Library tab.
- Choose the Other category.
- (Optional) To view a static preview of a dashboard without installing it, click Preview.
- Select the dashboards you want to install, then click Import.
For more information about installing dashboards, see Installing sample dashboards.
Troubleshooting
For information about troubleshooting metric ingestion problems, see Problems with collection from exporters in Troubleshooting ingestion-side problems.