o1-labs / o1-labs/Archive-Node-API
P1: DB pool-saturation metrics (RED metrics landed in #191)
Open
Nobody has claimed this yet.
enhancement
P1
production-readiness
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 9
- Avg merge
- 14h 20m
- Merged PRs (30d)
- 8
Description
Problem
There is no metrics endpoint — only optional Jaeger tracing. We can't see request rate, error rate, latency distribution, or DB pool saturation in production.
Proposal
- Expose Prometheus
/metricswith RED metrics (request rate, errors, duration histogram) and DB pool saturation gauges. - Document scrape config.
Acceptance
/metricsexposes RED + DB pool metrics suitable for alerting/dashboards.
Part of #163.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GraphQL server's existing optional Jaeger tracing and the entry point where HTTP endpoints are exposed. Determine how request metrics and database pool state can be observed; done means /metrics exposes RED and DB pool metrics suitable for alerting and dashboards, with scrape configuration documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100