On 10/24/05, Catalin Trifu <[EMAIL PROTECTED]> wrote:
I'm using awstats along with logrotate to do stats for 10 websites hosted on one server. Every night, logrotate runs (by cron), runs awstats on the access_log file for each site, gzips the log and moves it to another directory for backup. I like awstats because it allows you to have a custom log format and it "understands" virtual hosts. This is nice because I can have one log file for all my sites, in which I just append a VLOG name to a normal combined log format. I have an awstats config file for each site which all read the same file, but only look for their own domain name. I used webalizer for a while, but often had problems that if I processed a log that was in the middle of a day or month, it would not continue properly when it parsed the next log. With awstats, it runs every night and works great with a nice output. I would highly recommed it. Look here: http://awstats.sourceforge.net/docs/awstats_faq.html#ROTATE for info on using awstats with logrotate and look here: http://awstats.sourceforge.net/docs/awstats_compare.html for a comparison between awstats, analog, webalizer, and hitbox. (It is created by awstats though, so it might be a little biased).
HTH,
Preston
Hi,
I'm pretty new to log analyzers. Besides webalizer which got a
little bit old (still usefull nonetheless) i have no other experience.
I've googled and found awstats and analog.
If you would care to comment on this issue I would be grateful for
any hints.
Thanks.
Catalin
--
I'm using awstats along with logrotate to do stats for 10 websites hosted on one server. Every night, logrotate runs (by cron), runs awstats on the access_log file for each site, gzips the log and moves it to another directory for backup. I like awstats because it allows you to have a custom log format and it "understands" virtual hosts. This is nice because I can have one log file for all my sites, in which I just append a VLOG name to a normal combined log format. I have an awstats config file for each site which all read the same file, but only look for their own domain name. I used webalizer for a while, but often had problems that if I processed a log that was in the middle of a day or month, it would not continue properly when it parsed the next log. With awstats, it runs every night and works great with a nice output. I would highly recommed it. Look here: http://awstats.sourceforge.net/docs/awstats_faq.html#ROTATE for info on using awstats with logrotate and look here: http://awstats.sourceforge.net/docs/awstats_compare.html for a comparison between awstats, analog, webalizer, and hitbox. (It is created by awstats though, so it might be a little biased).
HTH,
Preston
