stats, stats, stats ;)

ts77

Well-Known Member
#1
Hi there,

maybe I missed it but how about:
- total requests delivered
- total traffic delivered
- max used connections (I want to know how near I got to the border ;))
- average traffic / requests since start

and what about a nice rrdtool-module like lighttpd has?
it can give you a quick overview how the load is spread throughout the day / week.

just some ideas.


thomas
 

mistwang

LiteSpeed Staff
#2
Thomas,

Thank you for the suggestions.

We plan to integrate with cacti for history stats, just like we did for awstats. Actually, one of user has done that already. In this way you could monitor multiple servers in one place and dump MRTG. ;-)

We did not include total requests and bandwidth delivered because those could get overflowed quickly, and AWstats access statistics is the better place to look at. The max used connections is useful and you can get it from the history graph when it is available. Our take is that long term stats should be in the history stats but not in the real time stats.

What do you think? :)

George
 

ts77

Well-Known Member
#3
Cacti sounds like a good solution. I used it in the past but dumped it for rrd.
Using it with multiple servers makes sense for using it again :).

We did not include total requests and bandwidth delivered because those could get overflowed quickly, and AWstats access statistics is the better place to look at.
Hmm, awstats doesn't have accumulated stats for all hosts together.
I guess you can easily work around the overflow problem ;) ... i.e. rounded numbers in MB or GB if the numbers get too large.
Its not essential just a "nice to have".


thanks,

thomas
 
Top