-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
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
parent_span_id being attached to root celerybeat transactions #1096
Comments
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Hello @wmak As this bug report is already quite old, could you please verify this with the latest Sentry SDK? Thanks! |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
sentry-python==1.0.0
Steps to Reproduce
https://gist.github.com/wmak/fffab40bdbe5329f2ef8bd0a4ff44659
celery -A main.celery worker
celery -A main.celery beat --loglevel=INFO --pidfile=''
Expected Result
I don't expect for celery tasks started by celerybeat to have the parent_span_id set to a span_id, especially when there isn't a corresponding transaction with that span to make the association, the repro attached here is flask + celerybeat. But also happens with Django + celerybeat
Actual Result
The parent_span_id was set in the trace context, so the transaction appears to be orphaned, when it in fact should be a root event instead
The text was updated successfully, but these errors were encountered: