Reduce the dataset for CMDB RELATIONSHIP HEALTH score computation

Anonymous_guy
Tera Expert

Hi community,

 

Is there any way to exclude some classes while computing the relationship score? As far as I know, inclusion rules can be configured to exclude specific classes to populate normal health score that includes completeness, correctness and compliance KPIs.

Why do we need to achieve this?

   - A customer who has very limited CI classes in their business would never show interest in viewing relationship health score (duplicate, orphan and stale relationships) as a whole.

Anonymous_guy_0-1734407922805.png

We are interested only in the 13k records shown above.

Anonymous_guy_1-1734408164327.png

But the relationship dashboard has 100k records in it, that is nothing but the total number of records in the CMDB relationship table with UNDESIRED CIs (from a business perspective). Can we configure relationship score job to consider only a subset of this data?

Any help would be much appreciated.