Hi kasun,
On Wed, Jul 31, 2013 at 1:18 PM, Kasun Gajasinghe <[email protected]> wrote: > We need step 2 since there must be a way to enable/disable webapp stats > tenant-wide. And, that's where we configure the BAM stream definition, BAM > Receiver URL, and credentials. So, we can't remove this one. > > I do not know the rationale behind having to enable/disable stat > publishing globally via bam.xml. We have simply followed the mechanism used > by ServiceDataPublishing to have consistency. BAM team, can you provide the > reason for this? > The ServiceDataPublishing is done by axis2 handlers, and therefore even if the the user doesn't want to send the statistics to BAM, these handlers will be invoked which is a performance hit. Due to this reason we thought of having this configuration to globally engage this handler or not in the request/response path. This was discussed in detail @dev mail thread 'Dev] [BLOCKER] BAM handlers taking 55% of the time in Web service invocation flow!'. Thanks, Sinthuja. > > We need to have an option to configure stat publishing per axis2 service. > This feature will not go in to 5.2.0 but will be available in a future > release. > > Thanks, > KasunG > > > On Wed, Jul 31, 2013 at 1:08 PM, Asanka Vithanage <[email protected]>wrote: > >> HI All, >> >> I have try to configure AS to publish web statistcs to BAM.But it seems >> (on user perspective) there are so many configuration steps need to follow >> to achieve this task. >> >> Steps required: >> 1. Need to enable <WebappDataPublishing>disable</WebappDataPublishing> on >> {AS_HOME}/repository/conf/etc/ and open bam.xml. >> >> 2. Need to select "Enable webapp stats" check box on >> "Home>Configure>Webapp Data Publishing" through AS management console >> >> 3. Need to select " Enable BAM Statistics" check box on individual web >> application dashboard >> >> >> >> I feel we can get rid of first two steps and just enough the third >> step.So user can enable the web statistics publishing for a web app by >> following just one simple step. >> WDYT? >> >> Further that with current implementation we can't enable stat publishing >> for services one by one. >> We have to enable or disable stats publishing for all deployed services. >> Isn't that better to allow enable stat publishing at each service level? >> >> >> >> -- >> Asanka Vithanage >> Senior Software Engineer -QA >> Mobile: +94 0716286708 >> Email: [email protected] >> WSO2 Inc. www.wso2.com >> >> > > > -- > *Kasun Gajasinghe* > Software Engineer; > Development Technologies Team, WSO2 Inc.; http://wso2.com > > > , > *email: **kasung AT spamfree wso2.com > > > ** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe > > > * > * > *blog: **http://kasunbg.org* <http://kasunbg.org> > > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > > * > * > -- *Sinthuja Rajendran* Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
