OTLP exporters should set User-Agent header as per specification

[pichlermarc]

Is your feature request related to a problem? Please describe.

Currently the User-Agent header is not set by our exporters as defined in the specification.

Describe the solution you'd like

The User-Agent Header should be added as OTel OTLP Exporter JavaScript/<exporter version> in all OTLP exporters.

Additional context

Specification: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#user-agent

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[pichlermarc]

not stale & working on this.

[arminru]

@pichlermarc See open-telemetry/opentelemetry-specification#3052 for the corrected format.

[dyladan]

@pichlermarc any update?

[pichlermarc]

@pichlermarc See open-telemetry/opentelemetry-specification#3052 for the corrected format.

Thanks!

@pichlermarc any update?

@dyladan No, not yet. I did not have time to work on that for a while. Also, it's not a single line change unfortunately.
I'll unassign myself for now in case someone has cycles and wants to pick it up.

Edit: I was not assigned. 😅 Added back the "up-for-grabs" label.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[raphael-theriault-swi]

The header is set for all Node.js exporters as of #4397, but still missing for browser exporters. It would probably make sense to centralize the logic in the otlp-exporter-base package.

[pichlermarc]

@raphael-theriault-swi yep - thanks for pointing that out, I completely forgot about this issue. We don't set the User-Agent it used to be prohibited, but it will still lead to error logs in some browsers so we opted not to do it.

I'm closing this issue as we can consider it done :)