Operations

Multi-server monitoring

See application state across one server or an entire Phelix fleet.

Monitor daemon

phelix monitor is a long-running, persistent gRPC daemon that keeps one machine synchronized with the Phelix backend:

  • Restores the managed apps that were previously running (auto-start applications).
  • Opens a single long-lived, TLS-secured gRPC stream to the Phelix backend.
  • Streams application status, resource metrics, and logs to the central server roughly every 2 seconds.
  • Reconnects automatically with exponential backoff if the connection is lost.
  • Provides real-time updates for every managed application across the fleet.
Terminal
phelix monitor

Service lifecycle

The daemon runs in the foreground and stays attached to the terminal when invoked manually. On Linux it is normally supervised directly by the systemd unit created by the installer — there is no backgrounding shell wrapper.

Terminal
sudo systemctl start phelix
sudo systemctl restart phelix
sudo systemctl stop phelix
sudo systemctl status phelix
sudo journalctl -u phelix -f

Server fleet

  1. 1
    Register
    Each server authenticates and opens its TLS-secured gRPC stream to the central service.
  2. 2
    Report
    Servers stream application status, resource metrics, and logs roughly every 2 seconds.
  3. 3
    Synchronize
    The dashboard unifies updates while each server retains local application state.

Requirements

Ensure internet access for authentication and monitoring, sufficient filesystem/process permissions, and network connectivity between participating servers.