How to Streamline Transaction Time Analysis in CA SiteMinder?

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

Description:

I have used TEC487823 and TEC487843 along with the respective guides to get the tracing needed to track requests. Through them I know the TransactionID of the Web Agent Trace appears in the Profiler Data field as "Attribute 221".

I am trying to determine the time taken per request but am having difficulty following the threads. How can I streamline my transaction time analysis?

Reference KBs:
https://support.ca.com/irj/portal/anonymous/redirArticles?reqPage=search&searchID=TEC487823
https://support.ca.com/irj/portal/anonymous/redirArticles?reqPage=search&searchID=TEC487843

Solution:

While CA does not provide any tools for analysis we can certainly assist in streamlining this by giving an outline of a solid method to analyze times. We can also let you know what to look for in order to analyze the time taken.

The following uses the Date, (Precise)Time, Pid Tid and Message fields.

The first part is the same for both Web Agent and Profiler logs.

  1. find where you have the each field.

  2. Create a "map" file of this.

  3. Create separate files for each Process (Pid field)/Thread (Tid field) combination.

The next part changes for Web Agents and Profilers.

For Web Agents:

  1. Read the "map" file.

Start a loop

  1. Read in process/thread file.

  2. Find "Start new request."; remember the date/time of this line.

  3. Find ", end new request."; remember the date/time of this line.

  4. Find the difference between the two lines.

  5. Note the process/thread/time difference.

End the loop

For Profilers:

1: Read the "map" file.

Start a loop

  1. Read in process/thread file.

  2. Find "Enter function CServer::ProcessRequest"; remember the date/time of this line.

  3. Find "Leave function CServer::ProcessRequest"; remember the date/time of this line.

  4. Find the difference between the two lines.

  5. Note the process/thread/time difference.

End the loop

Using the print out of the items from step 5 you get the time difference and process/thread file to read to get further information.

Note, the Components used are the full set of: Server, IsProtected, Login_Logout, IsAuthorized.