Cluster terlampir GKE memiliki integrasi bawaan dengan Cloud Monitoring untuk metrik sistem node, pod, dan container. Dengan begitu, Anda dapat dengan mudah melihat konsumsi resource workload di cluster, membuat dasbor, dan mengonfigurasi pemberitahuan.
Cluster terpasang GKE menginstal pengumpul metrik gke-metrics-agent di
cluster Anda. Agen ini didasarkan pada
OpenTelemetry Collector,
dan berjalan di setiap node dalam cluster. Agen ini mengambil sampel metrik setiap menit, dan mengupload pengukuran ke Cloud Monitoring.
Setelah metrik untuk cluster Anda diupload, metrik tersebut akan berada di projectGoogle Cloud Anda. Anda dapat menggabungkan data di semua cluster, membuat dasbor kustom, menjelajahi data satu cluster, melihat diagram garis, menyiapkan pemberitahuan, dan lainnya.
Menggunakan Metrics Explorer
Untuk melihat metrik untuk resource yang dimonitor menggunakan
Metrics Explorer, lakukan langkah berikut:
Di konsol Google Cloud , buka halaman
leaderboardMetrics explorer:
Jika Anda menggunakan kotak penelusuran untuk menemukan halaman ini, pilih hasil yang subjudulnya adalah Monitoring.
Di toolbar konsol Google Cloud , pilih project Google Cloud Anda.
Untuk konfigurasi App Hub, pilih
project host App Hub atau project pengelolaan folder yang mendukung aplikasi.
Pada elemen Metrik, luaskan menu Pilih metrik, masukkan Kubernetes Container di panel filter, lalu gunakan submenu untuk memilih jenis dan metrik resource tertentu:
Di menu Active resources, pilih Kubernetes Container.
Di menu Active metric categories, pilih Anthos.
Di menu Active metrics, pilih CPU usage time.
Klik Terapkan.
Untuk menghapus deret waktu dari tampilan, gunakan elemen Filter.
Untuk menggabungkan deret waktu, gunakan menu pada elemen Agregasi.
Misalnya, untuk menampilkan pemakaian CPU bagi VM Anda, berdasarkan zonanya, tetapkan menu pertama ke Rataan dan menu kedua ke zona.
Semua deret waktu ditampilkan saat menu pertama elemen Agregasi ditetapkan ke Unaggregated. Setelan default untuk elemen Agregasi ditentukan oleh jenis metrik yang Anda pilih.
Untuk kuota dan metrik lain yang melaporkan satu sampel per hari, lakukan tindakan berikut:
Di panel Display,
tetapkan Jenis widget ke Diagram batang bertumpuk.
Tetapkan jangka waktu setidaknya satu minggu.
Jenis resource yang dimonitor metrik
Metrik dikumpulkan menggunakan salah satu dari tiga jenis resource yang dipantau berikut.
Jenis ini sesuai dengan objek Kubernetes yang diukur:
Misalnya, pengukuran tentang Pod akan menggunakan jenis resource yang dimonitor
k8s_pod. Oleh karena itu, metrik ini akan menyertakan label untuk pod_name dan namespace_name, yang mengidentifikasi Pod tertentu. Jika Anda ingin melihat metrik untuk
cluster tertentu, gunakan format berikut:
attachedClusters/CLUSTER_NAME
Serangkaian jenis metrik yang berbeda digunakan untuk setiap jenis resource yang dimonitor.
Untuk mempelajari jenis metrik ini lebih lanjut, lihat
Metrik sistem GKE.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-31 UTC."],[],[],null,["This document describes how GKE attached clusters integrates with\nCloud Monitoring and how to view your metrics.\n\nBefore you begin\n\n1. Fulfill the\n [prerequisites for GKE attached clusters](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/cluster-prerequisites).\n\n2. [Authorize Cloud Logging and Cloud Monitoring](/kubernetes-engine/multi-cloud/docs/attached/generic/how-to/attach-cluster#telemetry-agent-auth)\n to set up permissions for Google Cloud Observability.\n\n\nOverview\n\nGKE attached clusters has built-in integration with Cloud Monitoring for system\nmetrics of nodes, pods, and containers. This allows you to easily see the resource\nconsumption of workloads in the cluster, build dashboards, and configure alerts.\n\nGKE attached clusters installs the metrics collector `gke-metrics-agent` in\nyour cluster. This agent is based on\n[OpenTelemetry Collector](https://opentelemetry.io/docs/collector/),\nand runs on every node in the cluster. It samples metrics every minute, and\nuploads measurements to Cloud Monitoring.\n\nOnce metrics for your cluster have been uploaded, they reside in your\nGoogle Cloud project. You can aggregate data across all of your\nclusters, build custom dashboards, explore a single cluster's data,\nview line charts, set up alerts, and more.\n\nUsing the Metrics Explorer\n\nTo view the metrics for a monitored resource by using the\nMetrics Explorer, do the following:\n\n1. In the Google Cloud console, go to the\n *leaderboard* **Metrics explorer** page:\n\n [Go to **Metrics explorer**](https://console.cloud.google.com/monitoring/metrics-explorer)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. In the toolbar of the Google Cloud console, select your Google Cloud project. For [App Hub](/app-hub/docs/overview) configurations, select the App Hub host project or the app-enabled folder's management project.\n3. In the **Metric** element, expand the **Select a metric** menu, enter `Kubernetes Container` in the filter bar, and then use the submenus to select a specific resource type and metric:\n 1. In the **Active resources** menu, select **Kubernetes Container**.\n 2. In the **Active metric categories** menu, select **Anthos**.\n 3. In the **Active metrics** menu, select **CPU usage time**.\n 4. Click **Apply**.\n4. To add filters, which remove time series from the query results, use the\n [**Filter** element](/monitoring/charts/metrics-selector#filter-option).\n\n5. To combine time series, use the menus on the\n [**Aggregation** element](/monitoring/charts/metrics-selector#select_display).\n For example, to display the CPU utilization for your VMs, based on their zone, set the\n first menu to **Mean** and the second menu to **zone**.\n\n All time series are displayed when the first menu of the **Aggregation** element is set\n to **Unaggregated** . The default settings for the **Aggregation** element\n are determined by the metric type you selected.\n6. For quota and other metrics that report one sample per day, do the following:\n 1. In the **Display** pane, set the **Widget type** to **Stacked bar chart**.\n 2. Set the time period to at least one week.\n\n\nMetrics monitored resource type\n\nMetrics are collected using one of the following three monitored resource types.\nThese types correspond to a Kubernetes object that the measurement is being made\nfor:\n\n- [k8s_node](https://cloud.google.com/monitoring/api/resources#tag_k8s_node)\n- [k8s_container](https://cloud.google.com/monitoring/api/resources#tag_k8s_container)\n- [k8s_pod](https://cloud.google.com/monitoring/api/resources#tag_k8s_pod)\n\nFor example, measurements about a Pod would use the monitored resource type\n`k8s_pod`. These metrics would therefore include labels for `pod_name` and\n`namespace_name`, that identify a particular Pod. If you want to see metrics for\na specific cluster, use the following format: \n\n attachedClusters/\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e\n\nA different set of *metrics types* are used for each *monitored resource type* .\nTo learn more about these metrics types, see\n[GKE system metrics](https://cloud.google.com/monitoring/api/metrics_kubernetes).\n\nWhat metrics are collected\n\n- [v1.32.0-gke.1](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.32.0-gke.1/metrics)\n- [v1.31.0-gke.4](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.31.0-gke.4/metrics)\n- [v1.31.0-gke.3](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.31.0-gke.3/metrics)\n- [v1.31.0-gke.2](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.31.0-gke.2/metrics)\n- [v1.31.0-gke.1](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.31.0-gke.1/metrics)\n- [v1.30.0-gke.7](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.7/metrics)\n- [v1.30.0-gke.6](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.6/metrics)\n- [v1.30.0-gke.5](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.5/metrics)\n- [v1.30.0-gke.4](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.4/metrics)\n- [v1.30.0-gke.3](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.3/metrics)\n- [v1.30.0-gke.2](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.2/metrics)\n- [v1.30.0-gke.1](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.30.0-gke.1/metrics)\n- [v1.29.0-gke.9](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.9/metrics)\n- [v1.29.0-gke.8](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.8/metrics)\n- [v1.29.0-gke.7](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.7/metrics)\n- [v1.29.0-gke.6](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.6/metrics)\n- [v1.29.0-gke.5](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.5/metrics)\n- [v1.29.0-gke.4](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.4/metrics)\n- [v1.29.0-gke.3](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.3/metrics)\n- [v1.29.0-gke.2](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.2/metrics)\n- [v1.29.0-gke.1](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.29.0-gke.1/metrics)\n- [v1.28.0-gke.9](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.9/metrics)\n- [v1.28.0-gke.8](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.8/metrics)\n- [v1.28.0-gke.7](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.7/metrics)\n- [v1.28.0-gke.6](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.6/metrics)\n- [v1.28.0-gke.5](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.5/metrics)\n- [v1.28.0-gke.4](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.4/metrics)\n- [v1.28.0-gke.3](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.3/metrics)\n- [v1.28.0-gke.2](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.2/metrics)\n- [v1.28.0-gke.1](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.28.0-gke.1/metrics)\n- [v1.27.0-gke.9](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.9/metrics)\n- [v1.27.0-gke.8](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.8/metrics)\n- [v1.27.0-gke.7](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.7/metrics)\n- [v1.27.0-gke.6](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.6/metrics)\n- [v1.27.0-gke.5](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.5/metrics)\n- [v1.27.0-gke.4](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.4/metrics)\n- [v1.27.0-gke.3](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.27.0-gke.3/metrics)\n- [v1.26.0-gke.9](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.26.0-gke.9/metrics)\n- [v1.26.0-gke.8](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.26.0-gke.8/metrics)\n- [v1.26.0-gke.7](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.26.0-gke.7/metrics)\n- [v1.26.0-gke.6](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.26.0-gke.6/metrics)\n- [v1.25.0-gke.8](/kubernetes-engine/multi-cloud/docs/attached/generic/reference/versions/v1.25.0-gke.8/metrics)\n\nWhat's next?\n\n- [Set up managed data collection with Managed Service for Prometheus](/kubernetes-engine/multi-cloud/docs/attached/generic/how-to/managed-service-prometheus)\n- [Using Metrics Explorer](/monitoring/charts/metrics-explorer)\n- [Create logs-based metrics](/logging/docs/logs-based-metrics)\n- [Building queries for Cloud Monitoring](/monitoring/mql/set-up-query-alert-mql)\n- [Setting up Alerting](/monitoring/alerts)\n- [The GKE overview](/kubernetes-engine/fleet-management/docs/enterprise-overview-dashboard)"]]