2.0 KiB
Pegasus Monitor 1.2.0 (build 3)
Changes
- Generic Linux agent reports discovered systemd service states: running, stopped, failed, disabled, not installed, and unknown.
- Optional services not installed do not count as failures.
- Per-server Required service toggles; any required service not reported as running is a failure.
- Service list in the menu bar, and discovery controls in the independent Settings window.
- Required services persist in existing server profiles; profiles from 1.1 migrate without losing connections.
- Manually add required units if no agent discovery has been performed.
- Existing Pegasus specialised agent and its health checks remain supported (service discovery requires updated generic agent).
Deploy updated Linux agent
From the macOS project folder, replace mag@REMOTE_HOST with the SSH login for the target server:
scp server/remote-health-json mag@REMOTE_HOST:/tmp/pegasus-monitor-health-json
ssh mag@REMOTE_HOST 'sudo install -m 755 /tmp/pegasus-monitor-health-json /usr/local/bin/pegasus-monitor-health-json'
ssh mag@REMOTE_HOST '/usr/local/bin/pegasus-monitor-health-json'
In the Settings window, point the server's remote command to /usr/local/bin/pegasus-monitor-health-json, refresh services and save required services. Keep Pegasus's original sudo -n /usr/local/bin/pegasus-health-json for its 72 specialised checks; it does not report the new per-service inventory.
Safety and expected behaviour
The Linux health agent is read-only; it does not install, start or stop services. Service discovery uses systemctl show on an allowlisted collection of commonly-used units. unknown indicates discovery could not establish a state and is not treated as installed or running. Required services that are missing, disabled, stopped, failed, unknown or unreported count as failures.
Apple notarization is only attempted by the release script on macOS with a valid configured orion-notary profile. No notarized DMG is included here.