27 releases (11 stable)

4.1.1 Mar 23, 2022
4.1.0 Oct 22, 2020
4.0.0 Aug 13, 2019
3.0.5 Jul 24, 2019
0.6.0 Jul 19, 2016

#159 in Debugging

Download history 35511/week @ 2022-08-15 34829/week @ 2022-08-22 35825/week @ 2022-08-29 36881/week @ 2022-09-05 35582/week @ 2022-09-12 37336/week @ 2022-09-19 40704/week @ 2022-09-26 40001/week @ 2022-10-03 37631/week @ 2022-10-10 41933/week @ 2022-10-17 40537/week @ 2022-10-24 37807/week @ 2022-10-31 41468/week @ 2022-11-07 43613/week @ 2022-11-14 37884/week @ 2022-11-21 41617/week @ 2022-11-28

166,085 downloads per month
Used in fewer than 57 crates

MPL-2.0 OR MIT OR Apache-2.0

17KB
168 lines

Travis CI Build Status slog-stdlog on crates.io slog-rs Gitter Chat Minimum Rust Version 1.38

slog-stdlog - log crate adapter for slog-rs

See slog-stdlog documentation for details.

For more information, help, to report issues etc. see slog-rs.


lib.rs:

log crate adapter for slog-rs

This crate provides two way compatibility with Rust standard log crate.

log -> slog

After calling init() slog-stdlog will take a role of log crate back-end, forwarding all the log logging to slog_scope::logger(). In other words, any log crate logging statement will behave like it was slog logging statement executed with logger returned by slog_scope::logger().

See documentation of slog-scope for more information about logging scopes.

See init documentation for an example.

slog -> log

StdLog is slog::Drain that will pass all Records passing through it to log crate just like they were crated with log crate logging macros in the first place.

slog-scope

Since log does not have any form of context, and does not support Logger slog-stdlog relies on "logging scopes" to establish it.

You must set up logging context for log -> slog via slog_scope::scope or slog_scope::set_global_logger. Setting a global logger upfront via slog_scope::set_global_logger is highly recommended.

Note: Since slog-stdlog v2, unlike previous releases, slog-stdlog uses logging scopes provided by slog-scope crate instead of it's own.

Refer to slog-scope crate documentation for more information.

Warning

Be careful when using both methods at the same time, as a loop can be easily created: log -> slog -> log -> ...

Compile-time log level filtering

For filtering debug! and other log statements at compile-time, configure the features on the log crate in your Cargo.toml:

log = { version = "*", features = ["max_level_trace", "release_max_level_warn"] }

Dependencies

~385–540KB