Ways to Contain/Control Transaction Traces.

Document ID : KB000010688
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

 One common issue that can impact agent/cluster performance is too many transaction traces. The following are some ways to control transaction traces. This will help control the number of transaction traces until a root cause for excessive traces is determined. Note that could be due to new Agent features being enabled by default.  

Background:

  This was created at APM Engineering's suggestion.

Environment:
All supported APM 10.x releases.
Instructions:

Some of the things to try are the following:

1. Disabling cross process trace 

Do the following to turn off automatic cross-process trace feature in the introscopeAgent.profile.  Changes to this property do not require the managed application to be restarted. Note that Smart Instrumentation can still be kept on.

     introscope.agent.deep.automatic.trace.crossprocess.enabled=false

2. Disabling tail filter 

   This can be done temporarily with the following agent settings.  You must restart the managed application to have this property take effect.

     introscope.agent.transactiontracer.tailfilterPropagate.enable=false

3. Disabling the error snapshot.  

 The property introscope.agent.errorsnapshots.enable must be set to true to enable the agent to capture error data. By default, the agent is enabled to capture error data.

Or consider setting the introscope.agent.errorsnapshots.throttle property to zero or a low number. This property specifies the maximum number of error snapshots that the agent can send in a 15-second period.

 

Additional Information: