Thomas Eizinger de35bb067e fix(telemetry): don't embed errors values in telemetry_event! (#7366) ...

Due to https://github.com/getsentry/sentry-rust/issues/702, errors which
are embedded as `tracing::Value` unfortunately get silently discarded
when reported as part of Sentry "Event"s and not "Exception"s.

The design idea of these telemetry events is that they aren't fatal
errors so we don't need to treat them with the highest priority. They
may also appear quite often, so to save performance and bandwidth, we
sample them at a rate of 1% at creation time.

In order to not lose the context of these errors, we instead format them
into the message. This makes them completely identical to the `debug!`
logs which we have on every call-site of `telemetry_event!` which
prompted me to make that implicit as part of creating the
`telemetry_event!`.

Resolves: #7343.

2024-11-18 18:17:08 +00:00

..

src

fix(telemetry): don't embed errors values in telemetry_event! (#7366)

2024-11-18 18:17:08 +00:00

Cargo.toml

build(deps): Bump thiserror from 1.0.64 to 1.0.68 in /rust (#7260)

2024-11-04 19:06:15 +00:00