search

zinc-collective / convene

An Operating System for the Solidarity Economy
https://convene.zinc.coop
Other
56 stars 19 forks source link

Bump sentry-ruby and sentry-rails #2298

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps sentry-ruby and sentry-rails. These dependencies needed to be updated together. Updates sentry-ruby from 5.16.1 to 5.17.0

Changelog

Sourced from sentry-ruby's changelog.

5.17.0

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:

      # 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) }

... (truncated)

Commits


Updates sentry-rails from 5.16.1 to 5.17.0

Changelog

Sourced from sentry-rails's changelog.

5.17.0

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:

      # 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) }

... (truncated)

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)