Spitfire 0.71.0 release notes
Released: 2026-11-02latest
- Tower install on every platform: the New Tower dialog gives the install command for Linux (install-tower.sh, a systemd service), Windows (install-tower.ps1, a Windows service), Docker and Helm with the token and the controller address filled in; the install waits for the Tower to connect and stops on a rejected token. install.sh docker --tower on and Helm's tower.enabled / collector.enabled bring a Tower and a Collector reading the host with the installation. Mobile notifications can now go through a Tower too (--push).
- The Spitfire Collector image: usespitfire/spitfire:<version>-collector, an OpenTelemetry Collector built with only the components Spitfire uses. The Collector config wizard also adds MySQL/MariaDB, SQL Server, Oracle, Redis and MongoDB servers and Prometheus endpoints; passwords go into environment variables, not the config. Docs: Towers and metrics → Other databases and Prometheus endpoints.
- Connect a service (OTel): the wizard on the Towers page asks for the language and runtime version, the addresses, keys and service name; the Java, .NET, Python, Node.js and PHP guides open with those values and the version's packages written in. Every guide has Linux (systemd), Docker, Kubernetes and Windows steps and IS_OTEL_ENABLED=true/false to switch it on and off; the pre-release checks apply the guides as written with sample services. Docs: Connecting services with OTel.
- The System page (/system, installation admin): the Towers and the last day of every server, database and service in hourly summaries with a status (busy, no readings) on one page. The guard now takes a server CPU limit too: when the chosen servers' CPU crosses it the load steps down, over the stop limit the run stops; the report names the server and its value (with the monitoring events module or its trial). Docs: System.
- External inputs: tools sending Alertmanager, Grafana alerting or generic JSON alerts can post them to Spitfire or to a Tower with their own sfhook_ token; the alerts show on the events of the run reports they overlap, resolved ones close. A Tower can optionally count syslog messages and SNMP v1/v2c traps per host and severity (messages are not kept, only counts). Docs: Towers and metrics → Webhook inputs, Syslog and SNMP traps.
Updating
Your installation tells you about a new release itself: admins see its notes and the update command for that installation at the top of the UI. The command backs up the database first and keeps the settings (Updating). You can also follow new releases with the RSS feed.