Hi, I've refactored the existing bam.webapp.stat.publisher component to publish to ST streamDef based on the "enable.metering" property in carbon.xml. Also added 2 new properties to capture the request and response sizes and publish those to BAM as well.
>From my test so far with regard to the tomcat patch in RequestInfo class and the statistics valve, it seems we can get the request and response message size as follows; Request size - request.getCoyoteRequest().getContentLengthLong(); Response size - response.getBytesWritten(true) // for some reason passing *false *always returns 0 I tried to validate the approach via the tomcat user's list, but got some hostile responses cz they thought I was doing something useless :). They suggest logging this info to the access log file (which is also done via a valve) and use a tool to analyze it which won't work for us. TODO - Need a config file to save the username/password used by the data publisher, is bam.xml the right place to have it ? - Update the hive scripts - Do some perf test to check if the valve introduces any perf issues, I feel we might be able to do some improvements to the valve as well, will check on that too .. On Tue, Jul 23, 2013 at 12:39 PM, Amila Maha Arachchi <[email protected]>wrote: > Hi Shariq, > > What is the $Subject? > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > -- Thanks, Shariq. Phone: +94 777 202 225
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
