Jason Lopatecki describes observability as more than a dashboard for humans: traces and evaluation results can provide the context an agent needs to investigate failures. In the demonstrated workflow, scheduled or event-driven investigations prepare issues and possible fixes before an engineer begins the review.
The Arize examples combine repository code, retrieved telemetry, configurable skills and a chosen agent harness or sandbox. Lopatecki distinguishes small fixes from changes that still need an engineer to drive them forward, and explains that online evaluations add useful signals to traces without replacing the underlying evidence.
Watch on YouTube
