A business-license Function invokes a fee-calculator Function, but Trace Explorer shows two unrelated traces. What is missing for a single tree covering both?
Select an answer to reveal the explanation.
Short Explanation
Chained functions need the Zipkin B3 headers passed along like a relay baton. Without them you get two orphaned traces and cannot see the hand-off.
Full Explanation
When one function calls another, propagate Zipkin headers X-B3-TraceId, X-B3-SpanId, X-B3-ParentSpanId, and X-B3-Sampled on the downstream invoke so one tree in Trace Explorer covers both functions. Without those headers you get two unrelated traces and cannot see the hand-off. Disabling caller tracing, Streaming keys, and usage plans do not merge distributed traces.