letsencrypt / letsencrypt/boulder
Add channelz listener
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
I'm troubleshooting an issue where I added an A record for a new SA server to the existing SA service record, but SA clients did not automatically start using that new SA server. I've traced this through grpc call metrics, but perhaps a tool like channelz would better be able to show what grpc clients are connected to what grpc servers?
I don't believe we'd need the web ui portion of this, but we would need to carefully craft grpc-curl invocations to authenticate.
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 repository files, tests, or entry points. Start by reading the linked Channelz introduction and reviewing the existing gRPC client/server metrics; done means exposing enough connection information to identify which clients connect to which servers without requiring the web UI, with authenticated grpc-curl usage considered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100