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
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to