tracing
env_logger
Our great sponsors
tracing | env_logger | |
---|---|---|
52 | 5 | |
4,939 | 750 | |
3.3% | 3.6% | |
7.8 | 8.8 | |
2 days ago | 9 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tracing
-
Decrusting the tracing crate [video] by Jon Gjengset
The video description is as follows:
In this stream, we peel back the crust on the tracing crate — https://github.com/tokio-rs/tracing/ — and explore its interface, structure, and mechanisms. We talk about spans, events, their attributes and fields, and how to think about them in async code. We also dig into what subscribers are, how they pick up events, and how you can construct your own subscribers through the layer abstraction. For more details about tracing, see https://docs.rs/tracing/latest/tracing/.
-
Vendor lock-in is in the small details
> What's been your biggest issues around ergonomics/amenities for OpenTelemetry?
I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.
-
Grimoire - A recipe management application.
The tracing (logging) mechanism in an asynchronous codebase (tracing).
-
How easy is it to swap out your async runtime?
Tracing is Tokio's alternative for async code.
-
Hey Rustaceans! Got a question? Ask here (27/2023)!
At a technical level, in Rust, both [tracing]https://crates.io/crates/tracing) and log are entire ecosystems (though for the latter at least there's also third party logging frameworks), and there's at least a bridge from log to tracing.
-
How can I write a tracing subscriber that saves to a database?
I am using https://github.com/tokio-rs/tracing for logging purposes in my application. I would like to develop a feature wherein logs should be saved to a database table (via sea-orm). Something similar is this, but it does not solve my needs fully.
-
A locking war story
I've used the tracing infrastructure with tracing_flame to profile some hot paths in async code: https://github.com/tokio-rs/tracing/tree/master/tracing-flame
-
I was wrong about rust
Oh nice! IIRC when I checked, it was the Unicode tables that smashed the code size. I recently hit the same issue with the tracing crate, where a crate feature (for env var filtering) pulled in regex and my binary was suddenly 1MB bigger.
-
Debugging and profiling embedded applications.
I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.
-
Custom Axum Logging for Routes?
tracing by itself only outputs log data, you need to consume them in a subscriber, the tracing-subscriber crate exists for this. (example)
env_logger
- Adding logging or println absolutely wrecks throughput of my axum server
-
How does env_logger work without being importing the library?
I've been using env_logger for setting log-levels through environment variables, and I've been confused about something. In every example of the library, they just say call env_logger::init() before instantiating any logger, and I do that. But the weird this is that, I can call this without a use env_logger line anywhere in my module or code. I've added env_logger to the Cargo.toml file, but that shouldn't be enough to inject this module into the runtime, should it? If that is the case, how are they doing this?
-
rsw - wasm-pack based build tool
# @see: https://github.com/env-logger-rs/env_logger # RUST_LOG=rsw= rsw # 1. info RUST_LOG=rsw=info rsw # 2. all: info, trace, debug, error, warn RUST_LOG=rsw rsw
-
Best way to handle verbose/optional output in a CLI program?
I use env_logger which allows the user to set verbosity through an environment variable. It also allows specifying which module to output logs from, or all.
What are some alternatives?
log4rs - A highly configurable logging framework for Rust
log - Logging implementation for Rust
slog - Structured, contextual, extensible, composable logging for Rust
rust-cli-boilerplate - Rust project boilerplate for CLI applications
opentelemetry-rust - The Rust OpenTelemetry implementation
vector - A high-performance observability data pipeline.
flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
warp - A super-easy, composable, web server framework for warp speeds.
criterion.rs - Statistics-driven benchmarking library for Rust
mirage - MirageOS is a library operating system that constructs unikernels