docs(supabase): add client-side trace propagation cross-links - #18972
Open
smeubank wants to merge 3 commits into
Open
docs(supabase): add client-side trace propagation cross-links#18972smeubank wants to merge 3 commits into
smeubank wants to merge 3 commits into
Conversation
Link Sentry's Supabase integration docs to the new Supabase client-side tracing feature. Adds a Trace Propagation section to the JS integration, a log correlation section to the Log Drains page, and new stub pages for Apple and Dart pointing to supabase.com/docs/guides/monitoring-and-debugging/client-side-tracing. Python docs are pending.
|
@smeubank is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Author
rejection hurts 🥹 |
this was wrong my colleague confirmed: "that's wrong. I verified against sentry-javascript source: Sentry's OTel propagator does **not** emit traceparent unless you also set propagateTraceparent: true in Sentry.init() . It defaults to false. Without it, a user following this doc gets zero trace headers on Supabase calls, silently. For the browser SDK there's a second gap: Sentry only attaches headers to cross-origin requests for hosts listed in tracePropagationTargets, and Supabase is always cross-origin, so the project's Supabase URL needs to be in that list too."
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link Sentry's Supabase integration docs to the new Supabase client-side tracing feature. Adds a Trace Propagation section to the JS integration, a log correlation section to the Log Drains page, and new stub pages for Apple and Dart pointing to supabase.com/docs/guides/monitoring-and-debugging/client-side-tracing.
Python docs are pending.
We've extended trace propagation support to more platforms and this should help bring visibility to that.
IS YOUR CHANGE URGENT?
Nope:) nice to have though