De-Duplication tasks and Archived CIs

Canjura
Tera Expert

Hi, 

 

We've found some de-duplication tasks that include the 'live' CI (from the cmdb_ci_x table) and a CI from the Archive table (ar_cmdb_ci_x). Is this a normal behavior? Is there a way to prevent de-duplication tasks to use CIs from the archive tables?

 

Thank you, 

3 REPLIES 3

KARTHIGA J
Tera Contributor

Hi Team, 

 

I have the above same issue, can anyone share the solution to fix it.

VivekSattanatha
Mega Sage

Better to add a CMDB health inclusion rule to filter out the archived records or target the tables/records that you really want the health dashboard should run.

 

KondurVishR1582
Tera Contributor

Hi @Canjura ,

The above mentioned behaviour is a normal behaviour and the following is the solution to avoid it 

The best way to is :

Navigate to CI Class Manager -> Select your CI class → Health → Health Inclusion Rule  section:

  • Define an Active record condition that filters out archived CIs

Common filter conditions include:

  • install_status != retired - Exclude retired CIs
  • operational_status = Operational - Include only operational CIs
  • Add a condition to exclude records from archive tables if needed