Skip to content
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

ref(tracing): Make sure error status is set on transactions #2818

Merged
merged 3 commits into from
Aug 19, 2020

Conversation

AbhiPrasad
Copy link
Member

@AbhiPrasad AbhiPrasad commented Aug 13, 2020

Make sure that for all transactions on the scope in the JS SDK, if an error occurs that the span status is changed to error. This previously only existed for transactions inside the tracing integration.

@AbhiPrasad AbhiPrasad requested a review from HazAT August 13, 2020 20:28
@@ -171,9 +170,6 @@ export class BrowserTracing implements Integration {
startTransactionOnLocationChange,
);

// TODO: Should this be default behaviour?
registerErrorInstrumentation();
Copy link
Member Author

Choose a reason for hiding this comment

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

The answer is yes, yes it should be 😄

@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2020

size-limit report

Path Size
@sentry/browser - CDN Bundle (gzipped) 17.67 KB (0%)
@sentry/browser - Webpack 18.46 KB (0%)
@sentry/react - Webpack 18.46 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped) 22.69 KB (0%)

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@AbhiPrasad AbhiPrasad merged commit aa28800 into master Aug 19, 2020
@AbhiPrasad AbhiPrasad deleted the abhi/global-errors branch August 19, 2020 11:44
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.

None yet

4 participants