The problem I see is all the configuration is stored in the registry. So this will be fixed when configuration is stored into a deployable files. Then dip-sync will solve the problem of clustering AFAIU.
* Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 On Fri, Aug 2, 2013 at 6:21 AM, Samisa Abeysinghe <[email protected]> wrote: > So in summary, what I understood is that, for WebApps monitoring, we > should have the same model as service monitoring, including the cluster > drill down capability. > Did I get it right? > > > On Thu, Aug 1, 2013 at 9:21 AM, Supun Malinga <[email protected]> wrote: > >> Also we would need to be able to use a config. based approach rather than >> ui for this.. >> >> thanks, >> >> >> On Wed, Jul 31, 2013 at 8:25 PM, Afkham Azeez <[email protected]> wrote: >> >>> An important aspect to keep in mind is monitoring artifacts deployed on >>> a cluster. The stats from multiple nodes have to be summarized & an >>> aggregated view should be shown. Our current System statistics UI is broken >>> in terms of showing stats in a cluster. >>> >>> Azeez >>> >>> >>> On Wed, Jul 31, 2013 at 6:00 PM, Maninda Edirisooriya >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> At present Service Statistics and Activity Service data are configured >>>> to be published at a single global location. That means all the service >>>> statistics data should go to a single stream and all the activity data >>>> should also go to a single stream. >>>> >>>> But in practice the user may host different types of apps in an AS >>>> instance that are used for different purposes. So one set of apps may need >>>> to be monitored separately for statistics. (for e.g., sales application >>>> should be monitored in a different stream than the stock level controlling >>>> service statistics stream, as their fields are different and use cases are >>>> different) Similarly only some services need to be monitored for activities >>>> with full SOAP header and SOAP body. And each service should be able to >>>> maintain its own stream for keeping messages for logging purpose or >>>> activity monitoring purpose. And the services need to be monitored, should >>>> be configured individually. >>>> >>>> I think this requirement is same for the Web App monitoring. When web >>>> app activities are monitored not all the web app data are interested. If >>>> all web app data are going to the same column family with different stream >>>> versions still the large column family will effect the performance of the >>>> Hive query / Cassandra operation. So each web app should be possible to be >>>> monitored individually with its own stream. >>>> >>>> Therefore, other than configuring each monitoring configuration (i.e., >>>> service stats, activity service, web app stats) in a global location in >>>> WSO2 AS, it is better to configure each service / web app individually. We >>>> can include a button like the "Enable Service Statistics" button per >>>> service / web app and when selected, the monitoring configuration UI should >>>> appear in the same page or should direct to a configuration page unique for >>>> each service / web app. It is fine to maintain a global configuration page >>>> for BAM connection credentials and connection parameters, as every stream >>>> should is assumed to be going to the same BAM server. >>>> >>>> If we are planning to deal with multiple BAM servers with a single AS, >>>> the configuration page should be configured to different BAM servers each >>>> having a unique name. When a service / web app is going to be configured >>>> for publishing, the BAM server can be selected from the existing set of BAM >>>> servers configured in the global location. >>>> * >>>> Maninda Edirisooriya* >>>> Software Engineer >>>> *WSO2, Inc. >>>> *lean.enterprise.middleware. >>>> >>>> *Blog* : http://maninda.blogspot.com/ >>>> *Phone* : +94 777603226 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* 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* >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Supun Malinga, >> >> Senior Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - [email protected] <[email protected]> >> mobile - 071 56 91 321 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
