Update sentry-ruby monorepo to v5.22.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sentry-rails (source, changelog)	5.16.1 -> 5.22.1
sentry-ruby (source, changelog)	5.16.1 -> 5.22.1
sentry-sidekiq (source, changelog)	5.16.1 -> 5.22.1

---

Release Notes

getsentry/sentry-ruby (sentry-rails)

v5.22.1

Compare Source

Bug Fixes

• Safe-navigate to session flusher #​2396
• Fix latency related nil error for Sidekiq Queues Module span data #​2486
  • Fixes #​2485

v5.22.0

Compare Source

Features

• Add include_sentry_event matcher for RSpec #​2424

• Add support for Sentry Cache instrumentation, when using Rails.cache #​2380

• Add support for Queue Instrumentation for Sidekiq. #​2403

• Add support for string errors in error reporter (#​2464)

• Reset trace_id and add root transaction for sidekiq-cron #​2446

• Add support for Excon HTTP client instrumentation (#​2383)

  Note: MemoryStore and FileStore require Rails 8.0+

Bug Fixes

• Fix Vernier profiler not stopping when already stopped #​2429
• Fix send_default_pii handling in rails controller spans #​2443
  • Fixes #​2438
• Fix RescuedExceptionInterceptor to handle an empty configuration #​2428
• Add mutex sync to SessionFlusher aggregates #​2469
  • Fixes #​2468
• Fix sentry-rails' backtrace cleaner issues (#​2475)
  • Fixes #​2472

v5.21.0

Compare Source

Features

• Experimental support for multi-threaded profiling using Vernier (#​2372)

  You can have much better profiles if you're using multi-threaded servers like Puma now by leveraging Vernier.
  To use it, first add vernier to your Gemfile and make sure it is loaded before sentry-ruby.

Gemfile

gem 'vernier'
gem 'sentry-ruby'

Then, set a `profiles_sample_rate` and the new `profiler_class` configuration in your sentry initializer to use the new profiler.

```ruby

### config/initializers/sentry.rb

Sentry.init do |config|

### ...
  config.profiles_sample_rate = 1.0
  config.profiler_class = Sentry::Vernier::Profiler
end

Internal

• Profile items have bigger size limit now (#​2421)
• Consistent string freezing (#​2422)

v5.20.1

Compare Source

Bug Fixes

• Skip rubocop.yml in spec.files (#​2420)

v5.20.0

Compare Source

• Add support for $SENTRY_DEBUG and $SENTRY_SPOTLIGHT (#​2374)
• Support human readable intervals in sidekiq-cron (#​2387)
• Set default app dirs pattern (#​2390)
• Add new strip_backtrace_load_path boolean config (default true) to enable disabling load path stripping (#​2409)

Bug Fixes

• Fix error events missing a DSC when there's an active span (#​2408)
• Verifies presence of client before adding a breadcrumb (#​2394)
• Fix Net:HTTP integration for non-ASCII URI's (#​2417)
• Prevent Hub from having nil scope and client (#​2402)

v5.19.0

Compare Source

Features

• Use Concurrent.available_processor_count instead of Concurrent.usable_processor_count (#​2358)

• Support for tracing Faraday requests (#​2345)

  • Closes #​1795
  • Please note that the Faraday instrumentation has some limitations in case of async requests: https://github.com/lostisland/faraday/issues/1381
  • https://github.com/lostisland/faraday/issues/1381

  Usage:

  Sentry.init do |config|

...

config.enabled_patches << :faraday

end

- Support for attachments ([#​2357](https://redirect.github.com/getsentry/sentry-ruby/pull/2357))

Usage:

```ruby
Sentry.add_attachment(path: '/foo/bar.txt')
Sentry.add_attachment(filename: 'payload.json', bytes: '{"value": 42}'))

• Transaction data are now included in the context (#​2365)

  • Closes #​2364

• Inject Sentry meta tags in the Rails application layout automatically in the generator (#​2369)

  To turn this behavior off, use

  bin/rails generate sentry --inject-meta false

Bug Fixes

• Fix skipping connect spans in open-telemetry #​2364

v5.18.2

Compare Source

Bug Fixes

• Don't overwrite ip_address if already set on user #​2350
  • Fixes #​2347
• teardown_sentry_test helper should clear global even processors too (#​2342)
• Suppress the unnecessary “unsupported options notice” (#​2349)

Internal

• Use Concurrent.usable_processor_count when it is available (#​2339)
• Report dropped spans in Client Reports (#​2346)

v5.18.1

Compare Source

Bug Fixes

• Drop Gem::Specification's usage so it doesn't break bundler standalone (#​2335)

v5.18.0

Compare Source

Features

• Add generator for initializer generation (#​2286)

  Rails users will be able to use bin/rails generate sentry to generate their config/initializers/sentry.rb file.

• Notify users when their custom options are discarded (#​2303)

• Add a new :graphql patch to automatically enable instrumenting GraphQL spans (#​2308)

  Usage:

  Sentry.init do |config|

...

  config.enabled_patches += [:graphql]
end
```

• Add Sentry.get_trace_propagation_meta helper for injecting meta tags into views (#​2314)

• Add query source support to sentry-rails (#​2313)

  The feature is only activated in apps that use Ruby 3.2+ and Rails 7.1+. By default only queries that take longer than 100ms will have source recorded, which can be adjusted by updating the value of config.rails.db_query_source_threshold_ms.

• Log envelope delivery message with debug instead of info (#​2320)

Bug Fixes

• Don't throw error on arbitrary arguments being passed to capture_event options #​2301
  • Fixes #​2299
• Decrease the default number of background worker threads by half (#​2305)
  • Fixes #​2297
• Don't mutate enabled_environments when using Sentry::TestHelper (#​2317)
• Don't use array for transaction names and sources on scope (#​2324)
  • Fixes #​2257
  • BREAKING This removes the internal scope.transaction_names method, please use scope.transaction_name instead

Internal

• Add origin to spans and transactions to track integration sources for instrumentation (#​2319)

v5.17.3

Compare Source

Internal

• Update key, unit and tags sanitization logic for metrics #​2292
• Consolidate client report and rate limit handling with data categories #​2294
• Record :network_error client reports for send_envelope #​2295

Bug Fixes

• Make sure isolated envelopes respect config.enabled_environments #​2291
  • Fixes #​2287

v5.17.2

Compare Source

Internal

• Add Mechanism interface and default to unhandled for integration exceptions #​2280

Bug Fixes

• Don't instantiate connection in ActiveRecordSubscriber (#​2278)

v5.17.1

Compare Source

Bug Fixes

• Fix NoMethodError / Make session_tracking check consistent (#​2269)

v5.17.0

Compare Source

Features

• Add support for distributed tracing in sentry-delayed_job #​2233
• Fix warning about default gems on Ruby 3.3.0 (#​2225)
• Add hint: support to Sentry::Rails::ErrorSubscriber #​2235
• Add Metrics support

  • Add main APIs and Aggregator thread #​2247

  • Add Sentry::Metrics.timing API for measuring block duration #​2254

  • Add metric summaries on spans #​2255

  • Add config.metrics.before_emit callback #​2258

  • Add code locations for metrics #​2263

    The SDK now supports recording and aggregating metrics. A new thread will be started
    for aggregation and will flush the pending data to Sentry every 5 seconds.

    To enable this behavior, use:

    Sentry.init do |config|

...

  config.metrics.enabled = true
end
```

And then in your application code, collect metrics as follows:

```ruby

increment a simple counter

Sentry::Metrics.increment('button_click')

set a value, unit and tags

Sentry::Metrics.increment('time', 5, unit: 'second', tags: { browser:' firefox' })

distribution - get statistical aggregates from an array of observations

Sentry::Metrics.distribution('page_load', 15.0, unit: 'millisecond')

gauge - record statistical aggregates directly on the SDK, more space efficient

Sentry::Metrics.gauge('page_load', 15.0, unit: 'millisecond')

set - get unique counts of elements

Sentry::Metrics.set('user_view', 'jane')

timing - measure duration of code block, defaults to seconds

will also automatically create a metric.timing span

Sentry::Metrics.timing('how_long') { sleep(1) }

timing - measure duration of code block in other duraton units

Sentry::Metrics.timing('how_long_ms', unit: 'millisecond') { sleep(0.5) }
```

You can filter some keys or update tags on the fly with the `before_emit` callback, which will be triggered before a metric is aggregated.

```ruby
Sentry.init do |config|

...

the 'foo' metric will be filtered and the tags will be updated to add :bar and remove :baz

  config.metrics.before_emit = lambda do |key, tags|
    return nil if key == 'foo'
    tags[:bar] = 42
    tags.delete(:baz)
    true
  end
end
```

By default, the SDK will send code locations for unique metrics (defined by type, key and unit) once a day and with every startup/shutdown of your application.
You can turn this off with the following:

```ruby
Sentry.init do |config|

...

  config.metrics.enable_code_locations = false
end
```

Bug Fixes

• Fix undefined method 'constantize' issue in sentry-resque (#​2248)
• Only instantiate SessionFlusher when the SDK is enabled under the current env #​2245
  • Fixes #​2234
• Update backtrace parsing regexp to support Ruby 3.4 (#​2252)
• Make sure sending_allowed? is respected irrespective of spotlight configuration (#​2231)
  • Fixes #​2226

---

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.