If you're using the current version of our Capacitor SDK, distributed tracing will work out of the box.
To get around possible Browser CORS issues, define your tracePropagationTargets.
Sentry.init({
dsn: "___PUBLIC_DSN___",
tracesSampleRate: 1.0,
tracePropagationTargets: ["https://myproject.org", /^\/api\//],
});When your application receives requests, they might include sentry-trace and baggage headers from an upstream service that is also using Sentry.
By default, the SDK will continue the trace from these incoming headers. However, this behavior can be undesirable if the requests are from a third-party service,
as it can lead to unwanted traces, increased billing, and skewed performance data.
To prevent this, you can enable strictTraceContinuation. When this option is set to true, the SDK checks the incoming request for Sentry trace information and only continues the trace if it belongs to the same Sentry organization.
Otherwise, it starts a new trace.
Sentry.init({
dsn: "___PUBLIC_DSN___",
tracesSampleRate: 1.0,
// Ensure that only traces from your own organization are continued
strictTraceContinuation: true,
});The SDK automatically parses the organization ID from your DSN. If you use a DSN format that doesn't include the organization ID (number followed by the letter "o"), or if you need to override it, you can provide it manually using the orgId option:
Sentry.init({
dsn: "___PUBLIC_DSN___",
tracesSampleRate: 1.0,
strictTraceContinuation: true,
// Manually provide your organization ID (overrides organization ID parsed from DSN)
orgId: 12345,
});If you want to disable distributed tracing and ensure no Sentry trace headers are sent, you can configure your SDK like this:
Sentry.init({
dsn: "___PUBLIC_DSN___",
// Overwrite the defaults to ensure no trace headers are sent
tracePropagationTargets: [],
});