Re: Identify areas in Sling where important metrics can be captured (SLING-5410)

Thanks for the feedback. Updated the SLING-5410 with suggestions above. Would followup with linked task and patches Chetan Mehrotra On Fri, Jan 8, 2016 at 12:37 AM, Michael Marth wrote: > With the same caveat (“just an ad hoc dream list”): > > - event creation/consumption

Re: Identify areas in Sling where important metrics can be captured (SLING-5410)

With the same caveat (“just an ad hoc dream list”): - event creation/consumption count/duration - Sling (servlet) filter processing duration In a nutshell any useful information that can help to debug issues like “my system/my request is slow” or like “my system seems overloaded”. Michael

Identify areas in Sling where important metrics can be captured (SLING-5410)

Hi Team, Now with work on new Metrics API (SLING-4080) nearing completion we can think about next step. Which is to identify those areas in core Sling processing code path where important metrics can be collected. Do share your thoughts here or at SLING-5410! Chetan Mehrotra