Skip to content

Releases and known limitations

The public portal, native Pi collectors, private Grafana dashboard, dedicated alerts and independent HTTPS check are deployed. The wiki is deployed through GitHub Pages. The portal footer reports its exact running source commit.

A seven-minute controlled collection pause verified public offline status, missing-telemetry alert firing, automatic recovery and alert resolution. A subsequent Pi reboot verified startup recovery and enforced memory limits. Build, API boundary, privacy and responsive Chromium/WebKit tests pass.

The wiki custom domain serves a valid GitHub Pages certificate, and HTTP-to-HTTPS enforcement is enabled. Grafana accepted the email integration test, and the recipient confirmed both firing and recovery emails.

Current firmware power flags are clear. A bounded 60-second test with two CPU workers reached 46.7°C without undervoltage or throttling flags. Earlier undervoltage still requires physical power-supply/cable inspection; this diagnostic does not prove an electrical issue is resolved.

Native host, memory, storage, network, systemd and supported Pi firmware measurements are collected. PSI is not exposed by the current kernel. Cached update metadata age and reboot-required state have no supported signal on this image. Missing values remain unavailable. Container resource monitoring and application instrumentation are documented opt-ins; no container runtime is installed solely for monitoring. SD-card health, wall power, fan speed, PMIC temperature and uninstrumented application traces are unavailable.

Public retention is 14 days within an 8 GiB hard filesystem bound. History starts at deployment; the portal explicitly separates observed coverage from sampled freshness availability. Private log retention was reported as 31 days. Private metrics retention and exact incremental billing terms remain unverified because the available account API permissions do not expose them. No account-wide retention settings or purchases were changed.