Hi Christopher,
On Wed, Jul 17, 2013 at 9:32 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Shariq, > > On 7/17/13 8:47 AM, Shariq wrote: > > On Wed, Jul 17, 2013 at 5:49 PM, André Warnier <a...@ice-sa.com> > > wrote: > > > >> Shariq wrote: > >> > >>> Hi, > >>> > >>> My requirement is to measure the request and response bandwidth > >>> of a webapp that's deployed in Tomcat. Basically capture each > >>> request and response bandwidth and store the statistics and do > >>> analytics on that data overtime. > >>> > >> > >> Bandwith > >> (http://en.wikipedia.org/wiki/**Bandwidth_%28computing%29< > http://en.wikipedia.org/wiki/Bandwidth_%28computing%29> > >> > >> > ) > >> refers to a number of bits/second transmitted over a > >> communications channel. > >> > >> This is typically something better captured by network equipment > >> (analysers, routers, switches), and it doesn't really make much > >> sense on an application base. > >> > >> Apart from that, the AccesLogValve can already tell you, on a URL > >> base, how much total time was needed to fulfill the request, and > >> how many bytes (x 8 bits) were sent as a response. (You can > >> probably also get the number of bytes of the request). > >> > >> But Tomcat is not the only element which intervenes here, and the > >> real bandwidth can also be limited by what the client (and > >> everything in-between) can absorb. > >> > >> Maybe before we go any further into this, you would like to make > >> more clear what exactly you are trying to measure, and for which > >> purpose ? > >> > > > > What I am trying to measure is the size (number of bytes) of the > > request / response for a webapp. So overtime we can produce > > statistics such as, for a given time interval how much bytes was > > served by server / tomcat for a particular webapp. Also we are > > looking to throttle webapps consuming a high bandwidth etc. > > > > The idea is gather raw statistics and process / aggregate them > > overtime ... > > I think what you are looking for is a typical web server access log. > Just log the bytes read/written for each request, and use one of the > many fine (and freely-available) tools out on the Internet to run > statistics on your web server logs. > Yes this is pretty much what I want to do, but I am still not able to find out how to get the bytes read/written in the valve. Any pointers on how I could find the bytes read/written for each request with a tomcat valve ?! > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJR5r/8AAoJEBzwKT+lPKRYSjIP/0j4S0COdKoGP2kclXu3xAxc > uRkO7MwJfmczXIBLBrRr+XoWqFEyYVXvM3XAUYPexh1vx+N1O0WYpokRgCw+478F > +idHJ4TXSaRicsTX5djJ5PK0qx1qCFMmCEL808NH9jT9mhALi2n9GgDZSPrgOopw > jQQyTsxFFL3+T91hUF9y3/joc0G2MpcWeUIsi75t3sBLuWz9OjfFuW8Ao7crBnV1 > o74BEqfghp2wIZQd0CwMeJfNqEkDJBrgsfcTmOI/Q3N6Osv3Kscw/NoM0ldN6c5S > yoY+AiK6fjyQlL9JpILwyApPERUj8VMcRkf2XRoJwXRQ6PtczWZhgIVn3moy5vEV > 1ry00n3FclfzaYKJBePtWVeX9PMaoBeRvjZIltL2OYtg/Gpb7zuN2c3lK9NBCzF8 > YE+oIBbwkZJPTgpUgUySFbOTUxcAilmmJDKMYWJv9LU7Af2D0XU0E1zxuqbZy/xV > VtKw7Uo4XlCq8xxpJb6M8+B0tZMsrVi1baiT7GH3R1St7hhsPhsKWgdb+at8TeO+ > CNFS4hVbrpv5ifP838T2VWTxxl+Zg/DFacpWb5C5KBaF7l1jIjIZ6OCPelHYicNm > 9cK5lv04mHg2+EWOVmnn7/t5cEyeAysu0uCyMEUFJGbqn0FXM6Ai8R0j9KP236Qn > 0i+geCjnVcYKycnsrwAc > =Wj9V > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >