-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(core): Capture # of dropped spans through beforeSendTransaction
#13022
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
Conversation
| const spans = event.spans || []; | ||
| // the transaction itself counts as one span, plus all the child spans that are added | ||
| const spanCount = 1 + spans.length; | ||
| this._outcomes['span'] = (this._outcomes['span'] || 0) + spanCount; |
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.
Noticed that this was actually buggy, because the key is built from reason + category 😬 now this is unified and should work consistently.
size-limit report 📦
|
Lms24
left a comment
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.
l: no particular strong feelings given these are client reports but should we add a test for them?
Yeah I thought about this too, I'll add some I think! |
c67e225 to
aeefa66
Compare
15d9059 to
f6ddc1c
Compare
Fixes #12849.
This is a bit tricky because
beforeSendTransactioncan return a promise, so in order to avoid dealing with this I put the # of spans on the sdk metadata, and then compare that afterwards.