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
IMPORTANT
If your application processes a large number of background jobs and has tracing enabled, it is recommended to check your
traces_sampler
(or switch totraces_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 0.1 when /delayed_job/ # or resque 0.001 # adjust this value else 0.0 # ignore all other transactions end end end
๐ท This is to prevent the background job tracing consumes too much of your transaction quota.
๐ Bug Fixes
- โ Add
-
v4.5.0 Changes
๐ Features
- ๐ Implement sentry-trace propagation #1446
The SDK will insert the
sentry-trace
to outgoing requests made withNet::HTTP
. Its value would look liked827317d25d5420aa3aa97a0257db998-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.
Example:
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 isfalse
.๐ Bug Fixes
-
v3.1.1 Changes
September 25, 2020 -
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)Before:
config.transport_failure_callback = lambda { |event| AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later }
After:
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 isnil
) and will be called with exception's backtraceRaven.configure do |config| config.backtrace_cleanup_callback = lambda do |backtrace| Rails.backtrace_cleaner.clean(backtrace) end end
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 end
๐ 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
-
v3.0.4 Changes
August 28, 2020 -
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
andEvent#log_message
interfaces
- It adds
-
v3.0.2 Changes
August 20, 2020- ๐ fix: Add gem target for craft