This would be useful for logging. Currently, when we have multiple tasks running concurrently and logging to the same log stream (like in AWS ECS), they don't have an easy way to distinguish themselves from each other. Passing the Celery task ID to the task function (maybe injecting it similarly to how task_progress is injected) would be helpful.
This would be useful for logging. Currently, when we have multiple tasks running concurrently and logging to the same log stream (like in AWS ECS), they don't have an easy way to distinguish themselves from each other. Passing the Celery task ID to the task function (maybe injecting it similarly to how
task_progressis injected) would be helpful.