POJO Method Tracing Limit and Cutoff Time (Sec)
These parameters will appear only if the advanced settings flag is set to ‘true’. Typically, if the monitoring mode of this test is set to Profiler , then, as part of the detailed diagnostics of a transaction, eG reports the execution time of every POJO, non-POJO, and recursive (i.e. methods that call themselves) method call that a JVM node makes when processing that transaction. Of these, POJO method calls are the most expensive, as they are usually large in number. To ensure that attempts made to collect detailed measures related to POJO method calls do not impact the overall responsiveness of the monitored transaction, eG, by default, collects and reports the execution time of only the following POJO method calls:
- The first 1000 POJO method calls made by the target JVM node for that transaction; (OR)
- The POJO method calls that were made by the target JVM node within 10 seconds from the start of the monitored transaction on that node;
Accordingly, the pojo method tracing limit is set to 1000 by default, and the pojo method tracing cutoff time is set to 10 (seconds) by default. Of these two limits, whichever limit is reached first will automatically be applied by eG for determining when to stop POJO tracing. In other words, once a JVM node starts processing a transaction, the agent begins tracking the POJO method calls made by that node for that transaction. In the process, if the agent finds that the configured tracing limit is reached before the tracing cutoff time is reached, then the agent will stop tracking the POJO method calls, as soon as the tracing limit is reached. On the other hand, if the tracing limit is not reached, then the agent will continue tracking the POJO method calls until the tracing cutoff time is reached. At the end of the cutoff time, the agent will stop tracking the POJO method calls. For instance, if the JVM node makes 1000 POJO method calls within say, 6 seconds from when it began processing the transaction, then the eG agent will not wait for the cutoff time of 10 seconds to be reached; instead, it will stop tracing at the end of the thousandth POJO method call, and report the execution time of each of the 1000 calls alone. On the other hand, if the JVM node does not make over 1000 POJO method calls till the 10 second cutoff expires, then the eG agent continues tracking the POJO method calls till the end of 10 seconds, and reports the details of all those that were calls made till the cutoff time.
Depending upon how many POJO calls you want to trace and how much overhead you want to impose on the agent and on the transaction, you can increase / decrease the pojo method tracing limit and pojo method tracing cutoff time specifications.