Configuring expiry time for log anomaly alerts

By default, alerts that are generated by a log anomaly expire in six hours (21,600 seconds). You can modify this value.

1. Access the IBM Cloud Pak Administration panel by following the instructions at UI console.
2. In the main navigation menu, click Workloads > Deployments.
3. Search by name, and type log-anomaly in the field. The aimanager-aio-log-anomaly-detector deployment is listed in the table.
4. Click aimanager-aio-log-anomaly-detector to visualize deployment details.
5. Click the Environments tab. A list of environment variables is displayed.
6. From the list, click Add more to add another environment variable.
7. Name the environment variable EXPIRY_SECONDS.
8. Set the value of the EXPIRY_SECONDS environment variable in seconds. For example, if you want to increase the expiry time to 24 hours, which is 86,400 seconds, set the value to 86400.
9. Click Save to save the changes. This action triggers a restart of the aimanager-aio-log-anomaly-detector pod, which takes a few minutes.

After the pod restarts, the new expiry time applies to any alerts that are generated by a log anomaly.