-
Notifications
You must be signed in to change notification settings - Fork 475
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
seeing many traces traces that have a duration of several hours or even over 1 day. #3169
Comments
Hey @drazisil-codecov, thanks for raising this. Could you point me to the repo the spans are coming from? Are these auto instrumented or custom spans? As the first step I'd recommend upgrading to SDK v2.5.1 since we refactored scope management significantly in 2.0. Also happy to submit a PR with this for you as soon as I have the repo. Alternatively, here's the migration guide. |
Hi, @sentrivana This would be https://github.com/codecov/codecov-api |
Thanks, will open a PR for y'all soon. |
How do you use Sentry?
Sentry Saas (sentry.io)
Version
python sentry-sdk>=1.40.0
Steps to Reproduce
Review https://codecov.sentry.io/performance/trace/6868afe00f97443ea7192b508da2b03b/?fov=1%2C154105386.00008392&pageEnd&pageStart&statsPeriod=30d×tamp=1717451835
Currently at 75012 events and climbing
Expected Result
Spans not connected when not related
Actual Result
many "linked" spans under the same trace id
The text was updated successfully, but these errors were encountered: