log
tracing
Our great sponsors
log | tracing | |
---|---|---|
28 | 52 | |
2,049 | 4,919 | |
2.7% | 2.9% | |
8.6 | 8.1 | |
18 days ago | 3 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
log
-
What Are The Rust Crates You Use In Almost Every Project That They Are Practically An Extension of The Standard Library?
log: Logging interface with various levels.
-
How easy is it to swap out your async runtime?
Depends on your logging crate. log does not depend on any async runtime.
-
log is going to bump msrv to 1.60
See the corresponing PR: https://github.com/rust-lang/log/pull/543
-
Rust and its friendly crates: Don't miss out on them!
log
-
Colorful logging with pizzazz!
It's a for-fun project that provides a configurable implementation for the log crate. This language and community is awesome, and I hope some of you get a kick out of this!
-
Ergonomic logging?
Firstly I would start by taking a look at how crates using log actually resolve this. Particularly the set_boxed_logger which simply calls Box::leak.
-
Logging Crate for CLI?
You might want to look at log and simple_log.
- Hey Rustaceans! Got a question? Ask here! (36/2022)!
-
Rust playground on iOS
4) Another route that I tried is to develop a simple terminal app using SwiftUI with a Xcode project to build that app + link against a Rust library compiled for iOS with the actual logic. I used swift-bridge for this and it works really well, to the point where I have a custom logger that you can simply use the print stuff to SwiftUI from Rust using the log crate. Once I have a bit more time, I will probably try figuring out how to clean this up a bit more.
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)
What are some alternatives?
slog - Structured, contextual, extensible, composable logging for Rust
log4rs - A highly configurable logging framework for Rust
rust-simple_logger - A rust logger that prints all messages with a readable output format.
env_logger - A logging implementation for `log` which is configured via an environment variable.
opentelemetry-rust - The Rust OpenTelemetry implementation
async-anyhow-logger - An easy crate for catching anyhow errors from an asynchronous function, and passing them to your logger
vector - A high-performance observability data pipeline.
InputBot - Rust library for creating global hotkeys, and simulating inputs
flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3