Upgrade and uninstall

Upgrading

Re-run the installer. It replaces the binary and restarts the service, and the server keeps its identity, its history and its thresholds.

curl -fsSL https://dev.uptimecraft.com/install.sh \
  | UPTIMECRAFT_ENROLLMENT_TOKEN=uc_enroll_... sh

You need a token for the command, but on an already-enrolled machine nothing is enrolled — the existing key is used. A short-lived token is fine for this.

To pin a version:

UPTIMECRAFT_VERSION=0.2.0 UPTIMECRAFT_ENROLLMENT_TOKEN=... sh

The server's page shows the running version and says so when a check needs a newer agent than the one installed.

It does not update itself

Deliberately, and we do not intend to change it.

A self-updating agent means every customer's fleet runs whatever we published this morning. One bad release would then take out monitoring everywhere at once — including the monitoring you would use to notice. It also makes us an attractive target: compromise our release pipeline and you have root on a lot of other people's servers, with no step in between where anyone could notice.

Instead the agent is a normal package. Your configuration management upgrades it when you decide, which is also the answer your auditors want.

The cost is that an old agent stays old. We keep agents working across versions rather than requiring upgrades, and a check that needs a newer one says so on the page instead of failing quietly.

Uninstalling

curl -fsSL https://dev.uptimecraft.com/uninstall.sh | sh

It stops and disables the service, removes the unit file, the binary, the configuration directory including your token, the state directory, and the uptimecraft system user.

It does not touch the dashboard. Revoke the server there as well, or you leave an entry that counts against your allowance and reports nothing.

To do it by hand:

systemctl disable --now uptimecraft-agent
rm -f /etc/systemd/system/uptimecraft-agent.service
rm -f /usr/local/bin/uptimecraft-agent
rm -rf /etc/uptimecraft /var/lib/uptimecraft
systemctl daemon-reload
userdel uptimecraft

Removing the data

Revoking stops collection; the history stays until retention expires. If you need it gone sooner than that, ask support and we will delete it.