Discovery last_discovered date not correct

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2016 01:43 PM
Where does the last_discovered date get generated? We have noticed a discrepancy in the dates. Even if we do a Quick Discovery on a computer, the last_discovered date does not reflect the discovery that was just done. Can someone just point me in the right direction? I have searched BR and Script Includes for this field, and I see places where that field is referenced, but not sure how that translates into finding why the date is not correctly populated.
Any ideas on where to go with this?
Thanks!
Mickey Cegon
FBL Financial Group, Inc.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2016 05:16 PM
Mickey,
Thats an odd one, I'm pretty sure this gets set in the DiscoveryIDSensor script include (line 404) but if it not updating the Most Recent Discovery (last_discovered) field as you are seeing then yeah, something is going wrong. Trust you have checked any local rules that may have been implemented preventing updates of any fields? Maybe try a manual update to see if that takes, (just to be sure). But if you have eliminated the obvious then definitely check with support!
-Doug

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2016 07:18 AM
Thanks for the quick response, Doug! I will take a look at the DiscoveryIDSensor script include. We've also noted that some of the last_discovered confusion is that it appears to populate the date in GMT time, I believe, so at first glance, it looked like it may not be updating correctly. Is there a way to have it always use the local time zone instead? When we update a CI, the updated date is local, but the last_discovered date is not.
Mickey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2016 08:48 AM
Mickey,
I think thats because the discovery date is a global parameter, theres no user context to determine what time zone it should show so its GMT. That would be my best guess to why they chose to do it that way..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-03-2024 05:20 PM
Hi @doug_schulze , I see that they are trying to set the value with current datetime. But i would like to know from where this script include is being triggered. I don't see any business rule calling this. We are trying to understand how exactly that script is being called and what is triggering it to set the "Most Recent Discovery". Please let me know if you have an answer.