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.

Monitor v0.1.2

Monitor v0.1.2

Feature and installation usability release.

Improved installation:

• one-line Server/Agent bootstrap
• Server default 127.0.0.1:25774
• configurable --listen/--port
• secure admin password setup
• secure Agent token bootstrap without argv
• exact pin --version

Safer lifecycle:

• managed systemd drop-in for custom listener
• reinstall/update preserve listener
• refuse unrelated occupied ports
• update/uninstall fail closed on foreign ExecStart
• unrelated drop-ins preserved
• normal uninstall preserves data; --purge removes

Interface:

• improved mobile public status density/presentation
• traffic GB/TB and exact traffic limit handling
• clickable site title

Security:

• password/token not accepted as bootstrap CLI args
• admin password changes as monitor user
• SHA256 verified before execution

Platforms:

• linux/amd64
• linux/arm64

Monitor v0.1.1

Monitor v0.1.1

Maintenance release fixing the v0.1.0 release installation/update path.

Fixed

• Release binaries are now made executable only after SHA256 verification and
  before their --version validation.
• Fixes fresh installation from GitHub Release assets.
• Fixes explicit-version updates from GitHub Release assets.

Included

• Linux Server and Agent for amd64 and arm64
• SHA256 verification
• Atomic installation/update behavior
• Update rollback protection
• Hardened systemd units
• SQLite WAL persistence
• Single-admin monitoring interface

Users should use v0.1.1 instead of v0.1.0 for release-script installation.

All attached binaries are covered by SHA256SUMS.

Monitor v0.1.0

Monitor v0.1.0

Initial public release of Monitor, a small, self-hosted Linux VPS monitoring system.

Highlights

• Lightweight Rust Server and Linux Agent
• Embedded web interface
• CPU, memory, disk, load and network monitoring
• Resource and traffic history
• Daily and billing-cycle traffic accounting
• Up to six ICMP latency targets
• Single-admin authentication
• SQLite WAL persistence
• Hardened systemd services
• Atomic install/update with checksum verification and rollback
• Linux amd64 and arm64 release binaries

Monitor intentionally does not include remote shell/command execution, plugins,
notifications, multi-user/RBAC, remote update daemons, Docker management, or
other remote-control functionality.

Requirements

Linux with systemd. Installation scripts also require curl, sha256sum and
iproute2 (ss).

All binaries in this release are covered by the attached SHA256SUMS.