|
4 | 4 |
|
5 | 5 | - Allow users to configure their asset-skipping pattern [#1915](https://github.com/getsentry/sentry-ruby/pull/1915)
|
6 | 6 |
|
7 |
| - Users can now configure their own pattern to skip asset requests' transactions |
| 7 | + Users can now configure their own pattern to skip asset requests' transactions |
| 8 | + |
| 9 | + ```rb |
| 10 | + Sentry.init do |config| |
| 11 | + config.rails.assets_regexp = /my_regexp/ |
| 12 | + end |
| 13 | + ``` |
8 | 14 |
|
9 |
| - ```rb |
10 |
| - Sentry.init do |config| |
11 |
| - config.rails.assets_regexp = /my_regexp/ |
12 |
| - end |
13 |
| - ``` |
14 | 15 | - Use `Sentry.with_child_span` in redis and net/http instead of `span.start_child` [#1920](https://github.com/getsentry/sentry-ruby/pull/1920)
|
15 |
| - - This might change the nesting of some spans and make it more accurate |
16 |
| - - Followup fix to set the sentry-trace header in the correct place [#1922](https://github.com/getsentry/sentry-ruby/pull/1922) |
| 16 | + - This might change the nesting of some spans and make it more accurate |
| 17 | + - Followup fix to set the sentry-trace header in the correct place [#1922](https://github.com/getsentry/sentry-ruby/pull/1922) |
17 | 18 |
|
18 | 19 | - Use `Exception#detailed_message` when generating exception message if applicable [#1924](https://github.com/getsentry/sentry-ruby/pull/1924)
|
| 20 | +- Make `sentry-sidekiq` compatible with Sidekiq 7 [#1930](https://github.com/getsentry/sentry-ruby/pull/1930) |
19 | 21 |
|
20 | 22 | ### Bug Fixes
|
21 | 23 |
|
22 | 24 | - `Sentry::BackgroundWorker` will release `ActiveRecord` connection pool only when the `ActiveRecord` connection is established
|
23 | 25 | - Remove bad encoding arguments in redis span descriptions [#1914](https://github.com/getsentry/sentry-ruby/pull/1914)
|
24 |
| - - Fixes [#1911](https://github.com/getsentry/sentry-ruby/issues/1911) |
| 26 | + - Fixes [#1911](https://github.com/getsentry/sentry-ruby/issues/1911) |
25 | 27 | - Add missing `initialized?` checks to `sentry-rails` [#1919](https://github.com/getsentry/sentry-ruby/pull/1919)
|
26 |
| - - Fixes [#1885](https://github.com/getsentry/sentry-ruby/issues/1885) |
| 28 | + - Fixes [#1885](https://github.com/getsentry/sentry-ruby/issues/1885) |
27 | 29 | - Update Tracing Span's op names [#1923](https://github.com/getsentry/sentry-ruby/pull/1923)
|
28 | 30 |
|
29 |
| - 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. |
30 |
| - **If you rely on Span op names for fine-grained event filtering, this may affect the data your app sends to Sentry.** |
| 31 | + 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. |
| 32 | + **If you rely on Span op names for fine-grained event filtering, this may affect the data your app sends to Sentry.** |
31 | 33 |
|
32 | 34 | ### Refactoring
|
33 | 35 |
|
|
0 commit comments