Thomas Eizinger 82fcad0a3b refactor(rust): only send telemetry spans to Sentry (#7153) ...

With the introduction of the `tracing-sentry` integration in #7105, we
started sending tracing spans to Sentry. By default, all spans with
level INFO and above get sampled at the configured rate and sent to
Sentry.

This results in a lot of useless transaction in Sentry because we use
INFO level spans in multiple places in connlib to attach contextual
information like the current connection ID.

This PR introduces the concept of `telemetry` spans which - similar to
the `telemetry` log target in #7147 - qualifies a span for being sent to
Sentry. By convention, these are also defined as requiring the TRACE
level. This ensures we won't ever see them as part of regular log
output.

2024-10-24 20:25:26 +00:00

..

src

refactor(rust): only send telemetry spans to Sentry (#7153)

2024-10-24 20:25:26 +00:00

Cargo.toml

chore(rust): capture backtraces for panics (#7133)

2024-10-24 14:18:40 +00:00