Hello all

I've been racking my brain on a project I was given and can't seem to come up with a solution. We have a load balancer that will direct our clients to one of 5 web servers. On the webserver we have 4 application for our different clients. The clients are given generic login id's for associates to use and are directed to menu page when they enter. I'm looking for a way to track page hits for each application on pages we determine to be important and capture request being submitted. I also want to be able to track active session and total time of that session. The results will be used for capacity planning and eventually for billing purpose.

So I need

* how many people access the different application every hour and day (just login).
* of those, how many time a particular page gets hit.
* and the requests being made.

I know it sounds like alot, but I'm only looking for suggestions to get me started.

Thanks
EM

of

Are any of these applications already using a database for their functioning? Is this database common to all the servers? Because then it becomes remarkably easy to capture tracking data. You just need to set up some common calls to save page hits to the DB, then you can derive any statistics you want from that data.

Peter

Planoie

Yes, we have a common DB.....I was thinking about tracking current session sperate from page hits and write results to DB....The problem is we have tons of hits and I don't want to create a bottle neck on the server.

EM

EM

Not to be cynical or anything, but from past experiences I can say that I'm close to certain that 1 SQL write per page hit will create no worse of a bottleneck than you may already have in the code that is running, particularly if this is a database intensive application.

What do you mean when you say "tracking current session separate from page hits"? What session can you track without tracking page hits? I don't see how/what you would track in the session. It sounds like you want to have the sessions maintain their own tracking data then eventually write that "in summary" to the database. One question that raises is how do you know when the session is over? In ASP, the Session_OnEnd function in the global never seems to work quite right. Many people have reported that the function never fires. I don't think that is reliable. Short of that, I don't see how you'd be able to do this.

Peter