Implement org and strictTraceContinuation init options

[alaycock]

Problem Statement

When I receive requests to my Node server, they will occasionally contain the sentry-trace and baggage headers. Sentry's automatic instrumentation will attach the provided span ID as a parent to my server traces. Subsequently, Sentry's default sampling function will use the existence of a parent span to enable sampling for the request.

The result is that external parties can manipulate my Sentry trace sampling. It impacts performance when profiling is enabled and biases trace sampling towards specific endpoints.

My workaround is to ignore the the parent span when sampling via tracesSampler, but this means I cannot easily enable distributed tracing.

Solution Brainstorm

If strictTraceContinuation is implemented, it would let me to ignore parent spans provided by my API users.

[Lms24]

Hi, thanks for writing in! We've started a conversation internally on the timeline for implementing this. We'll update this issue once we know more.