Staleness metric not available for Application class and child classes

[SandyBatcheller]

We have our Health Inclusion Rules set on the base Configuration Item class (cmdb_ci).  We can see that all 5 inclusion rules are on most child classes as well.  However, for a class like Application and it's child classes, we don't see the staleness rule inherited from the base cmdb_ci class.

We want to be able to track staleness on child classes of the Application class like IBM Webpshere, IBM Websphere MQ, Database Instance, MSFT SQL Instance, etc.

Is there a setting or property that determines which health metrics can be used for a class?

I've added a couple screenshots for what we are seeing.

[Sandeep90]

There are no properties which controls this, the default OOB behaviour should allow you to override any health inclusion rules for metrics for any sub class. Are you on a domain sepearted instance and also which version are you using? Even though it's not showing there is the health config not getting applied when health job runs ?

Can you also check cmdb_health_config table to see if you can view it ? config thats defined on the cmdb_ci will be carried over to all the sub classes.

[SandyBatcheller]

Hi Sandeep, 

We are on Rome and are not using domain separation.

It may be unrelated but what lead us down this path is that the Staleness indicator on the Health dashboard for some of these CIs is 0/0 when it should be something like 0/356 (if nothing is stale).  While troubleshooting this, we noticed that the Staleness rule doesn't show as per my question above for these same CI classes.  It doesn't appear the health jobs are updating the first 0 either showing there are no stale CIs when we know there are some.

I am able to access cmdb_health_config and do see all 5 health inclusion rules there.

[Sandeep90]

Hi Sandy,

I am not sure why the staleness is not getting displayed as it works on OOB Rome but health config is getting applied correctly,  0/0 is correct as your health inclusion rule on the cmdb_ci has sys_class_name=cmdb_ci_server at least from what I can read from the picture so it won't evaluate any CI's in the application so the total is 0.  Please refer to this doc to understand better how the totals are computed

[Sandeep90]

In case if anyone faces this issue, it is due to the property being set to true, https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag...  . It will exclude any dependent classes from staleness computation.