fix: skip stopped apps in telemetry to avoid zero-value averages on hub

Deployed-but-stopped apps were included in telemetry reports with all-zero
memory/CPU values, dragging down hub-side averages. Now isStackRunning()
filters to only running/starting/unhealthy/restarting states.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-23 15:05:39 +01:00
parent d3f7e39d6d
commit e737704e68
2 changed files with 19 additions and 2 deletions
+5
View File
@@ -1,5 +1,10 @@
## Changelog
### v0.28.4 — Telemetry: Skip Stopped Apps (2026-02-23)
#### Fixed
- **Stopped apps no longer send zero-value telemetry to hub** (`report/telemetry.go`) — Previously, deployed-but-stopped apps were included in the telemetry report with all-zero memory/CPU values, which dragged down hub-side averages. Now `buildAppTelemetry` checks `isStackRunning()` and only includes apps in running, starting, unhealthy, or restarting states.
### v0.28.3 — Catch-All Page, Deploy Controls, Dashboard Open (2026-02-23)
#### Added