---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Alert table clean up

# Alert table clean up {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The Scheduled Jobs feature runs a script to automatically close alerts in the Alerts \[em_alert\] table that meet specific conditions, helping reduce alert noise and keep the system clean and efficient.

## Vorbereitungen

Role required: evt_mgmt_admin

## Warum und wann dieser Vorgang ausgeführt wird

When the Event Management plugin is activated, by default a job is scheduled to run the <kbd class="ph userinput">Event Management - auto close alerts</kbd> script to automatically close alerts in the alerts table that meet the specified
conditions. The default retention policy for closed alerts is that the system deletes closed alerts if it is not updated for 90 days. For more information on the scheduled job, see [Table cleaner](https://www.servicenow.com/docs/access?context=table-cleaner&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

Due to the high level of traffic to the table, you cannot audit the Alert table \[em_alert\] as a whole. Instead, audit selected fields of interest on the table.

## Prozedur

1. Set the table to `audit = true`.
2. Set `audit = true` on the relevant fields.  
   To avoid an excess of audit records, audit only the fields that are necessary for auditing.
{#auto-close-alerts__steps_pkm_4ww_gyb}

## Ergebnisse

The <kbd class="ph userinput">Event Management - auto close alerts</kbd> script runs automatically and repeatedly at the scheduled time and closes alerts that meet the specified conditions.
**Zugehörige Konzepte**   

* [Rotate event and alert table for cleanup](https://servicenow-prod.fluidtopics.net/b8lLtn~GNmcupBsJpyT4Ww "The growth of data tables impedes performance. Preserve instance performance by event table rotation and alert table cleanup for status and alert history retention.")  
**Zugehörige Tasks**   

* [Modify event table rotation](https://servicenow-prod.fluidtopics.net/6yAyTVgk7GPwKHNAMGyqhA "Table rotation is used by Event Management, by default, to contain the growth of event [em_event] tables within the rotation table group.")
* [Purge impact status and alert history](https://servicenow-prod.fluidtopics.net/Q5LUIKm7P_GRNY0kpKF8Mw "Automatically cleans up outdated impact statuses and alert history from the database to free up space, improve system performance, and ensure only relevant data is retained.")