Delete Job Execution Data as an Administrative Task in the IGEL UMS

You can define an administrative task to delete the results of Jobs. The deletion helps with performance optimization, see Performance Optimizations in IGEL UMS.

For more information on Jobs, see Jobs - Sending Automated Commands to Devices in the IGEL UMS.

Menu path: UMS Administration > Administrative Tasks > Dialog "Create Administrative Task" > Action "Delete job execution data"

General

Name

Name for the task.

Action

→ Select Delete job execution data.

Configuration

Target directory for export files

Directory on the UMS Server in which the logging data are to be backed up before they are deleted from the UMS database. The data will only be deleted from the database if the backup was successful. If you leave the field empty, the directory \rmguiserver\temp will be used. The file name for the logging data is structured as follows: Igel_deleted_job_exec_.csv.

Deletion settings

You can specify here the criteria according to which task protocols are deleted.

• Keep no more than [number] executions per job: Each job has executions. Each execution can have thousands of results. This task deletes all executions and their results except for the specified number of the newest executions. (Default: 10)

• Delete events older than [number] days: Protocols that are older than the number of days specified here will be deleted. (Default: 5)