audit

git.splent.io/splent-io/splent_feature_audit

v0.2.0 full governance

About

An append-only audit trail: who did what, to what, from where and when, written by any feature through the framework's record_event, with an administrators' screen and retention

Provides

Models
AuditEvent
Services
AuditService
Routes
/admin/audit
Translations
es

Commands

  • $ splent feature:audit purge

    Delete the events past retention and blur the old addresses.

Run them in your workspace once the feature is installed in the selected product.

Configuration

Setting Default What it does
AUDIT_RETENTION_DAYS 90 Days an event is kept before splent feature:audit purge deletes it. 90 is what decision D19 sets for raw records.
AUDIT_PSEUDONYMIZE_AFTER_DAYS 0 Days after which the purge blurs an event's address (to its /24 or /48 network) and drops its user agent, keeping the rest until retention. 0 keeps them whole until the event is deleted.
AUDIT_SIGN_INS true Whether every sign-in and sign-out is an event. They are most of a busy site's trail.

These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production.

Dependencies

Works better with
Listens to
dataset-deleteddataset-publisheddataset-withdrawnidentity-disconnectedidentity-linkeduser-deletinguser-disableduser-enableduser-password-changeduser-registered

In product lines

Extension points

Templates
audit/admin/events.html
Services
AuditService
Models
AuditEvent
Routes
A refinement can add routes to its blueprint

Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.

Compatibility

Python
>=3.13
SPLENT framework
>=1.30.0