|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +## Unreleased |
| 4 | + |
| 5 | +### Features |
| 6 | + |
| 7 | +- ref(tracing): Add data option in tracing integration to force sampling of transaction ([#945](https://github.com/getsentry/sentry-rust/pull/945)) by @Ten0 |
| 8 | + - Additional special fields have been added that allow overriding certain data on the Sentry span: |
| 9 | + - `sentry.sample`: If the span initiates a transaction, this can be used to force whether the transaction will be sampled. |
| 10 | + |
3 | 11 | ## 0.46.0 |
4 | 12 |
|
5 | 13 | ### Breaking changes |
|
29 | 37 | - feat(log): support combined LogFilters and RecordMappings ([#914](https://github.com/getsentry/sentry-rust/pull/914)) by @lcian |
30 | 38 | - Breaking change: `sentry::integrations::log::LogFilter` has been changed to a `bitflags` struct. |
31 | 39 | - It's now possible to map a `log` record to multiple items in Sentry by combining multiple log filters in the filter, e.g. `log::Level::ERROR => LogFilter::Event | LogFilter::Log`. |
32 | | - - If using a custom `mapper` instead, it's possible to return a `Vec<sentry::integrations::log::RecordMapping>` to map a `log` record to multiple items in Sentry. |
| 40 | + - If using a custom `mapper` instead, it's possible to return a `Vec<sentry::integrations::log::RecordMapping>` to map a `log` record to multiple items in Sentry. |
33 | 41 |
|
34 | 42 | ### Behavioral changes |
35 | 43 |
|
|
69 | 77 | ### Features |
70 | 78 |
|
71 | 79 | - ref(tracing): rework tracing to Sentry span name/op conversion ([#887](https://github.com/getsentry/sentry-rust/pull/887)) by @lcian |
| 80 | + |
72 | 81 | - Additional special fields have been added that allow overriding certain data on the Sentry span: |
73 | 82 | - `sentry.op`: override the Sentry span op. |
74 | 83 | - `sentry.name`: override the Sentry span name. |
|
210 | 219 | ### Features |
211 | 220 |
|
212 | 221 | Support for [Sentry structured logs](https://docs.sentry.io/product/explore/logs/) has been added to the SDK. |
| 222 | + |
213 | 223 | - To set up logs, enable the `logs` feature of the `sentry` crate and set `enable_logs` to `true` in your client options. |
214 | 224 | - Then, use the `logger_trace!`, `logger_debug!`, `logger_info!`, `logger_warn!`, `logger_error!` and `logger_fatal!` macros to capture logs. |
215 | 225 | - To filter or update logs before they are sent, you can use the `before_send_log` client option. |
216 | | -- Please note that breaking changes could occur until the API is finalized. |
| 226 | +- Please note that breaking changes could occur until the API is finalized. |
217 | 227 |
|
218 | 228 | - feat(logs): add log protocol types (#821) by @lcian |
219 | 229 | - feat(logs): add ability to capture and send logs (#823) by @lcian & @Swatinem |
@@ -318,7 +328,7 @@ An OpenTelemetry integration has been released. Please refer to the changelog en |
318 | 328 | - The metrics feature and the code related to it has been removed from the crate, as the Sentry backend stopped ingesting metrics a while ago. |
319 | 329 | - Switch to MIT license (#724) by @cleptric |
320 | 330 | - The license for the crates has been changed to MIT. |
321 | | - |
| 331 | + |
322 | 332 | ### Features |
323 | 333 |
|
324 | 334 | - feat(actix): capture HTTP request body (#731) by @pacifistes |
|
0 commit comments