SysOps Audit History

Audit

Shows who changed what, when, and why across an incident and its approval and escalation path.

Session requiredAuthenticated routes expect a real session token or cookie.API base: https://dev.sysopsai.net/api
Traceability

Show the sequence, not just the final status.

The audit history surface is now route-native in `apps/web`, making human actions, automation, approvals, escalation, and communication traceability part of the real app shell.

Ticket createdOwner assignedVendor escalatedStakeholders notified
complete trail
8

Recorded events

captured
3

State or owner changes

visible
2

Automated actions

governed
1

External escalation

Activity History

Short, scannable history showing the key actions an executive, auditor, or IT manager would care about.

TimeActorActionWhy It Matters
09:02 AMSystemCreated `INC-2041` from service alertShows how incidents enter the platform automatically when a threshold is crossed.
09:03 AMAutomationSMS alert sent to on-call infrastructure team; John Doe notifiedShows AI / automation can trigger governed response actions immediately.
09:11 AMJohn DoeAccepted ownership and began diagnosisShows human confirmation and accountable ownership.
09:26 AMAI AssistSuggested runbook `NT-22053-123` attachedShows AI as a support tool, not as the final decision-maker.
09:44 AMInfrastructure leadEscalated to vendor with structured diagnostics packShows when work left internal control and why the ticket may remain open.
10:07 AMService desk leadPosted stakeholder-facing updateShows communication history, not just technical history.