IssueTracker

• Support Level: White: Free / Basic / Bronze

Business Impact

The Error Reporting page does not correlate errors seen in App Engine Python 3+ with request details of the request that caused it (request URL, response status, User-Agent).

• Application ID(s) including service and version: NA
  Log/Graph data:

Issue summary

In Python 2.7, the request log (logs/appengine.googleapis.com%2Frequest_log) included error details of the error thrown during handling a request. This request log had a severity of ERROR and was reported in Error Reporting with correlated request details (URL, Status code, User-Agent).

In Python 3.x, if a request ends in an exception being thrown, this error is logged in stderr (logs/stderr) with no request correlation, just the module and version ID of the app. The corresponding GAE request log is not marked as an ERROR log, and does not have the error details (message, traceback etc). Error Reporting displays the stderr logs without any request correlation details like request URL, response status, User-Agent.

Fix

The first step for an app is to set up correlated logging. If the app is using the Cloud Logging SDK, logging.exception() ensures the error gets flagged by Error Reporting. Unhandled exceptions from request handlers also get picked up by Error Reporting.

Currently, in second generation runtimes, the HTTP request details do not get displayed in the Error Reporting dashboard.

The ETA for this fix is end of Q1 2024.

Note: As part of the fix, only the HTTP request details will get displayed on the Error Reporting dashboard. Due to how logging works in second generation runtimes, the Response Code is not part of error logs, thus it will not be displayed in the Error Reporting dashboard.