You can do your own logging at the action level and this is pretty easy to throw in if you are using a common base action class. This tells you most of what you want to know as far as server-side processing goes. This timing would not include
JSP processing (including processing done with custom tags) and does not include the minor overhead that Struts adds in. Your application server might be able to provide higher level timing that includes all server-side processing.
True end user experience is a little tougher to measure and to some extent you need to figure out what is important to measure. Measuring performance under various loads can also get involved. Also, if you are just kicking statistics out to a log file, you need to do some processing of the log file to produce meaningful statistics. There are various commercial tools designed to do this type of stuff.
Joe: Thanks for the JAMon link...I might check into that.
- Brent