Rack::TrafficLogger

This is Rack middleware for logging incoming/outgoing HTTP/S traffic.

gem install rack-traffic-logger

require 'rack/traffic_logger'

Then, in your config.ru or wherever you set up your middleware stack:

use Rack::TrafficLogger, 'path/to/file.log'

By default, simple stream-like output will be written:

@ Wed 12 Nov '14 15:19:48.0 #48f8ed62
GET /home HTTP/1.1

@ Wed 12 Nov '14 15:19:48.0 #48f8ed62
HTTP/1.1 200 OK

The part after the # is the request log ID, which is unique to each request. It lets you match up a response with its request, in case you have multiple listeners.

You can add some colour, and JSON request/response body pretty-printing, by specifying a formatter:

use Rack::TrafficLogger, 'file.log', Rack::TrafficLogger::Formatter::Stream.new(color: true, pretty_print: true)

You can also output JSON (great for sending to log analyzers like Splunk):

use Rack::TrafficLogger, 'file.log', Rack::TrafficLogger::Formatter::JSON.new

By default, only basic request/response details are logged:

{
  "timestamp": "2014-11-12 15:30:20 +1100",
  "request_log_id": "d67e5591",
  "event": "request",
  "SERVER_NAME": "localhost",
  "REQUEST_METHOD": "GET",
  "PATH_INFO": "/home",
  "HTTP_VERSION": "HTTP/1.1",
  "SERVER_PORT": "80",
  "QUERY_STRING": "",
  "REMOTE_ADDR": "127.0.0.1"
}
{
  "timestamp": "2014-11-12 15:30:20 +1100",
  "request_log_id": "d67e5591",
  "event": "response",
  "http_version": "HTTP/1.1",
  "status_code": 200,
  "status_name": "OK"
}

You can specify other parts of requests/responses to be logged:

use Rack::TrafficLogger, 'file.log', :request_headers, :response_bodies

Optional sections include request_headers, request_bodies, response_headers, and response_bodies. You can also specify headers for both request and response headers, and bodies for both request and response bodies. Or, specify all if you want the lot. Combine tokens to get the output you need:

use Rack::TrafficLogger, 'file.log', :headers, :response_bodies # Everything except request bodies!
# Or:
use Rack::TrafficLogger, 'file.log', :all # Everything

If you want to use a custom formatter, make sure you include it before any filtering arguments:

use Rack::TrafficLogger, 'file.log', Rack::TrafficLogger::Formatter::JSON.new, :headers

You can specify that you want different parts logged based on the kind of request that was made:

use Rack::TrafficLogger, 'file.log', :headers, post: :request_bodies # Log headers for all requests, and also request bodies for POST requests

You can also exclude other request verbs entirely:

use Rack::TrafficLogger, 'file.log', only: {post: [:headers, :request_bodies]} # Log only POST requests, and include all headers, and request bodies

This can be shortened to:

use Rack::TrafficLogger, 'file.log', :post, :headers, :request_bodies

Or if you only want the basics of POST requests, without headers/bodies:

use Rack::TrafficLogger, 'file.log', :post

You can apply the same filtration based on response status codes:

use Rack::TrafficLogger, 'file.log', 404 # Only log requests that are not-found

Include as many as you like, and even use ranges:

use Rack::TrafficLogger, 'file.log', 301, 302, 400...600 # Log redirects and errors

If you need to, you can get pretty fancy:

use Rack::TrafficLogger, 'file.log', :request_headers, 401 => false, 500...600 => :all, 200...300 => {post: :request_bodies, delete: false}
use Rack::TrafficLogger, 'file.log', [:get, :head] => 200..204, post: {only: {201 => :request_bodies}}, [:put, :patch] => :all

Use shorthand syntax if you want to configure logging through a string-based configuration medium. The previous examples could also be written as:

use Rack::TrafficLogger, 'file.log', 'ih,401:f,5**:a,2**:{po:ib,de:f}'
use Rack::TrafficLogger, 'file.log', '[ge,he]:200-204,po:{o:{201:ib}},[pu,pa]:a'

It's ruby, plus these rules:

• Omit colons from Symbols. All strings of letters are converted to symbols (except false).
• Use colons in place of hash rockets.
• Use hyphens for ranges, i.e. 200-204 instead of 200..204.
• Use splats in place of large ranges, i.e. 40* instead of 400..409.
• Write only the first two letters of HTTP verbs, e.g. po for post.
• Use a for all, h for headers, b for bodies, ih for request_headers, ib for request_bodies, oh for response_headers, and ob for response_bodies (think of i for input, and o for output).
• Use o for only and f for false.

If you're reading log config from an environment variable, use express setup in place of use in a rack-up file to conditionally set up logging on your stack.

# config.ru
Rack::TrafficLogger.use on: self

Or, with some configuration:

# config.ru
Rack::TrafficLogger.use on: self,
                        filter: ENV['LOG_INBOUND_HTTP'],
                        formatter: Rack::TrafficLogger::Formatter::JSON.new,
                        log_path: ::File.expand_path('../log/http_in.log', __FILE__)

• Express setup will send use to the object passed to the on: argument. In a rack-up file, pass self.
• Logging will not be set up if filter is one of: 0 no false none off nil, or a blank string.
• Logging will revert to basic logging (no headers or bodies) if filter is one of 1 yes true normal basic minimal on.
• Omit filter to use default (basic) log filtering.
• Omit formatter to use default (stream-like) log formatting.
• Omit log_path to write directly to standard output (via /dev/stdout).

Under typical conditions, express setup internally calls:

on.use Rack::TrafficLogger, log_path, formatter, filter

Tailing a JSON log can induce migraines. There are a couple of solutions:

This gem is bundled with the parse-rack-traffic-log executable for this exact purpose.

tail -f traffic.log | parse-rack-traffic-log

This will let you tail a JSON log as if it were a regular log. You can add colors and/or JSON pretty printing using environment variables:

tail -f traffic.log | PRETTY_PRINT=1 COLOR=1 parse-rack-traffic-log

I haven't tested this with less but it should give the same result.

You can make the JSON formatter output pretty:

use Rack::TrafficLogger, 'file.log', Rack::TrafficLogger::Formatter::JSON.new(pretty_print: true)

Note that if you do, log parsers may have a hard time understanding your logs if they expect each event to be on a single line. If you think this could be an issue, use the first method instead.

If you use Faraday, you can log outbound HTTP traffic using the included middleware adapter.

Faraday.new(url: 'http://localhost') do |builder|
    builder.use Rack::TrafficLogger::FaradayAdapter, Rails.root.join('log/http_out.log').to_s
    builder.adapter Faraday.default_adapter
end

You can also use express setup:

Faraday.new(url: 'http://localhost') do |builder|
  Rack::TrafficLogger::FaradayAdapter.use on: builder,
                                          filter: ENV['LOG_OUTBOUND_HTTP'],
                                          formatter: Rack::TrafficLogger::Formatter::JSON.new,
                                          log_path: Rails.root.join('log/http_out.log').to_s
  builder.adapter Faraday.default_adapter
end