Flightcontrol incident

Backend errors when trying to use Grafana to view logs

Notice Resolved View vendor source →

Flightcontrol experienced a notice incident on March 23, 2026 affecting Logs, lasting 1h 9m. The incident has been resolved; the full update timeline is below.

Started
Mar 23, 2026, 03:18 PM UTC
Resolved
Mar 23, 2026, 04:27 PM UTC
Duration
1h 9m
Detected by Pingoru
Mar 23, 2026, 03:18 PM UTC

Affected components

Logs

Update timeline

  1. investigating Mar 23, 2026, 03:18 PM UTC

    Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use `fly logs` or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.

  2. identified Mar 23, 2026, 03:41 PM UTC

    Using the Logs panel in Grafana at https://fly-metrics.net/ will show a 502 error from the backend and won't show any logs. You can use `fly logs` or the live log viewer directly on https://fly.io/dashboard to view streaming logs for the time being.

  3. monitoring Mar 23, 2026, 03:55 PM UTC

    We've deployed a fix and are monitoring the results. Logs are now be visible on Grafana.

  4. resolved Mar 23, 2026, 04:27 PM UTC

    This incident is resolved, Grafana logs are now working properly.