Reduce the dataset for CMDB RELATIONSHIP HEALTH score computation

Anonymous_guy
Tera Expert

‎12-16-2024 08:08 PM

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.

 

0 Helpfuls
  • 890 Views
5 REPLIES 5

Sandeep90
ServiceNow Employee
ServiceNow Employee
In response to Anonymous_guy

‎12-20-2024 11:18 AM

Agreed, that’s correct—there isn’t a simpler way to address this for the relationship dashboard without enhancements. However, my point is that this information isn’t even useful and doesn’t need to be computed at all. Instead of processing it, I recommend fully disabling the job.

0 Helpfuls