Hi all

I am aware of and I am considering a couple of options for audit trail SQL.

Currently I am considering using:

1. Log4j2 writing an info log to a date based rolling log file when ever a non-select SQL jpa query is executed.
2. Still using Log4j2 as above, but instead of writing to a rolling log file, write the info logs to a separate (from the production Postgres datastore) Postgres datastore .
3. Manually call an insert jpa SQL command each time a DML call is made.

But for some reason I feel like there should be a more intuitive directly supported by the JPA specification (running on Wildfly, thus using Hibernate underneath) method of persisting all DML queries together with the details of the user account that executed the DML and the time stamp of execution, to a separate Postgres datastore.

Please provide feedback on what you suggest.

Thanks in advance.

The best way to achieve this goal is to proxy the JDBC DataSource or the Driver as explained in this article.

With this approach, you can even detect N+1 query issues automatically during testing.

Thanks, excellent link and information; most appreciated.

You are very welcome.