Which namespace a span belongs to
People who can see only some namespaces see the traces and APM data of those namespaces, and nothing else. That depends on each span carrying the right namespace. From chart version 0.2.19, the collector decides which namespace a span belongs to; the application sending it does not. Chart 0.2.19 was released on 2 November 2026.
Services that send directly (ports 4317 and 4318)
Section titled “Services that send directly (ports 4317 and 4318)”This covers the OpenTelemetry Operator’s auto-instrumentation, an SDK in your
code, and anything else that runs inside your application’s pod and sends to
seylo-otel on 4317 (gRPC) or 4318 (HTTP).
The collector deletes every k8s.* attribute the application set - namespace,
pod, Deployment and the rest - and works them out again from the address of
the pod the span came from. So a service cannot make its spans appear in
another namespace’s view, by mistake or on purpose. There is nothing to set in
your application for the namespace.
A span that does not come from a pod’s own address - a pod on the host network, a proxy in between, something outside the cluster - gets no namespace. People who can see the whole cluster still see it; people limited to some namespaces do not.
Your own collector, Beyla or OBI (ports 4327 and 4328)
Section titled “Your own collector, Beyla or OBI (ports 4327 and 4328)”A collector you run, or an eBPF agent such as Beyla or OBI, sends spans on
behalf of other pods. On 4317/4318 every one of those spans would be named
after the forwarder’s own pod. Forwarders send to the forwarder ports
instead - 4327 (gRPC) and 4328 (HTTP) on the same seylo-otel
Service - where the k8s.namespace.name the forwarder set is kept. A span that
arrives there without one gets no namespace.
Those ports exist only for the namespaces you list, and are closed by default.
For a collector in otel-gateway and Beyla in beyla:
helm upgrade seylo-observability oci://ghcr.io/seylo-inc/charts/seylo-observability \ --namespace seylo-observability --reset-then-reuse-values \ --set 'traces.trustedForwarders.namespaces={otel-gateway,beyla}'The list replaces the previous one, so name every forwarder’s namespace each
time. A value that cannot be a namespace name fails the upgrade with the value
that was wrong. Then point the forwarder at
http://seylo-otel.seylo-observability.svc:4328 (HTTP), or port 4327 (gRPC).
Admin → Integrations → Observability stores → Send traces and APM data
gives the exact configuration for your own collector and for Beyla, with your
install namespace filled in.
Two more conditions:
- The forwarder must run on the pod network. A pod on the host network sends from its node’s address, which a namespace rule does not match on most network plugins.
- Your collector should work out each span’s pod from the sender’s address
too, or an application could still choose its namespace through it. The
configuration Seylo gives does this: it deletes the application’s
k8s.*attributes, and runsk8sattributeswithpod_associationfrom the connection, in a pipeline of its own beside yours.
Upgrading to 0.2.19
Section titled “Upgrading to 0.2.19”The collector restarts once, so that it loads the new configuration.
If a collector or eBPF agent of yours already sends to 4317 or 4318, its spans are named after its own pod - attributed to the collector’s own namespace, or to none if it runs on the host network - until you list its namespace and move it to 4327 or 4328. Until then, people limited to the namespaces of the services behind it do not see those services’ traces or APM data.