Most recent discovery field in cmdb_ci_computer table showing tomorrows date if it discovered today

Community Alums
Not applicable

Hi All,

 

Most recent discovery field in the cmdb_ci_computer is showing tomorrow's date  in the display value, but if I see the xml it shows that its discovered today.

For eg: in the UI it shows as below Most recent discovery - 03-12-2023 04:36:43, but if I take the XML, it is showing as "<last_discovered>2023-12-02 17:36:43</last_discovered>" (which is correct). 

 

Any idea why its displaying tomorrow's date in the front end field value?

 

Thanks

1 ACCEPTED SOLUTION

BalaG
Kilo Sage

Time shown by is XML is the time of record in GMT. The displayed time is determined by user's (your) timezone setting. If for instance your time zone was set to some thing in East Asia or Australia, you may see tomorrow's timestamps.

View solution in original post

4 REPLIES 4

BalaG
Kilo Sage

Time shown by is XML is the time of record in GMT. The displayed time is determined by user's (your) timezone setting. If for instance your time zone was set to some thing in East Asia or Australia, you may see tomorrow's timestamps.

Ethan Davies
Mega Sage
Mega Sage

This is likely due to your timezone settings on your user record. Take a look at your user preferences and compare your timezone vs the instance timezone. It could also be the case that you are discovering something located in another timezone, the date Discovery is pulling from the device based in a different timezone may not be the same as yours or the instances.

Community Alums
Not applicable

Thank you for the suggestions. I'm trying to run the import as a system administrator and set the time zone to Australia/Melbourne. Will post the outcome here.

Got another question regarding the Most recent discovery.

There is a scheduled import called SG-SCCM Last Discovered Update. Currently the "Use last run datetime" checkbox is unchecked. Is that okay to be unchecked? I have read many places that this field needs to get cleared after each run.

 

Thanks,

Anjana

Yes, it should be unchecked in this case.