Tracing without Performance

[cleptric]

Tasks

Preview Give feedback

1. All events are always sent through the /envelope endpoint if performance is enabled. ref: Sent all events to the /envelope endpoint if tracing is enabled #1518
2. Add a mechanism to continue a trace from environment variables. feat: Add TransactionContext::fromEnvironment #1519
3. All error, transaction and check-in events sent to Sentry always contain a Dynamic Sampling Context (trace) envelope header item. feat: Tracing without Performance #1516
4. All error, transaction and check-in sent to Sentry always contain a trace context. feat: Tracing without Performance #1516
5. All outgoing HTTP requests always contain a sentry-trace and baggage header if the destination is allow-listed in trace_propagation_targets. Attach tracing headers #1547

To always have access to a trace and span ID, add a new internal PropagationContext property to the scope, an object holding a traceId and spanId and an optional dynamicSamplingContext.

Populate the traceId and spanId with valid, random IDs on construction.

You may update the traceId and dynamicSamplingContext from the request headers during an incoming request or if the process was exposed to a SENTRY_TRACE and/or SENTRY_BAGGAGE environment variable if performance is disabled.

The Dynamic Sampling Context should be lazily constructed once needed, using a new fromOptions function that constructs the DSC based on the client options if performance is disabled.

When captureEvent is called, you may use these values on the scope as a fallback to construct the trace context and envelope header item if no transaction exists in the SDK.

For outgoing HTTP requests, use the values in the scope as a fallback if no transaction is present. The sentry-trace will contain a trailing -0 indicating an unsampled transaction.