rcmgr: debug logs around blocked resources should come from the same place
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
I think there's some confusing when users look at the blocked resources log from the resource manager. Specifically the logs don't always line up with the metrics. I think the metrics are more accurate because they are being hooked in via the traces, while the logs are ad-hoc throughout the code.
The fix here is to create a trace reporter that consumes the trace event and logs blocked resource events.
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
Start by locating the resource manager's trace events, metrics hooks, and existing blocked-resource log statements. Add the trace reporter described in the issue, then verify that blocked-resource logs come from trace events and align with the metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100