You are able to supply an entity annotated with @RevisionEntity paired with a custom RevisionListener implementation where you can add custom columns to the revision-entity to store that type of information. Is that sufficient for the type of information you're referring to?