SRE, platform, security, and operations teams that let AI agents touch tickets, tools, APIs, and release workflows.
Help ops teams investigate what AI agents actually did.
AgentOps Flight Recorder is for SRE, platform, security, and operations teams that need an audit trail when AI agents run tools. It turns agent actions into Splunk-ready evidence and uses evidence-bound AI to explain the incident without inventing facts.
After a bad action, a chat transcript is not enough. Teams need to search what the agent did, where risk appeared, and who approved the next step.
The AI investigator is evidence-bound: it summarizes only from event IDs and SPL result rows, then asks a human to approve, reject, or hand off.
Agent work becomes Splunk-ready operational evidence instead of an unreviewable conversation.
Run The Review Flow
This is the working prototype path: load event evidence, narrow to risk or approvals, run a Splunk-style search, then generate an evidence-bound AI investigation draft.
index=agentops sourcetype="agentops:json" | sort 0 _time | table _time event.case_id event.event_id event.risk_level event.status event.summary
Evidence-Bound AI Investigator
Choose a filter or run the AI summary. The assistant is constrained to cite event IDs from the evidence trail.
Case Overview
Generated a case handoff report with cited evidence IDs and final rejection decision.
Generated DFIR report with evidence IDs, unsupported claims, and human containment decision.
Closed cloud-agent workflow case with source citations, cost guardrail, and human approval captured.
High-Risk And Blocked Actions
| Event | Case | Risk | Status | Reason |
|---|---|---|---|---|
| evt-0005 | CASE-AI-OPS-001 | medium | failed | Regression test failed around duplicate retry suppression. |
| evt-0006 | CASE-AI-OPS-001 | high | warning | Production payment behavior change plus failing regression test. |
| evt-0007 | CASE-AI-OPS-001 | critical | blocked | Production deployment is destructive and requires human approval. |
| evt-0008 | CASE-AI-OPS-001 | medium | success | Human requested more evidence instead of approving the production deployment. |
| evt-0015 | CASE-DFIR-002 | medium | warning | Initial model answer overclaimed malware execution before process evidence was present. |
| evt-0016 | CASE-DFIR-002 | high | warning | Unsupported certainty detected in analyst draft. |
| evt-0017 | CASE-DFIR-002 | medium | success | Hash lookup returned low-confidence phishing kit association; raw indicator was redacted in report output. |
| evt-0024 | CASE-CLOUD-003 | medium | warning | Projected monthly model spend exceeded the manager's prototype budget. |
Human Approval Queue
| Event | Case | Decision | Summary |
|---|---|---|---|
| evt-0007 | CASE-AI-OPS-001 | blocked_by_policy | Attempted production deployment was blocked by policy before execution. |
| evt-0008 | CASE-AI-OPS-001 | needs_more_evidence | Human requested more evidence instead of approving the production deployment. |
| evt-0010 | CASE-AI-OPS-001 | rejected | Service owner rejected the release until the retry regression is fixed. |
| evt-0018 | CASE-DFIR-002 | approved | Human approved containment of the reported message and requested no endpoint isolation. |
| evt-0025 | CASE-CLOUD-003 | approved | Human approved the workflow with a rule that expensive model calls are escalation-only. |
Saved SPL Searches
Timeline by case
index=agentops sourcetype="agentops:json" | sort 0 _time | table _time event.case_id event.event_id event.phase event.actor_type event.actor_name event.event_type event.status event.risk_level event.summary
High-risk or blocked actions
index=agentops sourcetype="agentops:json" (event.risk_level="high" OR event.risk_level="critical" OR event.status="blocked") | table _time event.case_id event.event_id event.risk_level event.status event.risk_reason event.summary
Human approval queue
index=agentops sourcetype="agentops:json" event.human_approval_required=true | table _time event.case_id event.event_id event.actor_name event.decision event.summary
Estimated model/tool cost by case
index=agentops sourcetype="agentops:json" | stats sum(event.cost_usd_estimate) as estimated_cost by event.case_id | sort - estimated_cost
Evidence Timeline
Human opened an AI-agent operations case after a release bot proposed a production change.
Agent created a read-only investigation plan with explicit approval gates before any production action.
Robot gathered the change ticket, linked pull request, deployment window, and service owner.
API confirmed the pull request touches payment retry behavior and has one approving review.
Agent found a failing retry regression test that was not mentioned in the change ticket.
Case risk escalated because the proposed release affects payments and has failing verification.
Attempted production deployment was blocked by policy before execution.
Human requested more evidence instead of approving the production deployment.
Robot requested service-owner signoff and attached the failed test evidence.
Service owner rejected the release until the retry regression is fixed.
Generated a case handoff report with cited evidence IDs and final rejection decision.
Security analyst opened a suspicious email investigation with attached endpoint telemetry.
Agent proposed an evidence-first DFIR plan: preserve artifacts, list hypotheses, then verify each claim.
Collected email headers, attachment hash, browser download timeline, and endpoint process list.
Agent generated an initial hypothesis but flagged one claim as unsupported by current evidence.
System marked the draft finding as provisional because execution evidence was missing.
Hash lookup returned low-confidence phishing kit association; raw indicator was redacted in report output.
Human approved containment of the reported message and requested no endpoint isolation.
Generated DFIR report with evidence IDs, unsupported claims, and human containment decision.
Support manager requested an agent that answers customer questions and escalates uncertain cases.
Agent created a workflow plan using retrieval, MCP tools, cost guardrails, and human escalation.
MCP retrieval returned the current refund policy and source URL for citation.
Agent drafted a customer answer grounded in the retrieved refund policy.
Cost guardrail warned that the high-quality model should be reserved for escalations.
Human approved the workflow with a rule that expensive model calls are escalation-only.
Closed cloud-agent workflow case with source citations, cost guardrail, and human approval captured.