Skip to main content

Data Purge

Data Purge

There is a possibility to delete completed run after a period of days. Here are the CS Configuration parameters that configure this job:

Parameter name

Parameter type

Default value

Scope

Description 

data_purge_keep_days number >= 090CS

The maximum number of days to keep data. 

Elasticsearch is configured to keep indexes no more that 125 day.

data_purge_purge_interval_daysnumber >= 11CSThe period in days to perform data purge (i.e. purge data every N days and remove all runs that older data_purge_keep_days). The data_purge_purge_interval_days must be < data_purge_keep_days 
data_purge_connection_timeout_minnumber > 110CSConnection timeout for HTTP request in minutes. Depends on data purge size. Should be increased if DataPurge logs contains timeout errors.

The system job runs every data_purge_purge_interval_days at midnight and removes all:

  • runs
  • logs
  • activity logs

that created older than data_purge_keep_days ago.

Data Purge logs

To audit the data purge job log files, use one of the search filter:

  • thread:"DataPurge-1"
  • logger:"eu.ibagroup.easyrpa.cs.service.datapurge.DataPurgeServiceImpl"

Metrics Data Purge

Metrics are stored in InfluxDB, and data is purge via retention policy. By default it is 90 days.

You can change it. For this you need login into InfluxDB administrator console and update retention policy for easyrpa bucket.

Application server post-installation

System

Access Type

Access URL

User name

Password

InfluxDBPublichttps://<app_server_host>:8446/admin$INFLUXDB_ADMIN_PASSWORD