Reporting: Cache Timestamp

Not planned

Follow

Jason

• March 15, 2016 04:48

I would like to request that the timestamp (either in GMT or offset to PST/PDT) be included when output report data so that we know when the data was last updated.

Obviously live (or close to it) data would be even more preferable, but hopefully adding a timestamp is a pretty light implementation compared to solving the overhead issues associated with reporting in real time.

0

• 

  Joe B.

  • March 15, 2016 22:24

  Hello Jason,

  We're working presently on closing the time gap to the near real-time transform of data into the data warehouse. Even with this, it seems it would be good information to have available, namely a "last updated at" timestamp of some sort, yes?

  0

  Comment actions Permalink
• 

  Jason

  • March 16, 2016 05:19

  If you can bring the gap between now and the values output in a report down to something around 30 minutes or less I think that completely eliminates the need for this feature request.

  I just figured that may be a relatively large undertaking when managing the scaling I'm sure you guys are planning for. Adding a timestamp to the output, as you suggest a simple "last updated at" would probably be pretty quick and painless to implement, and would at least let us know what data we're reporting on.

  Right now the problem is sometimes our reports update at 12PM and sometimes they don't update until 2:30PM, so we never really know what it is that we're looking at.

  0

  Comment actions Permalink
• 

  Quan Vu

  • March 16, 2016 21:32

  Hi Jason,

  I've gone ahead and filed this request with Engineering to have the timestamp added to both the Reporting UI and the downloaded report files. I'll update the request as more input comes through on this Community post.

  0

  Comment actions Permalink
• 

  Jason

  • March 16, 2016 22:39

  Thanks Quan!

  0

  Comment actions Permalink

Please sign in to leave a comment.