Exclude a specific class from calculating the Staleness is not working

[Suggy]

In cmdb health dashboard, I dont want Network adapter class to be considered for Staleness calculation.

So I created a Health inclusion rule, gave condition like 'IP address is ANYTHING' and did not consider the staleness metric

After creating the Health inclusion rule and running the health jobs, 'Network adapter' class is still reflecting on the dashboard. What could be the issue?

[Phil Scherry]

By setting a date in the far-reaching future, they do eventually go stale and someone can ensure the CMDB is cleaned up from CIs that don't provide a long-term benefit.  If you ignore them forever, then the data will 'clog' your CMDB.

EX: Once a server is retired, there is no advantage to having the memory modules, disks, and disk partitions.

[Harini17]

Hello Suggy, Can you tell me how you achieved the requirement? I have a similar usecase. 

[Phil Scherry]

Set the Staleness Metric for that particular class from the default 60 days to multiple years (3, 5 or 7).

[Phil Scherry]

After setting the Staleness Metric for a particular CI class from the default 60 days to multiple years (3, 5 or 7).  You also need to set up cleanup jobs to delete 'secondary' CIs.

EX: Once a server is retired, there is no advantage to having the memory modules, disks, and disk partitions.  So you set up a scheduled job to mark the memory modules as retired after the parent server has been retired for, say, 30 days.  Then schedule another job to delete the memory modules after they have been set to retired for 45 days.