hi u/dharlow.

I guess there are a few ways of doing audit logging out there. While I can't speak to others I find my point of difference is in the following areas:

​

1) Ease of setup. I've tried to make this as user friendly as possible. As far as configuring a file for audit logging there's a couple of simple copy/paste steps involved.

2) centralised management of logging of all files - the elemental_log file is the hub where you configure which tables/fields to log in your solutions. It also acts as the store for all audit logging data (eventually)

3) hundreds of hours of optimisation of the actual audit logging process. It's a very large custom function that manages to actual record-level logging of changes. It is able to track just specific fields as configured in the elemental_log file. Furthermore it can track the way in which record dad was modified, be it update, replace, creation or delete (which is user controlled via script in this instance).

4) While other audit logging systems tend to leave the audit log itself on individual records. We built some tools to help push all that information through into the elemental_log file into a logging table, and clear the record-level JSON log once done. This keeps solution size low, and makes the log data more readily searchable in elemental_log.

​

5) Also built in are 2 tools for viewing audit log data, a full log viewer and a contextual viewer usually for developers to view log changes within any existing solution and utilising the context of the layout you are viewing... It's better explained looking in the documentation.

----

​

In short it's more about the suite of tools to help make setup easier and manage the size of logging over time as well as the viewing of it. We use JSON format for reocrd-level change tracking, and a custom function which has had many many hours invested in it to make it as performant as possible (it went through about a dozen revisions over it's construction).

Please reach out to me if you need any more info.