Skip to content

Conversation

@Kyle-Verhoog
Copy link
Member

No description provided.

amqp==2.5.2
billiard==3.6.3.0
celery==4.4.2
-e git://github.com/thieman/dd-trace-py.git@69d6cfe419468e8a22710068cb74d55694f1d311#egg=ddtrace
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: update this to 0.37 when released

@Kyle-Verhoog Kyle-Verhoog added the WIP work in progress, do not merge label Mar 31, 2020
@caleb15
Copy link
Contributor

caleb15 commented Jun 24, 2021

what is "distributed tracing" exactly? I read about distributed tracing headers in https://ddtrace.readthedocs.io/en/stable/integrations.html#celery but I'm not sure what they are or when you would want to set DD_CELERY_DISTRIBUTED_TRACING to true

@caleb15
Copy link
Contributor

caleb15 commented Jun 24, 2021

Ah, after reading DataDog/dd-trace-py#1179 I think I understand it now. By setting DD_CELERY_DISTRIBUTED_TRACING to true the distributed tracing headers (ex: trace ID) are passed to celery, which lets datadog know that the celery span and the producer span are both part of the same transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

python WIP work in progress, do not merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants