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

Span not exported to Jaeger Collector #1435

Closed
poogurgaon opened this issue Jul 20, 2020 · 6 comments
Closed

Span not exported to Jaeger Collector #1435

poogurgaon opened this issue Jul 20, 2020 · 6 comments

Comments

@poogurgaon
Copy link

I have configured JaegerGrpcSpanExporter , so that it can export the created spans to Jaeger-Collector.

I don't want to export the spans to Jaeger-Agent. I have written down below code.
public BatchSpansProcessor getBatchSpanProcessor(){ return BatchSpansProcessor.newBuilder( JaegerGrpcSpanExporter.newBuilder().setServiceName("collector-exporter"). setChannel(ManagedChannelBuilder.forAddress(localhost,14268).usePlaintext(). build()).build(); }

when i change the port to 14250 i.e. Jaeger-agent port spans are exported to UI but with 14268 I am not able to find any trace at Jaeger UI.

May you please suggest if i need to change above code.

@objectiser
Copy link
Contributor

@poogurgaon The port 14250 is the gRPC port on the Jaeger collector, not the agent. So using port 14250 is correct.

@poogurgaon
Copy link
Author

@objectiser

Thanks for your response.

With port 14250 it is working fine on localhost.

But issue is arising when below use case executed:
I am having jaeger collector as a pod running on k8s cluster , No jaeger agent is running.

I did tried with port 14250 and 14268 after deploying my springboot app on k8scluster , but no spans propagated to JaegerUI
running on k8s cluster.

@thisthat
Copy link
Member

Hi @poogurgaon, localhost will work only if your container contains both the Jaeger service and your spring application. If the Jaeger service is in another container, you should replace it with the IP/hostname of such a container

@poogurgaon
Copy link
Author

Hi @poogurgaon, localhost will work only if your container contains both the Jaeger service and your spring application. If the Jaeger service is in another container, you should replace it with the IP/hostname of such a container

Hi @thisthat I have replaced the hostname with jaeger-host, but still facing same issue.

@thisthat
Copy link
Member

Please, wait until #1419 is merged. This PR proposes a better error reporting that you can use to identify the reason for the failure.

@poogurgaon
Copy link
Author

Please, wait until #1419 is merged. This PR proposes a better error reporting that you can use to identify the reason for the failure.

Great Thank You , I will wait.

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

No branches or pull requests

3 participants