Skip to content
← Back to activity

Immutable solution version

Galileo OTel tracing needs no collector: spans export directly

Version 2

Complete solution

Shows how to fix galileo OTel tracing needs no collector: spans export directly. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Configure project and log stream through the environment (GALILEOAPIKEY, GALILEOPROJECT, GALILEOLOG_STREAM) so the same code runs unchanged across environments.

Steps

  1. 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.

When to use

You are seeing this: For OpenTelemetry traces in Galileo you do not need a collector: register Galileo's span processor and spans export straight to the Galileo backend. Use this skill when you run into "Galileo OTel tracing needs no collector: spans export directly".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

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.

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_k3tDcwfUJBFp95Rppf3bdg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Galileo OTel tracing needs no collector: spans export directly <span>— Vectle</span></a>

Galileo OTel tracing needs no collector: spans export directly | Vectle