If you want to minimize the impact of recording the measurement I disagree.
The last time I looked at jamon recording a measurement was synchronized, so recording a measurement in a multithreaded environment was serialized an impacts your scalability. Also seeing the measurement distribution is very valuable and not possible with jamon. Spf4j Implements similar functionality with llquantize in DTrace. http://dtrace.org/blogs/bmc/2011/02/08/llquantize/ There are however other thing that jamon does better... --z On Feb 12, 2013, at 4:40 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > jamon or the more recent javasimon, moskito (even if not completely written > and buggy)... are better candidates IMO > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/2/12 Zoltan Farkas <zolyfar...@yahoo.com> > >> Worth taking a look at: >> >> code.google.com/p/spf4j >> >> >> --z >> >> On Feb 12, 2013, at 4:05 PM, Romain Manni-Bucau <rmannibu...@gmail.com> >> wrote: >> >>> well not enough time right now but i hope in some weeks >>> >>> the idea would be to get: >>> -> something to measure (i think it is already here) >>> -> some basic aop (abstraction, spring, cdi?) >>> -> some basic view of the measures (servlet or even a bootstrap webapp ;) >>> with sortable tables...) >>> -> some basic module for what metrics calls HealthCheck (checks the state >>> of a resource like a datasource) >>> >>> wdyt? >>> >>> *Romain Manni-Bucau* >>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >>> *Blog: **http://rmannibucau.wordpress.com/*< >> http://rmannibucau.wordpress.com/> >>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >>> *Github: https://github.com/rmannibucau* >>> >>> >>> >>> 2013/2/12 Olivier Lamy <ol...@apache.org> >>> >>>> 2013/2/11 Romain Manni-Bucau <rmannibu...@gmail.com>: >>>>> Hi guys, >>>>> >>>>> is there any activity (or plans) on commons monitoring? >>>> IMHO nothing :-) >>>>> >>>>> it seems pretty old and a lot of work should be done, i would like to >>>> know >>>>> if it is a project to make alive or not >>>> If you want to contribute why not. As the idea sounds interesting I >>>> can work a bit with you on. >>>> >>>>> >>>>> thanks >>>>> >>>>> *Romain Manni-Bucau* >>>>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >>>>> *Blog: **http://rmannibucau.wordpress.com/*< >>>> http://rmannibucau.wordpress.com/> >>>>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >>>>> *Github: https://github.com/rmannibucau* >>>> >>>> >>>> >>>> -- >>>> Olivier Lamy >>>> Talend: http://coders.talend.com >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >>
