How to exclude a CI Class from CMDB Health Check

Maurice Murphy · ‎04-27-2023

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 · ‎04-27-2023

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.

The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

View solution in original post

shembop · ‎12-15-2023

Is there a way to do this more on an exclude all unless I say so? Or would you have to go into each and every class to exclude from the health metric?

CMDB Whisperer · ‎12-15-2023

Yes there is! Just exclude the metrics in the base CI class by specifying a condition that is never true, and then override the inclusion rules for any subclass you want to measure.

The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

Maurice Murphy · ‎12-18-2023

We have done exactly this in our implementation. By excluding on a parent class, none of the child classes are included. If we require a child class to be tracked, we input the reverse of the recommended rule "SysID is NOT empty".

Hope this helps!

Colt · ‎01-09-2024

Is it possible to do this with Unclassed Hardware?

Maurice Murphy · ‎01-09-2024

We don't have any Unclassed Hardware in our instance, but checking the CI Class Manager, you should be able to do the same as above.

Just go to the CI Class Manager, pull up the Unclassed Hardware class, go to Health > Health Inclusion Rules, add "Sys ID is empty" as the filter, and then add all 5 items from the left slush bucket to the right.