letsencrypt / letsencrypt/boulder
Capture stdout / stderr to logger
Open
Nobody has claimed this yet.
area/libraries
kind/enhancement
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Similar to #4664, we should capture stdout / stderr, even when written to outside of the stdlib log package (for instance, panics). Some example code at https://github.com/golang/go/issues/325.
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
Start by reading issue #4664 and the linked Go issue #325 for the proposed stdout/stderr capture approach. Identify how Boulder initializes logging and where process output, including panics, currently bypasses the stdlib log package. Done means that output is captured and delivered to the logger without losing the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100