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

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

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

2 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

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

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

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)

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.