When running discovery jobs that have agents installed, sometimes the build teams will not follow the advice of the UCMDB team and they will just clone all the agents to new systems. This causes a rash of cloned UD_Unique_ID values which, in turn, cause massive reconciliation overhead and creates 'supernodes' in UCMDB that contain all the information from all affected CIs.
I would request we add the following to VERIFICATION rules in node identification:
<attribute-condition attributeName="ud_unique_id" operator="EqualIgnoreCase" includeNullValue="false" conditionType="approveAndContradict"/>
<attribute-condition attributeName="name" operator="EqualIgnoreCase" includeNullValue="false" conditionType="approveAndContradict"/>
This would have the effect of NOT merging CIs based only on a UD Unique ID being the same IF the names are different. Then the teams can track which UD Unique IDs have been duplicated and they can help the build teams to remediate that without impacting data quality inside UCMDB. In addition, since the validation rule exists still for UD Unique ID, the call home events would be processed normally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.