Removing what you installed
Find what you installed in the table first. The commands run from any folder and end with a check line that shows they worked. The order matters: first the agents in applications and the Collectors on servers, then the Tower, last Spitfire. The Collector script comes from the Tower, the Tower and runner scripts from Spitfire.
| What you installed | Section |
|---|---|
Spitfire (install.sh / install.ps1) |
Spitfire |
| Spitfire setup wizard (setup.exe, .msi, .dmg) | Setup wizards |
| Remote runner | Runner |
| Tower | Tower |
| Server Collector (legacy) | Collector |
| Spitfire Collector (server metrics + APM) | Spitfire Collector |
| OpenTelemetry agents and SDKs in applications | OTel agents |
| Kubernetes monitoring (manifests, RBAC, Helm) | Kubernetes |
| Monitoring users for databases, queues, web servers and so on | Data sources |
Log shipper (logs.sh / logs.ps1) |
Log shippers |
| SSH tunnel | SSH tunnel |
| Gate | Gate |
| Spitfire Recorder (Chrome extension) | Recorder |
Removing something does not delete its record in Spitfire. Close runner, Tower and Gate tokens with Revoke in the UI and delete sources from their lists; otherwise something installed again with the same token keeps connecting. This is the most common case: the server is gone, the token still works. We suggest finishing every removal by revoking the token.
Spitfire
On the machine where Spitfire runs:
~/spitfire/uninstall.sh docker
docker ps -q --filter label=com.docker.compose.project=spitfire | grep -q . || echo "OK: Spitfire removed"If you installed it into Kubernetes (Helm), with the C context and NS namespace of the install:
~/spitfire/uninstall.sh kubernetes --context C --namespace NSWindows (PowerShell):
& "$env:USERPROFILE\spitfire\uninstall.ps1" docker
if (-not (docker ps -q --filter label=com.docker.compose.project=spitfire)) { 'OK: Spitfire removed' }The database and the keys (.env / spitfire-secrets) are kept; install.sh brings everything back. To delete everything add --purge (Windows: -Purge).
--purge deletes the database, SPITFIRE_SECRET_KEY and the backups under backups/;
it cannot be undone. Copy any backup you want to keep out of the folder first.
Setup wizards
Windows, setup.exe: in the Start menu Spitfire → Uninstall Spitfire, or Settings → Apps → Installed apps → Spitfire → Uninstall. It asks before deleting the data. Silent:
& "$env:USERPROFILE\spitfire\windows\uninstall-spitfire.exe" /SAdd
/PURGEat the end to delete the data too. If you installed into another folder (/D=), change the path.Windows, .msi: Uninstall Spitfire in the Start menu, or Installed apps. Silent, with the .msi file you installed from:
Start-Process msiexec -Wait -ArgumentList '/x', "`"$env:TEMP\Spitfire.msi`"", '/qn'Add
'PURGE=1'to the list to delete the data too.Installed with WSL2: the Ubuntu distribution stays; to delete it too,
wsl --unregister Ubuntu-24.04(everything in the distribution is deleted).macOS, Spitfire.dmg: open the Spitfire Installer app again and choose Uninstall (it asks whether to keep the data), then drag the app from Applications to the Trash.
Check (Windows and macOS):
curl -fsS http://localhost:8470/readyz || echo "OK: Spitfire removed"Details: macOS wizard, Windows wizard.
Runner
On the runner server, run the one for the way you installed it. The Uninstalling a runner card at the bottom of the Runners page has the same commands with this Spitfire's address filled in.
| Install | Removal |
|---|---|
install.sh runner (Docker) |
~/spitfire/uninstall.sh runner |
docker run … spitfire-runner |
docker rm -f spitfire-runner |
install-runner.sh (systemd) |
curl -fsSLo /tmp/install-runner.sh https://<spitfire>/api/v1/runner-dist/install-runner.sh and sudo bash /tmp/install-runner.sh --uninstall |
Windows, install.ps1 runner (Docker Desktop) |
& "$env:USERPROFILE\spitfire\uninstall.ps1" runner |
Windows service, install-runner.ps1 |
install-runner.ps1 -Uninstall (administrator PowerShell) |
Check for the Linux service:
test ! -e /usr/local/bin/spitfire-runner && echo "OK: runner removed"--purge / -Purge also deletes the runner's state folder; a Tower's or a Collector's settings on the same server stay in /etc/spitfire (Windows: ProgramData\Spitfire). Then Revoke its key under Runners → Registration keys.
Tower
First remove the Collectors that send to this Tower, then the Tower. Per install:
| Install | Removal |
|---|---|
| Linux (systemd) | sudo bash /tmp/install-tower.sh --uninstall (the script is https://<spitfire>/api/v1/runner-dist/install-tower.sh) |
| Windows service | install-tower.ps1 -Uninstall (administrator PowerShell) |
docker run |
docker rm -f spitfire-tower |
| Beside the controller | ~/spitfire/install.sh docker --tower off |
Compose (~/spitfire-tower) |
docker compose --project-directory ~/spitfire-tower -f ~/spitfire-tower/docker-compose.yml down |
| Helm | Add --set tower.enabled=false --set collector.enabled=false to the installation's helm upgrade |
| Kubernetes manifest | kubectl delete the objects by name (not the namespace) |
The full commands and checks: Tower → Uninstalling; they are also on each Tower's page (Removing this Tower). Last, close the Tower with Revoke.
Server Collector (legacy)
For the separately installed legacy Server Collector (install-collector.sh). If the Spitfire Collector is on the server too, the Spitfire Collector uninstall removes the old one as well. On the Collector's server:
curl -fsSL "http://<tower>:4318/v1/agent/dist/install-collector.sh" -o /tmp/sf-install-collector.sh && sudo bash /tmp/sf-install-collector.sh --uninstall
test ! -e /usr/local/bin/spitfire-collector && echo "OK: Collector removed"Windows (administrator PowerShell):
Invoke-WebRequest -UseBasicParsing 'http://<tower>:4318/v1/agent/dist/install-collector.ps1' -OutFile "$env:TEMP\sf-install-collector.ps1"; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\sf-install-collector.ps1" -Uninstall
if (-not (Get-Service spitfire-collector -ErrorAction SilentlyContinue)) { 'OK: Collector removed' }In Docker: docker rm -f spitfire-collector. If the Tower is gone, download the script from Spitfire: https://<spitfire>/api/v1/runner-dist/install-collector.sh (Windows: .ps1). --purge: Server monitoring → Uninstall.
Spitfire Collector
The Collector that runs server metrics and APM in one install (formerly the APM Collector) goes with one command.
- Linux and macOS (as a user with
sudo):
curl -fsSL https://<spitfire>/api/v1/runner-dist/install-apm-collector.sh | sudo bash -s -- --uninstall- Windows (administrator PowerShell):
& ([scriptblock]::Create((Invoke-RestMethod -UseBasicParsing 'https://<spitfire>/api/v1/runner-dist/install-apm-collector.ps1'))) -Uninstall- Success check. On Linux it prints
OK:
test ! -e /opt/spitfire-apm && test ! -e /etc/spitfire-apm && test ! -e /var/lib/spitfire-apm && test ! -e /usr/local/bin/spitfire-collector && ! systemctl cat spitfire-apm-collector >/dev/null 2>&1 && echo "OK: Spitfire Collector removed"On Windows:
if (-not (Get-Service SpitfireAPMCollector, spitfire-collector -ErrorAction SilentlyContinue)) { 'OK: Spitfire Collector removed' }The command first reverts the settings added to applications, then deletes the service, the settings, the state, the log and anything left from the old Server Collector. To have applications return at once add --restart-apps (Windows: -RestartApps). If you installed it from a setup file:
- Windows, exe: in Installed apps uninstall Spitfire Collector (Spitfire APM Collector on older installs), or silently
& "$env:ProgramFiles\Spitfire\APM\setup\uninstall-apm-collector.exe" /S. - Windows, msi: Installed apps, or
msiexec /x spitfire-apm-collector.msi /qn(with the .msi you installed from). - macOS, dmg: double-click the app in the dmg and press Uninstall (asks for your admin password).
OTel agents and SDKs
The Turning off and removing section on each language's page first turns it off with IS_OTEL_ENABLED=false, then deletes the added files and lines.
- Services: Java, .NET, Node.js, Python, Go, PHP, Ruby, Rust, C++.
- Browser and mobile: HTML, React, React Native, Flutter, Android, iOS.
- Load balancers and proxies: Undoing it.
Kubernetes (operator): delete the annotation and restart the pods, then delete the
Instrumentation resource and the token Secret. <language> is java, dotnet, nodejs or
python:
kubectl patch deployment <deployment> -n <namespace> --type merge -p '{"spec":{"template":{"metadata":{"annotations":{"instrumentation.opentelemetry.io/inject-<language>":null}}}}}'
kubectl rollout restart deployment/<deployment> -n <namespace>
kubectl delete instrumentation <service-name> -n <namespace> --ignore-not-found
kubectl delete secret <service-name>-otel-token -n <namespace> --ignore-not-foundCheck: the new pods have no opentelemetry-auto-instrumentation-<language> init container:
kubectl get pods -n <namespace> -o jsonpath='{.items[*].spec.initContainers[*].name}' | grep -q opentelemetry-auto-instrumentation || echo "OK: agent removed"If you installed the Operator and cert-manager only for this (other teams in the cluster may use them, ask the cluster administrator first):
helm uninstall opentelemetry-operator --namespace opentelemetry-operator-system
helm uninstall cert-manager --namespace cert-managerKubernetes monitoring
The in-cluster Tower and Collectors go into the spitfire namespace, the ClusterRole and ClusterRoleBinding spitfire-collector are cluster-wide. Delete the objects by name and the namespace only when it is empty, as Spitfire's own Helm release may be there too:
Connecting Kubernetes → Undoing it. OpenShift:
Undoing it. The Tower that comes with Spitfire's Helm chart:
Tower → Uninstalling.
Data sources
The setup scripts create a monitoring user and grants, or add lines to configuration files. First delete the source in All integrations, then run the Uninstalling section on the source's page:
- Databases: PostgreSQL, MySQL, SQL Server, Oracle, MongoDB, CouchDB, Redis, Couchbase, Cassandra, InfluxDB, ClickHouse. Db2.
- Queues: Kafka, RabbitMQ, ActiveMQ. Coordination: ZooKeeper, etcd, Consul.
- Java servers, IIS, Web servers, API gateways, HBase, Middleware, IBM, Search, Network and SNMP.
- Cloud: AWS, Azure, GCP, vCenter, MongoDB Atlas, IBM Cloud.
If a script stopped halfway, a state file may be left under ~/.spitfire-setup/; the section covers it.
Log shippers
The shipper installed with logs.sh / logs.ps1 is removed by the same script: SF_ACTION=uninstall
on Linux, $env:SF_ACTION='uninstall' on Windows. The full commands:
Logs → Uninstalling.
SSH tunnel
Nothing is installed on the server. In the connection turn off Connect through an SSH server and save; the SSH secrets are deleted too. Delete the user and the authorized_keys line you created on the SSH server yourself.
Gate
On the Linux server where you installed the Gate:
curl -fsSLo /tmp/install-gate.sh https://<spitfire>/api/v1/runner-dist/install-gate.sh
sudo bash /tmp/install-gate.sh --uninstall
systemctl is-active spitfire-gate || echo "OK: Gate removed"--purge also deletes the Gate's identity on the notification server. Then Revoke the Gate token
on the System → Mobile & Gate page.
Recorder
In Chrome open chrome://extensions and press Remove on Spitfire Recorder; the address and token it saved go with it. Revoke the API token you gave the extension under Profile → API tokens.