Poor Identification Rules may impact data quality and cause duplications.
Make sure to review the out-of-the-box (OOTB) identification rules on your discovered classes during ServiceNow Discovery implementation. Reviewing these rules will ensure that you have an accurate Configuration Item (CI) representation in your CMDB.
You may need to adjust these rules to avoid duplications and other anomalies. The goal is to ensure that Identification Rules maintain a unique representation of your CIs. It may be helpful to think of the rules like coalesce options in Transform Maps.
- In the CI Class Manager, review the Identification Rules that will be populated from discovery.
- Unless you want specific rules for specific classes, always review the class at the top of the hierarchy.
- For instance, to review the server identification rules, you must examine the hardware rules, unless you want to change the rules specifically for the server class.
- If you review the rule at the server class level in the CI Class Manager, it will display as a “derived” rule from the Hardware table.
Note: Some OOTB discovery patterns return a generic name for applications. An example might be JbossServer@servername.com. So, if you have multiple instances of the application running on a single server, you may get duplicate CI names from discovery.
Resolution may require returning the JVM middleware’s unique name instead. Again, it all depends on your data needs.