MPP-3777 - Tune logs for Google Cloud Profiler #4545
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Google Cloud Profiler (GCP) creates a root logger with the standard configuration, if no existing root logger exists. This logger will output a standard log line to
stderr
, like:In production, anything sent to
stderr
is treated as an error.This adds a root logger that uses the Mozlog format, so that GCP and other 3rd-party package loggers will use JSON logging to
stderr
by default.This also sets
"propagate": False
on our loggers, to avoid two logs for each log call.How to test
Set these environment variables, for example in
.env
:On main, when you run
./manage.py runserver
, you should see messages like:When you visit http://127.0.0.1:8000/, you'll see paired log messages:
The
INFO:request.summary:
lines are added by the Google Cloud Provider setup, which changes the logging configuration.On this branch (
tune-logs-for-google-cloud-profiler-mpp-3777
), when you run./manage.py runserver
, you should see messages like:When you visit http://127.0.0.1:8000/, the second log lines are missing: