World's Fair 2025
Taming Rogue AI Agents with Observability-Driven Evaluation — Jim Bennett, Galileo
Overview
This talk addresses the challenge of ensuring AI agents function reliably by introducing observability-driven evaluation. It highlights that AI's non-deterministic nature makes traditional testing methods insufficient. The core thesis is that by using AI itself to evaluate AI outputs, developers can gain crucial insights into agent performance, identify failures at granular levels, and implement targeted improvements.
Who should watch
- AI Engineers
- Product Managers
- Builders of AI applications
- Anyone concerned with AI reliability and detecting unexpected agent behavior
- Teams implementing agentic workflows or tool-calling AI
Key takeaways
- Detecting problems in AI systems is difficult due to their non-deterministic nature, unlike traditional code with predictable unit tests.
- Complex agentic workflows involving multiple LLM calls, tool usage, and data retrieval are particularly hard to evaluate comprehensively.
- The principle of "set a thief to catch a thief" can be applied by using an AI to evaluate another AI's performance, achieving human-level accuracy in many cases.
- Granular evaluation is essential, breaking down performance metrics by individual steps within an agentic workflow rather than just assessing the overall outcome.
- Metrics like action completion (did the task finish) and action advancement (did it move towards the goal) can provide nuanced insights into agent performance.
- Leveraging more powerful or custom-trained LLMs for evaluation purposes can yield better results than using the same LLM within the application.
- Implementing evaluations from the outset of development, during prompt engineering and model selection, is crucial, with the next best time being immediately.
- Continuous monitoring and evaluation in production are necessary because users often interact with systems in unexpected ways.
Notable quotes
*Detecting problems with AI is hard. It is a nondeterministic problem.*
*We can use AI to evaluate is our AI application actually working.*
*The best time to put evaluations in is as you're doing prompt engineering model selection. The second best time is now.*
Unofficial community note. Prefer the recording for nuance.