open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Buffer javaagent logs emitted before logging initialization
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 214
Description
Is your feature request related to a problem? Please describe.
Early javaagent code runs before logging is initialized, so components such as ConfigurationFile and #19584 maintain separate deferred-log state.
Describe the solution you'd like
Add bounded, thread-safe buffering to InternalLogger. Flush buffered records when the selected logger is initialized, while handling disabled or failed logging and avoiding premature JUL initialization.
Describe alternatives you've considered
Keep component-specific queues, as in #19584.
Additional context
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
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 InternalLogger and the deferred-log state in ConfigurationFile, then inspect the discussion and implementation context from PR #19584. Define the buffering and initialization interactions before changing them. Done means bounded, thread-safe records are flushed after logger initialization while disabled or failed logging and premature JUL initialization are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100