TEC597762: A simple explanation for "Transaction trace component limit"

Document created by SamCreek Employee on May 26, 2016Last modified by SamCreek Employee on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC597762

Last Modified Date:  8/23/2013

 

  • Products
    • CA Application Performance Management
    • CA Introscope
  • Releases
    • CA Application Performance Management:Release:9.1.1
  • Components
    • WILY INTROSCOPE
    • INTROSCOPE AGENT
    • APM AGENTS

 

 

 

Description:

In an em.log or similar APM log, what does this mean, in simple terms?

[WARN] [IntroscopeAgent.WilyTransactionStructure]
Transaction trace component limit of 5000 reached, recording of any new components will cease for this transaction.

Solution:

The transaction trace limit is 5000 by default, and it just means that recording of events will be stopped until the limit is increased. It basically refers to trace entries.

A common way to get around this, is to increase the transaction trace limit, to allow for more debugging and other troubleshooting, but such should not be used long-term until the actual cause of excessive tracing has been determined.

 

 

 

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

Attachments

    Outcomes