Lifecycle Expiration Health Check

This health check is only applicable if you have enabled the Lifecycle Expiration feature on your ARTESCA cluster.

The goal of this health check is to ensure that the Lifecycle Expiration feature is functioning properly. By proceeding to this proactive monitoring, you can prevent issues such as the management and deletion of expired data.

To perform the lifecycle expiration health check, use the following workflows:

1. Checking Alerts

2. Monitoring the Kafka Dashboard

3. Monitoring the Lifecycle Dashboard

Checking Alerts

In the ARTESCA UI, open the Alerts menu. A healthy system does not have any Critical Alerts or Warnings. If you only see the watchdog notification, your system is in a good state.

For more information on alerts, refer to Alert Management.

Monitoring the Kafka Dashboard

To access the Kafka Dashboard, refer to Kafka Monitoring.

1. Look at the Messages In Per Topic dashboard to check the rate of the objects being pushed.

   

   • Messages flowing into the {ZENKO_ID}.backbeat-lifecycle-bucket-tasks topic mean that the conductor is detecting buckets with Lifecycle enabled and ordering for a scan, or that the bucket processor is scanning a large bucket.

   • Messages flowing into the {ZENKO_ID}.backbeat-lifecycle-object-tasks topic mean that the bucket processor is detecting expired objects and asking for them to be deleted.

   Tip

   You can filter topics by checking the box next to the ones you want to see. In the case of Lifecycle Expiration, select the two topics respectively ending with backbeat-lifecycle-bucket-tasks and backbeat-lifecycle-object-tasks.

   

2. Look at the Max lag in messages dashboard to check the rate of message consumption for the two topics.

   

   The lag on both topics is supposed to be low and converge to zero in normal cases.

   Tip

   You can filter consumer groups by checking the box next to the ones you want to see. In the case of Lifecycle Expiration, select the two groups respectively ending with backbeat-lifecycle-bucket-processor-group and backbeat-lifecycle-object-processor-group.

   

3. Compare the rate of the objects being pushed with the rate of message consumption. These are supposed to match the number of buckets and their respective objects, and the rules set up during the Lifecycle Expiration workflow creation.

Monitoring the Lifecycle Dashboard

Check the object deletion rate and performance.