Os clusters anexados do GKE contam com integração integrada com o Cloud Monitoring para métricas de sistema de nós, pods e contêineres. Isso permite que você visualize facilmente o consumo de recursos das cargas de trabalho no cluster, crie painéis e configure alertas.
Os clusters anexados do GKE instalam o coletor de métricas gke-metrics-agent no seu cluster. Este agente é baseado no OpenTelemetry Collector e é executado em todos os nós do cluster. Ele coleta métricas a cada minuto e as envia para o Cloud Monitoring.
Depois que as métricas do seu cluster forem carregadas, elas ficarão no seuGoogle Cloud projeto. Você pode agregar dados de todos os seus clusters, criar painéis personalizados, explorar os dados de um único cluster, visualizar gráficos de linhas, configurar alertas e muito mais.
Usando o Metrics Explorer
Para visualizar as métricas de um recurso monitorado usando o Metrics Explorer, faça o seguinte:
No Google Cloud console, vá para a página do explorador de métricasleaderboard :
Se você usar a barra de pesquisa para encontrar esta página, selecione o resultado cujo subtítulo é Monitoramento .
Na barra de ferramentas do Google Cloud console, selecione seu Google Cloud projeto. Para configurações do App Hub , selecione o projeto host do App Hub ou o projeto de gerenciamento da pasta habilitada para o aplicativo.
No elemento Métrica , expanda o menu Selecionar uma métrica , insira Kubernetes Container na barra de filtros e use os submenus para selecionar um tipo de recurso e uma métrica específicos:
No menu Recursos ativos , selecione Contêiner do Kubernetes .
No menu Categorias de métricas ativas , selecione Anthos .
No menu Métricas ativas , selecione Tempo de uso da CPU .
Clique em Aplicar .
Para remover séries temporais da exibição, use o elemento Filtro .
Para combinar séries temporais, use os menus no elemento Agregação . Por exemplo, para exibir a utilização da CPU das suas VMs, com base na zona, defina o primeiro menu como Média e o segundo como Zona .
Todas as séries temporais são exibidas quando o primeiro menu do elemento Agregação é definido como Não agregado . As configurações padrão para o elemento Agregação são determinadas pelo tipo de métrica selecionado.
Para cotas e outras métricas que relatam uma amostra por dia, faça o seguinte:
No painel Exibir , defina o Tipo de widget como Gráfico de barras empilhadas .
Defina o período de tempo para pelo menos uma semana.
Tipo de recurso monitorado por métricas
As métricas são coletadas usando um dos três tipos de recursos monitorados a seguir. Esses tipos correspondem a um objeto do Kubernetes para o qual a medição está sendo feita:
Por exemplo, medições sobre um Pod usariam o tipo de recurso monitorado k8s_pod . Essas métricas, portanto, incluiriam rótulos para pod_name e namespace_name , que identificam um Pod específico. Se quiser ver métricas para um cluster específico, use o seguinte formato:
attachedClusters/CLUSTER_NAME
Um conjunto diferente de tipos de métricas é usado para cada tipo de recurso monitorado . Para saber mais sobre esses tipos de métricas, consulte Métricas do sistema do GKE .
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-06-12 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)"]]