-
Notifications
You must be signed in to change notification settings - Fork 60
Inspektr Auditing
Inspektr is a very small library designed to capture and record the following pieces of runtime information from Spring framework's managed beans i.e. running inside Spring DI container:
- The WHO: who performed an action being audited.
- The WHAT: what system resource being targeted by this audited action
- The ACTION: what audited action is being performed
- The APPLICATION_CODE: an arbitrary string token identifying application running the audited action
- The WHEN: a timestamp of the audited action
- The CLIENT_IP: an IP address of the client invoking the audited action
- The SERVER_IP: an IP address of the server running the audited action
Nothing more, nothing less... at the moment at least.
The architecture of Inspektr Auditing library is very simple. At its core it has 3 main components:
-
AuditActionContext: an immutable value object holding the auditing information mentioned above which has been gathered at the audit point
-
AuditTrailManager: a central Service Provider Interface that describes the recording of the audit data contract.
-
AuditTrailManagementAspect: a POJO-style aspect responsible for capturing the auditing data at the configured audit points and passing it to the configured list of AuditTrailManagers for saving it