K
What is Server monitoring? Getting started Install the agent Metrics collected Uninstall MCP Integration

Uninstall the agent

Updated April 18, 2026

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. Deleting the server from the dashboard is a separate step.

Stop and remove

Run on the host:

TerminalBASH
curl -fsSL https://hyperping.com/install.sh | sh -s -- --uninstall
Service
Stops and disables hp-agent.service on Linux, unloads com.hyperping.agent on macOS.
Unit files
Removes /etc/systemd/system/hp-agent.service or /Library/LaunchDaemons/com.hyperping.agent.plist.
Binaries
Removes files from /usr/local/bin/ and /usr/local/libexec/.
Legacy
Cleans up 0.1.x service files if they exist.

What is kept by default

📘Config, state, and logs are preserved

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:

TerminalBASH
sudo rm -rf /etc/hyperping /var/lib/hyperping /var/log/hyperping

The 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

Dashboard and host are separate

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. Deletion invalidates the agent token server-side, so if the binary is still running it will start logging 401s. Run the uninstaller too.

Reinstall after uninstall

Step 01
Generate a fresh token
Add the server again (or regenerate the install token) from the Servers view.
Step 02
Re-run the installer
Paste the new install command on the host. The new token replaces any cached credential.
Step 03
Confirm in the dashboard
Refresh the Servers view. The server moves back to Reporting within about 30 seconds.