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

JAEGER_ENDPOINT not supported #1843

Closed
kvaidas opened this issue Nov 20, 2019 · 6 comments
Closed

JAEGER_ENDPOINT not supported #1843

kvaidas opened this issue Nov 20, 2019 · 6 comments
Labels
good first issue These are great first issues. If you are looking for a place to start, start here! hacktoberfest help wanted

Comments

@kvaidas
Copy link

kvaidas commented Nov 20, 2019

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

@bboreham
Copy link
Contributor

It certainly is possible to deliver traces to a Jaeger collector, since my system does it.
We set JAEGER_AGENT_HOST.

JAEGER_ENDPOINT was added after the code was written. Happy to accept a PR to add this either upstream or in Cortex.

@kvaidas
Copy link
Author

kvaidas commented Nov 24, 2019

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.

@bboreham
Copy link
Contributor

You're right, my traces get to the collector via an agent.

@pstibrany pstibrany added good first issue These are great first issues. If you are looking for a place to start, start here! hacktoberfest labels Sep 10, 2020
@ethervoid
Copy link
Contributor

One question, does this PR fix this issue?

@pracucci
Copy link
Contributor

One question, does this PR fix this issue?

I think so. @bboreham could you confirm, please?

@bboreham
Copy link
Contributor

I haven't tried it but that was the intention.
Closed by weaveworks/common#204 brought in by #3682

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue These are great first issues. If you are looking for a place to start, start here! hacktoberfest help wanted
Projects
None yet
Development

No branches or pull requests

5 participants