DX Application Performance Management

 View Only
  • 1.  StalledMethodTracer to signal slow requests not working for me

    Posted Aug 19, 2014 03:36 AM

    Hello,

     

    I setup a StalledMethodTracer (see my previous thread on how to set the nameformatter correctly: https://communities.ca.com/message/241701595#241701595) for certain service methods of the application we are monitoring. The goal is to have a Counter how many request within an interval are slow and how many are very slow.

     

    Thus for testing purposes I set this time to be very low, in order to see the metrics in our testing environment. I also added a MethodTracer to see the timings.

     

    SetTracerClassMapping: SOAPStalledMethodTracer com.wily.introscope.agent.trace.StalledMethodTracer com.wily.introscope.probebuilder.validate.StalledMethodTracerValidator

    SetTracerParameter: SOAPStalledMethodTracer nameformatter [package].nameformatter.soap.SOAPNameFormatter

    SetTracerParameter: SOAPStalledMethodTracer reentrancy instance

    SetTracerClassMapping: SOAPBlamedMethodTimer com.wily.introscope.agent.trace.hc2.MethodTimer com.wily.introscope.probebuilder.validate.MetricNameValidator

    SetTracerParameter: SOAPBlamedMethodTimer nameformatter [package].nameformatter.soap.SOAPNameFormatter

    SetTracerParameter: SOAPBlamedMethodTimer useblame true

     

    TraceComplexMethodsWithThresholdIfFlagged: [FLAG] SOAPStalledMethodTracer "TEST|Frontends|ByService|{Service}:Slow" 10

    TraceComplexMethodsWithThresholdIfFlagged: [FLAG] SOAPStalledMethodTracer "TEST|Frontends|ByService|{Service}:Very Slow" 20

    TraceComplexMethodsIfFlagged: [FLAG] SOAPBlamedMethodTimer "TEST|Frontends|ByService|{Service}:Response Time"

     

    When I run this configuration on our testing environment I nicely see the Response Time per {Service} ({Service} is produced by the nameformatter), but I do not see "Slow" and/or "Very Slow". This had me puzzling as the Response Times are higher (sometimes 100ms) than the set threshold of 10ms / 20ms (please see attached screenshot - I have a perintervalcounter as well that produces "Calls" - I removed that from the configuration above for clarity reasons). Do you have any idea what I do wrong?

    introscope-slowveryslow.png

     

    Edit: After some time I found a Slow and VerySlow metric. So basically my configuration should be correct. I just do not understand why I dont get the metric for all response times that are higher than the threshold. At 09.30 we had a very long response time (~4800ms).

     

    introscope-slowveryslow-2.png

     

    For that I did get a Slow and Very Slow metric:

     

    introscope-slowveryslow-4.png

    But why dont I get the metric for the next peaks for the response time. We see here times of 40 - 80ms in average, which threshold defined as 10ms and 20ms so all of them should also be counted to the slow and very slow metric.

     

    introscope-slowveryslow-3.png

     

    Thank you,

    Stefan



  • 2.  Re: StalledMethodTracer to signal slow requests not working for me

    Posted Sep 30, 2014 03:06 AM

    hm, anybody can help me with this? Do I misinterpret the StalledMethodTracer and my goal is not possible? Do you have any suggestion on where I should go next (support?)

     

    Thank you,

    Stefan