admin e737704e68 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>

2026-02-23 15:05:39 +01:00

..

builder.go

feat(telemetry): add per-app metrics and log telemetry to hub reports (v0.28.0)

2026-02-23 10:46:27 +01:00

infra_backup_linux.go

v0.15.5: Disaster recovery — Hub-based infra backup, auto-mount, restore UI

2026-02-19 13:16:46 +01:00

infra_backup_other.go

v0.15.5: Disaster recovery — Hub-based infra backup, auto-mount, restore UI

2026-02-19 13:16:46 +01:00

infra_backup.go

feat: drive migration & Tier 2 restic deprecation (v0.18.0)

2026-02-19 21:49:14 +01:00

infra_pull.go

v0.22.0: First-run setup wizard, local infra backup, hub verification

2026-02-21 12:33:17 +01:00

pusher.go

v0.24.0 — Pre-testing observability: debug logging, diagnostic dump, startup self-test

2026-02-21 18:32:26 +01:00

telemetry.go

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

2026-02-23 15:05:39 +01:00

types.go

feat(telemetry): add per-app metrics and log telemetry to hub reports (v0.28.0)

2026-02-23 10:46:27 +01:00