Forces JSON logging format by disabling "other" loggers (which may not be logging in JSON)
Upon merge, the new container will be pushed to the testing cluster, and we can evaluate the logging change there.
Testing
Using the prod docker-compose environment, you can observe that on current master, each request generates at least two events, on JSON and one plaintext:
Two changes here, both intended to standardize the production logging story:
Upon merge, the new container will be pushed to the testing cluster, and we can evaluate the logging change there.
Testing
Using the prod docker-compose environment, you can observe that on current master, each request generates at least two events, on JSON and one plaintext:
Whereas on this branch, after running
docker-compose -f prod-docker-compose.yaml up --build
, you'll see only one log event per request: