Spitfire 0.32.0 release notes
Released: 2026-10-10
- Trace drill-down on the Backend tab: click a test request's trace id to open its spans as a waterfall (service, operation, duration, error, database statement). Spans come from Spitfire's OTLP receiver, otherwise from the run's Tempo or Jaeger connection; when the trace is not found, it says so.
- Where the time went: from the test requests' traces, each load stage shows which service and database the time was spent in (span self time) as a share; the request's time outside the trace (network, load balancer) is its own row. The breaking point finding names the component whose share grew most, with the measured values (e.g. orders-db 12% → 71%). Shares are computed from the sampled (slowest and failed) requests.
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.