I didn't do anything except setup the global logger, but it will logging trace level log of
mio.
@loggerhead
log has it's own set of cargo features to control compile time logging level
And unlike slog it defaults to logging everything.
So you need to change it manually if you want differet behavior.
You can write a custom filter for that.
I'm not sure what do you mean.
stdlog global logger handler is set only for old-style log crate logging
And it works by forwarding everything using old logging (
log crate) through that given logger. Just like you would do it with slog info!(that_global_logger, "something").
It's an escape hatch to support older libraries that don't use slog.
You might want to use
slog-scope instead of you want to avoid passing a Logger instances around.
BTW, the document link in https://crates.io/crates/slog is out of time, it should be https://docs.rs/slog
#[macro_use(o, slog_log, slog_debug, slog_info, slog_warn, slog_error, slog_trace)]
extern crate slog;
#[macro_use]
extern crate slog_scope;
extern crate slog_term;
use slog::{Level, DrainExt};
fn main() {
let drain = slog_term::streamer().stderr().build();
let d = slog::level_filter(Level::Trace, drain);
let log = slog::Logger::root(d.fuse(), o!());
slog_scope::set_global_logger(log);
slog_scope::scope(slog_scope::logger().new(o!()), foo);
}
fn foo() {
error!("error {}", "I am foo");
warn!("warn {}", "I am foo");
info!("info {}", "I am foo");
debug!("debug {}", "I am foo");
trace!("trace {}", "I am foo");
}
This code will not output trace level logging
but if I change to any other level, it works as expected.
No matter where I put it, someone will miss it anyway. :)
I recently implemented a File drain, and ended up with
impl Drain for FileDrain {
type Ok = ();
type Err = Never;
fn log(&self, record: &Record, _: &OwnedKVList) -> ::std::result::Result<(), Never> {
if let Ok(mut log_file) = self.file.try_clone() {
match writeln!(log_file, "{}", record.msg()) {
Ok(()) => {}
Err(_e) => {}
}
}
Ok(())
}
}
I'd like to avoid the try_clone, but can't due the the &self restriction.
Also please move to (not so) new channel! :)
You can just put whatever you have in
RefCell in such drain.
And to use it in
Logger you'll have to synchronize it: wrap it in logger that wil make it Sync. Eg. slog_async::Async or Mutex.
Yes,
Mutex<D : Drain> implements Drain