Trace Viewer
The Trace Viewer provides a detailed view of every event in an agent’s execution, enabling debugging, auditing, and compliance review.
Accessing the Trace Viewer
- Navigate to Runs in the sidebar
- Click on any run
- Select the Traces tab
Interface Overview
┌─────────────────────────────────────────────────────────────────────┐
│ Trace Viewer: Run off_123 │
│ │
│ ┌─────────────────────────────────────────────────────────────────┐│
│ │ Filters ││
│ │ Event Type: [All ▼] Step: [All ▼] Time: [All ▼] Search: [___]││
│ └─────────────────────────────────────────────────────────────────┘│
│ │
│ Timeline View Table View JSON View │
│ ═══════════════════════════════════════════════════════════════════│
│ │
│ 14:29:55.123 ● run_started │
│ │ Agent: Employee Offboarding (v4) │
│ │ Input: {employee: "sarah.chen@..."} │
│ │ Hash: sha256:abc123... │
│ │ │
│ 14:29:55.456 ├─● step_started │
│ │ │ Step: 1 │
│ │ │ │
│ 14:29:56.789 │ ├─● think_completed │
│ │ │ Reasoning: "Analyzing request..." │
│ │ │ │
│ 14:29:57.012 │ ├─● decide_completed │
│ │ │ Decision: continue │
│ │ │ Action: fetch_employee_data │
│ │ │ │
│ 14:29:57.345 │ ├─● tool_called │
│ │ │ Tool: okta_get_user │
│ │ │ │
│ 14:29:58.678 │ ├─● tool_completed │
│ │ │ Success: true │
│ │ │ Duration: 1.3s │
│ │ │ │
│ 14:29:58.900 │ └─● step_completed │
│ │ Duration: 3.4s │
│ │ │
│ [Load More] [Export] [Verify Chain] │
│ │
└─────────────────────────────────────────────────────────────────────┘Filtering Traces
By Event Type
| Filter | Shows |
|---|---|
run_* | Run lifecycle events |
step_* | Step lifecycle events |
think_* | Think phase outputs |
decide_* | Decision outputs |
tool_* | Tool invocations |
decision_point_* | HITL events |
By Step
Filter to show only traces from a specific step number.
By Time Range
Focus on a specific time window within the run.
By Search
Full-text search across all trace payloads.
View Modes
Timeline View
Visual timeline showing trace sequence and relationships:
- Hierarchical grouping by step
- Duration indicators
- Color-coded event types
Table View
Structured table for detailed analysis:
| Time | Event | Step | Tool | Duration | Hash |
|---|---|---|---|---|---|
| 14:29:55.123 | run_started | - | - | - | abc123… |
| 14:29:55.456 | step_started | 1 | - | - | def456… |
| 14:29:57.345 | tool_called | 1 | okta_get_user | - | ghi789… |
| 14:29:58.678 | tool_completed | 1 | okta_get_user | 1.3s | jkl012… |
JSON View
Raw JSON for technical inspection:
{
"id": "trace_abc123",
"run_id": "run_off123",
"step_id": "step_001",
"event_type": "tool_completed",
"payload": {
"tool": "okta_get_user",
"input": {"email": "sarah.chen@company.com"},
"output": {
"id": "user_456",
"name": "Sarah Chen",
"department": "Engineering",
"apps": ["aws", "github", "slack"]
},
"duration_ms": 1334
},
"sequence_num": 5,
"previous_hash": "sha256:def456...",
"current_hash": "sha256:ghi789...",
"timestamp": "2026-01-15T14:29:58.678Z"
}Trace Details
Click any trace to expand full details:
┌─────────────────────────────────────────────────────────────────────┐
│ Trace Detail: tool_completed │
│ │
│ ID: trace_abc123 │
│ Sequence: 5 │
│ Timestamp: 2026-01-15T14:29:58.678Z │
│ │
│ ───────────────────────────────────────────────────────────────── │
│ │
│ Tool: okta_get_user │
│ Duration: 1.334s │
│ Success: true │
│ │
│ Input: │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ { │ │
│ │ "email": "sarah.chen@company.com" │ │
│ │ } │ │
│ └─────────────────────────────────────────────────────────────┘ │
│ │
│ Output: │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ { │ │
│ │ "id": "user_456", │ │
│ │ "name": "Sarah Chen", │ │
│ │ "department": "Engineering", │ │
│ │ "apps": ["aws", "github", "slack"] │ │
│ │ } │ │
│ └─────────────────────────────────────────────────────────────┘ │
│ │
│ ───────────────────────────────────────────────────────────────── │
│ │
│ Hash Chain: │
│ Previous: sha256:def456... │
│ Current: sha256:ghi789... │
│ │
│ [Copy JSON] [Verify Hash] │
│ │
└─────────────────────────────────────────────────────────────────────┘Exporting Traces
Export Options
| Format | Use Case |
|---|---|
| JSON | Technical analysis, API integration |
| CSV | Spreadsheet analysis, reporting |
| Compliance documentation |
Export Scope
- All traces: Complete audit trail
- Filtered: Only currently filtered traces
- Selected: Manually selected traces
Using Traces for Debugging
Common Debug Scenarios
Why did the agent choose this action?
→ Look at think_completed and decide_completed traces
What data did the tool receive/return?
→ Check tool_called and tool_completed traces
Why did the run fail?
→ Find run_failed trace and examine error details
How long did each step take?
→ Compare timestamps between step_started and step_completed
Debug Workflow
- Filter to the problematic step
- Expand think/decide traces to see reasoning
- Check tool inputs for correctness
- Verify tool outputs
- Look for error traces
Best Practices
Regular Review
- Review traces for failed runs
- Spot-check successful runs periodically
- Look for patterns in tool failures
Compliance Audits
- Export traces before audits
- Include verification certificates
- Document any anomalies
Performance Analysis
- Track tool durations over time
- Identify slow operations
- Optimize based on trace data