CI_Discovery source updated even when no CI updates are done?

Ed Laar
Mega Guru

‎09-09-2023 01:31 PM

Hi,

Probably a simple question to answer but just to set my mind in the good mood again.
Discovery or any other source can have a CI in it's data but the data of the CI in the CMDB is the same as the data of the CI in the source data so no CI update is needed as nothing changed about the CI. What should be done is updating the CI_Last discovered date with the Last scan date of the involved source to show that the CI was evaluated on that Last scan date.

Question here: Should the CI_Discovery source also been updated in this case?

So when CI data comes in from source A and the CI is evaluated but NOT updated should the CI_Last discovered be set AND the CI_Discovery source been set?

 

Why this question: We have an occasion that a CI_Source (VR-Rapid7) has CI in it's dbase but without updates and the CI_Last discovered is set but the CI_Discovery source is not set to VR-Rapid7 but is untouched. In case the VR-Rapid7 dbase has updates, the CI is updated, the CI_Last discovered is set AND the Discovery source is set to VR-Rapid7.

 

Is this normal, OOB behavior or are there system settings/ properties or something else responsible for this behavior??

 

Looking forward to your responses. Many thanks in advance.

 

Grtz,

 

Ed

 

 

0 Helpfuls
  • 830 Views
1 REPLY 1

Niklas Peterson
Mega Sage
Mega Sage

‎09-09-2023 11:12 PM

Hi Ed,

 

Good question, in my opinion it makes sense to update the discovery_source as well, considering you could have multiple sources settings last_discovered. It's nice to know which source "saw" it most recently.

 

I don't know the conditions for how it is being set but the documentation around IRE properties has some settings around this and that kind of implies that IRE will set the discovery_source.

 

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/re...

 

Maybe the glide.identification_engine.skip_updating_source_last_discovered_if_older can make a difference for you here. If I interprete it right, setting the property to false should update last_discovered and discovery_source always.

 

Regards,
Niklas 

0 Helpfuls