How to exclude a CI Class from CMDB Health Check

[Maurice Murphy]

Hi Community,

I am currently in an exploratory phase with CMDB and Discovery, and part of this is to get an accurate health report of our current CMDB which is currently only being utilized via an integration with SCCM.

We've noticed that everything from the health check jobs comes back within acceptable parameters (90%+), however the IP Address class of CI's are all coming back stale which is making the scan for correctness fail. 

We wanted to know if there was a way to exclude these items from the health check. We've attempted creating Inclusion rules which will only set an IP address as stale after several years, but the scan is still meeting the failure threshold. 

We don't want to increase the property for staleness as we think 60 days is a good indicator for staleness, and we don't want to increase the failure threshold all that high either unless we have to.

If there's a way to exclude OR a way to get our IP Addresses to not come back stale, that would help us proceed.

[CMDB Whisperer · Accepted solution]

If you are not going to be measuring a metric for a class of CIs, then you should exclude that class entirely for that metric.  So you can either omit the IP Address class entirely for that metric, OR if you need to override an inclusion rule set at the parent class level, you can simply set the inclusion rules to a condition that will never be true.  My go-to condition for this scenario is to include only CIs where "Sys ID is empty" which will never be true.

[Maurice Murphy]

Do you have a bit of insight on how we'd actually get that set up? Would that be within the CI Class Manager under the Inclusion Rules, or somewhere else? 

[CMDB Whisperer]

Yes.  In the CI Class Manager.

[Maurice Murphy]

Gotcha, thanks for pointing this out. I'll give this a try and run the correctness job again. If it works I'll set this as the solution!