Skip to content

Comments

feat(tracing): Drop unfinished spans from a transaction#635

Closed
relaxolotl wants to merge 23 commits intotracing/basic-spansfrom
tracing/omit-unfinished-spans
Closed

feat(tracing): Drop unfinished spans from a transaction#635
relaxolotl wants to merge 23 commits intotracing/basic-spansfrom
tracing/omit-unfinished-spans

Conversation

@relaxolotl
Copy link
Contributor

Remove all unfinished spans from transactions as they're being processed and sent over the wire to sentry. This addresses a TODO left behind in #634.

related to #601
picks up off of #634

@relaxolotl relaxolotl requested a review from a team December 18, 2021 06:28
@relaxolotl relaxolotl force-pushed the tracing/omit-unfinished-spans branch 2 times, most recently from ff00824 to 9e9ed29 Compare December 18, 2021 06:50
@relaxolotl relaxolotl force-pushed the tracing/omit-unfinished-spans branch from 9e9ed29 to 8f8ee90 Compare December 21, 2021 08:33
Copy link
Contributor

@Swatinem Swatinem left a comment

Choose a reason for hiding this comment

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

This ties in with my comment on the previous PR in this chain:
If we only ever record spans in finish (that means that start only creates the object but otherwise does nothing) this whole PR would become obsolete.

@relaxolotl relaxolotl marked this pull request as draft December 23, 2021 06:20
@relaxolotl relaxolotl force-pushed the tracing/basic-spans branch 3 times, most recently from 0bec560 to 8969d44 Compare December 23, 2021 22:43
@relaxolotl relaxolotl force-pushed the tracing/basic-spans branch 2 times, most recently from 1dd00df to 3208c6a Compare January 7, 2022 07:57
@relaxolotl relaxolotl closed this Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants