configure logger on worker initialization #4624
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.
Description Of Changes
Without this change, we don't configure the loguru logger on the worker app/process. This means that even though we may have set e.g.
logging.serialization = json
on the worker container, it wouldn't actually impact the log behavior on the worker in any way.With this change, before booting up the celery worker app, we now invoke the same
setup()
logging function that's invoked when creating our fides fast API app (i.e. withincreate_fides_app
). This ensures consistent logging configuration across both our server and worker apps 👍Code Changes
fides.api.util.logger.setup
within the_create_celery
helper function that's invoked as part of the worker runtime bootstrap, i.e. withinfides.api.worker.start_worker
Steps to Confirm
logging.serialization = "json"
andcelery.task_always_eager = false
in your app config (i.e. infides.toml
)nox -s dev -- worker
in fides (OSS)turbo run dev
in theclients
dirdocker logs -f fides-worker-1
Pre-Merge Checklist
CHANGELOG.md