Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Este guia mostra como conferir os registros do App Engine usando o
Explorador de registros e o console Google Cloud . Ao ver os registros do serviço, é possível
monitorar facilmente o desempenho dos serviços da Web.
Antes de começar
Este guia faz parte de uma série introdutória que orienta você na criação
de um app do App Engine. Para começar do início da série, consulte
Como criar um app Node.js no App Engine.
Na lista Recurso, selecione Aplicativo do GAE e clique em
Aplicar.
Em Pesquisar todos os campos, digite o nome do registro que você quer
pesquisar.
Use os filtros na parte superior da página para ver diferentes fluxos de registro como erro padrão, solicitações HTTP ou atividade interna do App Engine.
É possível pesquisar itens com conteúdo específico e restringir os registros a um determinado serviço ou versão do App Engine.
A seguir
Para criar ainda mais com o Node.js e o App Engine, consulte Tutoriais.
[[["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-08-19 UTC."],[[["\u003cp\u003eThis guide explains how to view App Engine logs to monitor the performance of your web services using the Logs Explorer and the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eYou can access the Logs Explorer in the Google Cloud console to view logs.\u003c/p\u003e\n"],["\u003cp\u003eWithin the Logs Explorer, you can filter logs by selecting the GAE application resource.\u003c/p\u003e\n"],["\u003cp\u003eYou are able to use the search bar to look for a specific type of log or restrict by a specific App Engine service or version.\u003c/p\u003e\n"]]],[],null,["# View your service's Logs\n\n\u003cbr /\u003e\n\n| **Note:** If you are deploying a new Node.js web service to Google Cloud, we recommend getting started with [Cloud Run](/run/docs/quickstarts/build-and-deploy/deploy-nodejs-service).\n\nThis guides shows you how to view App Engine logs by using the\nLogs Explorer and the Google Cloud console. By viewing your service's logs, you\ncan easily monitor the performance of your web services.\n\nBefore you begin\n----------------\n\nThis guide is part of an introductory series that walks you through how to build\nan App Engine app. To start from the beginning of the series, see\n[Building a Node.js App on App Engine](/appengine/docs/standard/nodejs/building-app).\n\nBefore continuing with this guide, review the steps for how to\n[update your web service](/appengine/docs/standard/nodejs/building-app/updating-web-service).\n\nView logs by using the Logs Explorer\n------------------------------------\n\nTo view your service's logs, do the following:\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/viewer?resource=gae_app)\n2. In the **Resource** list, select **GAE application** , and then click\n **Apply**.\n\n3. In the **Search all fields** field, enter the name of the log that you want\n to search.\n\nYou can use the filters at the top of the page to view different log streams\nsuch as standard error, HTTP requests, or App Engine internal activity.\n\nYou can search for items containing specific content, and you can also restrict\nthe logs to a specific App Engine service or version.\n\nWhat's next\n-----------\n\n- To build further with Node.js and App Engine, see [Tutorials](/docs/tutorials).\n\n- Learn more about [using the Logs Explorer](/logging/docs/view/logs-explorer-interface).\n\n- Learn more about [monitoring and alerting latency](/appengine/docs/standard/monitoring-and-alerting-latency)."]]
