open-telemetry / open-telemetry/opentelemetry-python-contrib
Avoid duplicate telemetry while using langchain instrumentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
As langchain and underlying library supporting telemetry can both emit telemetry producing duplicate data. One of the telemetry can be suppressed, please see discussion in the comments here:
https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3665#discussion_r2341713191
https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3665#issuecomment-3259366086
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 with the linked discussion in pull request 3665 and its issue comment to understand which LangChain and underlying-library telemetry is duplicated. Trace the relevant instrumentation entry points, then verify that the chosen telemetry is emitted only once while using LangChain instrumentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100