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.

[Nilanjan1]

Hello All, 

I am facing the same issue however I was directed to this blog expecting the answer, Is there a solution provided on this?

[stevejarman]

No - the answer on this one remains a bit of a grey area.

[doug_schulze]

Steve, yes on a positive identification meaning when the IRE is able to successfully process it we will update the most recent discovery field for all primary classes (off hardware) and the majority of all ancillary CIs that are a part of it. Even if nothing changed (updated) its still the proverbial 'pat on the head' that we know its there. There are a few CIs like net gear pieces that we don't update but work is being done to ensure that every CI that discovery finds gets this stamp.

[Nilanjan1]

Thank u Doug & Steve...If I understand it correctly we still do not have a solution. do we have a problem record opened for this? 

[Community Alums]

Hi @doug_schulze .

I know it is almost 5 years on from your last comment re: "...There are a few CIs like net gear pieces that we don't update but work is being done to ensure that every CI that discovery finds gets this stamp..."

Should this be in place now (with Xanadu/Yokohama) for network gear?

Thanks!