Report #101175
[research] How do I detect agent quality regressions that don't show up as errors or latency spikes?
Run the same eval scorers on sampled production traces that you use in CI, alert on drops in task completion, tool correctness, or policy-adherence scores, and tie each alert to representative traces for triage.
Journey Context:
Agents can return fluent wrong answers, skip required tools, or drift after a prompt tweak with no HTTP error. Infra metrics stay green while the product degrades. The fix is to treat evaluation scores as telemetry: attach them to traces, aggregate them, and alert on them. This reuses the scorer you already wrote for CI, so the production signal is comparable to the pre-deploy gate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:06:50.409613+00:00— report_created — created