osfd serves no Prometheus metrics #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported from the running system. The operator watches a vLLM Grafana dashboard. vLLM only sees
requests in flight: it cannot see a step running tests rather than calling the model, or a run waiting
on a human for hours. Those numbers live only in osfd, and
GET /metricstoday falls through to thesingle-page-app route and answers
text/html, so a Grafana scrape silently parses a web page.What it should do
Serve the Prometheus text exposition format (
text/plain; version=0.0.4) atGET /metrics, withgauges read off the existing projections:
osf_steps{status=…,kind=…}— step counts, so "running but doing local work" is visibleosf_runs{status=…}— run countsosf_gates_open— gates waiting on a humanosf_step_attempts_max— the highest attempt count of any live step, so a retry storm is a numberThe scrape reads the WAL snapshot and never queues behind the writer (it is scraped every 15 s,
forever). A handler reads projections and never writes.
Acceptance
tests/unit/test_metrics.py(4 tests, currently failing, including a latency test) is thespecification; do not weaken it.
Dogfood #1's brief, filed as an issue. Source:
docs/issues/06-osfd-has-no-prometheus-metrics.md.