Skip to content

fix: set ASGI logging level to WARNING to match WSGI behavior - #380

Closed
taeold wants to merge 2 commits into
GoogleCloudPlatform:mainfrom
taeold:dl-py-logs
Closed

fix: set ASGI logging level to WARNING to match WSGI behavior#380
taeold wants to merge 2 commits into
GoogleCloudPlatform:mainfrom
taeold:dl-py-logs

Conversation

@taeold

@taeold taeold commented Jun 17, 2025

Copy link
Copy Markdown
Contributor

ASGI logger defaults to INFO instead of WARNING which is the default for Python.

…enabled

When LOG_EXECUTION_ID is enabled, the WSGI implementation was setting the root logger
to WARNING level, which silenced info-level logs. This was inconsistent with:
- The ASGI implementation which correctly uses INFO level
- The default setup_logging() function which also uses INFO level

This change ensures that logger.info() calls are visible in both WSGI and ASGI stacks
when execution ID logging is enabled.
@taeold
taeold requested a review from maemayve June 17, 2025 22:14
@taeold taeold changed the title fix: set WSGI logging level to INFO instead of when enabling LOG_EXECUTION_ID Jun 17, 2025
@taeold

taeold commented Jun 17, 2025

Copy link
Copy Markdown
Contributor Author

Oh interesting. This directly conflicts w/ #336

@taeold

taeold commented Jun 17, 2025

Copy link
Copy Markdown
Contributor Author

Reported in #337

@taeold taeold changed the title fix: set WSGI logging level to INFO instead of WARNING when enabling LOG_EXECUTION_ID Jun 18, 2025
@taeold taeold closed this Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant