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

#135 in Debugging

Download history 60379/week @ 2024-10-30 57641/week @ 2024-11-06 56286/week @ 2024-11-13 61815/week @ 2024-11-20 62152/week @ 2024-11-27 67313/week @ 2024-12-04 69924/week @ 2024-12-11 52584/week @ 2024-12-18 17182/week @ 2024-12-25 40125/week @ 2025-01-01 59947/week @ 2025-01-08 65794/week @ 2025-01-15 66699/week @ 2025-01-22 69646/week @ 2025-01-29 70058/week @ 2025-02-05 50824/week @ 2025-02-12

268,460 downloads per month
Used in 170 crates (68 directly)

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

~450KB