clogger

The log format can be changed so the user can specify exactly which fields to log from the data range.

Features:

• Multi-instance capable and (optionally) reentrant. You can use Clogger in a multi-threaded server, and even multiple Cloggers logging to different locations and different formats in the same process.
• Pure Ruby version for non-MRI versions of Ruby (or via CLOGGER_PURE=1 in the environment). The optional C extension is loaded by default and supported under MRI 1.8.7, 1.9.1, 1.9.2 and Rubinius.
• Highly customizable with easy-to-read nginx-like log format variables.
• Pre-defines Apache Common Log Format, Apache Combined Log Format and Rack::CommonLogger (as distributed by Rack 1.0 and 1.1) formats. See Clogger::Format for the predefined formats.
• Untrusted values are escaped (all HTTP headers, request URI components) to make life easier for HTTP log parsers.

What is new in this release:

• Updated website URL, cleanups.

What is new in version 0.9.0:

• Using GVL for filesystem operations to avoid worst case scenarios. This may hurt performance for some folks with bad locking implementations and extremely fast filesystems.
• A couple of minor cleanups.

What is new in version 0.8.0:

• Clogger now delegates all unknown methods to the response body in cases where it needs to wrap the response body. This allows apps that use non-standard Rack extensions to continue working.

Requirements:

• Ruby Rack