This week's book giveaway is in the Programmer Certification forum. We're giving away four copies of OCP Oracle Certified Professional Java SE 11 Programmer I Study Guide: Exam 1Z0-815 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
My manager has asked me to find a solution to log "every" single activity and put it into the Database. Like from the time the users access the website, their IP address, what all links they clicked, what search parameters were given and also log any exception that were encountered and put that log into the database. Also, the code should be non-intrusive. I fail to understand the need and the feasibility of doing this. I tried to ask, but he left in a hurry and said that he's expecting me to propose a solution when he gets back. Anybody knows if there's a framework to do that ? First of all why would we require to log all activities of all the users? To my knowledge even if we are auditing, we don't sniff the links that a user might click.And why would we want to store that in a database?
Bad? It might be. And then again it might not be. It all depends on your application and how you implement this logging and what your response time goals are and so on.
posted 11 years ago
It is a high transaction application. There are 4 appservers clustered together.Right now, the response time is short.Basically, I am not sure about whether it is a usual practice for high transaction applications to log user activities like that. WebTrends is a good product for that, but it doesn't require changing much inside the application, and I would be surprised if it logs the application errors.It seems the application is trying to do too many things. Does the explanation make it easier to answer the question?
Originally posted by prashant bhardwaj: WebTrends is a good product for that, but it doesn't require changing much inside the application, and I would be surprised if it logs the application errors.
Don't assume you have to have a single solution to address all of those requirements. I wouldn't think it's a bad thing to log application errors to a different place than where you log all of the incoming transactions. In fact if you did that, they would just get lost in the noise.
posted 11 years ago
Thanks everyone for their inputs. My Boss realized how complex it is getting and now we are left with a much leaner task. In short, this is a mimic of WebTrends. May be the company didn't have the money to spare for that product.