Most Recent Discovery Not Getting updated even though the device shows it is being discovered recenlty

Nilanjan1
Mega Sage

Hello. 

This is a very strange issue I am getting. While I am running a weekly scans and can see all the IP subnets getting scanned, however when I check the table (Network Gear & Server) the most recent discovery date is not getting updated even though in the discovery status the CI has been discovered very recently. Can someone check asap and let me know. it is very uirgent

 

Regards

Nilanjan

1 ACCEPTED SOLUTION

I'm so glad to hear that you got it resolved @Nilanjan 🙂

Please mark the responses as helpful/correct so that we can close this thread and it can be helpful for other with the same question in the future.

Thanks,

Berny

View solution in original post

10 REPLIES 10

SiD2
ServiceNow Employee
ServiceNow Employee

Hi @bernyalvarado 

Thank you for clarification.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

Hello bernyalvarado, 

It seems that the discussion forum that you have given has not been concluded and there are no errors in probe which is actually preventing any further investigation. 

Regards

NIlanjan

@Nilanjan , I'm not sure if I follow you. What do you mean by "no errors in probe".

Either through probes/sensors or patterns, Discovery in not truly consistent to update most recent discovery field. It all depends on the CI Type (CI Class) you're discovering.

Is it a bug or error, not really because the discovery function still takes place. Is it inconvenient, it definitely is specially if you want to build some logic that relies on the most recent discovery. 

My advice is... make a list of the CI Types you care about. Do a Quick Discovery for 1 CI per each CI type. Check if the most recent discovery field got changed as a result of your quick discovery. If it did, the most recent discovery field then it should be get updated when your discovery process runs through Discovery Schedules. 

If there's a particular CI Type that is not updating the most recent discovery, you can always deep-dive into modifying probes/sensors or patterns to make sure it gets updated but the community is not the place where to show you that. The procedure it's quite involved for a simple community post and you will also be taking ownership of the elements which is not ideal due to the impact it could have during upgrades.  

Thanks,

Berny

Thank you @bernyalvarado actually I am aware of what is expected out of the discovery, the only issue that I am facing is the most recent discovery date and on the basis of various discussion forums the solution is still expected. Anyway I got the issue resolved it was with a small thing I overlooked related to a condition that was attached to the table. HopefullY I would get teh required data going forward with the next discoveries.

I'm so glad to hear that you got it resolved @Nilanjan 🙂

Please mark the responses as helpful/correct so that we can close this thread and it can be helpful for other with the same question in the future.

Thanks,

Berny