Monitor agent performance
Access monitoring views from your deployed agent’s dashboard. These views show how your agent performs with real user interactions:| View | What it shows |
|---|---|
| Overview | Deployment status and configuration details. |
| Performance | Evaluation metrics as visualizations alongside production traces. Review metrics over time to spot trends and identify patterns in successful versus problematic interactions. |
| Usage | User invocations and interaction tracking. |


Evaluate production traces
Production evaluations run out-of-band from your real-time agent app. Rather than evaluating inside the live request path, you write a separate evaluation script that fetches production traces, scores them, and logs the results back. This script runs as a Domino Job, typically on a schedule, so your agent’s latency is never affected by evaluation overhead. How it works:- Your agent serves users in real time and collects traces automatically.
- A separate scheduled Job fetches those traces, runs your evaluation logic, and logs scores back to each trace.
Find your agent ID and version
To fetch production traces programmatically, you need the agent ID and agent version. Find these in the Domino UI after deploying your agent:
The production evaluation script
Usesearch_agent_traces() to fetch traces for a specific agent version. Then evaluate and log results back with log_evaluation():
Iterate on configurations
When you identify issues or opportunities for improvement, relaunch your production agent’s configuration into a workspace. Track and monitor experiments has details on relaunching runs. This workflow lets you:- Reproduce the exact production configuration.
- Debug issues identified in production traces.
- Maintain clear lineage between production agents and their source experiments.
Next steps
- Develop agentic systems: Iterate on your agent configuration based on production insights.
- Experiment Manager: Test improvements before redeploying.
-
Python SDK for agents: A full API reference for
search_agent_traces,log_evaluation, and trace data classes.