Probe filter mechanism design gap - related CIs must not be filtered if relevant for reconciliation

[Daniel Engelmann]

the current probe filter mechanism does not send CIs to UCMDB if there was no change on the CI compared to last discovery run. whereas this can be good for performance, it is very problematic if those filtered CIs are needed to identify other CIs.

here 2 examples:

1. Location CIs: a location is identified by its name and also related location CIs, e.g. a room location requires the parent floor location CI to be uniquely identified. if there was a change on the room CI but not on the floor CI, only the room CI will be send to UCMDB which is not enough to reconcile it
2. SAP System CIs: a sap system CI is identified by its related sap application server CIs. if only the sap system was changed and send to UCMDB, it is not enough to reconcile without the related sap app servers

consequently, before the probe filters a CI, it needs to be checked if this CI is required to identify any other CI from the bulk

[Bill_Dyck]

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

[Bill_Dyck]

Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

[Bill_Dyck]

There is a qualified titled "DDM_REQUIRED_TOPOLOGY" that should be added to the Node CI type that will force the inclusion of related CIs necessary for reconciliation to be sent to UCMDB, even if they did not change in the most recent discovery scan while the node itself did change.