Name is ok. Yes, I think for advanced metrics config stuff, we will need to provide a file.
On Thu, Apr 7, 2016 at 2:02 PM, Isuru Perera <isu...@wso2.com> wrote: > Hi Azeez, > > How about carbon-metrics-extensions for new repo name? This new repo will > have the MSF4J REST API to get data from JDBC. > > I have another question regarding JDBC Reporter. Since all reporters are > now a part of metrics core, the JDBC reporter will also be available for > MSF4J. Earlier, MSF4J supported only Console, JMX and DAS reporters. In a > future MSF4J version, when metrics wants to use the JDBC reporter we need > to figure out a way to initialize the JDBC Data Source. > > In OSGi environment, I'm planning to use carbon-datasources [1]. However > we cannot use that in MSF4J. We need to be able to directly configure a > datasource for metrics. So, I thought of giving an option to initialize a > HikariCP [2] datasource directly from metrics. I can use a properties file > to configure HikariCP [3]. (I chose HikariCP as it's already used in > carbon-datasources). > > This means, when MSF4J wants to use JDBC Reporter, we need following > config files. > > - metrics.yml (To enable Metrics and JDBC Reporter) > - metrics-datasource.properties (To configure HikariCP datasource) > > WDYT? > > Thanks! > > Best Regards, > [1] https://github.com/wso2/carbon-datasources > [2] http://brettwooldridge.github.io/HikariCP/ > [3] https://github.com/brettwooldridge/HikariCP#initialization > > > On Thu, Mar 31, 2016 at 11:54 AM, Isuru Perera <isu...@wso2.com> wrote: > >> Hi Azeez, >> >> I meant the same thing as you. I should have explained it more clearly. :) >> >> So, I'll break metrics into 2 repositories. One repository will be having >> the core Metrics features, which *will be used* by MSF4J. >> >> Other metrics related repository will have the REST API, written with >> MSF4J. So, it depends on MSF4J. (I'm thinking of a name for the new repo) >> >> Thanks! >> >> Best Regards, >> >> >> On Thu, Mar 31, 2016 at 11:17 AM, Afkham Azeez <az...@wso2.com> wrote: >> >>> >>> >>> On Thu, Mar 31, 2016 at 11:03 AM, Isuru Perera <isu...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> I have another question. >>>> >>>> The MSF4J depends on Metrics and now Metrics needs MSF4J to implement >>>> REST services. So, there is a cyclic dependency. I think it's wrong that >>>> carbon-metrics repo [1] depending on msf4j repo [2]. >>>> >>>> One solution to this is to have separate repos for metrics. >>>> >>>> One repo will include only the metrics core features and it'll not >>>> depend on the MSF4J. Then MSF4J can depend on metrics core. We can create >>>> another repository to keep the REST services and gadgets to view the >>>> metrics. >>>> >>> >>> We are targeting MSF4J at external developers. Unlike our other >>> components & products, if the relevant code is in several places, it could >>> become cumbersome for external developers. I think what should be done is >>> have metrics-core, on which MSF4J depends, and then have metrics REST >>> services somewhere else. That can take a dependency on both metrics-core >>> and MSF4J. >>> >>> >>>> >>>> WDYT? >>>> >>>> Thanks! >>>> >>>> Best Regards, >>>> >>>> [1] https://github.com/wso2/carbon-metrics >>>> [2] https://github.com/wso2/msf4j >>>> >>>> On Thu, Mar 17, 2016 at 10:53 PM, Kishanthan Thangarajah < >>>> kishant...@wso2.com> wrote: >>>> >>>>> Like with generic HTTP Monitoring Dashboard (gadgets), we could have >>>>> generic gadgets for Metrics here so that products can reuse them with the >>>>> analytics dashboard. >>>>> >>>>> I think you can do a carbon 5 based release of the metrics >>>>> dependencies (a carbon feature release) and also expose those services >>>>> used >>>>> with metrics data fetching as microservices as you mentioned. >>>>> >>>>> On Mon, Mar 14, 2016 at 5:01 PM, Isuru Perera <isu...@wso2.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> Thanks for the feedback. So, we agree that the Carbon Metrics should >>>>>> continue supporting JDBC reporter and visualize the Metrics via gadgets. >>>>>> >>>>>> With Carbon Metrics v2.0.0, we will have the Console, JMX, JDBC and >>>>>> DAS reporters. >>>>>> >>>>>> I will remove all management console UIs. We need to develop REST >>>>>> APIs to get data from the database (The Metrics data reported by JDBC >>>>>> reporter). I'm planning to use MSF4J for developing REST APIs. I hope the >>>>>> security of the REST APIs will be handled by MSF4J. >>>>>> >>>>>> For Metrics visualization, we need to develop gadgets. The gadgets >>>>>> will support fetching data from the database (via MSF4J REST APIs) and >>>>>> from >>>>>> the DAS REST APIs. >>>>>> >>>>>> My next question is where we can keep these gadgets. Is it okay to >>>>>> develop these gadgets within Carbon Metrics repository? Since these >>>>>> gadgets >>>>>> will be in a CAPP and it needs to be deployed in a dashboard server, I >>>>>> think it's better to have these gadgets in a separate repository. For >>>>>> example, I think that there is no point having the Metrics CAPP in a >>>>>> Carbon >>>>>> Metrics feature as the Carbon Metrics features will be installed to a >>>>>> normal product (eg. ESB) and the analytics related features will not be >>>>>> available in a normal product. We need to install the CAPP to a dashboard >>>>>> server. So, how are we going to let other users to deploy Metrics CAPP? >>>>>> >>>>>> Please share your thoughts. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> Best Regards, >>>>>> >>>>>> >>>>>> On Mon, Feb 15, 2016 at 2:12 PM, Ramith Jayasinghe <ram...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> agreed. >>>>>>> >>>>>>> On Mon, Feb 15, 2016 at 2:08 PM, Sriskandarajah Suhothayan >>>>>>> <s...@wso2.com> wrote: >>>>>>> > By default all products will have DAS4X, hence we should be able >>>>>>> to see the >>>>>>> > metrics also there as that's part for analytics. Further DAS4X >>>>>>> also contains >>>>>>> > DS, therefore having the metrics as gadgets will make sense right? >>>>>>> > >>>>>>> > Regards >>>>>>> > Suho >>>>>>> > >>>>>>> > On Mon, Feb 15, 2016 at 10:20 AM, Ramith Jayasinghe < >>>>>>> ram...@wso2.com> wrote: >>>>>>> >> >>>>>>> >> HI suho, >>>>>>> >> Does this mean If someone what to see matrices in a UI they have >>>>>>> to >>>>>>> >> run DS? (or we install what ever feature in the product by >>>>>>> default) >>>>>>> >> regards >>>>>>> >> Ramith >>>>>>> >> >>>>>>> >> On Sat, Feb 13, 2016 at 1:17 PM, Sriskandarajah Suhothayan >>>>>>> >> <s...@wso2.com> wrote: >>>>>>> >> > IMHO we have to write some gadgets on DS as the way forward. >>>>>>> >> > We can use the inter gadget communication to select and update >>>>>>> other >>>>>>> >> > charts >>>>>>> >> > on which hierarchy we are currently in and use that info in >>>>>>> other >>>>>>> >> > gadgets to >>>>>>> >> > query data from the DBs. >>>>>>> >> > >>>>>>> >> > I think we still need to support RDBMs >>>>>>> >> > >>>>>>> >> > Regards >>>>>>> >> > Suho >>>>>>> >> > >>>>>>> >> > On Fri, Feb 12, 2016 at 5:25 PM, Ramith Jayasinghe < >>>>>>> ram...@wso2.com> >>>>>>> >> > wrote: >>>>>>> >> >> >>>>>>> >> >> Having a basic GUI to view statistics is very useful. but I'm >>>>>>> not sure >>>>>>> >> >> how that aligns with overall analytics story. >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> On Fri, Feb 12, 2016 at 5:02 PM, Isuru Perera <isu...@wso2.com> >>>>>>> wrote: >>>>>>> >> >> > Hi, >>>>>>> >> >> > >>>>>>> >> >> > I have few questions regarding $subject. >>>>>>> >> >> > >>>>>>> >> >> > The latest Carbon Metrics release (v1.2.1) has "features" >>>>>>> that can be >>>>>>> >> >> > installed on any Carbon 4.x.x products. It also has >>>>>>> Management >>>>>>> >> >> > Console >>>>>>> >> >> > UIs. >>>>>>> >> >> > For example: >>>>>>> https://docs.wso2.com/display/MB300/Using+JVM+Metrics >>>>>>> >> >> > >>>>>>> >> >> > This metrics management console UI can be extended via an >>>>>>> OSGi >>>>>>> >> >> > fragment >>>>>>> >> >> > bundle to develop custom UIs. For example: >>>>>>> >> >> > https://docs.wso2.com/display/MB300/Using+Messaging+Metrics >>>>>>> >> >> > >>>>>>> >> >> > This is one of main features in Carbon Metrics. >>>>>>> >> >> > >>>>>>> >> >> > The Metrics configurations are done in >>>>>>> >> >> > "$CARBON_HOME/repository/conf/metrics.xml". The >>>>>>> configuration is in >>>>>>> >> >> > XML. >>>>>>> >> >> > >>>>>>> >> >> > If we are supporting Carbon Metrics in Carbon 5, I think >>>>>>> following >>>>>>> >> >> > needs >>>>>>> >> >> > to >>>>>>> >> >> > be done. >>>>>>> >> >> > >>>>>>> >> >> > Use latest Carbon P2 Plugin and update Metrics features to be >>>>>>> >> >> > compatible >>>>>>> >> >> > with Carbon 5 >>>>>>> >> >> > Use YAML for configuration. >>>>>>> >> >> > Admin services for Metrics Data fetching need to be >>>>>>> converted as REST >>>>>>> >> >> > services. >>>>>>> >> >> > Remove Management Console UIs as there is no support for >>>>>>> Management >>>>>>> >> >> > Console >>>>>>> >> >> > UIs in Carbon 5. >>>>>>> >> >> > Set source and target Java version to Java 8. We can use >>>>>>> Java 8 >>>>>>> >> >> > features. >>>>>>> >> >> > >>>>>>> >> >> > If we remove Management Console UIs, how can we implement >>>>>>> the UIs to >>>>>>> >> >> > visualize Metrics data? >>>>>>> >> >> > >>>>>>> >> >> > I heard that we should use only DAS for visualizing Metrics. >>>>>>> But I >>>>>>> >> >> > prefer to >>>>>>> >> >> > have separate UI to visualize the metrics from the database. >>>>>>> Then we >>>>>>> >> >> > can >>>>>>> >> >> > use >>>>>>> >> >> > Metrics UIs without depending on WSO2 DAS. >>>>>>> >> >> > >>>>>>> >> >> > If we don't want to have a UI, we will have to drop the JDBC >>>>>>> reporter >>>>>>> >> >> > as >>>>>>> >> >> > well. >>>>>>> >> >> > >>>>>>> >> >> > Question to CEP Team: There is another UI to show >>>>>>> hierarchical >>>>>>> >> >> > metrics. >>>>>>> >> >> > What >>>>>>> >> >> > will happen to that in Carbon 5? >>>>>>> >> >> > >>>>>>> >> >> > How can we implement REST services in Carbon 5? (We may not >>>>>>> need this >>>>>>> >> >> > if >>>>>>> >> >> > we >>>>>>> >> >> > are not developing any UIs) >>>>>>> >> >> > >>>>>>> >> >> > By default, Metrics data are stored in local H2 database. >>>>>>> Can we use >>>>>>> >> >> > the >>>>>>> >> >> > same approach in Carbon 5? (This is not needed if we stop >>>>>>> using the >>>>>>> >> >> > JDBC >>>>>>> >> >> > reporter). >>>>>>> >> >> > >>>>>>> >> >> > There is also a properties file to configure Metric Levels. >>>>>>> I hope >>>>>>> >> >> > that's >>>>>>> >> >> > not a problem. >>>>>>> >> >> > >>>>>>> >> >> > The plan is to use v2.0.0 for Metrics release with Carbon 5. >>>>>>> We can >>>>>>> >> >> > maintain >>>>>>> >> >> > v1.x.x branch for Carbon 4.x.x products. >>>>>>> >> >> > >>>>>>> >> >> > Currently the WSO2 Gateway and MSF4J uses Carbon Metrics as >>>>>>> Maven >>>>>>> >> >> > Dependencies. We need a proper Carbon 5 supported release to >>>>>>> >> >> > integrate >>>>>>> >> >> > Carbon Metrics to these products. >>>>>>> >> >> > >>>>>>> >> >> > I really appreciate your feedback on this. >>>>>>> >> >> > >>>>>>> >> >> > Thanks! >>>>>>> >> >> > >>>>>>> >> >> > Best Regards, >>>>>>> >> >> > >>>>>>> >> >> > -- >>>>>>> >> >> > Isuru Perera >>>>>>> >> >> > Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >>>>>>> >> >> > Lean . Enterprise . Middleware >>>>>>> >> >> > >>>>>>> >> >> > about.me/chrishantha >>>>>>> >> >> > Contact: +IsuruPereraWSO2 >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> >> >> -- >>>>>>> >> >> Ramith Jayasinghe >>>>>>> >> >> Technical Lead >>>>>>> >> >> WSO2 Inc., http://wso2.com >>>>>>> >> >> lean.enterprise.middleware >>>>>>> >> >> >>>>>>> >> >> E: ram...@wso2.com >>>>>>> >> >> P: +94 777542851 >>>>>>> >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> >> > >>>>>>> >> > -- >>>>>>> >> > S. Suhothayan >>>>>>> >> > Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>> >> > WSO2 Inc. http://wso2.com >>>>>>> >> > lean . enterprise . middleware >>>>>>> >> > >>>>>>> >> > cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >>>>>>> >> > twitter: http://twitter.com/suhothayan | linked-in: >>>>>>> >> > http://lk.linkedin.com/in/suhothayan >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> -- >>>>>>> >> Ramith Jayasinghe >>>>>>> >> Technical Lead >>>>>>> >> WSO2 Inc., http://wso2.com >>>>>>> >> lean.enterprise.middleware >>>>>>> >> >>>>>>> >> E: ram...@wso2.com >>>>>>> >> P: +94 777542851 >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > -- >>>>>>> > S. Suhothayan >>>>>>> > Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>> > WSO2 Inc. http://wso2.com >>>>>>> > lean . enterprise . middleware >>>>>>> > >>>>>>> > cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >>>>>>> > twitter: http://twitter.com/suhothayan | linked-in: >>>>>>> > http://lk.linkedin.com/in/suhothayan >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ramith Jayasinghe >>>>>>> Technical Lead >>>>>>> WSO2 Inc., http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> E: ram...@wso2.com >>>>>>> P: +94 777542851 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Isuru Perera >>>>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> about.me/chrishantha >>>>>> Contact: +IsuruPereraWSO2 >>>>>> <https://www.google.com/+IsuruPereraWSO2/about> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Kishanthan Thangarajah* >>>>> Associate Technical Lead, >>>>> Platform Technologies Team, >>>>> WSO2, Inc. >>>>> lean.enterprise.middleware >>>>> >>>>> Mobile - +94773426635 >>>>> Blog - *http://kishanthan.wordpress.com >>>>> <http://kishanthan.wordpress.com>* >>>>> Twitter - *http://twitter.com/kishanthan >>>>> <http://twitter.com/kishanthan>* >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Isuru Perera >>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >>>> Lean . Enterprise . Middleware >>>> >>>> about.me/chrishantha >>>> Contact: +IsuruPereraWSO2 >>>> <https://www.google.com/+IsuruPereraWSO2/about> >>>> >>> >>> >>> >>> -- >>> *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 <%2B94%2077%203320919>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 >>> <http://lk.linkedin.com/in/afkhamazeez>* >>> >>> *Lean . Enterprise . Middleware* >>> >> >> >> >> -- >> Isuru Perera >> Associate Technical Lead | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about> >> > > > > -- > Isuru Perera > Associate Technical Lead | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > Contact: +IsuruPereraWSO2 <https://www.google.com/+IsuruPereraWSO2/about> > -- *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 3320919blog: **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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
