As a user learning about distributed tracing and OpenTelemetry I want to be able to send the hotrod traces to an OpenTelemetry Collector so they can be routed back to Jaeger.
This would let me verify my OpenTelemetry Collector is setup correctly and be able to see the same flow for my production applications. This will also allow users to learn more about various sampling strategies that exist within the OpenTelemetry Collector.
The JAEGER environment variables are currently added to the chart by default.
Proposal
I propose the helm chart allow arbitrary extraArgs and extraEnv objects like the rest of the helm charts. This would enable users to configure not only custom exporters but also other arguments such as --jaeger-ui
Requirement
As a user learning about distributed tracing and OpenTelemetry I want to be able to send the hotrod traces to an OpenTelemetry Collector so they can be routed back to Jaeger.
This would let me verify my OpenTelemetry Collector is setup correctly and be able to see the same flow for my production applications. This will also allow users to learn more about various sampling strategies that exist within the OpenTelemetry Collector.
Problem
The OpenTelemetry SDK has already been added to hotrod and is available via a command line flag (
--otel-exporter=otlp), but this is not able to be exposed in this helm chart.The JAEGER environment variables are currently added to the chart by default.
Proposal
I propose the helm chart allow arbitrary
extraArgsandextraEnvobjects like the rest of the helm charts. This would enable users to configure not only custom exporters but also other arguments such as--jaeger-uiOpen questions
No response