-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(tracing): Trim idle transaction spans if they exceed final timeout #8653
Conversation
size-limit report 📦
|
Dropping the span that goes over the final timeout sounds like a good quick solution. 👍 |
6adbbb4
to
b44cdd9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. 🚀
I think maybe we should fo a small troubleshooting docs update for people running into the long Tx.
Good idea, let me put in my todo! |
Supercedes #8505
resolves #8504
If an idle transaction's duration is longer than final timeout + idle timeout, opt to not capture and send it to Sentry.