Trim Statistics DB deletes all MOVEit Automation audit records older than a certain number of days, and optionally saves them to tab-separated files.
By default, MOVEit Automation has a pre-installed task that uses this script with parameters set to specific values. If you want to create your own task using this script, note the required parameters.
Input Parameters
\Program Files\MOVEit\MICStats\Logs
. If you do not want system and error logs, set this value to blank. \Program Files\MOVEit\MICStats
. If you do not want deleted records archived to a text file, set this to an empty value..tsv
files older than the specified number of days that are found in "\Program Files\MOVEit\MICStats\Logs
" (or the value of DirLog) are deleted. Deleted files are not put into the Recycle Bin, and cannot be retrieved..tsv
file in the format <table-name>-<archive-date yyyy-mm-dd>.tsv
For example, TaskRuns-2020-06-29.tsv
.tsv
archive file contains specific report information:TaskRuns-<yyyy-mm-dd>.tsv
- task run report dataStats-<yyyy-mm-dd>.tsv
- file/folder activity dataAudit-<yyyy-mm-dd>.tsv
- audit logs of user actions and changes to the Automation configuration.Notes
Use this built-in script as the only step of a task. Process-level per-file or once-after-all-files settings will be ignored.
Over time, the statistics database can accumulate many records, slowing performance and using excessive amounts of disk space. To prevent this, MOVEit Automation is typically configured to run this built-in script periodically, optionally saving them to a file or another database before deletion.
Example #1
Bob has noticed that the various task history dialogs in MOVEit Automation have been sluggish lately and asks Progress for some advice. Progress notices that Bob has more than two hundred tasks that poll FTP servers every five minutes, all day long. Most (98%) of these polls do not yield files, but MOVEit Automation continues to log this information during each poll. Over the course of a single day, this means that more than 55,000 "no xfer" actions are logged to the database. Bob knows that "no xfer" information can be of value in debugging, but Progress would prefer that he remove them after a few days and only retain "success" or "failure" audit entries for long periods of time. Bob and Progress decide to retain one week of "no xfer" records, and to keep 60 days of "success" and "failure" logs in the database. The "no xfer" records will not be saved to the longer term archive logs.
To accomplish this with MOVEit Automation: