[LLSC-51] Fix logging within backend #14
Open
+84
−19
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.
Notion ticket link
Add startup Logs (Fix logging) for backend
Implementation description
alembic.ini
config was taking control over logging configurations and suppressing other loggers. Given that going without thealembic.ini
config doesn't seem viable at the moment, I've stuck to basing all loggers in the API off of one sublogger, and using a function to create child loggers for more context.Steps to test
pdm run dev
To add a logger to a new service or file, use the
LOGGER_NAME
function inapp/utilities/constants.py
What should reviewers focus on?
Checklist