-
Notifications
You must be signed in to change notification settings - Fork 872
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
Comments
@poogurgaon The port |
Thanks for your response. With port 14250 it is working fine on localhost. But issue is arising when below use case executed: I did tried with port 14250 and 14268 after deploying my springboot app on k8scluster , but no spans propagated to JaegerUI |
Hi @poogurgaon, |
Hi @thisthat I have replaced the hostname with jaeger-host, but still facing same issue. |
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. |
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.
The text was updated successfully, but these errors were encountered: