audit-logging

Audit logging captures all admin actions—create, update, delete, and logins—with user ID, timestamp, IP address, and user agent. Integrate the AuditService into your admin endpoints and call log_action with the current user, action type, entity details, and HTTP request context to generate a complete audit trail stored in PostgreSQL.

Audit logging records user_id, timestamp, IP address, user agent, entity_type, entity_id, old_values, and new_values for every admin action. This ensures complete traceability for security investigations and compliance audits, with a minimum retention period of one year.

Yes. Audit logging supports exporting captured logs to CSV directly from the admin panel, allowing you to analyze admin actions, generate compliance reports, and archive audit trails outside your application.

Audit logging uses a dedicated PostgreSQL AuditLog model and a middleware-integrated audit service to automatically log all admin endpoint actions. Each log entry is persisted to the database and enforced with a one-year retention policy.

No. Audit logging is implemented via middleware and a dedicated audit service, allowing centralized configuration across all admin endpoints without modifying individual route handlers. Integration requires only calling log_action at relevant points.

Audit logging is specialized for compliance and security: it records *who* performed *what* action *when* and *from where*, capturing old and new values for forensic reconstruction. Standard application logs typically track system events and errors, not user accountability.