From 7724c54b4bd8edc9c9cca3e0ae1b459b4550e0fb Mon Sep 17 00:00:00 2001 From: Vika Date: Sun, 9 Jul 2023 01:32:31 +0300 Subject: main: use tracing_tree in debug builds This gives me much more readable traces. JSON logging is still superior in production, where logs are stored in systemd-journald and preferably need to be self-contained lines. --- kittybox-rs/Cargo.toml | 1 + 1 file changed, 1 insertion(+) (limited to 'kittybox-rs/Cargo.toml') diff --git a/kittybox-rs/Cargo.toml b/kittybox-rs/Cargo.toml index c5aedf1..4c7670d 100644 --- a/kittybox-rs/Cargo.toml +++ b/kittybox-rs/Cargo.toml @@ -83,6 +83,7 @@ relative-path = "^1.5.0" # Portable relative paths for Rust sha2 = "^0.9.8" # SHA-2 series of algorithms for Rust tracing = { version = "0.1.34", features = [] } tracing-tree = "0.2.1" +tracing-log = "0.1.3" tracing-subscriber = { version = "0.3.11", features = ["env-filter", "json"] } tower-http = { version = "0.3.3", features = ["trace", "cors", "catch-panic"] } tower = { version = "0.4.12", features = ["tracing"] } -- cgit 1.4.1