Servers also have capabilities to track page hits. For example
tomcat has the concept of a valve. A valve is basically a server level filter. The advantage of this is that you could have one place to view all pages from the server if you have multiple wars on it.
The open source JAMon can track page hits, as well as response times (min/max/avg), bytes sent (min/max/avg) and more. You can use its servlet filter, valve or other ways to monitor without changing your application. In addition JAMon can track your application exceptions,
JDBC performance, logging information and more. You can also keep a buffer that lets you look at your most recent page requests as well as their performance and a stack dump or error if there was one. All this is viewable via the JAMon web application.
Of course there are other products out there too. I guess the main thing is not to consider what is already out there before coding it yourself.
Here is a link that has more about JAMon http monitoring...
http://jamonapi.sourceforge.net/http_monitoring.html