Most Recent Discovery date behaviour

[stevejarman]

Hi all - I'm looking for a definitive answer on whether or not the Most Recent Discovery date on a CI should update EVERY time Discovery sees the CI, regardless of whether or not anything has changed? OR, does it only update the Most Recent Discovery date on a CI if/when it discovers changes to it? I feel like I'm seeing mixed results sometimes...

I've also noticed that an update to Most Recent Discovery field does NOT update the Updated (sys_updated_on) field. That's correct? It seems like changes to Most Recent Discovery field are exempt somehow from "dirtying" the record.

[Sharon Hobart]

Would this also still update if you had a Business Rule set the Abort Action set to true on an update to the CI in the CMDB?   I'm thinking it does but can't prove it out.  We have a crazy use case and I'm suspicious that the IRE still updates the Last_discovered update if you have a before BR on Update.

[giuseppebos]

I am facing a different issue but I wonder if you can advise. In my environment we attempt discovery against a large range of IPs and even if the "identification" of a certain IP does not happen (job times out before full completion) the Most Recent Discovery date for the CI with that IP appears to be changed to the date of that attempted scan. So it looks like it's been discovered on that date even if it is not really true. So, we have systems that have been removed from the environment but still have a CI with Most Recent Discovery date of today.

[Russ Hancock]

Hello,

I have a similar question.  In our particular situation, we are fine if the Most Recent Discovery field gets updated on every identification of a CI (even if nothing else is updated by Discovery on the CI), but what we are trying to avoid is to have the date in the Updated (sys_updated_on) field updated when nothing else is touched by Discovery on the CI.  Since we also have a nightly export to a Data Mart that we maintain, and this export uses the sys_updated_on field to determine if the CI needs to be sent to the Data Mart, the fact that this field is sometimes incorrectly being updated to the current date is a problem for us.

Does anyone have more information about what specific rules govern when the sys_updated_on field gets updated by Discovery?

Thanks!

Russ

[Adarsh kumar si]

Hello @Russ Hancock  . I am also facing same issue . Did you get any solution for this?

Thank you.

[Russ Hancock]

Hi @Adarsh kumar si, sorry, unfortunately not!