fprintf(stderr) output not captured in observer.log during initial startup
Open
Nobody has claimed this yet.
dima
type: task
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Description
During the initial startup phase, when the log file is first opened, the standard error stream (STDERR) is not redirected to the log file. The redirection of STDERR only occurs during subsequent log rotation. Consequently, any content printed to STDERR (e.g., via fprintf(stderr, ...)) before the first log rotation is not captured in the observer.log file.
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 identifies initial startup log opening and later log rotation as the relevant phases, but names no files, tests, or entry points. Trace STDERR redirection in those phases and verify that fprintf(stderr, ...) output before the first rotation appears in observer.log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100