Retention of alerts and incidents

The alert and incident retention conditions are determined by the following criteria:

There are no limitations on the size of a stored alert.

Setting the retention period for alerts and incidents

You can change the alert and incident retention period in one of the following ways:

To change the retention period for alerts and incidents in the KUMA web interface:

  1. In the KUMA web interface, go to the Settings → Other → General section.
  2. In the General window, under Core properties, specify the Alert retention period, days.

The retention period for alerts and incidents will be changed.

To change the retention period for alerts and incidents on the command line:

  1. Log in to the OS of the server where the KUMA Core is installed.
  2. In the /usr/lib/systemd/system/kuma-core.service file, edit the following string by inserting the necessary number of days:

    ExecStart=/opt/kaspersky/kuma/kuma core --alerts.retention <retention period for alerts and incidents in days> --external :7220 --internal :7210 --mongo mongodb://localhost:27017> --external :7220 --internal :7210

  3. Restart KUMA by running the following commands in sequence:
    1. systemctl daemon-reload
    2. systemctl restart kuma-core

The retention period for alerts and incidents will be changed.

Alert and incident deletion conditions

KUMA applies the following alert and incident deletion conditions:

The conditions are independent, none of the conditions are mutually exclusive.

Page top