CI deletion strategy for pattern discovery

[Arno Reintjens]

Hi all,

I have a question on the CI deletion strategy for pattern discovery.

Discovery has registered MSFT SQL Instances as absent. We want discovery to change this in Retired.

The document  CI deletion strategy for pattern discovery describes that you can define a main CI and after you discover the main CI 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.

My question is, how do you define a CI type as a main CI?

Does it make sense to add a record to [sa_ci_to_pattern] yourself?

We tried to add a record, where we made the link from pattern Windows – Server and CI class cmdb_ci_db_mssql_instance, with no result.

Any help would be greatly appreciated.

Cheers,

Arno

[Venky VA · Accepted solution]

CI that is mapped to the pattern is called Main CI

Change MSFT SQL Instances Related CI Types to Retired as in the following screenshot

[manminder]

Do we know how can we set the time frame for deletion strategy? Like how do we know how many days after deletion strategy will execute ?