I have the requirement to not only log database changes, but also audit log operations that access other storages like external services, files etc. Obviously, Envers cannot be used directly here as no database operations are involved. However, I would like to have the audit logging mechanism as consistent as possible throughout the application. So my question is, if anybody sees a way to take over the concepts of Envers for non-database loggings and create the logging entries manually or if you recommend to keep Envers logging and non-database logging completely separated.
Hmm, well you can have an entity which you modify with new log events, or a separate mechanism