Update sentry-ruby monorepo to v5.28.1 #95

renovate · 2024-01-27T08:38:26Z

This PR contains the following updates:

Package	Change	Age	Confidence
sentry-rails (source, changelog)	`5.15.2` -> `5.28.1`
sentry-ruby (source, changelog)	`5.15.2` -> `5.28.1`

Release Notes

getsentry/sentry-ruby (sentry-rails)

`v5.28.1`

Compare Source

Bug Fixes

The sentry.origin log event attribute is now correctly prefixed with auto.log (#2749)

`v5.28.0`

Compare Source

Features

Auto-enable Rails structured logging when enable_logs is true (#2721)

Miscellaneous

Deprecate all Metrics related APIs #2726

Sentry no longer has the Metrics Beta offering so
all the following APIs linked to Metrics have been deprecated and will be removed in the next major.
```
Sentry.init do |config|
```

...

  config.metrics.enabled = true
  config.metrics.enable_code_locations = true
  config.metrics.before_emit = lambda {}
end

Sentry::Metrics.increment('button_click')
Sentry::Metrics.distribution('page_load', 15.0, unit: 'millisecond')
Sentry::Metrics.gauge('page_load', 15.0, unit: 'millisecond')
Sentry::Metrics.set('user_view', 'jane')
Sentry::Metrics.timing('how_long') { sleep(1) }
```

Internal

Fix leftover config.logger call in graphql patch (#2722
Add Configuration.before and Configuration.after to run hooks before and after given event (#2724)

`v5.27.1`

Compare Source

Features

Support for :origin attribute in log events (#2712)

Bug Fixes

Skip including sentry.message.template in the log event attributes if there are no interpolation parameters provided (#2700)
Respect log_level when logging via :std_lib_logger patch (#2709)
Add sentry.origin attribute to log events (#2712)

`v5.27.0`

Compare Source

Feature

Propagated sampling rates as specified in Traces docs (#2671)
Support for Rails ActiveSupport log subscribers (#2690)
Support for defining custom Rails log subscribers that work with Sentry Structured Logging (#2689)

Rails applications can now define custom log subscribers that integrate with Sentry's structured logging system. The feature includes built-in subscribers for ActionController, ActiveRecord, ActiveJob, and ActionMailer events, with automatic parameter filtering that respects Rails' config.filter_parameters configuration.

To enable structured logging with Rails log subscribers:
```
Sentry.init do |config|
```

... your setup ...

Make sure structured logging is enabled

config.enable_logs = true

Enable default Rails log subscribers (ActionController and ActiveRecord)

config.rails.structured_logging.enabled = true

end


To configure all subscribers:

```ruby
Sentry.init do |config|

### ... your setup ...
### Make sure structured logging is enabled
  config.enable_logs = true

### Enable Rails log subscribers
  config.rails.structured_logging.enabled = true

### Add ActionMailer and ActiveJob subscribers
  config.rails.structured_logging.subscribers.update(
    action_mailer: Sentry::Rails::LogSubscribers::ActionMailerSubscriber,
    active_job: Sentry::Rails::LogSubscribers::ActiveJobSubscriber
  )
end

You can also define custom log subscribers by extending the base class:

class MyCustomSubscriber < Sentry::Rails::LogSubscriber
  attach_to :my_component

  def my_event(event)
    log_structured_event(
      message: "Custom event occurred",
      level: :info,
      attributes: { duration_ms: event.duration }
    )
  end
end

Sentry.init do |config|

### ... your setup ...
### Make sure structured logging is enabled
  config.enable_logs = true

### Enable Rails log subscribers
  config.rails.structured_logging.enabled = true

### Add custom subscriber
  config.rails.structured_logging.subscribers[:my_component] = MyCustomSubscriber
end

Introduce structured_logging config namespace (#2692)

Bug Fixes

Silence _perform method redefinition warning (#2682)
Update sentry trace regexp (#2678)
Remove redundant attr_reader (#2673)

Internal

Factor out do_request in HTTP transport (#2662)
Add Sentry::DebugTransport that captures events and stores them as JSON for debugging purposes (#2664)
Add Sentry::DebugStructuredLogger that caputres log events and stores them as JSON to a file for debugging purposes (#2693)
Rails test runner (#2687)
Update common gem deps for development (#2688)
Make devcontainer work with ancient Ruby/Rails (#2679)
Improved devcontainer setup with e2e test mini infra (#2672)
Address various flaky specs
- Fix test failures under JRuby (#2665)
- Fix flaky faraday spec (#2666)
- Fix flaky net/http spec (#2667)
- Fix flaky tracing specs (#2670)

`v5.26.0`

Compare Source

Feature

Support for :logger patch which enables sending logs to Sentry when enabled_logs is set to true (#2657)

Here's a sample config:
```
Sentry.init do |config|
```

... your setup ...

config.enable_logs = true
config.enabled_patches = [:logger]

end


##### Bug Fixes
- Skip creating `LogEventBuffer` if logging is not enabled ([#&#8203;2652](https://redirect.github.com/getsentry/sentry-ruby/pull/2652))

`v5.25.0`

Compare Source

Features

Support for before_send_log (#2634)
Default user attributes are now automatically added to logs (#2647)

Bug Fixes

Structured logging consumes way less memory now (#2643)

`v5.24.0`

Compare Source

Features

Add new sidekiq config report_only_dead_jobs (#2581)
Add max_nesting of 10 to breadcrumbs data serialization (#2583)
Add sidekiq config propagate_traces to control trace header injection (#2588)

If you use schedulers you can get one large trace with all your jobs which is undesirable.
We recommend using the following to propagate traces only from the Rails server and not elsewhere.
```
config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server')
```
Only expose active_storage keys on span data if send_default_pii is on (#2589)
Add new Sentry.logger for Structured Logging feature (#2620).

To enable structured logging you need to turn on the enable_logs configuration option:
```
Sentry.init do |config|
```

... your setup ...

config.enable_logs = true

end


Once you configured structured logging, you get access to a new `Sentry.logger` object that can be
used as a regular logger with additional structured data support:

```ruby
Sentry.logger.info("User logged in", user_id: 123)

Sentry.logger.error("Failed to process payment",
  transaction_id: "tx_123",
  error_code: "PAYMENT_FAILED"
)

You can also use message templates with positional or hash parameters:

Sentry.logger.info("User %{name} logged in", name: "Jane Doe")

Sentry.logger.info("User %s logged in", ["Jane Doe"])

Any other arbitrary attributes will be sent as part of the log event payload:

### Here `user_id` and `action` will be sent as extra attributes that Sentry Logs UI displays
Sentry.logger.info("User %{user} logged in", user: "Jane", user_id: 123, action: "create")

⚠️ When enable_logs is true, previous Sentry.logger should no longer be used for internal SDK
logging - it was replaced by Sentry.configuration.sdk_logger and should be used only by the SDK
itself and its extensions.

New configuration option called active_job_report_on_retry_error which enables reporting errors on each retry error (#2617)

Bug Fixes

Gracefully fail on malformed utf-8 breadcrumb message (#2582)
- Fixes #2376
Fix breadcrumb serialization error message to be an object (#2584)
- Fixes #2478
Fix compatibility issues with sidekiq-cron 2.2.0 (#2591)
Update sentry-sidekiq to work correctly with Sidekiq 8.0 and its new timestamp format (#2570)
Ensure we capture exceptions after each job retry (#2597)

Internal

Remove user_segment from DSC (#2586)
Replace logger with sdk_logger (#2621)
Sentry.logger is now deprecated when enable_logs is turned off. It's original behavior was ported to Sentry.configuration.sdk_logger. Please notice that this logger is internal and should only be used for SDK-specific logging needs. (#2621)

`v5.23.0`

Compare Source

Features

Add correct breadcrumb levels for 4xx/5xx response codes (#2549)

Bug Fixes

Fix argument serialization for ranges that consist of ActiveSupport::TimeWithZone (#2548)
Prevent starting Vernier in nested transactions (#2528)
Fix TypeError when Resque.inline == true (#2564)

Internal

Use File.open in LineCache (#2566)
Update java backtrace regexp (#2567)
Stop byteslicing empty strings in breadcrumbs (#2574)

Miscellaneous

Deprecate enable_tracing in favor of traces_sample_rate = 1.0 #2535

`v5.22.4`

Compare Source

Bug Fixes

Fix handling of cron with tz in Cron::Job (#2530)
Revert "[rails] support string errors in error reporter (#2464)" (#2533)
Removed unnecessary warning about missing stackprof when Vernier is configured as the profiler (#2537)
Fix regression with CheckInEvent in before_send (#2541)
- Fixes #2540

Internal

Introduced Configuration#validate to validate configuration in Sentry.init block (#2538)
Introduced Sentry.dependency_installed? to check if a 3rd party dependency is available ie Sentry.dependency_installed?(:Vernier) (#2542)

`v5.22.3`

Compare Source

Bug Fixes

Accept Hash in before_send* callbacks again (#2529)
- Fixes #2526

`v5.22.2`

Compare Source

Features

Improve the accuracy of duration calculations in cron jobs monitoring (#2471)
Use attempt_threshold to skip reporting on first N attempts (#2503)
Support code.namespace for Ruby 3.4+ stacktraces (#2506)

Bug fixes

Default to internal_error error type for OpenTelemetry spans #2473
Improve before_send and before_send_transaction's return value handling (#2504)
Fix a crash when calling Sentry.get_main_hub in a trap context (#2510)
Use URI::RFC2396_PARSER.escape explicitly to remove warning logs to stderr (#2509)

Internal

Test Ruby 3.4 in CI (#2506)
Upgrade actions workflows versions (#2506)
Stop relying on fugit (#2519)

`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

⚠️ Support for Queues tracking for ActiveJob required changing op in transaction context from "queue.sidekiq" to "queue.process". If you rely on this value (e.g. for sampling as described here), then you need to update your configuration accordingly.

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: lostisland/faraday#1381
- lostisland/faraday#1381
Usage:
```
Sentry.init do |config|
```

...

config.enabled_patches << :faraday

end


- Support for attachments ([#&#8203;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

`v5.16.1`

Compare Source

Bug Fixes

Pin sqlite3 gem for building because of failed release #2222

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

renovate bot requested a review from proelbtn January 27, 2024 08:38

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.16.1~~ Update sentry-ruby monorepo to v5.17.0 Mar 13, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 4af8927 to 9194be5 Compare March 13, 2024 17:51

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.17.0~~ Update sentry-ruby monorepo to v5.17.1 Mar 15, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 9194be5 to e3178ea Compare March 15, 2024 16:19

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.17.1~~ Update sentry-ruby monorepo to v5.17.2 Apr 4, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from e3178ea to 9d230a1 Compare April 4, 2024 12:13

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 9d230a1 to ad9f7c5 Compare April 11, 2024 17:35

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.17.2~~ Update sentry-ruby monorepo to v5.17.3 Apr 11, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from ad9f7c5 to e3020c5 Compare June 25, 2024 15:36

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.17.3~~ Update sentry-ruby monorepo to v5.18.0 Jun 25, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from e3020c5 to e1ed3ca Compare July 2, 2024 22:29

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.18.0~~ Update sentry-ruby monorepo to v5.18.1 Jul 2, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from e1ed3ca to 8be325c Compare July 23, 2024 17:39

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.18.1~~ Update sentry-ruby monorepo to v5.18.2 Jul 23, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 8be325c to 439e057 Compare August 13, 2024 16:55

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.18.2~~ Update sentry-ruby monorepo to v5.19.0 Aug 13, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 439e057 to bd6e681 Compare September 27, 2024 21:54

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.19.0~~ Update sentry-ruby monorepo to v5.20.0 Sep 27, 2024

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.20.0~~ Update sentry-ruby monorepo to v5.20.1 Sep 28, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from bd6e681 to a383ab5 Compare October 7, 2024 15:34

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.20.1~~ Update sentry-ruby monorepo to v5.21.0 Oct 7, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from a383ab5 to 9a20418 Compare December 4, 2024 15:40

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.21.0~~ Update sentry-ruby monorepo to v5.22.0 Dec 4, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 9a20418 to d8074f7 Compare December 8, 2024 16:13

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from d8074f7 to c86102a Compare December 16, 2024 13:28

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.22.0~~ Update sentry-ruby monorepo to v5.22.1 Dec 16, 2024

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from c86102a to cb4815d Compare January 24, 2025 14:11

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.22.1~~ Update sentry-ruby monorepo to v5.22.2 Jan 24, 2025

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.22.2~~ Update sentry-ruby monorepo to v5.22.3 Jan 29, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from cb4815d to 40bcc49 Compare January 29, 2025 13:15

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 40bcc49 to 284d0fa Compare February 6, 2025 12:48

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.22.3~~ Update sentry-ruby monorepo to v5.22.4 Feb 6, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 284d0fa to 5600623 Compare March 11, 2025 18:03

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.22.4~~ Update sentry-ruby monorepo to v5.23.0 Mar 11, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 5600623 to 580316a Compare May 15, 2025 13:23

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.23.0~~ Update sentry-ruby monorepo to v5.24.0 May 15, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 580316a to a774edc Compare June 12, 2025 14:01

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.24.0~~ Update sentry-ruby monorepo to v5.25.0 Jun 12, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from a774edc to c8fd9b8 Compare June 30, 2025 16:06

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.25.0~~ Update sentry-ruby monorepo to v5.26.0 Jun 30, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from c8fd9b8 to 1eee923 Compare August 10, 2025 13:27

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 1eee923 to cdacaa7 Compare September 8, 2025 14:07

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.26.0~~ Update sentry-ruby monorepo to v5.27.0 Sep 8, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from cdacaa7 to 77f2094 Compare September 22, 2025 17:12

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.27.0~~ Update sentry-ruby monorepo to v5.27.1 Sep 22, 2025

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch 2 times, most recently from 91b41f4 to 846f40b Compare September 26, 2025 13:37

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.27.1~~ Update sentry-ruby monorepo to v5.28.0 Sep 26, 2025

Update sentry-ruby monorepo to v5.28.1

42e119c

renovate bot force-pushed the renovate/sentry-ruby-monorepo branch from 846f40b to 42e119c Compare October 23, 2025 16:14

renovate bot changed the title ~~Update sentry-ruby monorepo to v5.28.0~~ Update sentry-ruby monorepo to v5.28.1 Oct 23, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update sentry-ruby monorepo to v5.28.1 #95

Update sentry-ruby monorepo to v5.28.1 #95

Uh oh!

renovate bot commented Jan 27, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Update sentry-ruby monorepo to v5.28.1 #95

Are you sure you want to change the base?

Update sentry-ruby monorepo to v5.28.1 #95

Uh oh!

Conversation

renovate bot commented Jan 27, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Bug Fixes

Features

Miscellaneous

...

Internal

Features

Bug Fixes

Feature

... your setup ...

Make sure structured logging is enabled

Enable default Rails log subscribers (ActionController and ActiveRecord)

Bug Fixes

Internal

Feature

... your setup ...

Features

Bug Fixes

Features

... your setup ...

Bug Fixes

Internal

Features

Bug Fixes

Internal

Miscellaneous

Bug Fixes

Internal

Bug Fixes

Features

Bug fixes

Internal

Bug Fixes

Features

Bug Fixes

Features

Gemfile

Internal

Bug Fixes

Bug Fixes

Features

...

Bug Fixes

Bug Fixes

Internal

Bug Fixes

Features

...

Bug Fixes

Internal

Internal

Bug Fixes

Internal

Bug Fixes

Bug Fixes

Features

...

increment a simple counter

set a value, unit and tags

distribution - get statistical aggregates from an array of observations

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

set - get unique counts of elements

timing - measure duration of code block, defaults to seconds

will also automatically create a metric.timing span

timing - measure duration of code block in other duraton units

...

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

...

Bug Fixes

Bug Fixes

Configuration

Uh oh!

Reviewers

renovate bot commented Jan 27, 2024 •

edited

Loading

will also automatically create a `metric.timing` span