I know log box can do this based on a “message” logging system, but
provide horrible data recovery from this making an audit trail
worthless (for example tell me everything that change for customer xyz
between 12am and 2pm on 12/12/12).
LogBox doesn’t provide any recovery mechanism. How you wish to read your logged messages is up to you.
I would like to see logBox be configured for additional fields added
to the debug,error, warning, info functions. That way it provides
separate index able fields. But based on the documentation, I am not
*sure if logBox has this out of the box :-*
Sure it does. If I were you, I would make a custom DB appender. Pass in everything you want logged in a struct in the “extraInfo” property of the log message. In your custom DB Appender you can put all that data in whatever columns of whatever table you want. Then, write whatever reports you wish off of the data in that table.
Also, you might want to check out using some AOP advices for logging if possible, since auditing is definitely a cross-cutting concern.
Thanks!
~Brad
