bug: websocket latency metrics incorrectly mention nanoseconds
Open
- Dominant language
- Rust
- Stars
- 17
- Forks
- 2
- Avg merge
- 17d 19h
- Merged PRs (30d)
- 1
Description
it's microseconds instead
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the websocket latency metrics implementation for the text that says nanoseconds and inspect how the unit is reported. Update the incorrect unit to microseconds, then run the relevant test or metrics check if one exists and confirm the reported latency unit is correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100