traceloop / traceloop/openllmetry
๐ Bug Report: Watsonx hardcoded values
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this bug for?
Watsonx Instrumentation
๐ Description
Some variables, showing in traceloop traces, are hardcoded.
For example, even if hitting watsonx in frankfurt, it shows that it's using https://us-south.ml.cloud.ibm.com, which is incorrect.
๐ Reproduction steps
Create a python script using watsonx in frankfurt for example, and see that in the traces it shows https://us-south.ml.cloud.ibm.com, as hardcoded in packages/opentelemetry-instrumentation-watsonx/opentelemetry/instrumentation/watsonx/init.py line 103
๐ Expected behavior
It should show the real parameter istead of harcoded ones.
๐ Actual Behavior with Screenshots
๐ค Python Version
3.12
๐ Provide any additional context for the Bug.
No response
๐ Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None
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
Inspect packages/opentelemetry-instrumentation-watsonx/opentelemetry/instrumentation/watsonx/init.py around line 103 and trace how the Watsonx endpoint is obtained for instrumentation. Reproduce with a Frankfurt configuration and confirm the trace reports the configured endpoint rather than the hardcoded us-south URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100