Steve, These are good suggestions, especially reporting totals and counts.
I think that there are good ways to report moving max and quantiles as well without keeping gobs of state, but just getting period averages right would be pretty cool. On Fri, Aug 12, 2011 at 11:14 AM, Steve Francis <[email protected]>wrote: > Hi > > I just wrote ZooKeeper monitoring for the SaaS monitoring company I > work for, at the request of one of our customers (sales-y brief view > of the ZooKeeper monitoring at > > http://www.logicmonitor.com/monitoring/applications/java-monitoring/zookeeper-monitoring/ > ). > (Feel free to contact me directly if anyone is interested in anything > specific.) > > I have a few suggestions as to how the exposed JMX objects could be > improved; > - instead of reporting average and max latency, which, so far as I can > tell from the source code, seems to be since server start (or the > Mbean to reset the stats is triggered), do the same as Tomcat, and > other projects: i.e. report the total processing time as one counter, > and also report the total number of requests processed. > Then if you want to calculate the average latency since server start, > it's easy, but more interesting its also easy to calculate the average > latency for any time period (such as the last minute - sample total > requests and latency at start and end of minute, subtract, divide, and > there you go.) This lets you graph and alert on latencies in a > meaningful way. >
