Why production agent monitoring matters
Agents in staging behave differently than agents under real user pressure:- Adversarial prompts and edge cases spike in production
- Model updates silently change behavior
- Tool calls fail or overreach without obvious errors
- Teams discover mistakes from user complaints — too late
What Histeeria monitors
| Signal | Captured |
|---|---|
| Input | Prompts, messages, RAG context |
| Output | Agent responses and action summaries |
| Session | Conversation and workflow run IDs |
| Metadata | Tags, user IDs, model version, escalation flags |
| Tokens | Optional input/output token counts |
| Multi-step traces | Intermediate steps in complex agents |
Real-time vs batch
- Real-time ingest — decisions appear in Monitoring within seconds
- Async evaluation — judgment scores follow via the evaluation engine
- Alerts — incidents land in Inbox when thresholds breach
How to set up agent monitoring
Create agent profile
Define role and policy in Agent profiles.
Generate API key
Link key to profile in API keys.
Add SDK
One
observe() call after each agent turn. Quickstart.Watch Command center
Metrics and decision stream in Command center.

