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

[Feature]: Allow hotrod export traces to other collectors, such as OTLP #462

Closed
fernferret opened this issue Mar 24, 2023 · 0 comments · Fixed by #463
Closed

[Feature]: Allow hotrod export traces to other collectors, such as OTLP #462

fernferret opened this issue Mar 24, 2023 · 0 comments · Fixed by #463
Labels
enhancement New feature or request

Comments

@fernferret
Copy link
Contributor

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

Open questions

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant