Expose Connection Failure in Metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
## Feature Request
### What problem are you trying to solve?
We had a service which failed to response with a proper connection within 100ms.
### How should the problem be solved?
This should be reflected somehow during metrics to be able to alert for this.
### Any alternatives you've considered?
nope :)
### How would users interact with this feature?
Have a clearly documented way of filtering proxy metrics so that we can alert on exactly the condition of Connection failure due to timeout within 100ms
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 the proxy metrics implementation and its documentation, then determine how connection timeouts are represented and what metric filter would distinguish failures within 100ms; done means the condition is exposed and documented for alerting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100