Thomas Eizinger 12ca4f1cc7 chore(connlib): introduce telemetry log target (#7147) ...

With #7105, all ERROR events from `tracing` get logged as exceptions in
Sentry and all WARN events get logged as "messages". We don't want to
fill up the user's harddrive with logs which means we have to be
somewhat conservative, what gets logged on INFO and above (with INFO
being the default log level). There are certain events though where it
would be useful to know, how often they happen because too many of them
can indicate a problem.

To solve this problem, we introduce a dedicated `telemetry` log target
that the tracing-sentry integration layer watches for. Events for the
`telemetry` log target that gets logged on TRACE will be sampled at a
rate of 1% and submitted as messages to Sentry.

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

..

src

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

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

Cargo.toml

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

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