Developers want a named custom span around a downstream Function call from a code-enforcement Fn. Which approach matches the official custom-span path?
Select an answer to reveal the explanation.
Short Explanation
Custom spans are little named bookmarks you finish and error-tag, shipped with a Zipkin-capable library to the APM collector when tracing is on. Metrics and Audit are not span transport.
Full Explanation
The official custom-span path uses a Zipkin-capable library, minimum FDK versions, OCI_TRACING_ENABLED (and tracing context) to detect tracing, and OCI_TRACE_COLLECTOR_URL or the context’s collector URL as the APM endpoint. Name spans after the work, finish them, and surface errors on the span. Metrics, Audit-only writes, and Service Mesh are not the documented custom-span mechanism for Functions.