5.11.0

Features

• Make :value in SingleExceptionInterface writable, so that it can be modified in before_send under event.exception.values[n].value #2072

• Add sampled field to dynamic_sampling_context #2092

• Consolidate HTTP span data conventions with OpenTelemetry with Sentry::Span::DataConventions #2093

• Consolidate database span data conventions with OpenTelemetry for ActiveRecord and Redis #2100

• Add new config.trace_propagation_targets option to set targets for which headers are propagated in outgoing HTTP requests #2079

  # takes an array of strings or regexps
  config.trace_propagation_targets = [/.*/]  # default is to all targets
  config.trace_propagation_targets = [/example.com/, 'foobar.org/api/v2']

• Tracing without Performance

  • Implement PropagationContext on Scope and add Sentry.get_trace_propagation_headers API #2084
  • Implement Sentry.continue_trace API #2089

  The SDK now supports connecting arbitrary events (Errors / Transactions / Replays) across distributed services and not just Transactions.
  To continue an incoming trace starting with this version of the SDK, use Sentry.continue_trace as follows.

  # rack application
  def call(env)
    transaction = Sentry.continue_trace(env, name: 'transaction', op: 'op')
    Sentry.start_transaction(transaction: transaction)
  end

  To inject headers into outgoing requests, use Sentry.get_trace_propagation_headers to get a hash of headers to add to your request.

Bug Fixes

• Duplicate Rails.logger before assigning it to the SDK (#2086)