env_logger
A logging implementation for `log` which is configured via an environment variable. (by rust-cli)
log
Logging implementation for Rust (by rust-lang)
| env_logger | log | |
|---|---|---|
| 5 | 28 | |
| 754 | 2,060 | |
| 1.2% | 1.9% | |
| 9.1 | 8.6 | |
| 18 days ago | about 1 month ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
env_logger
Posts with mentions or reviews of env_logger.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-05.
- 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.
log
Posts with mentions or reviews of log.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-22.
-
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.
What are some alternatives?
When comparing env_logger and log you can also consider the following projects:
tracing - Application level tracing for Rust.
slog - Structured, contextual, extensible, composable logging for Rust
rust-cli-boilerplate - Rust project boilerplate for CLI applications
log4rs - A highly configurable logging framework for Rust
rust-simple_logger - A rust logger that prints all messages with a readable output format.
async-anyhow-logger - An easy crate for catching anyhow errors from an asynchronous function, and passing them to your logger
InputBot - Rust library for creating global hotkeys, and simulating inputs
nvim-rs - A rust library for neovim clients
epoch-converter - epoch-converter enables conversion between seconds and units of time as well as between an epoch timestamp and units of time.
rand - A Rust library for random number generation.