Analytics Dashboard historical data re-sync; Automic Automation Engine

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

This article describes how to force the Automic Analytics collector to re-sync historical execution data (Activity History) from the Automation Engine database. This is required when historical data was missing during the initial collection or after an ILM recovery where execution history was repopulated.

Environment

• Automic Automation Engine 24.x
• Automic Analytics Backend

Cause

The Analytics collector uses the latest timestamp in the Postgres database to determine where to start collecting. If historical data is inserted into the Automation Engine database after the collector has already passed that date, the collector will not automatically pick up the older records.

Resolution

To force a re-collection of historical data, follow these steps:

1. Stop the Analytics Backend service.
2. Perform a backup of the PostgreSQL Analytics database.
3. Connect to the PostgreSQL database and truncate the following tables to reset the watermark:
   sql

   TRUNCATE TABLE AH;
   TRUNCATE TABLE AH_CLEANED;
   TRUNCATE TABLE AH_ENRICHER;

4. Navigate to the Analytics backend configuration file (application.properties).
5. Set or update the following property to define the desired lookback window (e.g., 365 days): collector.ae.initial_collect_before_now_days=365
6. Start the Analytics Backend service.

The collector will now begin re-syncing all data within the specified timeframe. This process may take significant time depending on the volume of data.