Does the Deletion Strategy auto delete the CI as well? Or is there anything when Discovery runs that auto deletes a CI such as a DB Catalog?

[jdeken]

I have seen where a Database Catalog CI was deleted by the Service Account used for Discovery. Is this caused by the Deletion Strategy being set on that table to Delete? I was thinking that it did not delete the actual CI but trying to understand what would.

Thanks in advance!

[SteveJoe]

This is probably caused by Discovery Failing and the Deletion Strategy set to Delete.  You can validate the Deletion stategy by going to this table (sa_ci_to_pattern.list) and checking the update/ create date.  It could be OOTB functionality.  I say this because I have seen this on my on instance and had to make modification.

From the Discovery Pattern Log, look for the Discovery Pattern Log - Delete Handler and seek if deleted any CI

Please see the following Production documentation, hope this helps

https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/set-deletion-strategy.html

[jdeken]

Thanks Steve. I guess that was my concern if it was something OOB because we didn't set anything when we implemented our new instance. The documentation keeps saying Configuration File which also confused me. Is Configuration file the same as just the CI? Which would mean it is deleting the CI when it can not be found in discovery. 

Thanks for the link and where to look as well. I found on the one CI where in the log it does have that Delete Handler statement and appears to delete the CI.  I will locate the delete strategy and update that to not delete. 

Thanks.

[Ashutosh Munot1]

HI,

Agree with Steve, this can be the delete strategy.

I hope you do not have any custom delete strategy in place.

Thanks,
Ashutosh

[jdeken]

Thanks for providing a second look and confirmation to my question. Thanks!