Skip to content

Commit 5415111

Browse files
authored
fix(oss-health): correct April 2026 telemetry snapshot and pause fetch cron (#508)
## Summary Manually correct the April 2026 telemetry snapshot on `cozystack.io/oss-health/telemetry/` with live VictoriaMetrics values (112 clusters / 450 nodes / 444 tenants as of 2026-04-22) and pause the daily fetch cron until the upstream server fix ships. Root cause: the telemetry-server `/api/overview` endpoint freezes the current-month snapshot at the first-of-month request. See cozystack/cozystack-telemetry-server#5 for the server fix. Until that is deployed, every `fetch-telemetry.yml` run would overwrite this correction with stale 43 / 164 / 83. ## What - `static/oss-health-data/telemetry.json`: - `month` (April 2026) → 112 / 450 / 444. Apps scaled linearly by the cluster ratio 112 / 43 ≈ 2.6047. - `quarter` and `year` averages recomputed: March derived from `(2 × old_avg − stale_april)`, new average computed with the corrected April. Apps given the same treatment. - `.github/workflows/fetch-telemetry.yml`: `schedule:` block commented out with a TODO pointing at the upstream fix. `workflow_dispatch:` kept for manual refresh. ## Why Without pausing the cron the next 08:00 UTC run would revert this commit. Keeping `workflow_dispatch:` means we can trigger the fetch on-demand once the server fix is live, to verify it returns live data before re-enabling the schedule. ## Test plan - [ ] Hugo build + Netlify preview show April 112 / 450 / 444 and scaled apps on `/oss-health/telemetry/` - [ ] GitHub Actions page shows `Fetch Telemetry Data` with only manual trigger - [ ] Once the server fix is deployed: trigger the workflow manually, confirm it produces a diff of 0 (or within rounding) against this committed JSON, then re-enable the daily schedule in a follow-up PR
2 parents 78f644b + ab06e60 commit 5415111

2 files changed

Lines changed: 102 additions & 98 deletions

File tree

‎.github/workflows/fetch-telemetry.yml‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,13 @@
11
name: Fetch Telemetry Data
22

33
on:
4-
schedule:
5-
# Run daily at 08:00 UTC (00:00 Pacific during PST, 01:00 during PDT)
6-
- cron: '0 8 * * *'
4+
# Daily cron is paused until the telemetry-server current-month fix ships.
5+
# Until then the live /api/overview response for the current month is a
6+
# frozen first-of-month snapshot, and an automatic fetch would overwrite
7+
# the manually-corrected telemetry.json with stale numbers. Re-enable the
8+
# schedule once cozystack-telemetry-server is deployed with the fix.
9+
# schedule:
10+
# - cron: '0 8 * * *'
711
workflow_dispatch:
812

913
permissions:

0 commit comments

Comments
 (0)