Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

add TLS config options for jaeger exporter

See original GitHub issue

Is your feature request related to a problem? Please describe. The jaeger exporter of openTelemetry-collector could be configured to disable TLS, but the openTelemetry JVM agent has no such an option to disable TLS.

example config for openTelemetry-collector

    exporters:
      jaeger:
        endpoint: jaeger-collector.jaeger:14250
        tls:
          insecure: true

Describe the solution you’d like It would be nice to have options to disable TLS. for example: System property: otel.exporter.jaeger.tls.insecure: true|false

environment variables: OTEL_EXPORTER_JAEGER_TLS_INSECURE=true|false

Additional context Add any other context or screenshots about the feature request here.

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

dawnbreakscommented, Mar 23, 2022

Thanks for pointing that out @dawnbreaks I will update the jaeger image we mirror in for our tests. Though I tried replacing the image with jaegertracing/all-in-one:1.32 in the integration test locally and it seems to pass so still not sure where we might have a bug

Thanks for your help. I have resolved this issue, and my applications are running on istio, i misconfigured the port name of the jaeger k8s service as HTTP, the sidecar cann’t proxy the request properly. after i rename the port name from HTTP to grpc, it works well. Sorry for inconvenience.

0reactions

anuraagacommented, Mar 23, 2022

Thanks for pointing that out @dawnbreaks I will update the jaeger image we mirror in for our tests. Though I tried replacing the image with jaegertracing/all-in-one:1.32 in the integration test locally and it seems to pass so still not sure where we might have a bug

Top Results From Across the Web

Deployment — Jaeger documentation

configuration files in JSON, TOML, YAML, HCL, or Java properties formats. To see the complete list of options, run the binary with help...

Configuration | OpenTelemetry

Exporters may come with default settings, but many require configuration to specify at least the destination and security settings. Any ...

Introducing native support for OpenTelemetry in Jaeger

Using the OTLP exporter, the SDKs can be configured to send the data directly to the Jaeger backend. The OTLP receiver accepts data...

Configuring and deploying distributed tracing data collection

Exporters may come with default settings, but many require configuration to specify ... jaeger-production-collector-headless.tracing-system.svc:14250 tls: ...

Distributed tracing OpenShift Container Platform 4.7

spec: mode: deployment config: | exporters: jaeger: endpoint: ... Option to enable TLS when sniffing an Elasticsearch Cluster. The client uses the sniffing ......