OTLP HTTP Exporter should append v1/{signal} to the endpoint URL when non-per-signal env var is used

[reese-lee]

Per the spec re: Endpoint URLs for OTLP/HTTP, when the non-per-signal endpoint env var (OTEL_EXPORTER_OTLP_ENDPOINT) is set, the exporter must construct per-signal URLs (either v1/traces or v1/metrics).

Currently, the exporter does not do this; v1/traces must be manually added to the end point when setting only OTEL_EXPORTER_OTLP_ENDPOINT. Not doing so produces a 404 error when attempting to export spans.

[flyinprogrammer]

😅 i thought i was going crazy, i can submit a PR to make this bit smarter, it might be considered a breaking change though 😢 so idk what all will be involved in merging this.

[reese-lee]

@flyinprogrammer I wanted to see if you plan on submitting a PR for this? I'd like to take a stab at it with my colleague otherwise. :)

[flyinprogrammer]

By all means submit one, I am swamped at work right now!

…

On Thu, Feb 24, 2022, 5:53 PM Reese Lee ***@***.***> wrote: @flyinprogrammer <https://github.com/flyinprogrammer> I wanted to see if you plan on submitting a PR for this? I'd like to take a stab at it with my colleague otherwise. :) — Reply to this email directly, view it on GitHub <#2443 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOCM36KQKUASP6X5E7UY4DU43AGHANCNFSM5NTH35EQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[reese-lee]

Thank you for the update! @TylerHelmuth and I will work on a PR for this.