op

Overview ¶

Package op provides the primitive used to wrap individual tool / SDK call sites so the runner can build a tool-call graph for each job execution.

Each Start call opens a span as a child of whatever span is already on the context (typically the per-step span opened in jobloop, which is itself a child of the per-execution root span). The returned context has:

1. The span installed via otel trace context (so any nested op.Start uses it as a parent automatically).
2. A logger derived from the contextual logger that injects the *Go context* itself as a zap field. The otelzap bridge inspects fields and, when one carries a context.Context, uses it as the emit context. That is the documented mechanism for promoting trace_id / span_id into the dedicated OTLP log record fields (otel_log_records.trace_id / otel_log_records.span_id) instead of the Map fallback.

Stamp every span with runner_job_id / runner_job_execution_id / step name from pkgctx.JobMetadata: OTEL span attributes do not inherit from parents, so the CH ingest path can only populate the dedicated columns when each span carries them directly.