Transaction call chains

Identify and debug the root causes for a problematic transaction by recording, and then reviewing, its call chain. A call chain consists of the ordered series of scripts executed during the life cycle of a transaction.

Transaction Call Chain tracking enables an administrator to register the URL of a problematic transaction for recording of the call chain during the next URL occurrence. It is helpful for diagnosing transaction performance issues.

To enable transaction call chain tracking, perform the following tasks:

1. When you find a problematic transaction on the Transaction Log or Slow Transaction list that requires debugging, select it to view its detail record. To aid in debugging, filter and group these lists by application scope, limiting transactions that appear to only those transactions originating in specific scopes.
   Note:

   To learn more about these lists, see Transaction logs and Slow transactions log record detail.
2. In the record detail form, click Record call chain of next occurrence, located under Related Links.
   • It designates that the next occurrence of the transaction URL should be persisted with all of its call chain information.
   • You can optionally designate a user ID so call chain recording only takes place during the next transaction occurrence for a specific user.

     

3. The next time a user accesses the URL, the Transaction Call Chain Register record is updated to contain a listing of the script resources executed to service the request.
4. In Transaction Call Chains, review the recorded call chain for the transaction, and then take needed the actions required to debug it.