I used ur configurations and got the below response bt still there is no exact time value.
Agent Id : xxxxx
Login Id : yyyyy
Object Type : Agent
Place :
Place ID : zzzzz
Place Status : 23
Time : 1435367705
Place Count : 1
Status : 23
Time : 1435367705
The time value which I got is about 100 days (even I restart the server).
Weird because the metric begins to be collected only the first time StatServer is requested for it. What I mean is, if you created this today, Yesterday StatServer was not collecting any information about this agent as had no clue of that metric…so, how can it be 100 days?
From where are those “logs” you show?
The “Time” you are referring to IS the UNIX EPOCH:
1435376204 = GMT: Sat, 27 Jun 2015 03:36:44 GMT
Conversion utilities exist on the web and other Posts on the Forum explain how to convert this to a standard time format. Basically, add 1435376204 seconds to 00:00:00 01/01/1970…
I think you are building a real-time interface, yes?
The TIME you can see allocated is the exact time/date that the STATUS of the Agent Object was reported by the StatServer. If you are building an App (and this is not CCP+), then you need to apply a local calculation within the App which counts the amount of time that has past, since the last STATUS update TIME from the StatServer. You will also need to send a regular request to the StatServer, to get regular STATUS updates. Or, if your App is 3rd party registered (as an Application in CIM), then that should be easy enough to set up as a regular (poll) request to a StatServer.
CCP+ does all of these things by design and I think you will need to find a way to emulate;
The TIME conversion to your local time zone.
The time that has elapsed since the last TIME update of the STATUS from the StatServer.
Regular polling of Updates from the StatServer to your App - or register the App with the StatServer to enable you to specify a polling interval.