docs(supabase): add client-side trace propagation cross-links - #18972
Merged
sfanahata merged 19 commits intoSep 8, 2026
Merged
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}
Add notes on unsampled traceparent-only requests, cross-event querying, and Edge Function CORS allow-listing for sentry-trace. Co-Authored-By: Kyle Tryon <kyle.tryon@sentry.io>
buenaflor
reviewed
Aug 26, 2026
Updated the integration instructions for Sentry and Supabase in Dart and Flutter apps, clarifying the requirements and providing code examples.
|
Deployment failed for project develop-docs with the following error: |
|
Deployment failed for project sentry-docs with the following error: |
buenaflor
requested review from
philprime
and removed request for
philipphofmann
August 26, 2026 15:38
spydon
reviewed
Aug 26, 2026
update to have one line per paragraph in the md
Point to the canonical platform URL so the Trace Propagation heading resolves instead of a synthesized node-guide path. Co-authored-by: Cursor <cursoragent@cursor.com>
buenaflor
approved these changes
Aug 31, 2026
KyleTryon
approved these changes
Sep 1, 2026
Contributor
Author
|
@buenaflor i think sosmone from sentry has to trigger the vercel deploy and then you can merge |
The Supabase page lives under `dart/common/`, which the Flutter guide inherits, so the single `Sentry.init` snippet was served to Flutter users as well. Flutter apps must initialize with `SentryFlutter.init` or they lose native crash handling and the Flutter-specific instrumentations. Split the snippet with `PlatformSection` so each platform sees only its own initializer, matching how `dart-integrations/grpc.mdx` and `tracing/streamed-spans` already handle this. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Every other Dart integration ships as a shared body in `includes/dart-integrations/` with a thin wrapper page under both `dart/common/integrations/` and `dart/guides/flutter/integrations/`. Supabase only had the common page, so the Flutter guide inherited the Dart title, description and sidebar position. Move the body into an include and add the Flutter wrapper so each guide gets its own metadata. Add the missing Supabase row to the integrations table, which is hand-maintained and drives discovery from the Flutter integrations index. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
`Supabase.initialize()` is a `supabase_flutter` singleton wrapper and does not exist in the pure Dart `supabase` package, which only exposes the `SupabaseClient` constructor. The Dart snippet therefore would not compile in a non-Flutter app. Construct `SupabaseClient` directly and pass `SentryHttpClient` as its `httpClient`. The Flutter snippet keeps `Supabase.initialize()`. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
This was the only include in `dart-integrations/` without imports, and the two variants now pull Supabase from different packages: `supabase` for Dart and `supabase_flutter` for Flutter. Without the import lines there is nothing telling the reader which package each symbol comes from. Co-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Hey @smeubank , looks like the 404 check is blocking the merge here. Is 'product/drains/supabase' a page that will be created in a PR that will be merged first? If not I would remove it or replace with a placeholder so this passes builds. |
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
7 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