Prometheus metrics endpoint for knox nodes #2

New Issue

2026-08-29T12:42:01Z

david commented

2026-08-29 12:42:01 +00:00

Expose a Prometheus /metrics endpoint on knox nodes so the swarm can be monitored.

Decisions:

Use prometheus/client_golang (official text exposition + Go runtime/process collectors)
Serve on a dedicated port via KNOX_METRICS_ADDR (separate from the gossip port)

Metrics:

Gauges (scrape-time DB snapshots): observations by source_id, last-24h observations, entries, projects, sessions, pending reflections, threads by status, peers total, knowledge vector (max hcl per node), observations by origin node
Counters (in-process): gossip pulls/pushes, observations pulled/pushed, gossip errors
knox_node_info{node_id,name} for scrape identification

Everything else (source-of-truth round-trip via reconcile, swarm membership) ships in-and-along the M1-M4 curl.

Expose a Prometheus /metrics endpoint on knox nodes so the swarm can be monitored. Decisions: - Use `prometheus/client_golang` (official text exposition + Go runtime/process collectors) - Serve on a dedicated port via `KNOX_METRICS_ADDR` (separate from the gossip port) Metrics: - Gauges (scrape-time DB snapshots): observations by source_id, last-24h observations, entries, projects, sessions, pending reflections, threads by status, peers total, knowledge vector (max hcl per node), observations by origin node - Counters (in-process): gossip pulls/pushes, observations pulled/pushed, gossip errors - `knox_node_info{node_id,name}` for scrape identification Everything else (source-of-truth round-trip via reconcile, swarm membership) ships in-and-along the M1-M4 curl.

david referenced this issue from a commit

2026-08-29 13:06:57 +00:00

feat: Prometheus metrics endpoint for knox nodes

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: david/knox#2