| Typical usage: |
footprints
-key <reg-exp>
|
|
To compile statistics on
<reg-exp>, where
<reg-exp> can include special
characters like
period (.) and
asterisk (*). For instance, a search
key like "/projects", will compile statistics on the URL "/project".
However using a search key like
"/projects/*" will compile
statistics on any URL starting with "/projects". Finally, using a
search key like
"*projects*",
will compile statistics on any URL with the word "projects" in them.
Using the search key
"*", will
compile statistics on every URL accessed (which is the default).
|
|
footprints -key
<reg-exp> -html
|
|
To compile statistics on <reg-exp>, but output in HTML.
|
|
footprints -key
<reg-exp> -ascending
|
|
To compile statistics on <reg-exp>, but display statistics
in ascending order rather than descending.
|
|
footprints -key
<reg-exp> -filename
</path/different/logfile>
|
|
To compile statistics on <reg-exp>, but read statistics
from your defined path and filename.
|
|
footprints -key
<reg-exp> -internal
|
|
To compile statistics on <reg-exp>, but discard all
requests from internal machines - machines of similar IP
addresses. (See $my_IP_number and $my_IP_name)
|
|
footprints -key
<reg-exp> -images
|
|
To compile statistics on <reg-exp>, but discard all
requests for "images". Images, are defeined as files with
the suffix gif, jpg, jpeg, xbm, tif, or png.
|
|
gzcat log.gz | footprints -key
<reg-exp> -
|
|
Typically, old log files are get compressed. As a result,
this script allows STDIN to be used in order to provide gzip'd
logs be piped into footprints.
|
|
footprints -key <reg-exp>
-directory <directory>
-expr <reg-exp>
|
|
Sometimes, you may want to compile statistics on an entire directory
of log files. With these two options you can define where and what
kind of files to read. For example, in a directory you may want to
read all files suffixed with ".log". So, you could do something like
-directory ~logs -expr "*.logs". (See $default_directory
and $default_expr)
|
|
footprints -key <reg-exp>
-verbose > ~/stats.txt
|
|
Some logs tend to be huge. You may wanna redirect the output to a
file. Using the verbose option, this will display a cute "thermometer"
animation, that represents how much time is left to finish.
|
|
footprints -key <reg-exp>
-minhits <#> -maxhits <#>
|
|
If your output is just too large, then you can narrow the range
of output by displaying only the sites, URLs, or domains, with
at least or at most the defined number you selected.
Note: you may define top for each section of output: url, host, and
domain. For instance, you can define something like:
-minhits url=10 -minhits site=5 -minhits domain=15.
|
|
footprints -key <reg-exp>
-top <#>
|
|
If your output is still too large, then you can narrow the range
of output by displaying only the top "#" of sites or URLs.
Note: you may define top for each section of output: url, host, and
domain. For instance, you can define something like:
-top url=10 -top site=5 -top domain=15.
|
|
footprints -key <reg-exp>
-nofootprints {blank, "all", "site", or "url"}
|
|
If you don't want all the possible trace of footprints, you can define
which set footprints that you do NOT want to calculate and display.
Note: a blank definition defaults to all ... you don't want any
footprints.
|
|
footprints -key
<reg-exp> -noerrors {blank, "all", "site", or "url"}
|
|
If you don't want all the possible trace of HTTP error
footprints, you can define which set of error footprints that
you do NOT want to calculate and display.
Note: a blank definition defaults to all ... you don't want any
error footprints.
|
|
footprints -key <reg-exp>
{-today, -yesterday, -tomorrow}
|
|
To compile statistics on just today or yesterday, or tomorrow. :-)
|
|
footprints -key <reg-exp>
-start <start date> -stop <stop date>
|
|
To compile statistics on a certain date range.
Date can be defined as follows: where month is the abbreviated word.
- d/Mon/yy (?)
- dd/Mon/yy
- d/Mon/yyyy (?)
- dd/Mon/yyyy
Note: it is not necessary to have both start and stop defined. You
may simply use one or the other.
|
|
WARNING: defining start/stop periods will have
discrepancies since the time order of some logging is imperfect.
Note, however, that the amount of error for the start time is
equivalent to the amount of error for the stop time. This can be viewed
two ways: they can cancel each other out, our your getting twice
the error. How painful!
|
|
