Every action, traced.
API request logging, ORM change tracking, and object history — compliance-ready audit trails for regulated industries, typically integrated in 2–5 days.
Every action, traced
In regulated industries, “who did what and when” isn’t optional — it’s required. This module provides comprehensive logging of API requests, key database changes, and user actions in your application.
Features
Traceability from the HTTP request to the field-level diff.
API request logging
Full request and response capture — method, path, headers, payload, response status; user attribution linking every request to the authenticated user; IP and device tracking with geolocation, user agent, and session info; and configurable verbosity — log everything or filter by endpoint, status code, or user role.
ORM change tracking
Automatic field-level diffing that captures before/after values for every model change; create, update, and delete events tracked across all registered models; relationship tracking for foreign keys and many-to-many relationships; and no application code changes — it hooks into Django signals transparently.
Object history
A timeline view with the full change history for any database object; point-in-time snapshots that reconstruct the state of any object at any past moment; and side-by-side comparison between any two versions.
Compliance features
Append-only storage patterns for audit entries; log retention policies configurable per regulation (GDPR, HIPAA, SOX, PCI); CSV and PDF export of audit trails for external review; and rules-based alerts for suspicious activity patterns.
Technical Details
| Component | Implementation |
|---|---|
| Backend | Django middleware, signals, custom audit models |
| API | DRF viewsets with filtering, search, and pagination |
| Frontend | React component: activity timeline, object history, diff viewer |
| Storage | PostgreSQL with partitioned tables for high-volume logging |
| Performance | Async logging via Celery to avoid request latency impact |
Integration Time
Typically 2–5 days for core API and ORM logging. Custom alerting rules may add additional time depending on requirements.
Why This Module Exists
We built this module for our own SaaS products in regulated industries. When auditors ask “show me every change to this record in the last 12 months,” we don’t scramble — we run a query.
Pairs Well With
Auth, SSO & RBAC — log all auth events and permission changes.
BI & Analytics — visualize audit data and compliance metrics.
Multi-Tenant SaaS — tenant-scoped audit trails.
Frequently asked questions
How long does integration take?
Typically 2–5 days for core API and ORM logging. Custom alerting rules may add additional time depending on requirements.
Does audit logging slow the application down?
No — logging runs asynchronously via Celery to avoid request latency impact, and storage uses PostgreSQL with partitioned tables for high-volume logging.
Which regulations do retention policies support?
Log retention policies are configurable per regulation — GDPR, HIPAA, SOX, and PCI — and audit trails export to CSV and PDF for external review by auditors.
Does it require changes to application code?
No. Change tracking hooks into Django signals transparently with no application code changes, capturing before/after values for create, update, and delete events across all registered models.
One of eight modules, battle-tested in production.
Audit Log pairs well with Auth, SSO & RBAC for logging every auth event and permission change, BI & Analytics for visualizing audit data, and Multi-Tenant SaaS for tenant-scoped audit trails.
Explore the Accelerator ModulesAnswer “who did what, when” in one query.
Book a discovery call — we’ll show you what full traceability looks like in your application and which regulations it maps to.