On Mon, May 7, 2012 at 10:22 AM, Amani Soysa <[email protected]> wrote: > > > On Mon, May 7, 2012 at 10:09 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> On Mon, May 7, 2012 at 9:47 AM, Amani Soysa <[email protected]> wrote: >> >>> Yes you cannot view the stacktrace from the current logging >>> implementation, because we are using file systems to store logs and we are >>> filtering logs line by line. This can be fixed by using a custom appender >>> like CassandraAppender or DBAppender. >>> >> >> At least if the tenants could see the stacktraces when things go wrong, >> that will be a MAJOR improvement. You generally don't look at logs when >> things work. You generally don't look at info level logs. You only look at >> logs when there are errors. In that aspect, our logging implementation is >> not useful for any sort of trouble shooting, like I experienced first hand >> when things failed for me. Can you treat this as a high priority item and >> get it fixed? >> > Yes will do... Ive been working on Virtual host features and was out of > touch with logging new improvements. I will talk to deep and fix these > issues ASAP. we were going with Cassandra approach in order to overcome > this issue. >
Please check the thread with subject "RFC: Architecture for Stratos Log Processing" related to new logging architecture in architecture list. In the implementation we can modify the syslog appender written by Amani to generate events and BAM eventreceiver will insert log lines to Cassandra CF. There may be some modifications to logging-mgt-console. Thanks, Deependra. >>> However most of the ESB related logs cannot be extracted using the >>> current logging implementation because synapse component is not >>> multi-tenant. There is another issue[1] related to this we are in the >>> process of fixing this issue. >>> >>> [1] - https://wso2.org/jira/browse/STRATOS-549 >>> >>> Regards >>> Amani >>> >>> >>> On Mon, May 7, 2012 at 9:34 AM, Afkham Azeez <[email protected]> wrote: >>> >>>> Actually there are major issues with logging. When most things fail, >>>> you cannot see any logs as a tenant. We genrally request for the logs from >>>> Sanjaya. So to make this useful, the log UI should show detailed >>>> stacktraces. >>>> >>>> >>>> On Mon, May 7, 2012 at 7:32 AM, Amani Soysa <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Sat, May 5, 2012 at 1:43 PM, Afkham Azeez <[email protected]> wrote: >>>>> >>>>>> I just tried the sample in this article and everything works >>>>>> perfectly. >>>>>> >>>>>> However, there is a major usability issue. Non of the messages logged >>>>>> by the log mediator are visible in the Stratos logs section. Nor are the >>>>>> error logs visible. Amani, can you look into this and fix it ASAP? >>>>>> >>>>> Yes I will look into this. >>>>> >>>>>> >>>>>> >>>>>> On Sat, May 5, 2012 at 1:13 PM, Afkham Azeez <[email protected]> wrote: >>>>>> >>>>>>> See the comment from a user on >>>>>>> http://wso2.org/library/articles/2011/01/wso2-esb-by-example-service-chaining >>>>>>> >>>>>>> Perhaps this is fixed now. >>>>>>> >>>>>>> -- >>>>>>> *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* >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *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* >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> *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* >>>> >>>> >>> >> >> >> -- >> *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* >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Deependra Ariyadewa WSO2, Inc. http://wso2.com/ http://wso2.org email [email protected]; cell +94 71 403 5996 ; Blog http://risenfall.wordpress.com/ PGP info: KeyID: 'DC627E6F'
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
