DevOps · Flashcard
What is the mesh's role in distributed tracing?
- AProxies create spans for each hop — but apps must forward trace headers between calls
- BProxies trace everything alone — the applications need no involvement whatsoever
- CProxies sample logs into traces — text lines are stitched together by timestamp
- DProxies only label the metrics — actual traces require a language-specific agent
Why this is the answer
Sidecars emit spans automatically, but they can't know request causality inside the app — code must propagate context headers from inbound to outbound calls. Fully zero-touch tracing is the classic misconception, traces aren't stitched from logs, and no language agent is required for the proxy spans themselves.
Official docs