CI deletion strategies for pattern discovery

When you perform discovery with a pattern, you can choose what to do with certain CIs that Discovery can no longer find.

Note: Deletion strategies are available only with patterns, not probes and sensors.
When you use a pattern to perform discovery, you identify a CI Type, which is the main CI you are trying to find, such as an IIS web server or Tomcat server. Discovery can also find related CIs and populate the CMDB accordingly. For example, after Discovery finds an IIS server with the IIS pattern, it can also find these related CIs:
  • The Windows machine
  • The configuration files for the IIS server
  • The web site that the IIS server hosts
The dependency map on the main CI also shows the related CIs, as illustrated by the following graphic:
Figure 1. An example of an IIS server main CI and its related CIs

After you discover the main CI and its related CIs for the first time with a pattern, Discovery puts an entry into the Related CI Types [sa_ci_to_pattern] table for each relation between the main CI a related CI type. These records are where you determine the deletion strategy for each related CI by the type to which it belongs. You cannot set a deletion strategy for the main CI.

You can view a list of the relations as the following image illustrates:
Figure 2. Example CIs related to an IIS server
An example of CIs related to an IIS server
The deletion strategy on a related CI takes effect when both of these conditions occur:
  • After you run Discovery with the pattern again.
  • Discovery successfully finds the main CI but cannot find the related CI.

These deletion strategy options are available:

Value Description
Keep Preserves the configuration file CI record and makes no other changes to the record. This option is the default setting.
Delete Deletes the configuration file CI record from the CMDB, and the relationship to the main CI.
Mark as absent Marks the Status [install_status] field of the configuration file CI record as Absent, meaning that Discovery cannot find the tracked configuration file. This status does not instruct the system to delete the actual CI or the relationship.
Delete relations Deletes only the CI relationships between the related CI and the main CI.

Set a deletion strategy

Set a deletion strategy when you want to take action on a related CI that Discovery can no longer find through pattern discovery.

Before you begin

  • Role required: cloud_admin, sm_admin, or admin
  • CIs: a main CI and related CIs that the discovery process found through pattern discovery

About this task

You can set a deletion strategy for all discovered CIs, including configuration file CIs. However the way you access the deletion strategy for tracked configuration files differs from the procedure in this topic. See Set the deletion strategy for tracked configuration files for instructions.

Procedure

  1. Open the list of related CI types by entering sa_ci_to_pattern.list in the application filter.
  2. Filter the list to find the CI type that is related to a main CI through pattern discovery.
  3. From the list view, double click the value in the field in the Deletion Strategy column.
  4. Select a new value:
    Value Description
    Keep Preserves the configuration file CI record and makes no other changes to the record. This option is the default setting.
    Delete Deletes the configuration file CI record from the CMDB, and the relationship to the main CI.
    Mark as absent Marks the Status [install_status] field of the configuration file CI record as Absent, meaning that Discovery cannot find the tracked configuration file. This status does not instruct the system to delete the actual CI or the relationship.
    Delete relations Deletes only the CI relationships between the related CI and the main CI.