I believe this means that we are not exposing enough information through ESB stats.
>From a monitoring perspective, the counts have to be correlated to when, what, why and how. Otherwise, this information is useless to anyone who wants to dig into stats and would have no value. On Thu, Nov 10, 2011 at 12:35 PM, Hiranya Jayathilaka <hira...@wso2.com>wrote: > This cannot be done without doing some major changes in the current > implementation. Also implementing this is probably not a good idea as that > will require Synapse to do some additional work per each invocation thus > increasing the latency. Current stat implementation has no impact on the > latency. (Current implementation is done that way for a reason) > > If you want to capture additional metrics such as the user and timestamp > please consider extending the current statistics implementation so the user > can specify a list of additional parameters to keep track of along with the > statistics. We can use XPath to specify these parameters and so that way > it's very generic. > > Thanks, > Hiranya > > On Thu, Nov 10, 2011 at 9:05 PM, Tharindu Mathew <thari...@wso2.com>wrote: > >> This is particularly interesting because right now we are losing data >> (who invocated, what time) that is very useful, when analyzing data later >> on. >> >> ESB folks, any help on this? >> >> >> >> On Thu, Nov 10, 2011 at 1:25 AM, Kasun Weranga <kas...@wso2.com> wrote: >> >>> >>> >>> On Wed, Nov 9, 2011 at 4:58 PM, Buddhika Chamith <buddhi...@wso2.com>wrote: >>> >>>> Hi, >>>> >>>> BAM currently uses a MediationStatisticsObserver implementation to >>>> gather mediation statistics from ESB. The obtained statistics are periodic >>>> and are cumulative. Is it possible to obtain these statistics per each >>>> invocation? >>>> >>> >>> +1, >>> >>> Currently we are getting aggregated count from last publish time, but >>> when load increases sometimes we get summery of about 6000 events for that >>> time period. So it is better if we can get statistics per each invocation, >>> like in service stats data publisher (use axis2 handler to get statistics >>> and publish asynchronously to bam). Also this will be helpful to get some >>> additional data like client IP, user-agent details and etc.. In addition to >>> that this change will be valuable for CEP integration in future too. >>> >>> Is there any way to get mediation statistics per invocation? >>> >>> >>>> Regards >>>> Buddhika >>>> >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Kasun Weranga* >>> Software Engineer >>> ** >>> *WSO2, Inc. >>> *lean.enterprise.middleware. >>> mobile : +94 772314602 >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :<http://sanjeewamalalgoda.blogspot.com/> >>> http://kasunweranga.blogspot.com/ >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Regards, >> >> Tharindu >> >> blog: http://mackiemathew.com/ >> >> > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Regards, Tharindu blog: http://mackiemathew.com/
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
