The Rust Ukrainian Community has a free bootcamp with open program: rustcamp. It covers many Rust topics and skills needed for successful Rust developer.
One of the topics is logging. I've been a mentor at every boot camp, and I was surprised to find out that logger configuration is a difficult topic for many people.

tracing and tracing_subscriber crates are extremely powerful and configurable. But, on the other hand, the API seems complicated and confusing. People read many articles, watch long videos, and still don't know what to do with all these subscribers, layers, and filters.
For me, all you need is to read the module-level documentation on docs.rs. Many people underestimate the module-level documentation. idk why. Perhaps this is a habit from other languages ​​where the documentation is poor and you need additional resources.

In the Rust ecosystem, all well-developed and popular crates have comprehensive documentation which is more than enough. To understand tracing_subscriber you just need to read the following:
🔘 tracing_subscriber#layers-and-filters
🔴 tracing_subscriber/layer
🟣 tracing_subscriber/layer#per-layer-filtering
That's all! Now you can start writing your super-duper logging config.
If you want you can try to do the task by yourself: 3_8_log: Task. The task isn't hard but still fun to solve.

The same situation with crypto libraries in Rust. When you try to use them for the first time, you face all these abstractions, generics, traits, weird APIs... But when you read module-level documentation, all becomes logical and understandable.