open-telemetry / open-telemetry/opentelemetry-python
Split timeout to read and connect timeouts in the exporters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
I would like to raise an option to split the timeout using a tuple(as mentioned here https://requests.readthedocs.io/en/latest/user/advanced/)
Is your feature request related to a problem?
No
Describe the solution you'd like
I would like to raise an option to split the timeout using a tuple(as mentioned here https://requests.readthedocs.io/en/latest/user/advanced/)
https://github.com/open-telemetry/opentelemetry-python/blob/a94eab984db6b794cc59cb2c16cd14d804d1eeaf/exporter/opentelemetry-exporter-otlp-proto-http/src/opentelemetry/exporter/otlp/proto/http/trace_exporter/__init__.py#L73
Additional Context
n/a
Would you like to implement a fix?
Yes
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 exporter/opentelemetry-exporter-otlp-proto-http/src/opentelemetry/exporter/otlp/proto/http/trace_exporter/init.py at line 73, then read the linked Requests advanced timeout documentation. Trace how the current timeout option is passed through the exporters; done means accepting separate connect and read timeout values as a tuple.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100