Short answer: choose the smallest exception-capture path that can reconstruct one failed financial agent run across every model call, tool call, retry, and outward notification. A lightweight capture API is enough only when it preserves that causal chain, records latency and cost inputs consistently, and fails without delaying the route. If it cannot, the operationally simpler choice is the fuller tracker, even when sourcemaps and replay are deliberately out of scope. This decision is about i...