open-telemetry / open-telemetry/opentelemetry-python-contrib
Wastonx Instrumentation Support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
What problem do you want to solve?
Contribute https://github.com/traceloop/openllmetry/tree/main/packages/opentelemetry-instrumentation-watsonx to opentelemetry
Describe the solution you'd like
https://github.com/traceloop/openllmetry/tree/main/packages/opentelemetry-instrumentation-watsonx
Describe alternatives you've considered
No response
Additional Context
No response
Would you like to implement a fix?
Yes
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 reviewing the linked opentelemetry-instrumentation-watsonx package in traceloop/openllmetry, then compare it with the instrumentation structure in opentelemetry-python-contrib. Done means equivalent watsonx instrumentation is contributed to this repository with appropriate validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100