You can specify what you want to do with tracked configuration file CI records when
pattern discovery can no longer find them.
About this task
You can set a deletion strategy for all discovered CIs, not
just configuration file CIs. However the way you access the deletion strategy for
standard CIs differs from configuration file CIs. See Set a deletion strategy for instructions.
Procedure
-
Navigate to and open the desired pattern.
-
Click the Tracked Files tab.
-
Under Related Links, click Edit deletion
strategy for the configuration files of this pattern.
The Related CI Types list appears showing you filtered records in the
Related CI Type [sa_ci_to_pattern] table. The filter shows you only records with
the CI type of Tracked Configuration files [cmdb_ci_config_file_tracked], which
is the table where the system saves configuration file CIs.
-
From the list view, double-click the value in the field in the
Deletion Strategy column for the tracked
configuration file.
-
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.Note: There are
two tables that do have their CIs deleted if marked as absent:
cmdb_ci_network_adapter and cmdb_ci_ip_address. |
| Delete relations |
Deletes only the CI relationships between the related CI and the main CI. |
| Mark as retired |
Marks the Status [install_status] field of the
configuration file CI record as Retired, meaning that
Discovery no longer uses this configuration file. This status does not instruct
the system to delete the actual CI or the relationship. |