You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some third party libraries may make log calls with keys which we don't want to log. We should be able to exclude these keys from the final log line.
For example, when overriding uvicorn logging. The color_message key is currently printed (it is used by their custom color formatter). If we could exclude this key, then we could prevent the following output:
at=INFO msg="Started server process [97819]" color_message="Started server process [%d]"
at=INFO msg="Waiting for application startup."
at=INFO msg="Application startup complete."
at=INFO msg="Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)" color_message="Uvicorn running on %s://%s:%d (Press CTRL+C to quit)"
The text was updated successfully, but these errors were encountered:
Some third party libraries may make log calls with keys which we don't want to log. We should be able to exclude these keys from the final log line.
For example, when overriding
uvicorn
logging. Thecolor_message
key is currently printed (it is used by their custom color formatter). If we could exclude this key, then we could prevent the following output:The text was updated successfully, but these errors were encountered: