Commands on the control socket are not traced #373

Closed
opened 2026-10-25 08:56:28 -07:00 by rays · 1 comment
Owner

Found reviewing what production's traces and metrics leave out, 2026-10-25. Web requests and the worker's jobs have traces; a command from the ipx CLI (add, import, fetch) arriving on the socket has none. Wanted: a span a command, and the job it queues inside its trace.

Found reviewing what production's traces and metrics leave out, 2026-10-25. Web requests and the worker's jobs have traces; a command from the ipx CLI (add, import, fetch) arriving on the socket has none. Wanted: a span a command, and the job it queues inside its trace.
rays added the enhancement label 2026-10-25 08:56:28 -07:00
Author
Owner

Fixed in dd91602: each command the worker runs is a command span (cmd) with its job inside; seen in Tempo for a fetch, 245 ms. Deployed 2026-10-25.

Fixed in dd91602: each command the worker runs is a command span (cmd) with its job inside; seen in Tempo for a fetch, 245 ms. Deployed 2026-10-25.
rays closed this issue 2026-10-25 09:35:54 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#373