How Issue Detection Works
Sentrial analyzes every session automatically to identify problems. No manual tagging required.Automatic Scanning
Every session is analyzed in real-time as events stream in.
AI Analysis
LLM evaluates sessions for failures, confusion, errors, and inefficiencies.
Smart Grouping
Similar issues are grouped together so you see patterns, not noise.
What We Detect
Sentrial identifies a wide range of issues across your agent sessions:| Issue | Description | Severity |
|---|---|---|
| Task Failures | Agent failed to complete the user’s request | High |
| Tool Errors | A tool call failed, returned unexpected results, or timed out | High |
| Hallucinations | Agent made claims not supported by context or tools | High |
| User Frustration | Signs of user dissatisfaction, repeated questions, or negative sentiment | Medium |
| Confusion Loops | Agent appears stuck, repeating actions or asking the same questions | Medium |
| Slow Responses | Session took significantly longer than expected | Low |
| High Cost | Session used more tokens/cost than typical | Low |
AI-Powered Diagnosis
When you click on an issue, Sentrial provides:- Root Cause Analysis — Why did this happen? What triggered it?
- Affected Sessions — All sessions impacted by this issue
- Recommended Fix — Specific suggestions to resolve the issue
- Code Context — Links to relevant code if GitHub is connected
The Signals Page
The Signals page in your dashboard is your command center for issues:Issue List
All detected issues sorted by severity and frequency.
Trend Charts
See how issue counts change over time.
Filters
Filter by agent, time range, severity, or issue type.
Quick Actions
Jump to diagnosis, affected sessions, or code fixes.
Fixing Issues in Code
Code Integration — Connect your GitHub repository and fix issues directly from the diagnosis page.
Chat with AI about the issue, get code suggestions, and create PRs — all in one flow.
Learn about Code Integration →
Best Practices
Track session outcomes
Track session outcomes
Always call
complete_session() with success=True/False so we can identify failures.Include failure reasons
Include failure reasons
When
success=False, include failure_reason for better diagnosis.Use consistent agent names
Use consistent agent names
Group sessions by
agent_name to see issues per agent type.Track user IDs
Track user IDs
Include
user_id to identify user-specific issues and patterns.
