tower-rs / tower-rs/tower-http
Metrics middleware
Open
Nobody has claimed this yet.
A-new-middleware
- Dominant language
- Rust
- Stars
- 913
- Forks
- 231
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 8
Description
A middleware that provides high level metrics would be really cool.
Should at least cover:
- Requests per second/minute
- Number of in flight requests
- Error rate (this requires the response classification stuff thats being worked here)
- Throughput, bytes per second/minute
At Embark we use prometheus and the metrics crate. But tower-http should probably allow you to use whatever metrics setup you want.
Contributor guide
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 reviewing the metrics middleware request and the response-classification work in tower-http pull request 49. Compare the requested in-flight requests, error rate, throughput, and request-rate metrics with the metrics crate and Prometheus use described in the issue. Done means agreeing on an extensible metrics setup and covering the listed requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, rust
- Domain
- backend-api-design, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100