[GitHub] [beam] kennknowles opened a new issue, #19112: Update github sync metadata timestamp to represent actual sync time

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #19112:
URL: https://github.com/apache/beam/issues/19112

   The community metrics data ingestion scripts run in a loop and import all new data since the last run. We have a [Source Data Freshness](http://104.154.241.245/d/data-freshness/source-data-freshness) dashboard which tracks the freshness of import data. A Jenkins job checks this data regularly to ensure our dashboards don't get stale.
   
   Currently the GitHub "last sync" time actually tracks the last activity found on import. This means that if there is no activity on GitHub our dashboards will appear stale and our prober job will fail. This can happen in normal scenarios (i.e. at night, or during weekends / holidays).
   
   We should update the last sync timestamp logic to be the actual timestamp of last poll, rather than the last data we found.
   
   Imported from Jira [BEAM-5924](https://issues.apache.org/jira/browse/BEAM-5924). Original Jira may contain additional context.
   Reported by: swegner.
   Subtask of issue #19110


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org