log4rs is a highly configurable logging framework modeled after Java's Logback and log4j libraries.

log4rs.yaml:

refresh_rate: 30 seconds
appenders:
  stdout:
    kind: console
  requests:
    kind: file
    path: "log/requests.log"
    encoder:
      pattern: "{d} - {m}{n}"
root:
  level: warn
  appenders:
    - stdout
loggers:
  app::backend::db:
    level: info
  app::requests:
    level: info
    appenders:
      - requests
    additive: false

lib.rs:

use log::{error, info, warn};
use log4rs;

fn main() {
    log4rs::init_file("config/log4rs.yaml", Default::default()).unwrap();

    info!("booting up");

    // ...
}

1.82

• Run the tests: cargo test --all-features
• Run the tests for windows with cross: cross test --target x86_64-pc-windows-gnu
• Run the tests for all individual features: ./test.sh
• Run the tests for all individual features for windows with cross: ./test.sh win

If you are using the file rotation in your configuration there is a known substantial performance issue with either the gzip or zstd features. When rolling files it will zip log archives automatically. This is a problem when the log archives are large as the zip process occurs in the main thread and will halt the process until the zip process completes.

The methods to mitigate this are as follows.

1. Use the background_rotation feature which spawns an os thread to do the compression.
2. Do not enable the gzip nor the zstd features.
3. Ensure the archives are small enough that the compression time is acceptable.

For more information see the PR that added background_rotation.

If you are building this library for a Wasm target with the time_trigger feature enabled, you need to make sure the Rust flag --cfg getrandom_backend="wasm_js" is supplied to the compiler. This should be automatic when compiling with Cargo, but some configurations and tooling might require you to set an environment variable:

export RUSTFLAGS='--cfg getrandom_backend="wasm_js"'

Licensed under either of

• Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.