Would it be better to have an option to record traffic for the last 'x minutes/seconds/hours' configurable on a per handler basis? The goal is to have hooks for nagios/cacti/etc to be able to pull live status info for monitoring purposes. If you want fine grained performance history then log files are the best approach, I just think a way to have beepers go off if a server starts getting huge amounts of traffic is a good thing.
For the record nagios and/or cacti could both keep track of 'in the last x' type of statistics based on totals but having solr compute that automatically would be nice. - will -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley Sent: Tuesday, June 19, 2007 10:27 AM To: solr-dev@lucene.apache.org Subject: requestsPerSecond, averageResponseTime requestsPerSecond and averageResponseTime were added to statistics for each response handler. Are these statistics really useful enough to keep as-is? averageResponseTime is cumulative since the server started, so it's not useful for monitoring purposes, but only benchmarking purposes (it won't tell you if your queries are getting slower all of a sudden). (it will also count slower warming queries, not just live queries). requestsPerSecond is likewise flawed... it won't let you detect a flood of traffic or a dropoff. Also, if you turned off traffic to the server yesterday, that will continue to be reflected in the requestsPerSecond today. Since it seems like these parameters are only useful for benchmarking (which can easily be done from log files), perhaps we should defer adding them until we can come up with versions that are useful for monitoring? -Yonik
