Method trimming and stack traces (agent for Java)

BMC Application Diagnostics Agent for Java uses the following techniques to determine which methods to display:

Trimming

Trimming is a process that results in smaller call trees, more focused error isolation, and a reduction in resource usage (including CPU, memory, and outbound bandwidth on the agent side, and inbound bandwidth and data-handling on the BMC Application Diagnostics Collector and Portal side). Trimming occurs during recording. Method request trees in the code section are trimmed by default, meaning that they contain only branches ending with an "interesting" method. A method is "interesting" when at least one of the following criteria applies:

  • The method's duration is longer than the trimming.threshold property configured in the agent policy file.
  • The method resulted in an error (exception).
  • The method is located on a branch that took more time than expected.
  • The method is an exit point.

Any methods that lead to an interesting method are also shown.

You configure trimming, and turn it on and off, through the agent policy file. To turn it on and off, you use the use.runtime.trimming property.

Stack traces for exceeded thresholds

The BMC Application Diagnostics agent displays the following types of methods:

  • Methods that are recognized as interesting before they are invoked. Detailed information is captured and displayed for these methods, according to policy level and recording rules. See Administering-BMC-Application-Diagnostics-Agent-policy-files and consult with BMC Application Diagnostics Customer Support to configure BMC Application Diagnostics recording settings.
  • Methods that exceed a defined threshold. The BMC Application Diagnostics Agent for Java did not recognize these methods as interesting before they were invoked. Such methods are captured as part of stacks leading to service-level agreement (SLA) breaches. No details are captured for these methods.

    If the instance has latency violations, the full stack trace is shown by default. You can hide the stack trace by clearing Show stack trace for exceeded thresholds check box.

Related Topics

Modifying-an-agent-policy-file

Configuring-stack-traces-for-exceeded-thresholds-agent-for-Java

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*