-
Notifications
You must be signed in to change notification settings - Fork 812
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
JAEGER_ENDPOINT not supported #1843
Comments
It certainly is possible to deliver traces to a Jaeger collector, since my system does it.
|
Did you mean deliver traces to a collector or an agent? Because if you set JAEGER_AGENT_HOST I assume you're sending the trace data to an agent while I was trying to send it to a collector. |
You're right, my traces get to the collector via an agent. |
One question, does this PR fix this issue? |
I haven't tried it but that was the intention. |
It appears that due to the current way that the dependency (https://github.com/weaveworks/common/blob/master/tracing/tracing.go) works, it's not possible to deliver traces to a Jaeger collector due to the configuration failing if only JAEGER_ENDPOINT is configured.
Maybe it would be useful to just implement the functionality that you get from weaveworks/common instead of depending on it (since that's what is currently breaking this)?
The text was updated successfully, but these errors were encountered: