Execution log requests and management
Execution log results are downloaded in a zip file that contains the results of the transaction. The file is retrieved from the BMC Synthetic Transaction Execution Adapter (TEA) Agent and it contains the results of transactions (such as TINIT and TMAIN) in TrueLog files and text files. The execution log results provide deep diagnostics for you to examine issues in the session.
This topic describes the management and contents of execution log requests:
Requests for execution logs
You can request execution logs from the Performance Analysis Session Overview page. For information, see Synthetic-transactions-in-the-Console.
Statuses of execution log requests
You can examine the status of execution log requests on the Execution Logs page.The following table describes information about the execution log requests:
Execution log report
To download and extract a requested execution log
You can download execution logs from the Execution Logs page.
- In the Application Management Console, select the Synthetic tab, and select Execution Logs.
- (Optional) To show only the files ready for download, from the Status column heading, select Complete.
- For the selected execution log request, select Download from the shortcut menu, and save the ZIP file.
- Extract the ZIP file and enter the results-archive password.
The results-archive password is the one you entered during TEA Agent installation.
You can also download execution log files from the Performance Analysis Session Overview page, as described in the Synthetic-transactions-in-the-Console topic.
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 a TrueLog (.xlg) file, that is viewable with the Silk TrueLog Explorer, and depending on the script definitions, it may contain other files such as .wrt files. The TrueLog Explorer is included with the software that you downloaded for the Borland Silk Performer Synthetic Transaction Monitoring for BMC Software.
The zip file also contains a summary file, transaction_result.txt, that comprises a summary of the transaction results.
To delete an execution log request
As space requires, execution logs are automatically removed from the request list. You can manually delete execution logs or abort requests that are in progress.
To perform this procedure, you must have Administrator-level access, or higher, or have tenant Application Owner-level access.
- In the Application Management Console, select the Synthetic tab, and select Execution Logs.
- For the selected execution log request, select Delete from the shortcut menu.
- To confirm the deletion, select OK.
To preserve an execution log, ensure that you keep a downloaded copy on a local computer.