Repository navigation
chore(telemetry): publish July 2026 and explain how the figures are derived - #644
Merged
Merged
Conversation
Timur Tukaev (tym83)
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp) and
myasnikovdaniil
as code owners
August 7, 2026 10:40
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
📝 WalkthroughWalkthroughThe telemetry workflow now runs monthly and publishes the previous calendar month. Telemetry data covers July 2026. The telemetry view explains cluster counting and peak-per-cluster aggregation. ChangesTelemetry update
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…erived July: 1295 clusters, 4114 nodes, 3050 tenants, up from June's 1162 / 3697 / 2180. Two application rows fall by more than half — VMDisk 3042 to 1258 and VMInstance 2748 to 1019 — and neither is a shrinking fleet. April and May reported 580/488 and 257/283, so June was the outlier: instance figures are each cluster's peak within the window, summed, and one short-lived burst raises a whole month. July sits above the spring trend, not below it. The page now says this. It carried nothing about how the numbers are derived, and a reader looking only at the table would reasonably conclude the fleet had halved. Signed-off-by: tym83 <[email protected]>
Timur Tukaev (tym83)
force-pushed
the
chore/telemetry-july-2026
branch
from
August 7, 2026 10:52
c682888 to
806dc91
Compare
Timur Tukaev (tym83)
changed the title
Aleksei Sviridkin (lexfrei)
added a commit
that referenced
this pull request
Sep 4, 2026
## Summary Re-enables the monthly telemetry cron. Split out from #644, which publishes the July data — this one is a process change and deserves its own decision. ## Why it was paused `/api/overview` undercounted by roughly threefold. It counted with an instant PromQL query, so it saw only the clusters that had reported in the last few minutes — about 50 — rather than those active over the period. The published numbers were pulled from the Grafana telemetry-overview dashboard by hand instead, and the workflow was reduced to `workflow_dispatch`. ## Why it can come back The server has counted over the period window since [cozystack-telemetry-server 43617cc](cozystack/cozystack-telemetry-server@43617cc) (2026-06-30): every selector is wrapped in `max_over_time(...[window])` covering the month. Checked before re-enabling — the API returns **1162 / 3697 / 2180** for June today, which matches the figures published by hand last month exactly. The discrepancy that justified the manual path is gone. ## Timing Runs on the 3rd and publishes the month before, which is the month the server has a final snapshot of. The previous month is derived from the day before the 1st of the current one, not from `date -d 'last month'`: that phrasing keeps the day number, so a run on the 29th, 30th or 31st resolves into the wrong month and silently skips one. Verified for 2026-08-03 → 2026-07, 2026-03-31 → 2026-02, 2026-01-01 → 2025-12. It stays a separate workflow rather than joining the monthly OSS Health job: those datasets come from public APIs, this one from our own telemetry server, and a failure there should not hold back the rest. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Telemetry data is now fetched automatically on the 3rd of each month for the previous completed month. - Manual telemetry runs remain available when needed. - Telemetry updates are clearly labeled with the reporting month for easier tracking. - **Documentation** - Updated telemetry workflow documentation to reflect the automated monthly process. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
July 2026 telemetry, plus a short note on the page explaining how the figures are derived.
The cron that would publish this automatically is a separate change — it is a process decision, not a data refresh.
The numbers
July: 1295 clusters, 4114 nodes, 3050 tenants (June: 1162 / 3697 / 2180).
Two application rows fall by more than half — VMDisk 3042 → 1258, VMInstance 2748 → 1019 — and neither is a shrinking fleet:
June was the outlier. Instance figures are each cluster's peak within the window, summed across clusters, so a single short-lived burst raises a whole month. July sits roughly 3× above the spring trend, not below it.
The note
The page carried nothing about how the numbers are derived. A reader looking only at the table this month would reasonably conclude the fleet had halved, so the telemetry block now says that clusters are those which reported at least once in the window, and that node, tenant and application figures are per-cluster peaks summed across clusters.
Verification
hugo --minifybuilds clean; the note and its style reach the rendered page.telemetry.jsonwas produced byhack/fetch_telemetry.pywithTELEMETRY_YEAR=2026 TELEMETRY_MONTH=7, unmodified by hand — the API's June figures match what was published manually last month to the digit.