Skip to content
A web server log file filter/summarizer which shows total page views and referrers.
Find file
Latest commit 5cb1960 Jan 1, 2010 @ossguy sort by views, then by page
Sort by the view count, then by the page name.  Previously, the
results were sorted by view count only and left unsorted after that,
making it difficult to see related pages with the same view count.
With this change, related pages (ie. similar names) are grouped,
making them easier to look at holistically while viewing the results.
Failed to load latest commit information.


filtlog - a web server log filter/summarizer

1. Running filtlog
2. Example log files
3. Configuring filtlog
4. Performance

1. Running filtlog

filtlog requires Ruby 1.8.7 or greater to run.  If you don't have Ruby, you can
download it from or, if you're using
Debian or a derivative such as Ubuntu, you can run "sudo apt-get install ruby".

To run filtlog with the default options, simply pass the web server log file(s)
you want to summarize to filtlog.rb (ie. "./filtlog.rb access.log").  The log
files are assumed to be in Apache Combined Log Format.  The output will look
something like this:

874     /?p=172 Vimeo Downloader 0.1 released
    230     -
846     /
    616     -

The first line is the page with the most hits (/?p=172) preceded by the number
of hits it received (874).  The lines that follow are the referrers used to find
that page, preceded by the number of times the referrer was used.  For more
information on HTTP referrers, see

In order to get page descriptions, like "Vimeo Downloader 0.1 released" above,
you need to add the corresponding information to page_names in filtlog.conf.
For more details, see the inline comments in filtlog.conf.example.

2. Example log files

If you want to see how filtlog works but don't have any log files to test it
with, you can find log files online.  Here are some log files found through a
Google search for 'get googlebot "yahoo slurp"':

3. Configuring filtlog

filtlog expects its configuration file to be located in filtlog.conf.  An
example configuration file is included as filtlog.conf.example.  You can copy
that file to filtlog.conf and modify it to suit your needs.  Full details on the
various configuration file options, including how to use user_agents.rb to help
filter results, are provided inline in filtlog.conf.example.

4. Performance

filtlog can take a while to run on a large set of log files.  As an example,
running filtlog on 28 log files containing a total of 103,143 lines takes
8.6 seconds to run using Ruby 1.8 on a 1.3 GHz Pentium M running Ubuntu 8.10 and
7.9 seconds using Ruby 1.9 on the same machine.

Since filtlog does not make significant use of Ruby's dynamic language features,
it should be easy to convert filtlog directly to C or some other static
language whose compiler could offer better performance.  ruby2c
( may be able to convert it automatically,
though this has not yet been tried.

  Copyright (C) 2009  Denver Gingerich <>

  Copying and distribution of this file, with or without modification,
  are permitted in any medium without royalty provided the copyright
  notice and this notice are preserved.
Something went wrong with that request. Please try again.