Skip to content

Ingot telemetry #37

Open
Open

Description

@alanshaw

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.

Acceptance criteria:

  • #35 merged.
  • Ingot-specific metrics emitted, namespaced clearly.

Activity

  1. changed the title [-]ms3t telemetry + Grafana dashboards[/-] [+]Ingot telemetry + Grafana dashboards[/+] on Jul 13, 2026
  2. transferred this issue fromfil-forge/sprueon Jul 13, 2026
  3. bajtos commented on Sep 11, 2026

    @bajtos
    Member

    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:

    • GET TTFB (time to first byte)
    • Error rate (4xx, 5xx separately)
    • Total request rate (per operation kind)
    • Ingress / egress bytes
  4. changed the title [-]Ingot telemetry + Grafana dashboards[/-] [+]Ingot telemetry[/+] on Sep 11, 2026
  5. self-assigned this
    on Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions