Causes of Excessive Transaction Traces for Java Agents and how to contain them.
Article ID: 16045
CA Application Performance Management Agent (APM / Wily / Introscope)
This knowledge document was suggested by APM Sustaining Engineering and supplements https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=10688 -- Ways to Contain/Control Transaction Traces.
What are some of the different ways that too many transaction traces can be produced for a Java Agent? If this happens, what short-term measures should be taken?
All Supported APM releases
The common scenarios for too many transaction traces are below as well as suggested short-term measures to control the situation.
- Excessive TTs in backend Agent triggered by upstream sampling. – disable/reduce upstream sampling.
- Excessive TTs triggered by Auto Tracing in 10.x Agents – disable Auto tracing.
- Excessive TTs in backend Agent triggered by upstreaming Auto Tracing – disable Auto tracing CPTT.
- Excessive TTs triggered by ERRORs – disable/reduce Errors produced.
- Excessive TTs in backend Agent triggered by upstream Agent due to tail filter. – disable tail filter propagation.
- Excessive TTs in backend Agent triggered by upstream Agents for unknown reasons – disable HTTP/SOAP/JMS/MQ header insert/read operations.
- Excessive TTs triggered by Field Packs – remove/upgrade Field Pack
- Excessive TTs for unknown reasons – disable global TT.