Re: [Dev] Status of webapp stat publishing for aPaaS
On Tue, Jul 23, 2013 at 5:45 PM, Amila Maha Arachchi ami...@wso2.comwrote: Thanks Shariq. If the bam.xml only shipped with AS? Seems like we'll have to use it for this purpose. Make sure to use secure vault for this. This is shipped with any product that has data agents, its basically use to enable / disable stat publishing, I added another GlobalPublisher element and specified the credentials, password has been secured using the vault. I noticed that each components is parsing the bam.xml which is wrong, and need to be fixed. Lets make sure the analyzed stats are ready by end of this week, so the AF team can start working on presentation layer. Now the stats publishing part is done and committed and also the request / response size is now being captured in the valve. AS team has written some scripts to analyze request / response times. There are quite a lot of other stats that are being published but not being utilized, need to check those and write the additional scripts. Shouldn't be that hard, will sync up with AF team on this. On Tue, Jul 23, 2013 at 5:02 PM, Shariq Muhammed sha...@wso2.com wrote: 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 ami...@wso2.comwrote: 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 -- *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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Status of webapp stat publishing for aPaaS
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 ami...@wso2.comwrote: 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Status of webapp stat publishing for aPaaS
Thanks Shariq. If the bam.xml only shipped with AS? Seems like we'll have to use it for this purpose. Make sure to use secure vault for this. Lets make sure the analyzed stats are ready by end of this week, so the AF team can start working on presentation layer. On Tue, Jul 23, 2013 at 5:02 PM, Shariq Muhammed sha...@wso2.com wrote: 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 ami...@wso2.comwrote: 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 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
