METHOD_NAME: o nome da operação ou do método do serviço. Para chamadas de API, esse nome deve ser o nome do método da API.
LOCATION: o local do recurso. Pode ser uma região, uma zona ou global. Por exemplo, as entradas currentLocations: "us-central1"(regional) ou currentLocations: "us-central1-a" indicam que a região é "us-central1" ou currentLocations: "global".
Identifique o valor methodName associado no registro de erros. Esse nome representa o método da API em que o limite de taxa foi excedido, por exemplo: v1.compute.instances.stop.
Identifique o local relevante nos registros de auditoria.
Verifique as cotas e os limites do Concurrent operations per project.
A página Cotas lista o uso e os limites das cotas para seu projeto.
A lista é classificada por padrão para mostrar primeiramente as cotas mais usadas,
o que ajuda a ver os limites que correm risco de serem excedidos.
Para filtrar a lista e ver o uso e o limite de uma cota específica,
selecione Cota ou Métrica no campo Filtro.
Por exemplo, selecione a cota pelo nome Concurrent global operations per project operation type ou
selecione Service: Compute Engine API, type: System Limit e uma palavra-chave concurrent para listar todas as cotas de operação simultânea. A filtragem fornece uma lista de cotas simultâneas. Nessa lista, é possível pesquisar a cota afetada.
Para filtrar a cota de uma operação específica, adicione Dimensões à consulta de filtro
e selecione o operation_type (mostrado como methodName nos registros de auditoria).
Por exemplo, selecione instances_stop
para ver o uso da cota e o limite da operação instances.stop.
Para filtrar a cota de uma região específica, adicione Dimensões à consulta de filtro
e selecione a região (mostrada como currentLocations nos registros de auditoria).
Por exemplo, selecione us-central1 para ver o uso da cota e o limite da região us-central1.
Os filtros region e operation_type podem ser usados juntos para conferir o uso e o limite da cota de uma operação específica em uma região específica.
gcloud
Use a CLI do Google Cloud para ver o uso e o limite de cotas de
operação simultânea.
Para usar essa abordagem, instale
o componente
de comandos alfa. Se você estiver usando o Cloud Shell para interagir com Google Cloud, a
Google Cloud CLI será instalada.
Para conferir uma cota de operação, use o seguinte comando:
gcloud alpha services quota list \
--service=compute.googleapis.com \
--consumer=projects/PROJECT_ID
Substitua PROJECT_ID pelo ID do projeto com a cota que você
quer visualizar.
Essas cotas geralmente são agrupadas em duas categorias:
Confira o gráfico de uso da cota. Se o uso estiver próximo ou acima do limite da cota durante o período dos registros de erros, isso significa que a cota ou o limite do sistema foi excedido.
Para conferir gráficos que mostram o uso atual e o pico de uso, acesse a cota e clique em monitoringMonitoramento.
Talvez seja necessário rolar até o fim da tabela.
O gráfico de monitoramento vai confirmar a causa do erro rateLimitExceeded, com a cota/limite específico. Se os valores atuais estiverem acima dos limites, isso significa que o limite do sistema foi excedido.
Como os limites do sistema não podem ser modificados, recomendamos as seguintes práticas recomendadas para reduzir o número de operações simultâneas.
[[["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-09-03 UTC."],[[["\u003cp\u003eThis document guides you through troubleshooting \u003ccode\u003erateLimitExceeded\u003c/code\u003e errors in Compute Engine, which indicate concurrent operation limit issues.\u003c/p\u003e\n"],["\u003cp\u003eTo find the cause, use the Logs Explorer to filter Compute Engine API error logs using a specific query that looks for \u003ccode\u003erateLimitExceeded\u003c/code\u003e messages, service names, and error codes.\u003c/p\u003e\n"],["\u003cp\u003eThe error logs provide details like the \u003ccode\u003emethodName\u003c/code\u003e of the affected API call and the \u003ccode\u003eLOCATION\u003c/code\u003e of the resource, which can then be used to determine the specific quota being exceeded.\u003c/p\u003e\n"],["\u003cp\u003eThe Quotas page in the Google Cloud console, or the gcloud CLI, can be used to check concurrent operation quotas per project, per project per operation type, or by specific regions to see if current usage is nearing or exceeding set limits.\u003c/p\u003e\n"],["\u003cp\u003eTo avoid future \u003ccode\u003erateLimitExceeded\u003c/code\u003e errors, best practices include waiting for operations to complete, relying on error codes, minimizing retries, using client-side rate limiters, and splitting applications across multiple projects.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Compute Engine concurrent operations quota\n\n*** ** * ** ***\n\nThis document describes how to troubleshoot concurrent operation limits in Compute Engine that are caused by [`rateLimitExceeded`](https://cloud.google.com/compute/operations-quota) errors.\n\nTo help identify the cause of a `rateLimitExceeded` error, use the following troubleshooting steps:\n\n1. In the Google Cloud console, go to the **Logs Explorer** page:\n\n [Go to **Logs Explorer**](https://console.cloud.google.com/logs/query)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Logging**.\n2. To filter the error logs generated by Compute Engine API, enter the following logging query in the query editor.\n\n ```\n log_id(\"cloudaudit.googleapis.com/activity\")\n protoPayload.serviceName=\"compute.googleapis.com\"\n protoPayload.response.error.code=403\n protoPayload.status.message=\"Rate Limit Exceeded\"\n ```\n\n The filtered error logs should look similar to the following: \n\n ```\n \"protoPayload\":{\n \"@type\": \"type.googleapis.com/google.cloud.audit.AuditLog\",\n \"status\": {\n \"message\": \"Rate Limit Exceeded\"\n }\n \"serviceName\": \"compute.googleapis.com\",\n \"methodName\": \"METHOD_NAME\",\n ...\n ...\n \"response\": {\n \"error\": {\n \"message\": \"Rate Limit Exceeded\",\n \"code\": 403,\n \"errors\": [\n {\n \"message\": \"Rate Limit Exceeded\",\n \"reason\": \"rateLimitExceeded\",\n \"domain\": \"usageLimits\"\n }\n ]\n },\n \"@type\": \"type.googleapis.com/error\"\n },\n \"resourceLocation\": {\n \"currentLocations\": [\n \"LOCATION\"\n ]\n },\n ...\n ... \n ```\n\n The error details contain the following values:\n - \u003cvar translate=\"no\"\u003eMETHOD_NAME\u003c/var\u003e: The name of the service method or operation. For API calls, this name should be the name of the API method.\n\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: The location of the resource. This can be a region, zone or global. For example, the entries `currentLocations: \"us-central1\"`(Regional) or `currentLocations: \"us-central1-a\"` indicate that the region is `\"us-central1\"` or `currentLocations: \"global\"`.\n\n3. Identify the associated `methodName` value from the error log. This name represents the API method for which the rate limit exceeded, for example: `v1.compute.instances.stop`.\n\n4. Identify the relevant location in the audit logs.\n\n5. Check the `Concurrent operations per project` quotas and limits.\n\n ### Console\n\n 1. In the Google Cloud console, go to the **Quotas** page.\n\n [Go to Quotas](https://console.cloud.google.com/iam-admin/quotas)\n\n The **Quotas** page lists the quota usage and limits for your project.\n By default, the list is sorted to show your most used quotas first,\n which helps you see limits that are at risk of being exceeded.\n 2. To filter the list and to view the usage and limit for any specific quota,\n select **Quota** or **Metric** in the **Filter** field.\n\n For example, either select the Quota by the name `Concurrent global operations per project operation type` or\n select `Service: Compute Engine API`, `type: System Limit` and a key word `concurrent` to list all the concurrent operation quotas. Filtering provides a list of concurrent quotas. From this list, you can search for the affected quota.\n To filter the quota for a specific operation, add **Dimensions** to the filter query\n and select the **operation_type** (shown as **methodName** in the audit logs).\n\n For example, select `instances_stop`\n to see the quota usage and limit for the operation `instances.stop`.\n\n To filter the quota for a specific region, add **Dimensions** to the filter query\n and select the **region** (shown as **currentLocations** in the audit logs).\n\n For example, select `us-central1` to see the quota usage and limit for `us-central1` region.\n\n Filters **region** and **operation_type** can be used together to view the quota usage and limit for a specific operation in a specific region.\n\n ### gcloud\n\n\n | **Preview**\n |\n |\n | This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n | of the [Service Specific Terms](/terms/service-terms#1).\n |\n | Pre-GA products and features are available \"as is\" and might have limited support.\n |\n | For more information, see the\n | [launch stage descriptions](/products#product-launch-stages).\n\n \u003cbr /\u003e\n\n You can use the Google Cloud CLI to view the usage and limit of concurrent\n operation quotas.\n\n To use this approach, ensure that you have installed\n the [alpha commands](/sdk/docs/components#alpha_and_beta_components)\n component. If you're using Cloud Shell to interact with Google Cloud, the\n Google Cloud CLI is installed for you.\n\n To view an operation quota, use the following command: \n\n ```\n gcloud alpha services quota list \\\n --service=compute.googleapis.com \\\n --consumer=projects/PROJECT_ID\n ```\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the ID of the project for which you\n want to view the quota.\n\n These quotas are generally grouped into two categories:\n - Global or regional\n - Per project or per project per operation type\n\n For more information, see [Concurrent operation quota groups](https://cloud.google.com/compute/operations-quota#operation_groups).\n6. Check the usage chart for the quota. If the usage is close to or above the quota limit during the period of error logs, it means that the quota or system limit is exceeded.\n\n To view charts that show current and peak usage, go to the quota and then\n click monitoring **Monitoring**.\n You might need to scroll right to the end of the table.\n\n The monitoring graph will confirm the cause of `rateLimitExceeded` error, with the specific quota/limit. If the current values are above the limit values, it means that the system limit is exceeded.\n Since system limits can't be modified, we recommend the following best practices to reduce the number of concurrent operations.\n\n Some of the best practices are as follows:\n - [Wait for operations to be done](/compute/docs/api/best-practices#wait-for-operations)\n - [Rely on error codes, not error messages](/compute/docs/api/best-practices#rely-on-errors-not-messages)\n - [Minimize client-side retries to preserve API rate limits](/compute/docs/api/best-practices#preserve-API-rate-limits)\n\n Any of the following methods can be used to minimize retries:\n - [Avoid short polling](/compute/docs/api/best-practices#avoid-short-polling)\n - [Use bursting sparingly and selectively](/compute/docs/api/best-practices#limit-bursting)\n - [Always make your calls in a retry loop with exponential backoff](/compute/docs/api/best-practices#retry-with-exponential-backoff)\n - [Use a client-side rate limiter](/compute/docs/api/best-practices#use-client-side-rate-limiter)\n - [Split up your applications across multiple projects](/compute/docs/api/best-practices#multiple-projects)"]]
