On my AKS cluster, I want to trace my Spring microservices with Jaeger. I deployed Istio and set the “JAEGER_PROPAGATION = b3” environment variable in my app’s deployments. This made me see the traces without hierarchy. Every trace was made of a single span. A helpful guy told me to change my service port names from “8761”, “8888”, etc. to “http”. It worked, but in my production env, I can’t change these port names. Is there another solution?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Set tracing to external Jaeger collector multi cluster environment | 3 | 1913 | November 8, 2019 | |
| Unable to forward logs to Jaeger | 1 | 1487 | June 7, 2019 | |
| Jaeger Traces issue | 6 | 844 | November 13, 2019 | |
| Setting the value of values.global.tracer.zipkin.address has no effect | 1 | 682 | August 10, 2022 | |
|
Jaeger Tracing application traces aren't seen
|
5 | 2381 | November 13, 2020 |