Signals have no metrics, and failed Jev calls do not show as failed traces #270

Closed
opened 2026-10-16 19:55:31 -07:00 by rays · 1 comment
Owner

Signals (#254) log and trace each Jev call, but /metrics says nothing about them: how many items are judged, how calls to Jev end (key refused, malformed, TypeSafe failing), how long they take, or whether the judge is still passing. The dashboard has no Signals panels. The jev span records an error field but never sets the span's status, so Tempo's failed traces leave Jev's out, a timeout records nothing at all, and the calls send no traceparent.

Signals (#254) log and trace each Jev call, but /metrics says nothing about them: how many items are judged, how calls to Jev end (key refused, malformed, TypeSafe failing), how long they take, or whether the judge is still passing. The dashboard has no Signals panels. The jev span records an `error` field but never sets the span's status, so Tempo's failed traces leave Jev's out, a timeout records nothing at all, and the calls send no traceparent.
rays added the enhancement label 2026-10-16 19:55:31 -07:00
Author
Owner

Fixed in 33eb1f4: /metrics has ipx_signals_judged_total, ipx_signals_hits_total, ipx_jev_requests_total{result}, ipx_jev_seconds_total, ipx_signals_last_pass_age_seconds and ipx_signals_keys_refused; the dashboard has an "ipx: Signals" row; jev and jev_icon spans set an error status on any failure and send traceparent. Deployed as 1.3.1-dev.

Fixed in 33eb1f4: /metrics has ipx_signals_judged_total, ipx_signals_hits_total, ipx_jev_requests_total{result}, ipx_jev_seconds_total, ipx_signals_last_pass_age_seconds and ipx_signals_keys_refused; the dashboard has an "ipx: Signals" row; jev and jev_icon spans set an error status on any failure and send traceparent. Deployed as 1.3.1-dev.
rays closed this issue 2026-10-16 19:59:42 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#270