Skip to content

feat(node): Ensure tracePropagationTargets are respected #11285

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

Merged
merged 5 commits into from
Mar 27, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented Mar 26, 2024

This PR ensures that tracePropagationTargets are respected for node API requests.

I also updated the node-fetch instrumentation, because that fixed an issue where http.url was not correctly set.

I also updated the other node-fastify E2E tests to be less flaky (we could have race conditions of transactions we were waiting for). I bumped @types/node to the correct version to ensure I can use crypto properly in tests (and that generally makes sense, I'd say).

Closes #11272

@mydea mydea requested review from lforst, AbhiPrasad and s1gr1d March 26, 2024 14:33
@mydea mydea self-assigned this Mar 26, 2024

This comment was marked as outdated.

Copy link
Contributor

github-actions bot commented Mar 26, 2024

size-limit report 📦

Path Size
@sentry/browser (incl. Tracing, Replay, Feedback) 80.56 KB (0%)
@sentry/browser (incl. Tracing, Replay) 71.89 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas) 75.7 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 65.44 KB (0%)
@sentry/browser (incl. Tracing) 36.71 KB (0%)
@sentry/browser (incl. browserTracingIntegration) 36.71 KB (0%)
@sentry/browser (incl. feedbackIntegration) 31.37 KB (0%)
@sentry/browser (incl. feedbackModalIntegration) 31.48 KB (0%)
@sentry/browser (incl. feedbackScreenshotIntegration) 31.49 KB (0%)
@sentry/browser (incl. sendFeedback) 27.44 KB (0%)
@sentry/browser 22.58 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) 74.9 KB (0%)
CDN Bundle (incl. Tracing, Replay) 69.73 KB (0%)
CDN Bundle (incl. Tracing) 36.3 KB (0%)
CDN Bundle 23.94 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed 219.01 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed 109.57 KB (0%)
CDN Bundle - uncompressed 70.92 KB (0%)
@sentry/react (incl. Tracing, Replay) 71.87 KB (0%)
@sentry/react 22.61 KB (0%)

@mydea mydea force-pushed the fn/node-propagation branch from c9fe753 to b2ea066 Compare March 27, 2024 08:22
@mydea mydea merged commit ad6f789 into develop Mar 27, 2024
@mydea mydea deleted the fn/node-propagation branch March 27, 2024 09:21
AbhiPrasad added a commit that referenced this pull request Mar 27, 2024
With this change, there are two remaining references to
node-experimental.

1. nextjs, which is handled by
#11016
2. express integration tests, which I will address after
#11285 gets merged

Once those two are done, we can remove the old node packages entirely!
cadesalaberry pushed a commit to cadesalaberry/sentry-javascript that referenced this pull request Apr 19, 2024
…#11285)

This PR ensures that `tracePropagationTargets` are respected for node
API requests.

I also updated the node-fetch instrumentation, because that fixed an
issue where `http.url` was not correctly set.

I also updated the other node-fastify E2E tests to be less flaky (we
could have race conditions of transactions we were waiting for). I
bumped `@types/node` to the correct version to ensure I can use `crypto`
properly in tests (and that generally makes sense, I'd say).

Closes getsentry#11272
cadesalaberry pushed a commit to cadesalaberry/sentry-javascript that referenced this pull request Apr 19, 2024
With this change, there are two remaining references to
node-experimental.

1. nextjs, which is handled by
getsentry#11016
2. express integration tests, which I will address after
getsentry#11285 gets merged

Once those two are done, we can remove the old node packages entirely!
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.

[v8] Ensure tracePropagationTargets are respected for @sentry/node
2 participants