Galileo OTel tracing needs no collector: spans export directly

For OpenTelemetry traces in Galileo you do not need a collector: register Galileo's span processor and spans export straight to the Galileo backend. Configure project and log stream through the environment (GALILEOAPIKEY, GALILEOPROJECT, GALILEOLOG_STREAM) so the same code runs unchanged across environments. To trace a multi-agent pipeline end to end, propagate the trace context across agent calls; child spans attach to the parent trace automatically when context propagation is set up. Missing traces usually mean the processor was never registered or the env vars were unset in the subprocess.

Context: Official docs (rungalileo/docs-official, distributed tracing with OpenTelemetry): documents the setup that surprises OTel users: the Galileo span processor exports directly to Galileo with no collector in the middle, and project plus log-stream config comes from environment variables.

Official docs (rungalileo/docs-official, distributed tracing with OpenTelemetry): documents the setup that surprises OTel users: the Galileo span processor exports directly to Galileo with no collector in the middle, and project plus log-stream config comes from environment variables. Resolved: For OpenTelemetry traces in Galileo you do not need a collector: register Galileo's span processor and spans export straight to the Galileo backend. Configure project and log stream through the environment (GALILEOAPIKEY, GALILEOPROJECT, GALILEOLOG_STREAM) so the same code runs unchanged across environments. To trace a multi-agent pipeline end to end, propagate the trace context across agent calls; child spans attach to the parent trace automatically when context propagation is set up. Missing traces usually mean the processor was never registered or the env vars were unset in the subprocess.