All Versions
Latest Version
Avg Release Cycle
28 days
Latest Release

Changelog History
Page 4

  • v4.6.0 Changes

    ๐Ÿ”‹ Features

    • โž• Add sentry-resque #1476
    • โž• Add tracing support to sentry-resque #1480
    • ๐Ÿ’Ž Set user to the current scope via sidekiq middleware #1469
    • โž• Add tracing support to sentry-delayed_job #1482


    If your application processes a large number of background jobs and has tracing enabled, it is recommended to check your traces_sampler (or switch to traces_sampler) and give the background job operations a smaller rate:

    Sentry.init do |config|
      config.traces_sampler = lambda do |sampling_context|
        transaction_context = sampling_context[:transaction_context]
        op = transaction_context[:op]
        case op
        when /request/
          # sampling for requests
        when /delayed_job/ # or resque
          0.001 # adjust this value
          0.0 # ignore all other transactions

    ๐Ÿ‘ท This is to prevent the background job tracing consumes too much of your transaction quota.

    ๐Ÿ› Bug Fixes

    • ๐Ÿ’Ž Force encode request body if it's a string #1484
  • v4.5.2 Changes

    ๐Ÿ”จ Refactoring

    • โœ‚ Remove redundant files #1477

    ๐Ÿ› Bug Fixes

    • ๐Ÿš€ Disable release detection when SDK is not configured to send events #1471
  • v4.5.1 Changes

    ๐Ÿ› Bug Fixes

    • โœ‚ Remove response from breadcrumb and span #1463
      • Fixes the issue mentioned in this comment
    • ๐Ÿ‘ท Correct the timing of loading ActiveJobExtensions #1464
    • ๐Ÿ’Ž Limit breadcrumb's message length #1465
  • v4.5.0 Changes

    ๐Ÿ”‹ Features

    • ๐Ÿ’Ž Implement sentry-trace propagation #1446

    The SDK will insert the sentry-trace to outgoing requests made with Net::HTTP. Its value would look like d827317d25d5420aa3aa97a0257db998-57757614642bdff5-1.

    ๐ŸŽ If the receiver service also uses Sentry and the SDK supports performance monitoring, its tracing event will be connected with the sender application's.


    0๏ธโƒฃ This feature is activated by default. But users can use the new config.propagate_traces config option to disable it.

    • Add configuration option skip_rake_integration #1453

    0๏ธโƒฃ With this new option, users can skip exceptions reported from rake tasks by setting it true. Default is false.

    ๐Ÿ› Bug Fixes

    • ๐Ÿ‘ Allow toggling background sending on the fly #1447
    • ๐Ÿ‘ท Disable background worker for runner mode #1448
  • v3.1.1 Changes

    September 25, 2020


    โž• Add request id to headers if exists (#1033)

    ๐Ÿ‘ Allow blocks on user_context (#1023)

    ๐Ÿ”ง Enable configurable rack environment recorded parameters (#860)

    โœ‚ Remove ActiveJob keys for both Sidekiq and DelayedJob (#898)

    ๐Ÿ›  Fix

    • โœ‚ Remove circular dependency in transport/http.rb (#1035)
  • v3.1.0 Changes

    September 17, 2020

    ๐Ÿ”‹ Feature

    • ๐Ÿ’Ž Exclude all 4xx Rails errors (#1004)

      See the full list here

    • Add some error context in transport_failure_callback (#1003)


      config.transport_failure_callback = lambda { |event|
        AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later


      config.transport_failure_callback = lambda { |event, error|
        AdminMailer.email_admins("Oh god, it's on fire because #{error.message}!", event).deliver_later
    • ๐Ÿ‘Œ Support cleaning up exception backtrace with customized backtrace_cleaner (#1011)

      The new config backtrace_cleanup_callback takes a lambda/proc object (default is nil) and will be called with exception's backtrace

      Raven.configure do |config|
        config.backtrace_cleanup_callback = lambda do |backtrace|

      And with the Rails integration, it'll automatically use a customized Raven::Rails::BacktraceCleaner to clean up exception's backtrace. It's basically Rails 6's backtrace cleaner but without silencers.

      The main reason to add this cleaner is to remove template methods from the trace, e.g.

      app/views/welcome/view_error.html.erb in _app_views_welcome_view_error_html_erb__2807287320172182514_65600 at line 1

      will become

      app/views/welcome/view_error.html.erb at line 1

      This can help Sentry group issues more accurately. See #957 for more information about this.

      If you don't want this change, you can disable it with:

      Raven.configure do |config|
        config.backtrace_cleanup_callback = nil
    • ๐Ÿ’Ž Make dsn value accessable from config (#1012)

      You can now access the dsn value via Raven.configuration.dsn

    ๐Ÿ—„ Deprecation

    • ๐Ÿ—„ Deprecate dasherized filenames (#1006)

      If you're using

      gem 'sentry-raven', require: 'sentry-raven-without-integrations'
      # or 
      require "sentry-raven-without-integrations"

      you will start seeing deprecation warnings. Please change them into

      gem 'sentry-raven', require: 'sentry_raven_without_integrations'
      # or 
      require "sentry_raven_without_integrations"
    • ๐Ÿ’Ž Unify breadcrumb loggers activation (#1016)

      Currently, we activate our breadcrumb loggers differently:

      require "raven/breadcrumbs/sentry_logger"
      Raven.configuration.rails_activesupport_breadcrumbs = true

      It's not a nice user interface, so this PR adds a new configuration option breadcrumbs_logger to improve this:

      Raven.configuration.breadcrumbs_logger = :sentry_logger
      Raven.configuration.breadcrumbs_logger = :active_support_logger
      Raven.configuration.breadcrumbs_logger = [:sentry_logger, :active_support_logger]

      Please migrate to the new activation apporach, otherwise you'll see depraction warnings. And old ones will be dropped in version 4.0.

    ๐Ÿ”จ Refactor

    • ๐Ÿ’Ž Accept non-string message in Event.from_exception (#1005)
    • ๐Ÿ”จ Refactor event initialization (#1010)
    • ๐Ÿ”จ Refactor sidekiq integration (#1019)

    ๐Ÿ›  Fix

    • ๐Ÿ’Ž Replace sys_command usages in context.rb (#1017)
    • ๐Ÿ›  Fix merge error from rack-timeout raven_context on old releases (#1007)
    • Return value of rescue_with_handler when intercepting ActiveJob exceptions (#1027)
  • v3.0.4 Changes

    August 28, 2020
    • ๐Ÿ›  fix: Don't log warning messages when it doesn't need to (#1000)
    • ๐Ÿ›  fix: Revert "Refactor Raven::Client class" (#1002)
  • v3.0.3 Changes

    August 27, 2020
    • ๐Ÿ›  fix: Ensure Processor::Cookie can run after Processor::RemoveCircularReferences (#996)
    • ๐Ÿ›  fix: Avoid mutating user passed in options (#994)
    • ๐Ÿ›  fix: Fix/Refactor Raven::Cli (#989)
    • ๐Ÿ”จ ref: Refactor Raven::Client class (#995)
      • It adds Event#message_from_exception and Event#log_message interfaces
  • v3.0.2 Changes

    August 20, 2020
    • ๐Ÿ›  fix: Add gem target for craft
  • v3.0.1 Changes

    August 20, 2020
    • ๐Ÿ›  fix: Improve SanitizeData processor (#984)
    • ๐Ÿ›  fix: Masking cookies as key/pair instead of a single string (#983)
    • ๐Ÿ›  fix: Transports classes' requiring issue (#986)
    • ๐Ÿ›  fix: Frozen string issues (#977)
    • ๐Ÿ’Ž feat: Officially support Rails 6 (#982)