# OpenTelemetry proposes environment variables for context propagation across processes

DevFeed: [OpenTelemetry proposes environment variables for context propagation across processes](<https://devfeed.tech/articles/help-us-stabilize-environment-variable-context-propagation-32571.md>)

Original publisher: [Read original article](<https://opentelemetry.io/blog/2026/environment-variable-context-propagation/>)

Author: OpenTelemetry Authors; Docs CC BY

Published: 2026-09-11T11:01:22Z

Content type: article

Language: en

Sources: [Blog on OpenTelemetry](<https://devfeed.tech/sources/blog-on-opentelemetry.md>)

Topics: [context](<https://devfeed.tech/topics/context.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Processes](<https://devfeed.tech/topics/processes.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [data-processing](<https://devfeed.tech/topics/data-processing.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [data-processing](<https://devfeed.tech/tags/data-processing.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [processes](<https://devfeed.tech/tags/processes.md>), [spans](<https://devfeed.tech/tags/spans.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [w3c](<https://devfeed.tech/tags/w3c.md>)

## AI overview

The OpenTelemetry Specification has a release candidate for using environment variables to carry trace context and baggage between processes. The article explains how this can connect spans across workflow runners, shells, build tools, test processes, and similar workloads when protocol headers or message metadata are unavailable, and requests feedback before the specification becomes Stable.

## Source excerpt

A trace does not always cross a network boundary. A workflow runner starts a shell, the shell launches a build tool, and the build tool starts test processes. Batch and data-processing systems create similar chains of child processes. Without a shared way to pass trace information across these boundaries, spans from each process can end up in separate traces. If context propagation is new to you, it is the mechanism that carries information from one service or process to the next. For tracing, this includes the trace and span identifiers that let new spans join the same trace. It can also carry baggage: application-defined key-value pairs that are passed to downstream work.