apache / apache/beam

Update github sync metadata timestamp to represent actual sync time

Open
#19,112 0 comments 0 reactions 0 assignees View on GitHub
community-metrics P3 project-management sub-task
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.