Log user activity and more - how to think?
Posted: Wed Jul 08, 2009 9:54 am
Hi all!
I am developing a web application and the possibility of logging basically all user activity and other activities triggered by different events in the application, is of great importance. I have done some google searching on the topic, but haven't found what I need.
I need to log what triggered the activity, when and what the activity was - basically. Think the Facebook feed, or something like that. This meaning that some parts of the log will be visible to the users, other parts only to the administrator, and how the log entry is displayed is depending on what is being logged. To spice it up a little extra, the application is multi-lingual, meaning I can't enter a text in the db, stating what has happened, because it must be possible to translate it.
Can someone please get me started on how I should think about this matter?
I want the DB to stay normalized, therefore a log table with a lot of different columns to cover all possible information that different events might need to log, is not a good option.
I am developing a web application and the possibility of logging basically all user activity and other activities triggered by different events in the application, is of great importance. I have done some google searching on the topic, but haven't found what I need.
I need to log what triggered the activity, when and what the activity was - basically. Think the Facebook feed, or something like that. This meaning that some parts of the log will be visible to the users, other parts only to the administrator, and how the log entry is displayed is depending on what is being logged. To spice it up a little extra, the application is multi-lingual, meaning I can't enter a text in the db, stating what has happened, because it must be possible to translate it.
Can someone please get me started on how I should think about this matter?
I want the DB to stay normalized, therefore a log table with a lot of different columns to cover all possible information that different events might need to log, is not a good option.