Writing Application Logs

When a request is sent to your application running in App Engine, request and response details are logged automatically, and can be viewed in the Google Cloud Platform Console Stackdriver Logs Viewer.

See Quota Policy for the logs retention policy and for the maximum size of log entries. If you want to store your logs for a longer period, you can export your logs to Cloud Storage. You can also export your logs to BigQuery and Pub/Sub for further processing.

For a list of available logs you can use, see App Engine standard environment logs.

Writing application logs

When your application handles a request, it can write its own logging messages to stdout and stderr. Write your application logs using stdout for output and stderr for errors. These files are automatically collected and can be viewed in the Logs Viewer. Note that this does not provide log levels that you can use for filtering in the Logs Viewer; however, the Logs Viewer does provide other filtering, such as text, timestamp, etc. Only the most recent entries in the Logs Viewer are retained in order to limit their size.

To emit a log item from your Node.js app, you can use the console.log() or console.error() functions, which have the following log levels:

  • Items emitted with console.log() have the INFO log level.
  • Items emitted with console.error() have the ERROR log level.
  • Internal system messages have the DEBUG log level.

For Node.js apps, you can optionally use the Bunyan or Winston plugins, or use the Stackdriver Logging Cloud Client Library for Node.js directly. For more information, see Setting Up Stackdriver Logging for Node.js.

Viewing application logs

You can view your application logs using the Logs Viewer:

  1. Go to the Stackdriver > Logging page in the GCP Console:

    Go to the Logs Viewer page

  2. Select an existing GCP project at the top of the page.

  3. From the drop-down menus, select GAE Application as your resource type to see your App Engine logs.

You can use the drop-down menus and other components of the Logs Viewer to filter or search the logs for relevant entries. See Logs Viewer filter interfaces for more details.

Filtering application logs

To filter log entries by label or text search in the Logs Viewer, see Basic Logs Filters.

To write advanced logs filters to further specify a set of log entries, see Advanced Logs Filters.

To view the logs for specific instances, services, or versions, filter by that resource's ID in the Logs Viewer. To find service and version IDs look in the App Engine dashboard.

In the Logs Viewer, log entries correlated by the same trace can be viewed in a "parent-child" format.

See the GitHub documentation for instructions for correlating log entries.

Once you have correlated the log entries, following are instructions for viewing correlated log entries:

  1. Open your App Engine logs in the Logs Viewer; for details, see Viewing application logs.

  2. Expand a request log by clicking the small black triangle to the left of the log entry. You see your request and app logs displayed in a nested format.

Additionally:

  • The highest severity from the "child" log entries does not automatically apply to the top-level entry. If that behavior is desired, manually set the highest severity in the top-level entry.
  • Set the httpRequest.requestUrl field for the top-level log.
Was this page helpful? Let us know how we did:

Send feedback about...

App Engine standard environment for Node.js docs