We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When a job/task fails the logs contain what happened, but often you want to add a error message/explanation as part of the log
Is there a way to do this?
At first glance it would seem a json col in the events table would work and allow submitting "context" info as part of the job attempt/fail
Thanks
The text was updated successfully, but these errors were encountered:
https://procrastinate.readthedocs.io/en/stable/howto/production/logging.html#make-the-most-out-of-the-logging-system
Does the above section help?
In the case of a failed job, there would be an exc_info atttribute in the extra field that holds the caught exception.
exc_info
extra
Another way is to define a middleware and catch/re-raise exceptions there.
I can see how it would be useful to have error context persisted for failed job events.
Sorry, something went wrong.
No branches or pull requests
When a job/task fails the logs contain what happened, but often you want to add a error message/explanation as part of the log
Is there a way to do this?
At first glance it would seem a json col in the events table would work and allow submitting "context" info as part of the job attempt/fail
Thanks
The text was updated successfully, but these errors were encountered: