On Mon, Feb 1, 2016 at 2:21 PM, Anjana Fernando <[email protected]> wrote:
> Hi, > > The initial use case I had with Log Analyzer was, as a general log > analysis tool, where users can just point to a log location, can be > WSO2/non-WSO2 logs, and run queries against it / create dashboards. The > concern I've with integrating log analyzer also with our new analytics > distributions is, whether we will have some considering overlapping > functionality between the two. The DAS4X analytics effort is to basically > create mostly the static dashboards that would be there (maybe with > alerts), which can be successfully done by internally publishing all the > events required for those. But then, if we also say, you can/should use log > analyzer (which is a different UI/experience altogether) to create > dashboards/queries, that we missed from the earlier effort, that does not > sound right. > Anjana, point is dynamic/ad-hoc query use cases. E.g. 1) You see a new error, and want to check has it happend before. 2) You see two error happening together. You need to know it has happend together before. > > So the point is, as I see, if we do the pure DAS4X solution right for a > product, they do not have an immediate need to use the log analysis > features again to do any custom analysis. But of course, if they want to > process the logs also nevertheless, they can setup the log analyzer product > and do it, for example, as a replacement to syslog, for centralized log > storage. > > Cheers, > Anjana. > > On Mon, Feb 1, 2016 at 2:04 PM, Srinath Perera <[email protected]> wrote: > >> Hi All, >> >> I believe we should integrate Log Analyzer with analytics distributions >> of the products. >> >> It is true some of the information you can take from Log analyzer is >> already available under normal analytics. For those, we do not need to use >> Log analyzer. >> >> However, log analyzer let us find and understand use cases that is not >> already instrumented. For example, when we see a error, we might check has >> a similar error happened before. Basically we can check ad-hoc dynamic use >> cases via log analyzer. Example of this is analytics done by our Cloud >> team. >> >> In general, log analyzer will be used by advanced users who will >> understand inner workings for the product. It will be a very powerful >> debugging tool. >> >> However, if we want to embed the log analyzer, then it is challenging due >> to ruby based log stash we use with log analyzer. I think in that case, we >> also need a java based log agent. >> >> Please comment. >> >> Thanks >> Srinath >> -- >> ============================ >> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >> Site: http://people.apache.org/~hemapani/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
