You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
however, the default protocol for js is http/protobuf (cf. here)
→ unsupported media type errors, as described in #259
works as designed, because telemetry-to-otlp relies on otlp config via env vars. however, bad dx.
"workaround": set env var OTEL_EXPORTER_OTLP_PROTOCOL=grpc
"solution" (this issue): if no env var re protocol is set (general and signal-specific!) but the endpoint config specifies port 4317, set signal-specific protocol config to grpc
The text was updated successfully, but these errors were encountered:
on kyma with cls and kind
telemetry-to-otlp
, we have get this env (exerpt):→ protocol isn't defined
however, the default protocol for js is
http/protobuf
(cf. here)→ unsupported media type errors, as described in #259
works as designed, because
telemetry-to-otlp
relies on otlp config via env vars. however, bad dx.OTEL_EXPORTER_OTLP_PROTOCOL=grpc
4317
, set signal-specific protocol config togrpc
The text was updated successfully, but these errors were encountered: