Estratégias para solução de problemas do App Engine
As seções a seguir explicam como aplicar estratégias gerais de solução de problemas
para resolver o erro. Se os erros continuarem
mesmo depois de seguir as etapas nos guias de solução de problemas, consulte O que vem a seguir.
Com os registros correlacionados, é possível identificar a solicitação que precisa de mais análises, encontrar o trace da solicitação e analisar a causa raiz do problema. Para mais
informações sobre como gravar registros, consulte Gravar registros de aplicativos.
Resolver a latência inesperada
Se você tiver problemas com a latência, faça o seguinte:
Verifique se a latência está afetando todas as solicitações para seu serviço ou apenas uma pequena porcentagem. O painel de latência do App Engine mostra a latência dos percentis 50º, 95º e 99º.
Se você tiver alta latência nas três métricas, terá alta latência
em pelo menos 50% das solicitações. Se você só encontrar latência alta no gráfico do 99º percentil, isso significa que 1% das suas solicitações têm latência alta.
Identifique a solicitação com alta latência para entender a origem dela. Use o Cloud Trace ou o Cloud Logging para entender quanto tempo uma solicitação específica levou. Para mais informações, consulte Noções básicas sobre a latência do app.
Para identificar solicitações com alta latência usando o Cloud Logging, aplique o filtro traceSampled=true para correlacionar os registros no Cloud Logging com os rastros no Cloud Trace. Para mais informações, consulte Integrar com o Cloud Logging.
Siga estas etapas para corrigir problemas de latência e melhorar a performance do serviço:
Por padrão, seu serviço do App Engine é acessível na Internet pública. No entanto,
é possível modificar o serviço para ter mais restrições na conectividade de entrada e saída
da rede.
É possível restringir as conexões de entrada com as configurações de entrada ou com as regras de firewall do App Engine. Se você tiver problemas para se conectar ao serviço do App Engine de
redes VPC ou recursos da Internet, verifique o seguinte:
Para resolver outros problemas de conectividade, faça o seguinte:
Defina uma instância no modo de depuração
e use SSH para a instância enquanto ela continua recebendo tráfego em tempo real. Depois
de se conectar à instância, você pode depurar a instância usando ferramentas comuns de linha
de comando.
[[["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-01 UTC."],[[["\u003cp\u003eThis page provides guidance on troubleshooting errors encountered while using App Engine, with links to resources for deployment, serving, latency, and connectivity issues.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your application uses Cloud Logging effectively to correlate request logs with application logs, which aids in identifying and analyzing the root cause of issues.\u003c/p\u003e\n"],["\u003cp\u003eWhen addressing latency problems, determine if it affects all requests or a small percentage and utilize the App Engine latency dashboard, Cloud Trace, or Cloud Logging to pinpoint the source of latency.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine service connectivity issues can be resolved by reviewing ingress settings, App Engine firewall rules, and VPC network firewall rules, and by using debug mode to access instances.\u003c/p\u003e\n"],["\u003cp\u003eIf you continue to encounter errors even after following the troubleshooting steps, then contact support for further assistance.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot App Engine errors\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes the troubleshooting process for errors you might encounter while\nusing App Engine. For information about incidents affecting Google Cloud\nservices, refer to the [Google Cloud Service Health Dashboard](https://status.cloud.google.com/summary) and [All incidents reported for App Engine](https://status.cloud.google.com/products/kchyUtnkMHJWaAva8aYc/history).\n\nSee the following pages for guidance on how to resolve issues related to your app:\n\n- [Troubleshoot deployment issues](/appengine/docs/flexible/troubleshooter/deployment)\n- [Troubleshoot serving issues](/appengine/docs/flexible/troubleshooter/serving)\n- [Troubleshoot elevated latency in your app](/appengine/docs/flexible/troubleshooter/latency)\n- [App Engine connectivity strategies](/appengine/docs/flexible/troubleshooter/connectivity)\n\nApp Engine troubleshooting strategies\n-------------------------------------\n\nThe following sections explain how you can apply general troubleshooting\nstrategies to resolve your error. If you continue to encounter errors\neven after following the steps in the troubleshooting guides, see [What's next](#whats-next).\n\n### Output good logs using Cloud Logging\n\nTroubleshooting your app running on App Engine is easier if you have good\napplication logs for debugging. Ensure your application writes logs in a way that\n[correlates request logs with the application logs](/appengine/docs/flexible/writing-application-logs#correlate_logs).\n\nWith correlated logs you can identify the request that needs further analysis,\nfind the request trace, and analyze the root cause of the issue. For more\ninformation on writing logs, see [Write application logs](/appengine/docs/flexible/writing-application-logs#writing_app_logs).\n\n### Resolve unexpected latency\n\nIf you encounter issues with latency, do the following:\n\n1. Check if the latency is affecting all requests to your service or only a\n small percentage. The [App Engine latency dashboard](/appengine/docs/flexible/monitoring-and-alerting-latency#checking_the_latency_dashboard) shows 50th,\n 95th, and 99th percentile latency.\n\n If you have high latency on all three of these metrics, you have high latency\n for at least 50% of your requests. If you only see high latency in the\n 99th percentile graph, you have high latency in 1% of your requests.\n2. Identify the request with high latency to understand the source of\n latency. You can use Cloud Trace or Cloud Logging to understand how\n long a particular request has taken. For more information, see [Understanding app latency](/appengine/docs/flexible/monitoring-and-alerting-latency#understanding_app_latency).\n\n To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace. For more information, see [Integrate with Cloud Logging](/trace/docs/trace-log-integration).\n3. Try the following steps to fix latency issues, and improve service performance:\n\n - Adjust your [CPU, memory, and disk resources](/appengine/docs/flexible/reference/app-yaml#services).\n\n - Adjust [scaling settings](/appengine/docs/flexible/how-instances-are-managed#instance_scaling).\n\n \u003c!-- --\u003e\n\n - Consider using [Profiler](/appengine/docs/flexible/cloud-profiler).\n\n - Modify your source code.\n\nFor more information on how to troubleshoot elevated latency issues, see [Troubleshoot elevated latency in your app](/appengine/docs/flexible/troubleshooter/latency).\n\n### Resolve issues with connectivity\n\nBy default, your App Engine service is accessible on the public internet, however,\nyou can modify the service to have more restrictions on ingress and egress\nnetwork connectivity.\n\nYou can restrict ingress connections with the ingress settings, or through App Engine firewall rules. If you have trouble connecting to your App Engine service from\nVPC networks or internet resources, check the following:\n\n- [Ingress settings](/appengine/docs/flexible/ingress-settings)\n- [App Engine firewall](/appengine/docs/flexible/understanding-firewalls)\n\nTo resolve other connectivity issues, do the following:\n\n- Set an instance into [debug mode](/appengine/docs/flexible/debugging-an-instance),\n and SSH to the instance while it continues to take live traffic. After\n connecting to the instance, you can debug the instance using common command\n line tools.\n\n- Check the [firewall rules on your VPC network](/firewall/docs/firewalls) to make\n sure traffic isn't blocked.\n\n- Check if you have [disabled the external IP](/appengine/docs/flexible/disable-external-ip).\n\nFor more information on how to troubleshoot connectivity issues, see\n[App Engine connectivity strategies](/appengine/docs/flexible/troubleshooter/connectivity).\n\n### What's next\n\nIf you can't find a solution to your problem in the App Engine\ndocumentation, follow these steps:\n\n- Open a support case by contacting [Cloud Customer Care](/support-hub).\n- Get support from the community by [asking questions on StackOverflow](https://stackoverflow.com/questions/tagged/google-app-engine), or search for similar issues using the `google-app-engine` tag.\n- Open bugs or feature requests by using the [public issue tracker](/support/docs/issue-trackers).\n\nFor more information, see [App Engine community](/appengine/docs/flexible/community)."]]
