feat(opentelemetry-node): add user agent header in all exporters & honour env vars for TLS in HTTP export#1104
Conversation
Summary of changes:
0.206.0 -> 0.207.0 @opentelemetry/exporter-logs-otlp-grpc (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/exporter-logs-otlp-http (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/exporter-logs-otlp-proto (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/exporter-metrics-otlp-grpc (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/exporter-metrics-otlp-http (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/exporter-metrics-otlp-proto (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/instrumentation-grpc (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/instrumentation-http (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/sdk-logs (range-bump)
0.206.0 -> 0.207.0 @opentelemetry/sdk-node (range-bump)
2.1.0 -> 2.2.0 @opentelemetry/core
2.1.0 -> 2.2.0 @opentelemetry/resources
2.1.0 -> 2.2.0 @opentelemetry/sdk-metrics
|
|
|
last version of I'll debug this in a separate branch. |
|
@trentm Although I can merge now I think this needs another review from you. Thanks |
|
|
||
| // Setting the User-Agent for exporters created by EDOT Node.js. | ||
| // | ||
| // Eventually the upstream exporters will support an option for this |
There was a problem hiding this comment.
Note for reviewer: this is something to discuss. By keeping the patch we will have the UA header even if exporters are provided by the user. Removing the patch means we need to resolve exporters (like the upstream SDK already does) and set the UA when instantiating them. There will be no EDOT reference in the UA header is exporters are provided by the user.
|
Thanks! |
Co-authored-by: Trent Mick <trent.mick@elastic.co>
This PR updates the core packages which include a couple of fixes
It also restores the upstream GCP resource detector from upstream contrib repository since the fixes prevent internal spans to be exported to the collector.
Closes: #961
Closes: #1017
Summary of changes: