Requesting and managing execution logs


Execution log results provide deep diagnostics for you to examine issues in the session. Execution log results are downloaded in a zip file that contains the results of the transaction. The file is retrieved from the Synthetic Transaction Execution Adapter (TEA) Agent and it contains the results of transactions (such as TINIT and TMAIN) in execution log files and text files. 


This topic describes the management and contents of execution logs: 

To request an execution log

  1. Do one of the following:

    • From the Applications View, drill down into the Synthetic tier, through the Locations view, to the Executions view. 

    • From the Synthetic Health view, drill down to the Analysis view and select the Executions tab or Violations tab.
  2. From the action menu for a specific entry, select Download Execution Log.

  3. When the download is complete, extract the ZIP file and enter the results-archive password.
    The results-archive password is the one you entered during TEA Agent installation .

    Note

     The file name of the results archive is the time and date of execution in UTC time.

Execution log contents

An execution log contains the results of a transaction, sent in a zip file from the Synthetic TEA Agent. The zip file contains an execution log (.tlz, or, .xlg) file, that is viewable with Silk TrueLog Explorer, and depending on the script definitions, it may contain other files such as .wrt files. Silk TrueLog Explorer is included with the software that you downloaded for Micro Focus Silk Performer for TrueSight Synthetic.

Notes

  • You must have Silk TrueLog Explorer with Silk Performer installed on the computer from which you want to open and view the execution log file.
  • Transaction names cannot be longer than 40 characters. Any transaction names that are longer than 40 characters are truncated.

The zip file also contains a summary file, transaction_result.txt, that comprises a summary of the transaction results.

To preserve an execution log, ensure that you keep a downloaded copy on a local computer.

Related topics

Monitoring synthetic transactions by execution

Monitoring synthetic transactions to predict application health

Setting execution log retention levels

Setting the files included in an execution log

Editing an application's synthetic settings

Analyzing a synthetic transaction 

 
 

Was this page helpful? Yes No Submitting... Thank you

Comments