Clean alert history and impact status tables

Schedule jobs to mark and remove old alert records in the Alert History [em_alert_history] and Impact Status [em_impact_status] tables, to prevent the tables from becoming overloaded with data.

Before you begin

Role required: evt_mgmt_admin

About this task

Schedule the following jobs to remove old alert records:

• Backfill: Determines when alerts are to be marked for deletion.
• Clean: Deletes the alerts.

Note: The records in the [em_alert_history] and [em_impact_status] tables are deleted by default after three months. This is controlled by the properties evt_mgmt.impact_calculation.cleanup_age_seconds.em_alert_history and evt_mgmt.impact_calculation.cleanup_age_seconds.em_impact_status. The default value is 7,776,000 seconds (equivalent to 90 days).

Procedure

1. Navigate to All > System Definition > Scheduled Jobs.

   The Scheduled Jobs page appears.

2. To determine how often to mark alerts for deletion on the Impact Status table:

   1. Locate and select the Event Management - Backfill Impact Status Table job.

      The Scheduled Script Execution page appears.

2.  In the **Repeat Interval** field, configure how often you want the job to run.

    To run the job immediately, select **Execute Now**.

3.  Select **Update**.

1. To remove old alerts from the Impact Status table:

   1. Locate and select the Event Management - Clean Impact Status Table job.

      The Scheduled Script Execution page appears.

2.  In the **Repeat Interval** field, configure how often you want the job to run.

    To run the job immediately, select **Execute Now**.

3.  Select **Update**.

1. Repeat steps 2 and 3 to perform the Backfill and Clean jobs on the Alert History Table.

Parent Topic:Purge impact status and alert history