feat(node): Add tracing without performance to Node http integration#8450
feat(node): Add tracing without performance to Node http integration#8450AbhiPrasad merged 2 commits intodevelopfrom
Conversation
|
All these test failures are v confusing as well 😢 |
f75aa41 to
f6b4193
Compare
|
Alright I'm forcing sampling decisions for the integration tests, hopefully that helps with the problems. The biggest problem with our Remix and Nextjs integration tests is that the Sentry instances bleeds into the tests for some reason - we need true encapsulation like our e2e tests I think. Also both the nextjs and remix tests are super tough to debug - the DX needs to be improved here. |
|
~alright so looks like we're good for nextjs (other than flakes), only remix is being weird 🤔 ~ nvm 😭 |
size-limit report 📦
|
|
One day tests will pass and it will be glorious... |
af3dd18 to
2950ca6
Compare
|
e2e tests should be taken care of by #8486 |
f0fefc0 to
a38d24d
Compare
| return; | ||
| } | ||
|
|
||
| // TODO (v8): `tracePropagationTargets` and `shouldCreateSpanForRequest` will be removed from clientOptions |
There was a problem hiding this comment.
l: Should we keep this v8 comment around?
There was a problem hiding this comment.
Don't think so, it doesn't apply anymore and deprecation should take care of the tracePropagationTargets option.
Lms24
left a comment
There was a problem hiding this comment.
Nice refactor around header normalization and setting the headers!
ref #8352
Updates the Node HTTP integration to always attach
sentry-traceheaders to outgoing requests.This can be controlled with the top level
tracePropagationOptionsoption.