8000 Send `sentry-org_id` in baggage · Issue #16290 · getsentry/sentry-javascript · GitHub
[go: up one dir, main page]

Skip to content

Send sentry-org_id in baggage #16290

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

Closed
mydea opened this issue May 14, 2025 — with Linear · 1 comment · Fixed by #16305
Closed

Send sentry-org_id in baggage #16290

mydea opened this issue May 14, 2025 — with Linear · 1 comment · Fixed by #16305
Assignees

Comments

Copy link
Member
mydea commented May 14, 2025

We want to make sure to send the org_id in baggage with outgoing requests, so that other SDKs can verify strict trace continuation.

  1. The org id can be extracted from the DSN via regex, see https://develop.sentry.dev/sdk/telemetry/traces/#stricttracecontinuation
  2. Optionally users should be able to pass orgId to their sentry init, which should take precedence if set (this is really more of a edge case/power user thing - on saas, DSN extraction should always work!)
  3. If nothing can be found/extracted, no baggage entry should be set
  4. This should be sent both in browser as well as in node.
s1gr1d added a commit that referenced this issue May 16, 2025
…baggage) (#16305)

Adds the organization ID to the DSC (dynamic sampling context). This
will add the org ID as `sentry-org_id` to the baggage.

This org ID is parsed from the DSN. With the `orgId` option it's
possible to overwrite the automatically parsed organization ID.

closes #16290
Copy link
Contributor

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16305, which was included in the 9.20.0 release.

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 a pull request may close this issue.

2 participants
0