Store extended Celery task attributes in backend #3855
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
> Enables extended task result attributes (name, args, kwargs, worker, > retries, queue, delivery_info) to be written to backend. https://docs.celeryq.dev/en/stable/userguide/configuration.html#result-extended Without this the information in the result backend is rather opaque. You can only see the task_id's of tasks that have executed. With the setting enabled you can see the task name, queue and other metadata.
|
Ping @browniebroke |
|
That screenshot is when using a different result backend than the one we use by default, isn't it? It doesn't seem to cause any issues with Redis as far as I can tell. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://docs.celeryq.dev/en/stable/userguide/configuration.html#result-extended
Without this the information in the result backend is rather opaque. You
can only see the task_id's of tasks that have executed. With the setting
enabled you can see the task name, queue and other metadata.
To demonstrate - the top task is with CELERY_RESULT_EXTENDED enabled
while the rest have the value disabled.