Setting execution log retention levels

Execution logs contain the details of executions of scripts run by the Synthetic TEA Agent. When problems occur in your applications, execution logs can provide valuable details about what happened.

Execution logs are stored on the TEA Agent file system. By default, 15 execution log files for each Execution Plan are retained (see the procedure for setting up an Execution Plan in Editing an application's synthetic settings for details about when execution logs are saved). Dowloaded execution logs are stored on the App Visibility portal server. By default, the maximum total volume of execution logs stored on the server is 2 GB. The oldest execution logs are always deleted every 24 hours, to keep the total volume below this threshold. You can modify these numbers as follows:

To modify the number of execution logs saved on the TEA Agent

Note

Before changing this value, make sure you have sufficient disk space available on the TEA Agent computer.

  1. On the computer where the TEA Agent is installed, from the installation directory, open \TEAAgent\WorkingFolder\Conf\agent_configuration.xml.
  2. Set the <ArchiveRollingMax> parameter to the number of execution logs that you want to be retained on the TEA Agent computer.

    Example
     <ArchiveRollingMax>15</ArchiveRollingMax>
    • Default: 15
    • Minimum: 1
    • Maximum: 5000
  3. Save the file, and restart the TEA Agent.

To modify App Visibility portal execution log retention levels

Note

Downloaded execution logs are stored in the App Visibility portal database. Before changing these values, make sure your database has sufficient space allocated to accommodate the increased execution log volume.

  1. On the computer where the App Visibility portal server is installed, from the installation directory, open \portal\properties\portal.properties.
  2. Set the values of the following parameters.

    ParameterDescriptionDefault
    execution.log.retention.task.period.hours
    Frequency (in hours) of the cleanup task that erases old execution logs in excess of the allocated capacity24
    execution.log.db.max.capacity.mb
    Maximum capacity (in MB) allocated to execution logs in the App Visibility database2000
  3. Save the file and restart the App Visibility portal.

Related topic

Requesting and managing execution logs



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

Comments