Update or uninstall the collector

Updating the collector is one command. Uninstalling is two short tasks — one on the server, one in the dashboard — and skipping either half leaves something behind. Both need a root shell on the server.

Update: re-run the install command

There is no auto-update. To upgrade, re-run the server’s install command — the script downloads the current binary, swaps it in place, refreshes the configuration, and restarts the service. Charts and history continue uninterrupted, and a re-run also re-probes the hardware, which is how the collector picks up drives or Docker installed since the first run. Install the collector covers the details, including where to find your API key if you no longer have the original command.

Uninstall, half one: remove the collector from the server

The install script has no --uninstall flag; removal is five commands.

1. Stop the service and remove it from boot:

   systemctl disable --now monitorable-collector

   Removed "/etc/systemd/system/multi-user.target.wants/monitorable-collector.service".

2. Delete the service unit — it holds the server’s API key — and reload systemd:

   rm /etc/systemd/system/monitorable-collector.service
   systemctl daemon-reload

   From here, systemctl status monitorable-collector answers Unit monitorable-collector.service could not be found.

3. Delete the collector’s four directories — binary, configuration, state, and logs:

   rm -rf /opt/monitorable /etc/monitorable /var/lib/monitorable /var/log/monitorable

4. If the install detected an NVMe drive, it added one udev rule; remove it and reload. On servers without NVMe the file doesn’t exist and the -f makes that a no-op:

   rm -f /etc/udev/rules.d/99-monitorable-nvme-smart.rules
   udevadm control --reload-rules

5. Delete the monitorable system user — this also removes its group:

   userdel monitorable

Nothing else to hunt down: the collector never writes outside the paths above.

Uninstall, half two: remove the server in the dashboard

On the server’s page, open Server actions and click Remove Server, then confirm the prompt: “Are you sure you want to remove this server? This action cannot be undone.”

Caution

Removing a server deletes its metric history with it, and there is no undo. It also revokes the server’s API key on the spot. Re-adding a server with the same name gives you a fresh key and empty charts — history does not carry over.

If you skip one half

The two halves are independent, so each can be forgotten — with a different symptom each way:

• Collector removed, server row left in the dashboard: the row turns Offline and stays there. If an alert template is assigned, the Collector offline rule fires — for a server you meant to decommission. Remove the row.
• Server row removed, collector left running: revoking the API key turns every batch the orphaned collector sends into a rejected one; its log fills with Exporting failed. Dropping data. and HTTP Status Code 401. The collector keeps burning CPU and bandwidth on this until you uninstall it.