Bug
In backend/internal/pusher/pusher.go, the ClientFrame_Kick case creates no OpenTelemetry span, unlike all other frame cases (SetStatus, SetAfk, Recording, etc. which all call s.tracer.Start and pspan.End()).
Impact
The kick publish is untraced, and since there's no span at all, there's no pspan.End() call. This is inconsistent with every other frame handler and means kick operations are invisible in traces.
Fix
Add a pusher.nats.publish.kick span with attributes, use pctx for otel injection, record errors on publish failure, and call pspan.End() — matching the pattern of all other frame cases.
PR
#226
Bug
In
backend/internal/pusher/pusher.go, theClientFrame_Kickcase creates no OpenTelemetry span, unlike all other frame cases (SetStatus, SetAfk, Recording, etc. which all calls.tracer.Startandpspan.End()).Impact
The kick publish is untraced, and since there's no span at all, there's no
pspan.End()call. This is inconsistent with every other frame handler and means kick operations are invisible in traces.Fix
Add a
pusher.nats.publish.kickspan with attributes, usepctxfor otel injection, record errors on publish failure, and callpspan.End()— matching the pattern of all other frame cases.PR
#226