5.6.0
Features
-
Allow users to configure their asset-skipping pattern #1915
Users can now configure their own pattern to skip asset requests' transactions
Sentry.init do |config| config.rails.assets_regexp = /my_regexp/ end
-
Use
Sentry.with_child_spanin redis and net/http instead ofspan.start_child#1920- This might change the nesting of some spans and make it more accurate
- Followup fix to set the sentry-trace header in the correct place #1922
-
Use
Exception#detailed_messagewhen generating exception message if applicable #1924 -
Make
sentry-sidekiqcompatible with Sidekiq 7 #1930
Bug Fixes
-
Sentry::BackgroundWorkerwill releaseActiveRecordconnection pool only when theActiveRecordconnection is established -
Remove bad encoding arguments in redis span descriptions #1914
- Fixes #1911
-
Add missing
initialized?checks tosentry-rails#1919- Fixes #1885
-
Update Tracing Span's op names #1923
Currently, Ruby integrations' Span op names aren't aligned with the core specification's convention, so we decided to update them altogether in this PR.
If you rely on Span op names for fine-grained event filtering, this may affect the data your app sends to Sentry.
Also make sure to update yourtraces_samplerif you rely on theopfor filtering some requests.
Refactoring
- Make transaction a required argument of Span #1921