Poll an ArcGIS Server for Features - what's in the query cache?
Accepted Solutions
Hi Jess,
Yes, there is a way to figure this out - I highly recommend you review this helpful blog post: https://community.esri.com/community/gis/enterprise-gis/geoevent/blog/2015/05/21/debugging-geoevent-...
Basically, you'll want to turn on DEBUG level logging on com.esri.ges.transport.featureService.FeatureServiceInboundTransport
With that, you will see this in the Manager UI (or you can review the log files themselves):
In this example, the timestamp being used is 2018-11-05 18:57:46
If you went a bit too far ahead in time in your testing, you can reset the cache by restarting GeoEvent. Hope this helps!
Hi Jess,
Yes, there is a way to figure this out - I highly recommend you review this helpful blog post: https://community.esri.com/community/gis/enterprise-gis/geoevent/blog/2015/05/21/debugging-geoevent-...
Basically, you'll want to turn on DEBUG level logging on com.esri.ges.transport.featureService.FeatureServiceInboundTransport
With that, you will see this in the Manager UI (or you can review the log files themselves):
In this example, the timestamp being used is 2018-11-05 18:57:46
If you went a bit too far ahead in time in your testing, you can reset the cache by restarting GeoEvent. Hope this helps!
I have a quick follow up to this one --
We have configured editor tracking to store dates in our local time zone (mountain) so as to not cause confusion when users see the raw data. The feature service that's being polled is also configured for dates in MTN time.
Looking at the debugger messages, it seems that the cache time is being converted to UTC (7 hours ahead) -- so any new data that comes in during the next 7 hours window is missed --
I'm wondering if there's a way to reinforce the time zone through GeoEvent -- either through the input connector to cache the local time or to convert the time in the new records to UTC before evaluating the filter?
