Monitor MDM SaaS > Monitoring purge jobs > Monitoring purge entity jobs

Monitoring purge entity jobs

A purge entity job permanently deletes records that belong to a specific business entity or code values of a specific code list, along with their dependencies.

A purge entity job includes the following steps, and you can view the data processing analytics for each step:

•Purge records
•Index for search
•Purge business entity activity report index
•Store cleanup

Purge records

The purge record step permanently deletes records that belong to a specific business entity or code values of a specific code list, along with their dependencies. This step deletes all the data that includes historical data, and data from source systems and relationships.

The following table describes the metrics that you can view for the purge records step:

Metric ID	Description
relationships	Number of relationship records purged.
potential_group	Number of potential match pair groups purged.
xref	Number of source records purged.
indexDeleteFailures	Number of records whose search indexes weren't purged.
matchPairs	Number of match record pairs purged.
changelist	Number of records with changes that were part of approval workflows that were purged.
match-rel	Number of record pairs with relationships purged.
orphanedXrefs	Number of source records that weren't purged.
indexDeletes	Number of records whose search indexes were purged.
businessEntity	Number of master records in the specific business entity that were purged.
indexDeleteNotFound	Number of records with no search indexes that were purged.
potential_group_snapshot	Number of consolidated potential match pair groups purged.

Index for search

The index for search step purges search indexes for the specific business entity records and reindexes the available business entity records based on the search configuration.

The following table describes the metrics that you can view for the index for search step:

Metric ID	Description
SEARCH_INDEX_TOTAL_RECORDS	Total number of records that the step processed.
SEARCH_INDEX_FAILED_RECORDS	Number of records that weren't indexed.
SEARCH_INDEX_SUCCESS_RECORDS	Number of records that are indexed for search requests.
SEARCH_INDEX_UPSERT_SUCCESS	Number of records for which the search indexes are added or updated.
SEARCH_INDEX_UPSERT_FAILURE	Number of records that weren't indexed for search.
SEARCH_INDEX_DELETE_SUCCESS	Number of records whose indexes were purged.
SEARCH_INDEX_DELETE_FAILURE	Number of records whose indexes failed to be purged.

Note:

When you purge code values of code lists, the index for search step displays the metrics as 0 because the purge records step deletes the index.

Purge business entity activity report index

The purge BE activity report index step purges report indexes for the specific business entity records.

The following table describes the metrics that you can view for the purge BE activity report index step:

Metric ID	Description
TOTAL_COUNT	Total number of report indexes that the step processed.
SUCCESS_COUNT	Number of report indexes that were purged successfully.
FAILURE_COUNT	Number of report indexes that weren't purged.

Store cleanup

The store cleanup step removes intermediate data and backend files related to match pair details and the job. This step ensures a fresh start of processes after purging data.