Stale CI Inclusion Health Metric

[benjaminayo]

Hello,

I am looking to only include my principal CI classes in the Stale Metric but seem to be getting more CIs counted due to removing the staleness inclusion rule on the parent table(cmdb_ci). What is best practice in setting up health inclusion rules for specific classes and not reporting Ci classes without creating a staleness report for every class

[Avin ANZ]

In my view the best practice would be to leave the staleness rule as it is for the stale duration and use a Health Inclusion Rule to control the population being evaluated. If you only want Principal CI Classes to be included then it is better to configure the staleness health inclusion rule for those classes and optionally exclude retired/non-operational CIs as well. It better to avoid creating individual staleness rule for every class unless the class requires a different stale duration , for parent rules this can then be inherited by the child classes.

[Mehta]

Hi @benjaminayo , 

The Best way possible to configure the staleness rule is for each individual class you want to the metric to evaluate and have different number or data hierarchy .  if you have 60 days for each child class or for major child class that extends the CI Computer table then configure the rule for 60days on CI computer table. if needed for some other number of days can be configured for each individual class. example hand held might need 30 then configure 30 days rule on CI handheld Device table.

[Harish Bainsla]

Hi @benjaminayo 

please check below video for better understanding in depth 

https://youtu.be/XXaYqJF0zUY?si=OSjH-baNryH8gjQy