Archival Policy

Robility Designer and Runner generate and manage log files locally on the machine where the respective components are installed. To ensure optimal storage usage and maintain a consistent logging strategy, the following archival policy is implemented:

1. Daily Log File Generation and Size Limit

a. Each day, a new log file is generated for Robility Designer and Runner activities.
b. The maximum size of a single log file is capped at 10 MB per day.
c. If the daily log data exceeds this 10 MB threshold, the application will automatically generate an additional log file for the same day to accommodate the overflow.

2. Archive Storage and Purge Policy

a. Archived log files are stored in a designated archive folder on the local machine.
b. A First-In-First-Out (FIFO) purge policy is enforced to manage storage consumption.
c. Under this policy, the oldest archived files are automatically deleted once the folder reaches its retention capacity.

3. Retention Limits

a. The archive folder maintains a maximum of 30 archived log files at any given time.
b. Each archived file is limited to a maximum size of 10 MB.
c. This results in a total potential archive size of up to 300 MB per component (Designer and Runner), stored locally.

To learn about Runner archive settings, click here. 

Important-

1. It is important to note that log files are not uploaded to the Robility Manager as part of the standard archival process.

2. All logging, archiving, and purging operations are managed locally on the system running the Designer or Runner.

3. To view the path where the folders are located, click here.