Repository navigation
use and honor OTEL_EXPORTER_OTLP_PROTOCOL #142
Description
In the review of #138 @cyrille-leclerc notes that when merged, otel-cli will be oblivious to OTEL_EXPORTER_OTLP_PROTOCOL, so it's possible for a user to set that envvar in conflict with otel-cli's assumptions, and create a broken situation.
To resolve this, otel-cli will need to support the OTEL_EXPORTER_OTLP_PROTOCOL variable and variants itself, and prioritize them over the rules documented in the README. This will allow for grpc to use http endpoints cleanly according to the spec, while allowing otel-cli to deviate a bit to provide a clearer UX to command-line users.
I'm going to merge #138 and will take care of this before releasing v0.1.0 (next release) so the behavior is set and consistent going forward.
Activity
update opentelemetry SDK to 1.11.2 (#138)
cyrille-leclerc commentedon Jan 27, 2023
Thank you very much @tobert. Some use cases I have in mind to NOT use
grpcfor OTLP:add http testing (#143)
tobert commentedon Jan 30, 2023
It looks like opentelemetry-go does not support JSON export over OTLP. I'm going to remove mentions and hints at support for it so we just have http/protobuf and grpc. If folks really want/need http/json we'll have to implement it manually in otel-cli.
cyrille-leclerc commentedon Jan 30, 2023
Thanks @tobert !
From what I understood, OTLP on
http/jsonis primarily used for RUM use cases, for the opentelemetry-js SDK (see exporter-trace-otlp-http and opentelemetry-exporter-metrics-otlp-http).http/protobufis more for server side usage, when GRPC is not supported.#142 follow spec for OTLP protocol (#148)
tobert commentedon Feb 2, 2023
I believe this is solved in the v0.1.0 release :) Please reopen if I missed something important.
https://github.com/equinix-labs/otel-cli/releases/tag/v0.1.0