This repository has been archived by the owner on Sep 12, 2023. It is now read-only.
feat(logging): alternate loggers #48
Comments
|
Same goes with saq |
peterschutt
added a commit
that referenced
this issue
Nov 4, 2022
Configures the app to log with `structlog`. For #48
peterschutt
added a commit
that referenced
this issue
Nov 5, 2022
* feat(logs): structlog configuration. Configures the app to log with `structlog`. Closes #48 * Update docs/logging.md * docs(log): fixes. * feat(log): makes log processors configurable for the plugin. Also, some refactoring to accommodate the worker logger with separation of concerns. * feat(log): Adds log configuration for the worker.
Merged
peterschutt
added a commit
that referenced
this issue
Nov 5, 2022
* feat(logs): structlog configuration. Configures the app to log with `structlog`. Closes #48 * Update docs/logging.md * docs(log): fixes. * feat(log): makes log processors configurable for the plugin. Also, some refactoring to accommodate the worker logger with separation of concerns. * feat(log): Adds log configuration for the worker.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to be using structlog moving forward, so would be good to work out how this can be made configurable.
Also, for the structlog pattern, a
logdependency that injects a context local log object would be a nice to have. And, can that log object be shared with uvicorn??The text was updated successfully, but these errors were encountered: