| 1 |
On 10/24/05, Catalin Trifu <catalin@××××××××××××.de> wrote: |
| 2 |
> |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> I'm pretty new to log analyzers. Besides webalizer which got a |
| 6 |
> little bit old (still usefull nonetheless) i have no other experience. |
| 7 |
> I've googled and found awstats and analog. |
| 8 |
> If you would care to comment on this issue I would be grateful for |
| 9 |
> any hints. |
| 10 |
> |
| 11 |
> Thanks. |
| 12 |
> Catalin |
| 13 |
> |
| 14 |
> -- |
| 15 |
|
| 16 |
|
| 17 |
|
| 18 |
I'm using awstats along with logrotate to do stats for 10 websites hosted on |
| 19 |
one server. Every night, logrotate runs (by cron), runs awstats on the |
| 20 |
access_log file for each site, gzips the log and moves it to another |
| 21 |
directory for backup. I like awstats because it allows you to have a custom |
| 22 |
log format and it "understands" virtual hosts. This is nice because I can |
| 23 |
have one log file for all my sites, in which I just append a VLOG name to a |
| 24 |
normal combined log format. I have an awstats config file for each site |
| 25 |
which all read the same file, but only look for their own domain name. I |
| 26 |
used webalizer for a while, but often had problems that if I processed a log |
| 27 |
that was in the middle of a day or month, it would not continue properly |
| 28 |
when it parsed the next log. With awstats, it runs every night and works |
| 29 |
great with a nice output. I would highly recommed it. Look here: |
| 30 |
http://awstats.sourceforge.net/docs/awstats_faq.html#ROTATE for info on |
| 31 |
using awstats with logrotate and look here: |
| 32 |
http://awstats.sourceforge.net/docs/awstats_compare.html for a comparison |
| 33 |
between awstats, analog, webalizer, and hitbox. (It is created by awstats |
| 34 |
though, so it might be a little biased). |
| 35 |
|
| 36 |
HTH, |
| 37 |
|
| 38 |
Preston |
Archives