CMDB CI Staleness Metric - Advanced Criteria

[AdamJ]

Hello,

I am familiar with how to update and manage staleness metrics using the CI class manager. However I'm wondering if there are options for utilising more advanced criteria for what determines staleness for a class. 

e.g. If my organisation are utilising tags to mark CI's as, let's say "staleness exempt", is it possible to have only CI's that are: Not updated in 60 days AND Do not have a tag of "staleness exempt".

Thanks,

[Ashok Sasidhara]

You can use health inclusion rules. It is explained in the following URL:

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...

The attached screenshot shows how your requirement will look.

[Josh P1]

We had a similar problem:  we only wanted to include classes that were flagged as principal and not have to maintain 40+ individual inclusion rules.  We noticed that the CI Class Manager Inclusion rules filter interface was limited because it adhered to the attribute type definitions.  A way around this is to import directly to the CMDB Health Config table (cmdb_health_config) to update the inclusion rules.  Using the import we were able to update the appropriate entries to include javascript as the Inclusion condition:

You might be able to use this strategy to similarly include the necessary javascript to lookup if CIs have tags as I noticed the Tags (sys_tags) is not available as one of the filter objects.

Hope it helps!