I've been thinking about this kind of thing as well; having a JMX bean for each Page instance and tracking number of render requests, number of event requests, number of ajax even requests, and ellapsed processing time for each.
Obviously, it's a bit late for 5.2 ... it may be time to cut a 5.3 dev branch off the current 5.2 code base. On Sun, Oct 10, 2010 at 2:05 PM, Josh Canfield <joshcanfi...@gmail.com> wrote: > I'm thinking about rolling my own generic monitoring/statistics solution for > tapestry 5 and I figured I should see if something is out there already > before I spent too much time on it. > > This is to be used in production and connected to an external monitoring > system, probably via JMX, but we might be flexible. > > Anything come to mind? > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
