Skip to content

Conversation

@HazAT
Copy link
Member

@HazAT HazAT commented Jun 8, 2020

We want that normal error events to also receive the trace context.
This is a product feature we rely on to connect error with transactions.

@HazAT HazAT requested a review from kamilogorek as a code owner June 8, 2020 11:24
@HazAT HazAT self-assigned this Jun 8, 2020
@HazAT HazAT changed the title feat: Re-add TraceContext feat: Re-add TraceContext for all events Jun 8, 2020
@HazAT HazAT changed the title feat: Re-add TraceContext for all events fix: Re-add TraceContext for all events Jun 8, 2020
}) as Transaction;

// We set the transaction here on the scope so error events pick up the trace context and attach it to the error
hub.configureScope(scope => scope.setSpan(Tracing._activeTransaction));
Copy link
Contributor

Choose a reason for hiding this comment

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

This does it for the "idle transaction" -- what about manual instrumentation / Sentry.startTransaction?

cc @mitsuhiko

Copy link
Member Author

Choose a reason for hiding this comment

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

Probably something to document.

@getsentry-bot
Copy link
Contributor

Messages
📖

@sentry/browser bundle gzip'ed minified size: (ES5: 17.0586 kB) (ES6: 16.1162 kB)

📖 ✅ TSLint passed

Generated by 🚫 dangerJS against 22d9839

@HazAT HazAT merged commit 5091fbf into master Jun 8, 2020
@HazAT HazAT deleted the feat/re-add-trace-context branch June 8, 2020 12:06
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.

5 participants