Operate and improve

Monitor reliability in production

Reliability is not a launch milestone. Watch success and error rates on live traffic and alert when behavior drifts from the baseline your testing set.

The world keeps changing

Even an agent that tested well will drift, because models change, data changes, and usage changes. Monitoring is how you keep measuring reliability after launch, on the real traffic that testing could only approximate.

Watch outcomes, not just uptime

Track task success, error, and retry rates over time, alongside cost and latency. Uptime tells you the service is running; outcome metrics tell you it is still doing the job correctly. Alert when any of them drifts from the baseline you established in testing.

Capture the corrections

When a human overrides or fixes the agent, that is a strong signal something is unreliable. Capture those moments, because they point straight at the failures worth fixing next.

Key takeaways

  • Keep measuring reliability on live traffic after launch.
  • Alert on drift in success, error, and retry rates, not just uptime.
  • Treat human overrides as high-value signals of unreliability.

Further reading

  • Langfuse langfuse.comOpen-source tracing and evaluation that captures each step of a run for debugging and monitoring.