Uninstall the agent
The same installer script removes the Hyperping agent when you pass --uninstall. The service is stopped and deregistered and the binaries are removed, but configuration and state stay on disk so you can reinstall without losing the agent token. Removing the server from the dashboard or rotating its credential are separate actions.
Uninstall (this page) is a host-side action — it stops the service on that machine. Revoke invalidates the agent's credential server-side without removing the server row. Delete hard-removes the server row and frees its quota slot. They compose: if you're decommissioning a host, the clean sequence is uninstall, then delete.
Stop and remove
Run on the host:
curl -fsSL https://hyperping.com/install.sh | sh -s -- --uninstallhp-agent.service on Linux, unloads com.hyperping.agent on macOS./etc/systemd/system/hp-agent.service or /Library/LaunchDaemons/com.hyperping.agent.plist./usr/local/bin/ and /usr/local/libexec/.What is kept by default
The uninstaller leaves /etc/hyperping/ (including the agent token), /var/lib/hyperping/, and /var/log/hyperping/ untouched. If you plan to reinstall on the same host, keeping these in place lets the agent come back online without re-enrolling.
Fully remove everything
To purge all Hyperping files:
sudo rm -rf /etc/hyperping /var/lib/hyperping /var/log/hyperpingThe hyperping system user on Linux is harmless, but you can remove it with sudo userdel hyperping if your compliance policy requires it.
Remove from the dashboard
Uninstalling is a host-side action. To remove the server entry and stop billing for that slot, open the Servers view, open the server, and click Delete server. Deletion invalidates the agent token server-side, so if the binary is still running it will start logging 401s. Run the uninstaller too.
Rotate the credential without uninstalling
If you only need to rotate the host's agent token — for example after suspected compromise of /etc/hyperping/agent.env — use Revoke agent from the server menu instead. The server row stays, the running binary starts 401-ing, and re-running the installer with a new install token brings the host back with a fresh credential and the same UUID (so metric history is preserved). See Re-enrollment.
