What’s captured
Each audit record includes:| Field | Description |
|---|---|
| Identity | Which agent made the request (name, ID, labels) |
| Task | Which task session was active (name, context, labels) |
| Tool | Which tool was called and with what arguments |
| Decision | Allow or deny |
| Reason | Why the decision was made — which policy matched, or if it was the default action |
| Policy results | Per-policy evaluation results showing which rules passed and which didn’t |
| Response | The upstream response and duration (for allowed calls) |
| Timestamp | When the call was made |
Why it matters
Audit logs serve three purposes:- Compliance — prove to auditors that agents only accessed what they were authorized to access. Meets EU AI Act, GDPR, and SOC2 transparency requirements.
- Debugging — understand why a tool call was denied. See exactly which policy rule blocked it and what context was evaluated.
- Monitoring — track agent behavior over time. Spot anomalies, measure usage patterns, identify policy gaps.
Viewing audit logs
Navigate to Executions in the console to browse audit logs. You can filter by:- Identity name
- Task name
- Tool name
- Decision (allow/deny)
- Time range
Durability
Audit records are designed to survive entity deletion:- If you delete an identity, its audit records remain
- If you delete a task, its audit records remain
- Audit records are only deleted when the entire project is deleted
Audit log retention depends on your plan. Free plans retain logs for 24 hours. Business plans retain logs for 30 days. Enterprise plans retain logs for 1 year.
Example audit record
Next steps
View executions
Browse and filter audit logs in the console.
Policies
Understand how policies create the rules that audit logs record.