From dd0b6b340b7867a9df3c7990e776104e769f6172 Mon Sep 17 00:00:00 2001 From: Judah Caruso Date: Fri, 14 Aug 2026 13:20:59 -0600 Subject: [PATCH] feat(zeronym): record the diverted migration's txid in the shim log The divert path logged only whether the hub accepted the transaction, which is enough to know something was diverted but not enough to line a shim log up against the hub's own record when an operator is chasing a stuck migration. Correlating the two currently means matching on timestamps alone. The hub's SendResponse already carries the txid in `error_message` on success, so the value is in hand at the point of logging and needs no extra call. Co-Authored-By: Claude Opus 5 --- zeronym/shim/src/intercept.rs | 1 + 1 file changed, 1 insertion(+) diff --git a/zeronym/shim/src/intercept.rs b/zeronym/shim/src/intercept.rs index dce5eab..33b64e8 100644 --- a/zeronym/shim/src/intercept.rs +++ b/zeronym/shim/src/intercept.rs @@ -187,6 +187,7 @@ async fn divert( tracing::info!( target: "zis::classify", accepted = error_code == 0, + txid = %message, "migration diverted to the hub" ); Ok(grpc_send_response(error_code, &message))