Jaeger - Distributed Tracing Platform
Replies: 3 comments 5 replies
-
|
Same issue for me also... Any solution @AnnaSiac |
Beta Was this translation helpful? Give feedback.
-
|
No, nothing yet @Benboy10 ... Others have signaled similar issues in the Discussions, and no one got a published answer, so sadly I don't think the dev team plans on addressing this issue :'( |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. Only the all-in-one deployment works in kubernetes, the query pod seems to be unaware of the collector service. |
Beta Was this translation helpful? Give feedback.
-
|
same here, with minikube+Istio. I can only see one service: 'jaeger-all-in-one' |
Beta Was this translation helpful? Give feedback.
-
|
I am also running istio, and am running multiple instrumented test applications. The only in-memory configuration that works is AIO, I can run separate collector / query services successfully if I swing it over to my elasticsearch cluster. If storage.memory is supported only for AIO it might just be a docs issue. |
Beta Was this translation helpful? Give feedback.
-
|
memory storage only works in all-in-one configuration, because it is not shared outside of the process. If you split collector and query into separate processes (as recommended for production installations) then each of then will have its own copy of memory storage. It is possible to reuse memory storage with https://www.jaegertracing.io/docs/1.60/deployment/#remote-storage-component |
Beta Was this translation helpful? Give feedback.
-
|
You applications need to be instrumented for tracing, either explicitly or via automatic instrumentation. See OTEL project for that. Jaeger is a tracing backend, it does not make your application traceable. |
Beta Was this translation helpful? Give feedback.
-
|
I am using istio, so traces should show up, but they are not. |
Beta Was this translation helpful? Give feedback.
-
What happened?
When accessing the UI of a Jaeger instance installed on a simple Kubernetes cluster on Minikube, no traces are displayed except those corresponding to the fact of loading the UI. The "system architecture" section only shows the message "No service dependencies found."
I would like to be able to get information on my cluster architecture and the traces of the pods' communications.
Steps to reproduce
Build a minimal K8s cluster in Minikube, containing a MongoDB and a web application that uses the mongodb (I can send here the YAML files to build the exact replica of my cluster if needed).
Install Jaeger with these commands:
kubectl create namespace observabilitykubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.6.3/cert-manager.yamlwget https://github.com/jaegertracing/jaeger-operator/releases/download/v1.46.0/jaeger-operator.yamlkubectl create -f jaeger-operator.yaml -n observabilitykubectl apply -f simplest.yaml# simplest.yaml is the minimal template found in the official doc hereDisplay the UI by running the command:
kubectl port-forward service/simplest-query 8080:16686and going to localhost:8080 on a Firefox browser
Expected behavior
To see more traces than just the one from the service jaeger-query (see screenshot). For example those from the webapp and the database running inside the cluster.
Relevant log output
Screenshot
Additional context
The exact same problem was encountered when installing Jaeger in a bigger, working cluster on Google Kubernetes Engine. I tried on the GKE cluster:
Nothing changed.
As the ES storage appeared empty, I believe it is a problem between the agents and the collector, but I didn't know how to investigate further.
Jaeger backend version
v1.46.0
SDK
I don't know
Pipeline
I don't know
Stogage backend
I don't know
Operating system
Ubuntu 22.04 in WSL inside Windows 10
Deployment model
Kubernetes (minikube), deployment via the
kubectl applycommandDeployment configs
No response
Beta Was this translation helpful? Give feedback.
All reactions