Skip to content

ref(client): Put org_id resolution in the Client - #1326

Open
szokeasaurusrex wants to merge 1 commit into
masterfrom
szokeasaurusrex/extract-org_id-determination
Open

szokeasaurusrex wants to merge 1 commit into
masterfrom
szokeasaurusrex/extract-org_id-determination

Conversation

@szokeasaurusrex

@szokeasaurusrex szokeasaurusrex commented Sep 22, 2026 •

Copy link
Copy Markdown
Member

Centralize the logic for determining org_id on the Client; previously, it was living in the performance module as we use it there to determine org ID for strict trace continuation.

This change also includes an optimization of storing the resolved org_id on the Client; previously every continued incoming trace resulted in a re-parsing of the DSN's host when no explicit org_id was set.

This change will allow us to more easily access the org_id elsewhere we may need it.

Centralize the logic for determining `org_id` on the `Client`; previously, it was living in the `performance` module as we use it there to determine org ID for strict trace continuation.

This change also includes an optimization of storing the resolved `org_id` on the `Client`; previously every continued incoming trace resulted in a re-parsing of the DSN's host when no explicit `org_id` was set.

This change will allow us to more easily access the `org_id` elsewhere we may need it.
@szokeasaurusrex
szokeasaurusrex added this pull request to stack #1332 September 22, 2026 13:39
@szokeasaurusrex
szokeasaurusrex marked this pull request as ready for review September 22, 2026 13:41
@szokeasaurusrex
szokeasaurusrex requested a review from a team as a code owner September 22, 2026 13:41

This branch has not been deployed

No deployments
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.

2 participants