The StatisticsPublishers (or the new agents) will continue to publish stats at the node level to BAM sever.
On Wed, Feb 22, 2012 at 1:43 PM, Tharindu Mathew <thari...@wso2.com> wrote: > So, this means that the original statistics will not be altered. It is > just the presentation that will change. If I want to obtain statistics of > the individual node from the backend I can still get that. > > Is this correct? > > If this is the case, it should preserve the individual stats while adding > in cluster wide stats. Some users maybe interested in individual node stats > as well. > > > On Wed, Feb 22, 2012 at 1:27 PM, Afkham Azeez <az...@wso2.com> wrote: > >> This is related to the user experience of the system statistics UI. Say a >> sends 3 requests to the same service, and then when he goes to the service >> stats page of that service, he sees only 1 request since the LB has routed >> the 3 requests to 3 different nodes. That is broken. We ned to fix that. >> The nodes will still continue to gather stats at an individual node level, >> but the UI will show aggregated stats. >> >> >> On Tue, Feb 21, 2012 at 1:01 PM, Tharindu Mathew <thari...@wso2.com>wrote: >> >>> Hi Azeez, >>> >>> Wouldn't we lost the ability to view statistics from a single node when >>> we do this? Different nodes showing different statistics is ok. >>> >>> To view cluster wise, we are using BAM as a point for cluster >>> monitoring. We have done a sample on handling this aspect from the BAM >>> side, where we aggregate and show cluster wise. >>> >>> On Tue, Feb 21, 2012 at 12:38 PM, Afkham Azeez <az...@wso2.com> wrote: >>> >>>> When you get directed to different nodes in the cluster, you will see >>>> different values for system statistics. For example, the service >>>> request/response counts may be different. To overcome this, we need to send >>>> a cluster message to all members in the relevant cluster, gather the stats >>>> from those members, and then display them. Who is going to work on this? It >>>> is not very difficult to implement. >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>>> >>>> _______________________________________________ >>>> Stratos-dev mailing list >>>> stratos-...@wso2.org >>>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev >>>> >>>> >>> >>> >>> -- >>> Regards, >>> >>> Tharindu >>> >>> blog: http://mackiemathew.com/ >>> M: +94777759908 >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > M: +94777759908 > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
