Audit Logging Strategies

Question

I am trying to decide on the best method for audit logging within my application. The main reason for the log is reporting the sequence of events (changes).

I have a

Answer 1

An audit log is basically a chronological list of events that occurred, who performed these events, and what the events were.

I think a flat view would be better as it can be easily ordered and queried. So I'm leaning more towards your option #2/#3.

Include things like the transaction type, the time, the user id, a description of what's changed, and other pertinent information related to your product.

You can also add things to your product over time and you won't need to continually modify your audit log module.