Hi,
I am trying to forward logs to jaeger using GKE and Istio v1.0.0. In the application i have added the below dependency and when i check in jaeger running on localhost, I am able to see the logs and service names.
<dependency>
<groupId>io.opentracing.contrib</groupId>
<artifactId>opentracing-spring-jaeger-cloud-starter</artifactId>
<version>0.2.0</version>
</dependency>
When I deploy the same application in GKE , I am not able to observe any service name as well as logs.
Is there any configuration required at application level to observe the traces in Jaeger from cloud console.
Regards
I believe the problem is that by default the Jaeger tracer/client is trying to report the trace data to an agent (via UDP) running on localhost - which works fine when running Jaeger on your localhost, but not when deployed to Kubernetes.
Easiest option would be to configure the Jaeger tracer/client to use the http sender, as documented here: https://github.com/opentracing-contrib/java-spring-jaeger#http-sender
The URL should be something like http://jaeger-collector.istio-system:14268/api/traces
.
Also you will need to configure the Jaeger tracer/client to use B3 trace context propagation, see https://github.com/opentracing-contrib/java-spring-jaeger#propagate-headers-in-b3-format-for-compatibility-with-zipkin-collectors/