Skip to content

PingLake v0.3.0

Latest
Latest

Choose a tag to compare

View all tags
@ASL-Vanity ASL-Vanity released this 04 Oct 13:18
· 2 commits to main since this release
v0.3.0
4d8a25c

PingLake v0.3.0

PingLake v0.3.0 combines the redesigned dashboard from v0.2.0 with the complete monitoring extension.

Included

  • Monitoring v2 protocol with v1 Agent/Hub compatibility and schema v5 → v6 migration.
  • Per-core CPU, memory/Swap, disk I/O/inode, network health and TCP state collection.
  • Linux systemd and Windows SCM service checks, process checks, local port checks, and ICMP/TCP/HTTP(S)/DNS probes.
  • Persistent Agent reporting spool with bounded retries, expiry and drop accounting.
  • Canonical Hub samples, deduplication/conflict rejection, revisioned monitoring configuration, historical data and P50/P95/P99 statistics.
  • Browser-to-node HTTPS latency measurement with Origin/CORS/cache controls.
  • New compact multi-theme dashboard with host cards/list, monitoring tabs, groups, services, probes, alerts, and responsive mobile navigation.
  • Updated README, Chinese user guide, upgrade/rollback instructions, monitoring validation documents, and E2E scripts.

Upgrade notes

Upgrade Hub first. Create a consistent SQLite backup that includes committed WAL contents before starting schema migration. Upgrade Agents one at a time while retaining their existing state directory and enrollment credentials. A v6 database requires a v6-compatible Hub binary for rollback; restore the pre-upgrade database together with the old binary when rolling back.

Validation and production record

The release was checked with the Web typecheck/build/tests, Rust format/tests/clippy/release builds, and the local monitoring E2E smoke and monitoring suites. Linux and Windows Hub/Agent binaries are attached with SHA-256 checksums.

On 2026-10-04, S4 Hub was upgraded first and verified with schema version 6, a Ready 1/1 K3s Pod, HTTP 200 health, and retained nodes/metrics. S1, S2, S3, and S4 Agents were then upgraded one at a time to 0.3.0; each systemd service is active with exit status 0. The pre-upgrade v0.2.0 Hub binary, per-Agent v0.2.0 binary, Agent state directories, and a SQLite backup containing .db, .db-wal, and .db-shm were retained. Real external HTTPS browser measurements, Windows LocalService permission checks, and final desktop/mobile visual acceptance remain environment-specific manual checks.

Assets 7
Loading