UVMS stores items in a database. These items must be purged regularly to avoid problems with disk space and performance.
For UVMS to work in correctly, the number of alerts in UVMS should be inferior to 100,000. So the purge criteria in UVMS and the alert rule should be defined accordingly.
|
Variable / Label |
Description |
|
|---|---|---|
|
Database purge cycle (hours) GLOBAL_PURGE_CYCLE |
S |
(in hours) |
|
Start time of the first global purge after UVMS startup GLOBAL_PURGE_START_TIME |
S |
HH:MM. Start time of purge of all items and alerts. |
|
Audit Trail Retention Cycle (days) AUDIT_TRAIL_ENTRIES_RETENTION |
D |
All actions performed in UVMS (UVC and command line interface) are archived in the Audit Trail. This variable indicates the number of days the archive will kept. |
|
Roles cache retention cycle (minutes) ROLE_CACHE_CLEANUP_INTERVAL |
S |
A UVMS thread stores the role cache and empty it every minute. If no security change is done, this cache can be increased to avoid unnecessary requests from UVMS. 1 minute by default |
|
Alert Retention Cycle (days) JOB_ALERT_RETENTION_CYCLE |
D |
The default value is 14 days. |
In UVMS logs, there is one entry when the purge is triggered and another with the result of the purge.