How to retire a discovery source in CMDB 360?

John Goldstein
Tera Contributor

Hello Experts,

 

Version: Washington D.C.

 

We are not using Service Now discovery but instead use a collection of import jobs and service graph connectors to populate our CMDB. We are using CMDB 360, previously multi-source CMDB. Each of the imports sends the data through IRE and has a defined discovery source in the job. We have retired a source of virtual machines because we were able to expand the scope of an existing discovery job to include the objects from the retired source.

 

My question is, how do I retire the discovery source? I would like to cleanup the source so that the records are not included in the CMDB Workspace metric "CIs not reported by discovery sources". This metric includes records that have not been seen from a discovery source in more than 7 days. Since we have retired the discovery source all the previous CIs are now included in this result set.

 

Thanks,

John

5 REPLIES 5

Niklas Peterson
Mega Sage
Mega Sage

Hi @John Goldstein ,

 

I may be misunderstanding you here but do you really need to do something about this? The metric "CIs not reported by discovery sources" is for a discovery source not specific ones. So if you replace one source with another, the CIs should still be updated. And if they are updated by the new source they should not be included in this metric.

 

Regards,
Niklas

Hi @Niklas Peterson ,

 

That is what I thought as well but that is not the behavior of the metric. In the settings for the CMDB 360 page the description says "but at least one discovery source has not reported on that CI in the specified number of days."
CIs_not_reported_settings.png

 

Regards,

John

Hi,

 

Interesting. It also says "Number of days since CIs were last discovered by a discovery source" so a bit of mixed signals here.

Anyway, I would try to delete all the updates from your old source for a CI in the cmdb_multisource_data table and see if the CI disappears from the metric. I don't have any sample data in my instance to test it right now but I guess the metric is using that data to determine which sources have updated the CI in the past.

 

Regards,
Niklas

Hello,

 

The setting for the number of days refers to any discovery source and how long it has been since the CI was last discovered by that source. In our case, the first discovery source was ImportSet. We then changed to data from a discovery source called VM-Inventory. Even though most recent discovery is today by VM-Inventory they show up in the metric because ImportSet was last used more than 7 days ago.

 

I tried to delete records in cmdb_multisource_data table but even using my account with Admin role I don't have the option to delete records. That was why I was looking for advice on how to properly retire a discovery source.