liquidmetal-dev / liquidmetal-dev/flintlock
Expose flintlock metrics
Open
Nobody has claimed this yet.
lifecycle/stale
priority/important-soon
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
Expose flintlock specific metrics so that they can be scraped by prom (or something else).
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
The issue names no files, tests, or entry points. Start by locating where Flintlock exposes its services and whether any metrics instrumentation already exists, then determine the Prometheus scraping approach; done means Flintlock-specific metrics are available for Prometheus or another scraper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100