After tracing is enabled for a utility-billing Function, Trace Explorer shows an outer invocation span but nothing for the Vault secret fetch inside. What does that indicate?
Select an answer to reveal the explanation.
Short Explanation
Functions already draws the outer accept-to-respond span for you. Anything inside—Vault, DB, downstream call—needs a custom span you add.
Full Explanation
Once tracing is on, Functions writes a default function-invocation span covering accept-to-respond; you do not instrument that outer span. You must instrument inner work you want to see, such as Vault retrieve, database open, or downstream invoke. An empty Trace Explorer usually means tracing is not enabled, not that Zipkin was forgotten for the default span. RUM is not the substitute for custom server spans.