I generally have 2 different approaches. I have taken the dominolog.nsf (and/or the text log files) and exported them to MySQL for reporting. From porting them to MySQL I can use the same weblog analysis tools as you would for an Apache server -- like Webalizer, etc.
The second approach was similar to Jorge, but instead of storing with a Lotus Notes database I would store it to MySQL via a WQO LotusScript agent using LS:DO to insert the row to the table (in Linux you can unixODBC). One of my clients wedj.com has from 10,000 to 20,000 unique visitors a day. The Linux server does not slow down nor does it have any delay in loading. Using a relation back end remove the burden from the NSF file. Plus the server does not have to worry about indexing a huge domlog.nsf for a site such as this.
I generally have 2 different approaches. I have taken the dominolog.nsf (and/or the text log files) and exported them to MySQL for reporting. From porting them to MySQL I can use the same weblog analysis tools as you would for an Apache server -- like Webalizer, etc.
The second approach was similar to Jorge, but instead of storing with a Lotus Notes database I would store it to MySQL via a WQO LotusScript agent using LS:DO to insert the row to the table (in Linux you can unixODBC). One of my clients wedj.com has from 10,000 to 20,000 unique visitors a day. The Linux server does not slow down nor does it have any delay in loading. Using a relation back end remove the burden from the NSF file. Plus the server does not have to worry about indexing a huge domlog.nsf for a site such as this.
HTH