open-telemetry / open-telemetry/opentelemetry-java-instrumentation

Should agent return a ComponentLoader from ExtendedOpenTelemetry?

Open
#15,406 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs triage
Dominant language
Java
Stars
2.6k
Forks
1.2k
Avg merge
2d 18h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.

Right now, agent throws an exception

Describe the solution you'd like

We need to discuss https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/15178#discussion_r2543069447

Describe alternatives you've considered

No response

Additional context

No response

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the discussion linked from PR 15178, then trace how ExtendedOpenTelemetry handles the agent case that currently throws an exception. Done means the expected ComponentLoader behavior is agreed and the agent no longer throws for that case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.