+1 for introducing pluggable log provider concept for log UI. Manu, I think you can contribute your code written to pull logs from elastic search.
On Tue, May 13, 2014 at 10:04 AM, Manuranga Perera <[email protected]> wrote: > Under current clustering guidelines, in order to view logs in any product, > a Cassandra cluster has to be maintained separately. The logs are published > to Cassandra, and subsequently pulled and viewed in the console log viewer > component. In a non-clustered environment, it uses the in-memory data > structure to pull logs form. Currently this code sections are separated by > 'if-else' constructs. > > This proposal suggests to refactor the log reader specific logic to > separate classes with a common super class, such that it can be switched > through configuration (much like log appenders). > > Furthermore, (even though it's not a part of this proposal) I would like > to point out, that having a Cassandra dependency on a simple functionality > like viewing logs is not optimal. > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
