Skip to content
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

default to grpc on kyma #272

Open
sjvans opened this issue Jan 7, 2025 · 0 comments
Open

default to grpc on kyma #272

sjvans opened this issue Jan 7, 2025 · 0 comments
Labels

Comments

@sjvans
Copy link
Contributor

sjvans commented Jan 7, 2025

on kyma with cls and kind telemetry-to-otlp, we have get this env (exerpt):

  - name: OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
    value: http://telemetry-otlp-traces.kyma-system.svc.cluster.local:4317/
  - name: OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
    value: http://telemetry-otlp-metrics.kyma-system.svc.cluster.local:4317/

→ 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.

  • "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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant