DX Application Performance Management

Expand all | Collapse all

Query related Camel Field pack

Jump to Best Answer
  • 1.  Query related Camel Field pack

    Posted 02-09-2018 12:12 PM
      |   view attached

    Hi Team,

    We are using camel field pack in one the application we are monitoring. We are getting two of  blame point metrics name as accumulated route net processing time (ms) and average net process time (ms) under the Splitter component in the APM console but  we are not sure what exactly they signify and what’s difference between the two. Did not find the definition of the above two blame point metrics in docops.ca.com as well.

    I will be more than happy if you can share any document which explains the definition of the blame point metrics of camel field pack.

     

    Attaching the Screen grab from APM console for your reference.

     

    Cheers

    Jay

    Cell No:551-263-9681

    Attachment(s)

    docx
    Camel Fieldpack.docx   26K 1 version


  • 2.  Re: Query related Camel Field pack
    Best Answer

    Posted 02-09-2018 04:42 PM

    Hello Jay,

     

    I found this internally on the two metrics...

     

    The Accumulated Route Net Processing Time (ms) is the accumulated processing time of a processor on a per Thread level for a route.

     

    The Average Net Process Time (ms) reports the net processing time for every single requests on a per route level.



  • 3.  Re: Query related Camel Field pack

    Posted 02-12-2018 04:03 PM

    Hi Thomas,

    Thanks a ton for this response.

    Will it be possible for you to share any document which explains the definition of the blame point metrics of camel field pack?

     

    Cheers

    Jay

    Cell No:551-263-9681



  • 4.  Re: Query related Camel Field pack

    Posted 02-28-2018 11:07 AM

    Sorry for the late reply. I haven't found a way to link the read me directly, but here are our descriptions for each metric...

    Usage metrics

    Processors inside a route are mostly executed in sequence in nested calls. One Processor executes its task and straight invokes the next Process in the route. The Problem here is that the response times of many Processors include the response time of another processor. As described above, e.g. the response time of the BeanProcessor includes the Response Time of the Logging Processor and the Response Time of the Logging Processor would in the same way include the response time of the ExternalProcessExecutor.

    Net Time Reporting and calculation

    The net time for each Processor is calculated individually for each Internal Processor (org.apache.camel.processor.CamelInternalProcessor) execution in the Camel framework.

    • Accumulated Route Net Processing Time %: A route can be executed across multiple threads. As described above, the Processes are the execution steps of a route. The metric Accumulated Route Net Processing Time % compares the individual response time of the Processor with the response time of the route in the actual Thread. Using the Accumulated Route Net Processing Time % you can identify the most time consuming components in average of a route in percent. Important here is that multiple requests to a Processor * per thread * are combined.
    • Accumulated Route Net Processing Time (ms): in the same fashion as the Accumulated Route Net Processing Time %, the Accumulated Route Net Processing Time (ms) is the accumulated processing time of a processor on a * per thread * level for a route. Using the Accumulated Route Net Processing Time (ms) you can identify the total time it took for the Processor working on a Route in milliseconds.
    • Average Net Process Time (ms): While the accumulated times above use the total processing time inside a thread across multiple invocations, the Average Net Process Time (ms) reports the net processing time for every single requests on a * per route level *. Using the Average Net Process Time (ms) you can identify long running Processors and by comparing it with the Average Net Process Time (ms) you are able to see the time difference between Processors which are executed very frequently and are taking a large accumulated time and Processors where individual calls consume a long time.