mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-03-21 21:41:48 +00:00
12ca4f1cc7
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.
23 lines
606 B
TOML
23 lines
606 B
TOML
[package]
|
|
name = "firezone-logging"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
authors = ["Firezone, Inc."]
|
|
publish = false
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
anyhow = "1"
|
|
nu-ansi-term = { version = "0.50" }
|
|
rand = "0.8"
|
|
sentry-tracing = "0.34.0"
|
|
time = { version = "0.3.36", features = ["formatting"] }
|
|
tracing = { workspace = true }
|
|
tracing-appender = { version = "0.2.2" }
|
|
tracing-log = "0.2"
|
|
tracing-stackdriver = { version = "0.11.0" }
|
|
tracing-subscriber = { workspace = true, features = ["env-filter"] }
|
|
|
|
[lints]
|
|
workspace = true
|