Use > Data Flow Management > Adapter Management > Adapter Configuration > Automatically Deleted CIs and Relationships and Candidates for Deletion CIs

Automatically Deleted CIs and Relationships and Candidates for Deletion CIs

During discovery, the Data Flow Probe compares CIs found during the previous, successful job invocation with those found during the current job invocation. A missing component, such as a disk or software, is assumed to have been removed from the system, and its CI is automatically deleted from the Probe's database.

By default, the Data Flow Probe deletes CI instances of certain CITs, for example, the current configuration for the Host Resources and Host Applications jobs (snmp: file system, installed software, osuser, service).

DFM enables you to customize which CI instances the Probe should automatically delete for specific jobs.

You can also mark a CIT as a candidate for deletion. In this case, if no CI instances of that CIT are discovered, the CIT is isolated rather than automatically deleted. Carefully choose the CITs that are to be candidates for deletion. For example, process CITs are not good candidates because they often shut down and start up again and, as a result, may be deleted at every invocation.

Example of Automatic Deletion

During the previous job invocation, the Data Flow Probe ran the Host Resources by WMI job and discovered a host with disks a, b, c, and d. During the current job invocation, the Probe discovers disks a, b, and c, compares this result with the previous result. Since it finds that disk d is missing, it deletes the CI for disk d.


  • The Data Flow Probe does not wait for the aging mechanism to perform the calculation, but immediately sends a deletion request to the server. For details about aging, see The Aging Mechanism Overview.

  • The change is defined on the job's adapter.

  • If discovery fails and errors occur, objects are sent for deletion according to how the results are managed. For details, see Adapter Configuration Tab.

  • You can use this procedure to delete relationships, too. For example, the containment relationship is used between a node and an IP address. A laptop machine is allocated a different IP address very often. By deleting the relationship, you prevent the accumulation of old IP addresses attached to this node.

  • You can view deleted CIs in the Probe log and in the Deleted column in the Discovery Results pane. For details, see Data Flow Probe Log Files and Discovery Results Tab/Pane.

For details on configuring automatic deletion, see How to Configure the Data Flow Probe to Automatically Delete CIs.

Related Topics Link IconRelated Information