Load Balancer Hybrid Identification Rules

[SRSkaggs]

I have a situation where F5 load balancers are being discovered just fine, but there are multiple F5 load balancers with the same name and serial number. But there isn't any de-duplication tasks or messages indicating they are duplicates. I noticed it has a hybrid identification rule at the parent load balancer class. I am not sure if that is what is causing it, but I am wondering if there is something I am missing here.

[AJ-TechTrek]

Hi @SRSkaggs ,

As per my understanding How Duplicate CI metric uses hybrid rules in health results.

When CMDB Health calculates duplicates:

• It leverages the effective identification rules in the IRE (including hybrid ones).

• If the rule can’t uniquely identify a CI (even after checking both attributes and relationships), IRE considers there might be duplicate candidates.

• These get logged into the Duplicate CI metric result:

  • Table: cmdb_health_duplicate

  • And shown in CMDB Health dashboard.

So:

 If your hybrid rule is too loose (e.g., only uses relationship to parent which itself isn’t unique), you’ll see more duplicates detected.

 If your hybrid rule is strong (attributes + strong parent), fewer duplicates.

Hybrid rules affect:

• What IRE considers as the unique key for a CI.

• The stricter/more precise your hybrid rules → fewer duplicates.

• The looser/more ambiguous → more duplicates.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025