Upgrading the Fivenines agent

The fivenines agent does not auto-update, by design. It is a push-only binary with no remote-control channel, so nobody, including fivenines, can change what runs on your servers. You decide when an upgrade happens, and it happens with one command.

Upgrading downloads the latest release, replaces the binary, and restarts the service. Your token and configuration are preserved: you never need to re-enroll a host.

Check your current version

• Dashboard: each host page shows the agent version it is running. When a newer release is available, the host page shows an upgrade prompt with the exact command for that host's install type.

• On the server: fivenines-agent --version

Upgrade a Linux host (system install)

wget -T 3 -q https://releases.fivenines.io/latest/fivenines_update.sh && sudo sh fivenines_update.sh

The script detects your architecture (amd64/arm64) and libc (glibc or musl), downloads the matching build from releases.fivenines.io (with GitHub as a fallback mirror), stops the service, replaces the binary, refreshes the service definition, and restarts it. Works with systemd and OpenRC (Alpine). Your token in /etc/fivenines_agent/TOKEN is untouched.

Upgrade a Linux host (user-level install, no sudo)

wget -T 3 -q https://releases.fivenines.io/latest/fivenines_update_user.sh && sh fivenines_update_user.sh

Updates an agent installed under ~/.local/fivenines and restarts it. It requires the existing installation and reuses its token.

Upgrade a Windows host

In PowerShell as Administrator:

iwr -UseBasicParsing https://releases.fivenines.io/latest/fivenines_update.ps1 | iex

The script downloads the latest MSI and lets the Windows Installer upgrade machinery do the rest: the old service is stopped and removed, files are replaced, the service is re-registered under its dedicated local service account, and your existing token is reused. It requires an existing installation; for a fresh install use fivenines_setup.ps1 -Token <token>.

Upgrade a Synology NAS

Each release publishes .spk packages (x86_64 and aarch64). Download the new package from the release page and install it through Package Center; the upgrade replaces the previous version in place.

Verify the upgrade

The service restart takes a few seconds, so at most one collection tick is skipped. Within about a minute the host page shows the new agent version and the upgrade prompt disappears.

Locally:

• fivenines-agent --version

• Linux (system): systemctl status fivenines-agent, or rc-service fivenines-agent status on Alpine

Keep a whole fleet up to date

• The dashboard flags every host running an outdated agent, with the command ready to copy.

• The Agent Outdated workflow trigger can notify you or open an incident while any host runs an agent older than the current release, with an optional minimum-version override. The quickest setup is the "Agent Update Required" workflow template.

Which version do I need?

Monitoring modules require a minimum agent version. If you enable a module the host's agent cannot provide yet, the dashboard tells you which version to reach.

Release notes for every version are on the releases page: https://github.com/Five-Nines-io/fivenines_agent/releases. The agent is open source, so you can review exactly what each release changes.

Pin or roll back a version

Every build is published as a GitHub release asset. To install a specific version, point the update script at it:

FIVENINES_AGENT_URL="https://github.com/Five-Nines-io/fivenines_agent/releases/download/v1.8.1/fivenines-agent-linux-amd64.tar.gz" sudo sh fivenines_update.sh

Use the -alpine- assets for musl systems and -arm64 for ARM hosts.

Questions

If an upgrade misbehaves, contact support@fivenines.io with the host name and the script output.