What is Audit4j?
Audit4j is comprehensive auditing framework which can be used to track any kind of audit log including server, application and database. Audit4j is entirely annotation driven, hence you can adopt to your application using minimum configurations.
What is different between Audit trace and Log?
A log is often unpreserved whereas; an audit trace is secure and preservable. As a result, recording sensitive information, or data which will be required at a later time will not be handled by a log. Other issue is usually logs are not recording actor(Who did), action(What did) and origin(Comes from), but audit log should contains those information. However, an audit trail addresses these issues.
What are the main features of Audit4j?
- Can be Asynchronous/Synchronous, according to the requirement.
- Fully customizable annotations.
- In-built plugins (File and Console).
- Minimum configurations.
- Rich extendible API - Custom/third party plugins can be used by via the API.
How is the performance after integrating the Audit4J with my application?
Audit4J supports asynchronous events (and synchronous events – depends on the requirement). Since the architecture is based on asynchronous event mechanisms, application will not be added additional latency (or less than 10 micro second.) after integrating the audit4j and its plugins.
How does the Audit4j architecture work?
Audit4J is entirely based on a modular architecture. There are three different types of plugins that support connecting various types of external tools with the core module.
- Caller Plugins - Sending audit events from various sources.
- Layout Plugins - Format and organize audit events.
- Handler Plugins - Process and save audit information.
The javadoc can be referred in order to obtain further information regarding this.
Currently, what are the available integrations for Audit4j?
1.Audit4j-Spring Integration. 2.Audit4j-Weld Integration. 3.Audit4j-Guice Integration. 4.Audit4j-database Integration. 5.Audit4j-http.