mirror of
https://github.com/agent-substrate/substrate.git
synced 2026-11-11 10:23:17 +08:00
An actor's own OpenTelemetry SDK does not use the ateom relay; it dials
the collector over the network, and the actor egress lockdown denies
that connection unless the actor has an EgressPolicy rule for it.
Verified on kind and on GKE (main 4e079e7b): with no policy every export
fails with "connection reset by peer" and the gateway logs "actor has no
egress policy"; with an http rule naming the collector Service on
4317/4318 spans and metrics arrive.
Add a section to the observability guide with the rule for the kind and
GKE managed collectors, why it has to be an http rule (OTLP/gRPC is
h2c), that it is per actor, the reconnect lag a running actor sees after
the policy appears, and that IP-based k8sattributes enrichment
attributes the actor's telemetry to the egress gateway pod. Point to it
from the egress traffic doc.