Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Configurar coleta de dados gerenciada com o Managed Service para Prometheus
Esta página explica como você pode configurar a coleta de dados gerenciada com Google Cloud Serviço Gerenciado para Prometheus para GKE no Azure. Este recurso está disponível em clusters do Azure que executam o Kubernetes versão 1.25 ou posterior. Também é compatível com clusters do Kubernetes na versão 1.24 para clientes que já se inscreveram para uma prévia deste recurso naquela versão.
Com esse recurso, você pode usar um recurso do PodMonitoring para escolher as métricas que deseja ingerir no Cloud Monitoring. Você pode então visualizar essas métricas no Google Cloud console.
Limitações
Este recurso não está disponível em clusters do Kubernetes anteriores à versão 1.24.
Este recurso requer uma carga de trabalho do Linux.
Configurar coleta de dados gerenciada
Para configurar a coleta de dados gerenciada com o Managed Service for Prometheus, conclua as seguintes etapas:
Autorize as contas de serviço gmp-system/collector e gmp-system/rule-evaluator a gravar suas métricas:
Substitua GOOGLE_PROJECT_ID pelo seu Google CloudID do projeto.
Adicionar esta ligação IAM falha a menos que pelo menos um cluster tenha sido criado em seu Google Cloud projeto. Isso ocorre porque o pool de identidades de carga de trabalho ao qual ele se refere ( GOOGLE_PROJECT_ID .svc.id.goog ) não é provisionado até a criação do cluster.
Crie um cluster com o comando padrão gcloudCreate your cluster , mas inclua o sinalizador opcional --enable-managed-prometheus . Por exemplo:
Para configurar quais métricas de carga de trabalho você deseja ingerir, configure um recurso PodMonitoring . Para ver um exemplo, consulte Configurar um recurso PodMonitoring na documentação da coleta de dados gerenciados com o Managed Service for Prometheus.
Após habilitar a coleta de dados gerenciada com o Managed Service for Prometheus, o GKE no Azure cria o namespace gmp-system . Não modifique nem implante nada neste namespace. O GKE no Azure também cria o namespace gmp-public . O Managed Service for Prometheus usa o namespace gmp-public para implantar o recurso OperatorConfig .
Atualize sua configuração do Prometheus
Para desabilitar ou reabilitar a coleta de dados do Prometheus, use o comando padrão gcloudUpdate your cluster , mas adicione um parâmetro opcional --disable-managed-prometheus ou --enable-managed-prometheus. Por exemplo:
gcloudcontainerazureclustersupdate\...
--disable-managed-prometheus
OR
--enable-managed-prometheus
[[["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,["Set up managed data collection with Managed Service for Prometheus\n\nThis page explains how you can set up managed data collection with\n[Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) for\nGKE on Azure. This feature is available on Azure clusters\nrunning Kubernetes version 1.25 or later. It is also supported on Kubernetes\nclusters at version 1.24 for customers who had earlier signed up for a\npreview of this feature on that version.\n\nWith this feature, you can use a PodMonitoring resource to choose the metrics\nthat you want to ingest into Cloud Monitoring. You can then view these\nmetrics in the Google Cloud console.\n\nLimitations\n\n- This feature is not available on Kubernetes clusters earlier than version 1.24.\n\n\u003c!-- --\u003e\n\n- This feature requires a Linux workload.\n\nSet up managed data collection\n\nTo set up managed data collection with Managed Service for Prometheus, complete the following steps:\n| **Note:** Starting with Kubernetes version 1.28, manual policy binding to authorize service accounts for data collection is no longer necessary. The required permissions are now automatically granted to this service account. You can therefore disregard step 1 in this section.\n\n1. Authorize the `gmp-system/collector` and `gmp-system/rule-evaluator` service\n accounts to write your metrics:\n\n gcloud projects add-iam-policy-binding \u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e \\\n --member=\"serviceAccount:\u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e.svc.id.goog[gmp-system/collector]\" \\\n --role=roles/monitoring.metricWriter\n gcloud projects add-iam-policy-binding \u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e \\\n --member=\"serviceAccount:\u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e.svc.id.goog[gmp-system/rule-evaluator]\" \\\n --role=roles/monitoring.viewer\n gcloud projects add-iam-policy-binding \u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e \\\n --member=\"serviceAccount:\u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e.svc.id.goog[gmp-system/rule-evaluator]\" \\\n --role=roles/monitoring.metricWriter\n\n Replace \u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e with your Google Cloud\n project ID.\n\n Adding this IAM binding fails unless at least one\n cluster has been created in your Google Cloud project. This is because the\n workload identity pool it refers to\n (\u003cvar translate=\"no\"\u003eGOOGLE_PROJECT_ID\u003c/var\u003e`.svc.id.goog`) isn't provisioned until\n cluster creation.\n2. Create a cluster with the standard `gcloud`\n [Create your cluster](/kubernetes-engine/multi-cloud/docs/azure/how-to/create-cluster#create_your_cluster)\n command, but include the optional `--enable-managed-prometheus` flag. For\n example:\n\n gcloud container azure clusters create \\\n ...\n --enable-managed-prometheus\n\n3. To configure which workload metrics you want to ingest, set up a\n [PodMonitoring](https://github.com/GoogleCloudPlatform/prometheus-engine/blob/v0.4.3-gke.0/doc/api.md#podmonitoring)\n resource. For an example, see\n [Configure a PodMonitoring resource](/stackdriver/docs/managed-prometheus/setup-managed#gmp-pod-monitoring)\n in the managed data collection with Managed Service for Prometheus documentation.\n\nAfter you enable managed data collection with Managed Service for Prometheus, GKE on Azure creates the\n`gmp-system` namespace. Don't modify or deploy anything in this namespace.\nGKE on Azure also creates the `gmp-public` namespace. Managed Service\nfor Prometheus uses the `gmp-public` namespace to deploy the\n[OperatorConfig](https://github.com/GoogleCloudPlatform/prometheus-engine/blob/v0.4.3-gke.0/doc/api.md#operatorconfig)\nresource.\n\nUpdate your Prometheus configuration To disable or re-enable Prometheus data collection, use the standard `gcloud` [Update your cluster](/kubernetes-engine/multi-cloud/docs/azure/how-to/update-cluster#update_your_cluster) command, but add a --disable-managed-prometheus or --enable-managed-prometheus optional parameter. For example:\n\n\u003cbr /\u003e\n\n gcloud container azure clusters update \\\n ...\n --disable-managed-prometheus\n OR\n --enable-managed-prometheus\n\nWhat's next\n\n- Discover how to [Configure a query user interface](/stackdriver/docs/managed-prometheus/query) in the managed data collection with Managed Service for Prometheus documentation.\n- Learn about [Managed rule evaluation and alerting](/stackdriver/docs/managed-prometheus/rules-managed) in the Google Cloud Managed Service for Prometheus documentation."]]
