Logs, logs everywhere, but which ones to keep? :)
Posted: Sat Dec 05, 2009 10:17 pm
I'm working on a audit logging system to tie into another system and am just wondering how detailed should I be with what I record?
I am using a MySQL archive storage engine and have an AuditLog object (with various derived classes).
So, should I log application wide actions, or just actions relevant to the business logic? As in ignore MySQL connections as the MySQL server is worrying about that?
I realise the answer to this really does depend on the context of the system; as there is some financial information being stored, logging is in paranoid mode there.
Also, how many logs should be made per day before you start to rethink what's being stored? 100 logs a day is nothing, but 1000000 could cause some concern?
Maybe it doesn't matter at all... :S
I am using a MySQL archive storage engine and have an AuditLog object (with various derived classes).
So, should I log application wide actions, or just actions relevant to the business logic? As in ignore MySQL connections as the MySQL server is worrying about that?
I realise the answer to this really does depend on the context of the system; as there is some financial information being stored, logging is in paranoid mode there.
Maybe it doesn't matter at all... :S