How to use rolling file appender? about log4rs HOT 7 CLOSED

The rolling file appender is turned off by default - you can turn it on with a Cargo feature:

[dependencies]
log4rs = { version = "0.5", features = ["rolling_file_appender", "compound_policy", "size_trigger", "fixed_window_roller"] }

You can also just use the all_components feature to avoid having to deal with turning on everything individually, though that'll add a couple of megabytes to the binary size.

from log4rs.

Ah I see - thanks, that fixed it.

from log4rs.

@sfackler Would you expect the following config to do rolling up correctly? The first log file comes up, but once it reaches configured trigger limit the file doesn't grow but there are no file rotations. Have I missed something?

# Scan this file for changes every 30 seconds
refresh_rate: 30 seconds

appenders:
  journey-service:
    kind: rolling_file
    path: "logs/journey-service.log"
    policy:
      # Identifies which policy is to be used. If no kind is specified, it will
      # default to "compound".
      kind: compound
      # The remainder of the configuration is passed along to the policy's
      # deserializer, and will vary based on the kind of policy.
      trigger:
        kind: size
        limit: 1mb
      roller:
        kind: fixed_window
        base: 1
        count: 5
        pattern: "logs/journey-service.{}.log"

# Set the default logging level to "warn" and attach the "stdout" appender to the root
root:
  level: info
  appenders:
    - journey-service

from log4rs.

That seems like it should work. What OS are you on?

from log4rs.

On Linux (Fedora 22/CentOS 7), think daemonizing the process has some weird effect. I think the working directory gets changed after daemonizing.

Is there any documentation to explain what types are supported and what any of those kind, base, counts etc. mean please?

from log4rs.

Docs for configuration are attached to the Deserializer types e.g.: https://docs.rs/log4rs/0.6.1/log4rs/append/rolling_file/struct.RollingFileAppenderDeserializer.html

Ah yeah, I could see daemonization causing issues there. You may want to set the paths to be absolute. The loggers should print errors to stderror if things like rotation fail - you could check there to see what they say.

from log4rs.

The set of kinds is here: https://github.com/sfackler/log4rs/blob/master/src/file.rs#L205

from log4rs.