-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect default url for OTLP HTTP #1078
Comments
Thanks for the report @dyladan! Do you have availability to open a PR with a fix? |
open-telemetry/opentelemetry-specification#2014 changed the default from |
There are probably other discrepancies in the exporter configuration we should look at. I don't think we've kept a close eye on the spec evolution since the original implementation of the exporter. For example, there is some remaining work from #277 (comment) to rename the gem and add support for the |
Correct handling of
opentelemetry-ruby/exporter/otlp/lib/opentelemetry/exporter/otlp/exporter.rb Lines 57 to 61 in 46020cc
My reading of the spec is that "default value" implies "default value assumed for We could potentially restructure the code to make spec conformance clearer. Spec conformance for explicitly set opentelemetry-ruby/exporter/otlp/test/opentelemetry/exporter/otlp/exporter_test.rb Lines 65 to 84 in a8a596f
and spec conformance for the default OTEL_EXPORTER_OTLP_ENDPOINT value is asserted here: opentelemetry-ruby/exporter/otlp/test/opentelemetry/exporter/otlp/exporter_test.rb Lines 14 to 27 in a8a596f
although as mentioned, we haven't implemented the https -> http change from open-telemetry/opentelemetry-specification#2014
|
I think the only change required here is to change the default to |
While doing our due diligence before the 1.0 OTLP Trace Exporter release for JS we noticed that not all exporter implementations follow spec.
Spec states OTLP HTTP should use
http://localhost:4318
by default.Ruby is using
https://localhost:4318/v1/traces
(https should be http): linkThe text was updated successfully, but these errors were encountered: