You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instrument Ingot to emit the metrics only Ingot can provide: MST traversal depth and round trips per PUT, as an operator-facing cost signal, and total request rate per S3 operation kind, which Caddy can't tell apart. The request-rate panel is FIL-1280. This serves the story that operators see Forge metrics and alerts in Grafana. Where it costs nothing, match the metric naming in fil-one/fil-one.
Decided 2026-09-22: GET TTFB, error rate (4xx, 5xx) and ingress/egress bytes come from Caddy, and the FIL-1208 dashboard already reads them there. Depends on #37, which defines the paths to instrument.
In my opinion, we should collect these metrics from Caddy, not Ingot, so that we incidents where Caddy cannot reach the upstream service and returns 502 error:
Activity
[-]ms3t telemetry + Grafana dashboards[/-][+]Ingot telemetry + Grafana dashboards[/+]bajtos commentedon Sep 11, 2026
In my opinion, we should collect these metrics from Caddy, not Ingot, so that we incidents where Caddy cannot reach the upstream service and returns 502 error:
[-]Ingot telemetry + Grafana dashboards[/-][+]Ingot telemetry[/+]