oasisprotocol / oasisprotocol/oasis-core
Expose labels/tags in instrumentation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
prometheus has the concept of adding various metadata / tags/ labels to reported metrics, that it can natively segment / aggregate on.
For some of our classes of metrics, it'll be easier to have a single metric with differentiated metadata, rather than a new time series for each sub-set. We should expose a hook for adding these labels.
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 locating the existing instrumentation and Prometheus metric emission paths in the repository. Determine which metric classes need label support and define what the label hook should expose; done means those metrics can accept differentiated labels without requiring separate time series for each subset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100