Repository navigation
structure the logs - #3188
structure the logs#3188
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Alc-Alc
left a comment
There was a problem hiding this comment.
reviewing is hard because logging API is just not the greatest
|
Hi, I am the author of django-structlog. I noticed you started using django-structlog and you also use celery. I'd like to make sure you are aware that django-structlog also offers a celery integration. When configured, it automatically logs celery events (ex task_started, task_finished, etc.) and it also binds useful metadata to the logs (task_id, the request_id of the request that initated the task, parent_it, and more). I just wanted to be sure you did not miss this because I believe this could be useful for you. Have a great day. https://django-structlog.readthedocs.io/en/latest/events.html#celery |
|
thanks @jrobichaud ! we will do a follow up to add structure any missed logs. @Alc-Alc want to add this to list? |
sure, I will have it done later today |
Use django-structlog along with nginx config to structure log output on deploys
Local logs use structlog.dev.ConsoleRenderer so its pretty/easy to ready still when developing