typelevel / typelevel/keypool

Metrics

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
39
Forks
18
Avg merge
8h 26m
Merged PRs (30d)
4

Description

People want metrics on their pools. We should expose and approach that people can expose their metrics over the state of their pools. Both checked out and checked in keys. And how many are in each state.

  • We need an abstraction that can be leveraged independently by different implementors.
  • We need a concrete implementation (probably epimetheus) consuming this and able to create concrete metrics so other implementors have prior art.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the pool implementation and how checked-out and checked-in keys are represented, then review existing extension patterns before proposing the abstraction. Done means an independently usable metrics abstraction and a concrete implementation exposing counts for both pool states.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
backend, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.