filtlog/README at master · ossguy/filtlog · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
filtlog - a web server log filter/summarizer

http://github.com/ossguy/filtlog


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 http://www.ruby-lang.org/en/downloads/ 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     -
    75      http://ossguy.com/?p=172
    13      http://www.google.com/search?q=vimeo+downloader&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
    6       http://www.google.com/search?hl=en&q=vimeo+downloader&aq=f&oq=
    5       http://ossguy.com/
...
846     /
    616     -
    21      http://ossguy.com/?p=266
    14      http://ossguy.com/?p=226
    12      http://www.followsite.com/bot.html
    12      http://www.gnu.org/people/
    11      http://ossguy.com/
...

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 http://en.wikipedia.org/wiki/HTTP_referrer.

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"':

http://www.myndrun.is/log/
http://abc-ls.com/logs/
http://mayflowerphoto.com/logs/


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
(http://rubyforge.org/projects/ruby2c/) may be able to convert it automatically,
though this has not yet been tried.


--
  Copyright (C) 2009  Denver Gingerich <denver@ossguy.com>

  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.