Repository navigation
Add per-server metrics and a Prometheus endpoint - #6
Merged
Merged
Conversation
Derive tool-call metrics from the audit log with one aggregation query shared by PostgreSQL and SQLite: outcome counts per upstream and a fixed latency histogram from 5 ms to 15 s. The gateway serves Prometheus metrics on a separate in-cluster port (gateway.metrics.port, default 9464) that the Ingress does not route: call counters by outcome, a latency histogram, and upstream up, status and last-failure gauges. The pod carries prometheus.io scrape annotations. Administrators see each server's calls, error rate and average and p95 latency for the last 24 hours on its Connections card and at GET /api/metrics?hours=<1-168>. Members do not receive team-wide metrics.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Derive tool-call metrics from the audit log with one aggregation query shared by PostgreSQL and SQLite: outcome counts per upstream and a fixed latency histogram from 5 ms to 15 s.
The gateway serves Prometheus metrics on a separate in-cluster port (gateway.metrics.port, default 9464) that the Ingress does not route: call counters by outcome, a latency histogram, and upstream up, status and last-failure gauges. The pod carries prometheus.io scrape annotations.
Administrators see each server's calls, error rate and average and p95 latency for the last 24 hours on its Connections card and at GET /api/metrics?hours=<1-168>. Members do not receive team-wide metrics.