Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/kubernetes-engine/docs/how-to/cadvisor-kubelet-metrics below:

Collect and view cAdvisor/Kubelet metrics | Google Kubernetes Engine (GKE)

Stay organized with collections Save and categorize content based on your preferences.

This page describes how to configure a Google Kubernetes Engine (GKE) cluster to send a curated set of cAdvisor/Kubelet metrics to Cloud Monitoring using Google Cloud Managed Service for Prometheus. This page also describes how these metrics are formatted when they are written to Monitoring, and how to query metrics.

The curated set of metrics is a subset of the set of cAdvisor/Kubelet metrics built into every Kubernetes deployment by default and includes metrics related to reducing ingestion volume and associated costs.

Before you start, make sure that you have performed the following tasks:

• Enable the Google Kubernetes Engine API.
Enable Google Kubernetes Engine API
• If you want to use the Google Cloud CLI for this task, install and then initialize the gcloud CLI. If you previously installed the gcloud CLI, get the latest version by running gcloud components update. Note: For existing gcloud CLI installations, make sure to set the compute/region property. If you use primarily zonal clusters, set the compute/zone instead. By setting a default location, you can avoid errors in the gcloud CLI like the following: One of [--zone, --region] must be supplied: Please specify location. You might need to specify the location in certain commands if the location of your cluster differs from the default that you set.

To collect cAdvisor/Kubelet metrics, your GKE cluster must meet the following requirements:

• The cluster must be running GKE version 1.29.3-gke.1093000 or later. cAdvisor/Kubelet packages are enabled by default when you create a cluster running version 1.29.3-gke.1093000 or later.
• The cluster must have system metrics enabled.
• The cluster has Google Cloud Managed Service for Prometheus managed collection enabled. Google Cloud Managed Service for Prometheus managed collection is enabled by default for new clusters.

You can enable cAdvisor/Kubelet metrics in an existing GKE cluster using the Google Cloud console, the gcloud CLI, or Terraform.

To configure cAdvisor/Kubelet metrics from the Details tab for the cluster, do the following:

1. In the Google Cloud console, go to the Kubernetes clusters page:

   Go to Kubernetes clusters

   If you use the search bar to find this page, then select the result whose subheading is Kubernetes Engine.

2. Click your cluster's name.

3. In the Features row labelled Cloud Monitoring, click the Edit icon.

4. In the Edit Cloud Monitoring dialog that appears, confirm that Enable Cloud Monitoring is selected.

5. In the Components drop-down menu, select the cAdvisor/Kubelet components from which you would like to collect metrics:

   • cAdvisor
   • Kubelet

6. Click OK.

7. Click Save Changes.

Update your cluster to collect metrics:

gcloud container clusters update CLUSTER_NAME \
    --location=COMPUTE_LOCATION \
    --enable-managed-prometheus \
    --monitoring=SYSTEM,CADVISOR,KUBELET

Replace the following:

• CLUSTER_NAME: the name of the existing cluster.
• COMPUTE_LOCATION: the Compute Engine location of the cluster.

The set of values supplied to the monitoring flag overrides any previous setting.

To configure the collection of cAdvisor/Kubelet metrics by using Terraform, see the monitoring_config block in the Terraform registry for google_container_cluster. For general information about using Google Cloud with Terraform, see Terraform with Google Cloud.

All Kubernetes cAdvisor/Kubelet metrics written to Cloud Monitoring use the resource type prometheus_target. Each metric name is prefixed with prometheus.googleapis.com/ and has a suffix indicating the Prometheus metric type, such as /gauge, /histogram, or /counter. Otherwise, each metric name is identical to the metric name exposed by open source Kubernetes.

The cAdvisor/Kubelet metrics can be exported from Cloud Monitoring by using the Cloud Monitoring API. Because all cAdvisor/Kubelet metrics are ingested by using Google Cloud Managed Service for Prometheus, cAdvisor/Kubelet metrics can be queried by using Prometheus Query Language (PromQL). They can also be queried by using by using Monitoring Query Language (MQL).

When you query cAdvisor/Kubelet metrics, the name you use depends on whether you are using PromQL or Cloud Monitoring-based features like MQL or the Metrics Explorer menu-driven interface.

The following tables of cAdvisor/Kubelet metrics show two versions of each metric name:

• PromQL metric name: When using PromQL in Cloud Monitoring pages of the Google Cloud console or in PromQL fields of the Cloud Monitoring API, use the PromQL metric name.
• Cloud Monitoring metric name When using other Cloud Monitoring features, use the Cloud Monitoring metric name in the tables below. This name must be prefixed with prometheus.googleapis.com/, which has been omitted from the entries in the table.

The Cloud Monitoring metric names in this table must be prefixed with prometheus.googleapis.com/. That prefix has been omitted from the entries in the table.

cpu

cpu

cpu

disk

diskIO

diskIO

diskIO

disk

diskIO

diskIO

diskIO

memory

memory

network

network

network

network

network

network

The Cloud Monitoring metric names in this table must be prefixed with prometheus.googleapis.com/. That prefix has been omitted from the entries in the table.

node

operation_type

container_state

operation_type

namespace

namespace

namespace

namespace

namespace

namespace

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-12 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-12 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4