Perf4J does expose a JMX monitoring system if you so desire: http://perf4j.codehaus.org/devguide.html#Exposing_Performance_Statistics_as_JMX_Attributes
(note: I'm not saying don't find an alternative, I'm saying Perf4J at the top was a proper abstraction for what you just asked for) On Fri, Jan 30, 2015 at 3:41 AM, Jérôme LELEU <lel...@gmail.com> wrote: > Hi, > > I've heard a few times that there were performance issues with log4j v1, > but I didn't encounter any even on pretty high loaded systems. > > It makes sense to move to log4j v2 as log4j v1 won't evolve any more: it's > more to reduce our technical debt than to get better performance, because I > think we would need some rewrite to take advantage of the disruptor > architecture of log4j v2 (async logs). > logback is a great candidate too. > > Fore sure, perf4j is dead and should be removed. > I'm not sure that the CAS server should really proposed a limited > monitoring and graphics system as we currently do, I would go more for an > easily extendable plugin monitoring system as there are some many ways to > monitor applications and CAS deployers should already have their own > monitoring system in their own infrastructure. Maybe we should have an > optional JMX monitoring support. > > Best regards, > > > > > > > Jérôme LELEU > Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj > Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org > > 2015-01-29 19:23 GMT+01:00 Misagh Moayyed <mmoay...@unicon.net>: > >> Team, >> >> I have been looking at and reading a lot about log4j v2 and almost all >> feedback and reviews have been positive, especially in terms of >> performance. I have been quietly working on evaluating the effort required >> to get CAS using log4j v2 and with the little that I have done, all has >> been going well, except one roadblock and that is perf4j. This is the >> component/dependency that outputs perf data on various CASImpl functions >> and collects the stats later on to present to the web layer as a graph. The >> problem is, the module is very much outdated and the graph/stats >> functionality is tied to log4j v1. So with that context, here are my >> questions: >> >> >> >> 1. How do folks generally feel about upgrading to log4j v2? >> >> 2. Would anyone be offended if we removed perf4j and substituted >> it with something that is better maintained and more recent, both in terms >> of gathering stats as well the ability to visually represent them? >> >> 3. …or, maybe not even provide that functionality any more as its >> seem to be somewhat dormant? >> >> >> >> Regards, >> >> >> >> - Misagh >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> >> > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
