michaelfeil / michaelfeil/infinity
Better Prometheus metrics: Idea collection thread
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
### Feature request
So far, Prometheus metrics collected are performed via `prometheus-fastapi-instrumentator`.
### Motivation
The idea would be, to improve better tracing that is more tailored to the actual workload & routes / capabilities of the embed / rerank / classify endpoint.
### Your contribution
Looking for contributors & active users in prod that have ideas for better metric endpoints.
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
Review the current prometheus-fastapi-instrumentator usage and the embed, rerank, and classify endpoints mentioned in the issue. The thread does not name files or tests, and work is not ready to start until the desired metrics and implementation scope are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, prometheus, python
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100