chore(telemetry): publish July 2026 and explain how the figures are derived

[Timur Tukaev (tym83)]

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:

	Apr	May	Jun	Jul
VMDisk	580	488	3042	1258
VMInstance	257	283	2748	1019

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 --minify builds clean; the note and its style reach the rendered page. telemetry.json was produced by hack/fetch_telemetry.py with TELEMETRY_YEAR=2026 TELEMETRY_MONTH=7, unmodified by hand — the API's June figures match what was published manually last month to the digit.

[netlify]

✅ Deploy Preview for cozystack ready!

Name	Link
🔨 Latest commit	806dc91
🔍 Latest deploy log	https://app.netlify.com/projects/cozystack/deploys/6a75b90b5c8846000884db58
😎 Deploy Preview	https://deploy-preview-644--cozystack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The 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.

Changes

Telemetry update

Layer / File(s)	Summary
Automated prior-month telemetry publishing .github/workflows/fetch-telemetry.yml	The workflow runs on the third day of each month, resolves the previous month, passes it to the fetch script, and includes it in commit messages.
July 2026 telemetry dataset static/oss-health-data/telemetry.json	Monthly, quarterly, and yearly telemetry periods now contain data through July 2026.
Telemetry methodology note layouts/_default/oss-health-app.html, assets/scss/_oss_health.scss	The telemetry view displays aggregation rules below the applications section with dedicated note styling.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: kvaps

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the July 2026 telemetry publication and the explanation of how the figures are derived.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/telemetry-july-2026

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}