Add pipeline/parent context to root execution span

[morgan-wowk]

Summary

execution.parent_id and execution.task_id are now emitted on the root execution span when an execution belongs to a parent pipeline run. This links individual execution traces to their parent pipeline run, enabling correlation with future pipeline-level business logic traces.

When parent_execution_id or task_id_in_parent_execution are absent, the attributes are omitted from the span entirely.

Screenshots

[morgan-wowk]

• Add CPU, memory, and accelerator resource requests to PENDING span #258
• Add pipeline/parent context to root execution span #257 👈 (View in Graphite)
• Add cache hit/miss context to root execution span #256
• Add launcher type and cluster URL to root execution span #255
• Add k8s pod/cluster attributes to PENDING status span #254
• Enrich error/success status spans with failure context #253
• Add retroactive OTel execution lifecycle tracing #252
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[morgan-wowk]

Merge activity

• Jun 5, 5:07 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 5, 5:15 PM UTC: Graphite rebased this pull request as part of a merge.
• Jun 5, 5:15 PM UTC: @morgan-wowk merged this pull request with Graphite.