dstandish opened a new pull request, #69633:
URL: https://github.com/apache/airflow/pull/69633
Lets a Dag run opt into being **embedded inside an external trace** instead
of always starting its own root trace. A run triggered by an external system
that already emits a trace — an upstream orchestrator, event pipeline, CI job,
or another Airflow — can now appear as part of that larger workflow end-to-end.
A reserved run conf key, `airflow/parent_trace_context` (a W3C `traceparent`
string, or a `{traceparent, tracestate}` mapping), is read at run-creation
time. When present, the run's trace carrier rides the external `trace_id` (so
the whole run — `dag_run` span plus all task/worker spans — lives inside the
external trace) and parent-based samplers inherit the external sampling
decision; the emitted `dag_run` span nests under the external span. When the
key is absent, the run remains a **root** trace exactly as before.
Malformed/missing values are ignored rather than failing run creation.
This joins the existing per-run trace controls `airflow/trace_sampled` and
`airflow/task_span_detail_level`, and is documented alongside them. Supersedes
the auto-nesting approach in #67424 (see the redesigned spec on the issue).
closes: #67210
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.8)
Generated-by: Claude Code (Opus 4.8) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
