Operation Audit

Audit Logging 💎

For compliance and security analysis, knowing the current state isn’t enough—you need a history of changes. Super maintains a secure, write-only audit log of all administrative actions.

Log Format

Audit logs are stored separately from application logs, typically in ./logs/audit.log. They follow a structured text format:

[TIMESTAMP] IP=... User=[NAME (ROLE)] Action=METHOD Path=URI Status=CODE

Example Entries

1. Admin logs in and creates a token:

[2023-10-27 10:00:01] IP=192.168.1.50 User=[RootAdmin (Admin)] Action=POST Path=/api/auth/tokens Status=201

2. Operator restarts a service:

[2023-10-27 10:05:23] IP=192.168.1.50 User=[ci-bot (Operator)] Action=POST Path=/api/programs/api-server/restart Status=200

3. Viewer attempts unauthorized action (Denied):

[2023-10-27 10:15:00] IP=10.0.0.5 User=[guest (Viewer)] Action=DELETE Path=/api/programs/db Status=403

System Events

Internal system lifecycle events are also recorded in the audit log for a complete timeline:

[2023-10-27 09:00:00] [SYSTEM] Superd Boot: production-server-01
[2023-10-27 09:00:01] [SYSTEM] Process 'api-server' started.
[2023-10-27 14:30:00] [SYSTEM] 🚨 FATAL: 'worker-proc' - Stopped after 3 retries.

Resource Isolation Event Notifications