Useful for metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
This is very simple, but I like it.
I think metrics can also be done this way. On large deployment foot print projects fixing a bug can require putting in a metric to watch it in production.
I also like the idea of putting in alarms and weightings in the code.
The devops team can't know what to measure at the application level. They only know high level generic things they need to measure.
What do people think of develops being able to describe these aspects in the code at design time ??
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
The issue does not name any files, tests, or entry points. Start by reviewing the repository structure and existing instrumentation, then clarify the proposed metric, alarm, and weighting model before implementation; completion criteria are not defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100