Monitor v0.1.3

Monitor v0.1.3

Highlights

• Faster admin initial load.
• Rollback-safe schema upgrades preserving the pre-update database/WAL generation.
• Schema 2 foundation with additive transactional migration.
• Traffic reset modes: monthly for the current billing cycle and never for lifetime totals.
• Correct reset-day behavior across restarts and overlapping billing windows.
• ICMP and TCP latency probing.
• Agent config protocol v2 with backward compatibility.
• Bounded concurrent TCP probing under one round deadline.
• Packet-loss history derived from existing success/sample counters.
• Current open minute included exactly once in 1-minute and 5-minute ping history.
• Additional traffic recovery hardening across billing boundaries.

Compatibility

• v0.1.2 Agent + v0.1.3 Server: supported; config protocol v1 / ICMP-only.
• v0.1.3 Agent + v0.1.2 Server: supported; falls back to config protocol v1.
• v0.1.3 Agent + v0.1.3 Server: config protocol v2 with ICMP + TCP.
• Agent report protocol remains v1.

Upgrade notes

v0.1.3 migrates the database from schema 1 to schema 2 on first start.

The supplied updater preserves the pre-update database and WAL generation so rollback remains safe if the upgraded service fails to start.

After a database has migrated to schema 2, manually replacing the server binary with v0.1.2 is not supported because the older server cannot open the migrated database. Use the updater/rollback workflow instead.

Known limitations

• Persisted admin traffic totals may lag live values by up to the checkpoint interval.
• A hard kill may lose the currently open history minute.
• Resource history may briefly omit the newest minute between finalize and flush.

SHA256

See the attached SHA256SUMS file.