Thomas Eizinger 1f7a0430b7 chore(rust): record tracing WARNs as Sentry exceptions (#7166) ...

It appears that I have misunderstood the documentation of
`sentry-tracing`. When a message gets logged as an event (rather than an
"exception") `std::error::Error`s attached as tracing `Value`s do not
get recorded. It doesn't really matter whether we record our events as
exceptions or messages. We should ideally look at all of them and
particularly noisy ones can be muted forever in Sentry so we don't end
up in a "boy who cried wolf" situation. Therefore, this PR changes our
event filter to also submit WARNs as exceptions to make sure they get
logged accordingly.

Resolves: #7161.
Related: https://github.com/getsentry/sentry-rust/issues/702.

2024-10-28 14:07:42 +00:00

..

src

chore(rust): record tracing WARNs as Sentry exceptions (#7166)

2024-10-28 14:07:42 +00:00

Cargo.toml

chore(connlib): introduce telemetry log target (#7147)

2024-10-24 01:24:45 +00:00