Scope and requirements

The tested pilot targets are Ubuntu 26.04 Server and Desktop. The collector needs systemd, Python 3.9 or later, CA certificates, an administrator with sudo and outbound HTTPS to the application. Other Linux distributions have not been accepted as supported targets. No Docker or Python package installation is needed for the agent.

Linux 0.9.0 introduced selected-service monitoring. This capability includes resource readings, inventory, APT update visibility and selected systemd service monitoring. Obtain the current release through your deployment's downloads page; this documentation is not an installer mirror.

Install and enroll

Installation is available only through your existing private deployment administrator. Public downloads and enrollment are closed.

Open the configured application's /downloads/ page. Copy its verified installation command into the Ubuntu terminal. That command downloads and checks the release before asking for administrator installation. Use a fresh Linux enrollment code at the hidden prompt. The guided installer can finish without enrollment if you are not ready.

Installation creates an unprivileged background service. The development package is unsigned; a checksum is useful for integrity but is not a publisher signature. Follow your administrator's trust procedure. Never use an insecure TLS bypass.

Check a running installation

These are local diagnostic commands for an installed agent:

fleet-monitor-agent version
sudo fleet-monitor-agent status
sudo fleet-monitor-agent logs
systemctl is-active fleet-monitor-agent
systemctl is-enabled fleet-monitor-agent

Expect a running service, boot startup enabled and a recent server-confirmed check-in. CPU needs two samples after process startup. Closing the terminal does not stop monitoring. If the service is active but confirmation is old, inspect connectivity, certificate trust and the application address before re-enrolling.

Agent updates from the application

Development releases from 0.10.0 add a root systemd updater for agent-update requests from the signed-in application. The ordinary collector keeps its restricted account. Local helper setup and actual application-requested installation have recorded acceptance on the tested platform. Helper startup after reboot and broader lifecycle checks remain separate; this is lab evidence, not production readiness. See agent-update setup and progress.

Stopping the collector does not disable the separate updater. Use the local disable controls if that helper should not poll. It accepts only the configured server's agent-release requests; it does not install OS patches or run arbitrary scripts. Follow the current download page rather than treating an older documented capability version as the latest package.

Update without a new identity

fleet-monitor-agent update --check
fleet-monitor-agent update

The update command verifies the configured server and package and requests sudo when needed. It preserves enrollment. A deliberately stopped service stays stopped during the low-level update flow. Very old releases without an update command need the current verified installer once.

Optional desktop companion

On Ubuntu Desktop, the companion provides connection status, portal access, copyable status and local update controls. Its GTK/AppIndicator dependencies and installation steps are supplied with the deployment. Ubuntu Server needs no GUI libraries. Run the companion as your normal user. Closing its window or quitting its icon leaves the service running; starting the icon at login is separate from starting monitoring at boot.

Troubleshoot and retire

If a service was intentionally stopped, review why before starting it. sudo fleet-monitor-agent start starts monitoring and enables boot startup. stop stops the current run; it does not disable startup at the next boot.

sudo fleet-monitor-agent uninstall removes the service and program while retaining identity. The additional --purge option erases local identity and settings. Use it only when that is intended, and revoke the device in the portal when retiring it. Do not publish the contents of the private state directory.

Upstream reference: systemd service lifecycle.

Remove or retire a device

Follow the platform-specific uninstall guide. Ordinary removal retains enrollment for reinstallation; revoke the device separately in the application when retiring it.