opentelemetry-exporter-otlp-proto-http: Update exporter to use new HTTP transport package#5219
opentelemetry-exporter-otlp-proto-http: Update exporter to use new HTTP transport package#5219herin049 wants to merge 21 commits into
Conversation
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
Sorry for the delay, this is still dependent on this PR: #5252 due to the decision to isolate the Once #5252 is merged, then it will unblock a lot of work. (e.g. finishing the OTLP JSON exporter and generalizing the OTLP HTTP exporter) |
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
|
superseded by #5389 |
Description
This PR updates the
opentelemetry-exporter-otlp-proto-httppackage to switch to using the abstractions/utilities added in theopentelemetry-exporter-http-transportpackage. Notably, this involves switching to the sharedOTLPHTTPClientclient (reducing code duplication between exporters), and adding an optional, private_transportargument that accepts an arbitrary transport implementation. These changes also switch to usingurllib3as the default transport, unless the user specifies otherwise, either by directly passing arequestsSession, initializing the_OTEL_PYTHON_EXPORTER_OTLP_HTTP_CREDENTIAL_PROVIDERenvironment variable or directly passing a custom transport via the_transportkeyword argument.Fixes #3439, #4171, #2990
Depends on #5194
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Contrib Repo Change?
Checklist: