Kubernetes - Service Mesh
You deployed Istio with observability enabled but notice no traces appear in Jaeger UI. Which of the following is the most likely cause?
You deployed Istio with observability enabled but notice no traces appear in Jaeger UI. Which of the following is the most likely cause?
medium📝 Troubleshoot Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Identify cause of missing traces in Jaeger
Jaeger receives traces from Istio sidecar proxies. If sidecars are missing, no traces are sent.Step 2: Evaluate options for trace absence
Istio sidecar proxy injection is missing on your application pods correctly identifies missing sidecar injection as the cause. Prometheus scraping affects metrics, not traces. Storage or log verbosity do not directly cause missing traces.Final Answer:
Istio sidecar proxy injection is missing on your application pods -> Option DQuick Check:
Missing sidecar = no traces in Jaeger [OK]
Quick Trick: No Jaeger traces? Check sidecar injection on pods [OK]
Common Mistakes:
- Blaming Prometheus for trace issues
- Assuming storage issues cause missing traces
- Thinking log verbosity affects tracing
Master "Service Mesh" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes