Log Alternatives
Similar projects and alternatives to log
-
-
-
-
async-anyhow-logger
An easy crate for catching anyhow errors from an asynchronous function, and passing them to your logger
-
-
-
env_logger
A logging implementation for `log` which is configured via an environment variable.
-
rust-simple_logger
A rust logger that prints all messages with a readable output format.
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
-
-
tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
-
-
-
regex
An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
-
-
-
-
-
-
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better log alternative or higher similarity.
Reviews and mentions
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 2021-11-19.
- "This paper examines this most frequently deployed of software architectures: the BIG BALL OF MUD. A BIG BALL OF MUD is a casually, even haphazardly, structured system. Its organization, if one can call it that, is dictated more by expediency than design. "
-
First library - feedback would be greatly appreciated
Printing in epoch_units is very surprising. You can use the log crate to log messages, but it's often unnecessary for libraries.
-
Writing a QML Application in Rust (Part 2)
We first need to add log and env_logger as dependencies in Cargo.toml.
-
Blocking prints in async code
I just asked myself the question why it seems generally accepted to block when writing to stdout or stderr. Most tokio examples just use std::print! which is a blocking call. Also the log crate as well as the tracing crate, which is connected to tokio and made to be used in async code, only have sync apis. Is there any explanation why? Is it just general acceptance because this is just the most ergonomic way? Especially if piping stdout somewhere print calls might block a long time and logging to files might do so too. Are there any good logging crates (optimally using tokio) which don't require sync calls to be inserted everywhere. In my current project blocking because of some flush to persistent memory isn't really acceptable but i still would like to log and trace events. Thanks for your time and have a nice day.
-
Rust cli example #2: Ferris hunts errors
A logging facade provides a single logging API that abstracts over the actual logging implementation. Libraries can use the logging API provided by this crate, and the consumer of those libraries can choose the logging implementation that is most suitable for its use case. Sources
-
Go: the Good, the Bad and the Ugly
Yes - you use a third party crate. This is one of Rust's design decisions - to push things to external crates. It has done so with other things - the most known are logging, regular expressions, and random number generation. The idea is that instead of a huge standard library that includes everything, you have a great dependency manager that lets easily add these functionalities that were moved outside (or use their alternatives, if you find that one of the alternatives better suits your needs)
-
The Rust dbg! macro
However, I've found this: https://github.com/rust-lang/log/pull/317 and this, in particular: https://github.com/rust-lang/log/pull/316#issuecomment-456154244.
-
Hey Rustaceans! Got an easy question? Ask here (25/2021)!
Cant you use https://crates.io/crates/log , and implement your own logger that sends the actual output over a mpsc channel to a logging thread that is allowed to block, and can handle your other requirements ? ( https://docs.rs/log/0.4.14/log/ - implementing a logger )
-
Logging library
I am looking for a logging library capable of logging into the event system (similar to syslog in C++). I've seen the log rust library. Unfortunately, I've seen the possible implementations (such as env_logger, but without knowing which, still maintained, library has the possibility to write in the event system.
-
[Media] Any reason the crate download statistic are low at the end of each month? It seems a large number of crates follow this pattern. I'm just curious on why this happens?
log: https://crates.io/crates/log
-
Hey Rustaceans! Got an easy question? Ask here (21/2021)!
Something like fern or log4rs should be able to be configurable in any way you like. It might be possible to use one of the less complex options as well. Choose one that works for you from the executables section here.
-
Seasoned game devs, what do you use for logging? What about tracing?
I wrote my own logger that conforms to the API supplied by the log crate. My implementation writes to stdout, to my in game console, and to a file. I flush on every message with the severity of "error" so that I don't lose the last message if it's an explanation of a crash or such. If the game crashes, the panic message is written to the log using backtrace. Only the 10 most recent logs are saved on the user's disk, as to not waste too much of their hard drive space.
-
How to issue runtime warnings from within a library?
The most popular crate for this ATM is log.
-
async-anyhow-logger: An easy way to handle logging anyhow errors in an asynchronous programs!
this doesn't handle any logging by itself, it's just a wrapper that sends things to the error log if a task returns Err, using the log crate. there's tracing-log if you use tracing, to provide compatibility between tracing and log.
-
Best way to handle verbose/optional output in a CLI program?
Does https://crates.io/crates/log allow to configure global log level?
Stats
Basic log repo stats
15
1,209
6.6
18 days ago
rust-lang/log is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
Popular Comparisons
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
Are you hiring? Post a new remote job listing for free.