rocessing 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
>> wrote:
>> >&g
On Mon, Oct 11, 2010 at 6:05 PM, Howard Lewis Ship wrote:
> 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.
>
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 Canfi
o cut a 5.3 dev
> branch off the current 5.2 code base.
>
> On Sun, Oct 10, 2010 at 2:05 PM, Josh Canfield 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
&g
cut a 5.3 dev
branch off the current 5.2 code base.
On Sun, Oct 10, 2010 at 2:05 PM, Josh Canfield 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
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
