Hi Sanjiva, Thanks for the clarification. Yes, it is straightforward to implement streaming the live logs as you mentioned. We will add this functionality to the APIM Log Analyzer Analytics dashboard which we are currently developing.
-- Thanks, Miyuru Dayarathna Senior Technical Lead Mobile: +94713527783 Blog: http://miyurublog.blogspot.com On Wed, Mar 30, 2016 at 8:22 AM, Sanjiva Weerawarana <[email protected]> wrote: > Miyuru the requirement is to stream the live blogs ...IMO that's very > straightforward because we just need to have maybe a partitioning scheme in > CEP by tenant and then push the raw events to a websocket channel. Of > course that should start only when a user opens that window in the API > Cloud. > > On Fri, Mar 25, 2016 at 3:38 PM, Miyuru Dayarathna <[email protected]> > wrote: > >> Hi Nuwan, >> >> It is possible to implement this feature to some extent in our current >> version. Sajith is working on to implement this functionality in our demo >> dashboard. For use case #1, we will provide drill down function on a >> particular error category. There we will be directed to a data table where >> each row corresponds to a single error event. Clicking one row will lead to >> events which has taken place within a time span (say N minutes) before and >> after the error occurred. However, in this version we will not have text >> search functionality, rather user will scroll through the text and identify >> the causes for such errors. We will create a prototype in next week on this >> scenario. >> >> @Srinath >> Thanks for providing a summary of the points discussed. You have >> summarized all the main points we discussed during the meeting. >> >> -- >> Thanks, >> Miyuru Dayarathna >> Senior Technical Lead >> Mobile: +94713527783 >> Blog: http://miyurublog.blogspot.com >> >> On Fri, Mar 25, 2016 at 9:32 AM, Nuwan Dias <[email protected]> wrote: >> >>> Regarding giving access to the raw logs for searching, etc, is it >>> feasible to support it in this release? This is a high priority request >>> coming in from API cloud. >>> >>> On Fri, Mar 25, 2016 at 9:28 AM, Srinath Perera <[email protected]> >>> wrote: >>> >>>> As per meeting ( Sanjiva, Shankar, Sumedha, Anjana, Miyuru, Seshika, >>>> Suho, Nirmal, Nuwan, Malith, SajithP, SameeraR .. pls add) >>>> >>>> >>>> 1. Drop #3 >>>> 2. Other than at above use cases are OK. >>>> 3. Need to integrate this with APIM Admin dashboard and for ESB >>>> analytics, it can run with analytics4ESB. >>>> 4. We need to polish the UIs, make the look professional >>>> >>>> Miyuru, add anything I missed. >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Mar 24, 2016 at 1:53 PM, Miyuru Dayarathna <[email protected]> >>>> wrote: >>>> >>>>> Hi Srinath, >>>>> >>>>> Yes, all the above mentioned use cases can be implemented with the >>>>> logs available from APIM and ESB. >>>>> >>>>> -- >>>>> Thanks, >>>>> Miyuru Dayarathna >>>>> Senior Technical Lead >>>>> Mobile: +94713527783 >>>>> Blog: http://miyurublog.blogspot.com >>>>> >>>>> On Thu, Mar 17, 2016 at 10:56 AM, Srinath Perera <[email protected]> >>>>> wrote: >>>>> >>>>>> Does all these logs available for APIM and ESB? >>>>>> >>>>>> --Srinath >>>>>> >>>>>> On Wed, Mar 16, 2016 at 2:37 PM, Miyuru Dayarathna <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> We have created a set of use cases to be implemented as part of the >>>>>>> developments of Log Analyzer Analytics for API Manager. >>>>>>> Specifically we will be creating a set of charts which will provide us >>>>>>> information on the following use cases on API Manager. >>>>>>> >>>>>>> 1. Number of errors (classes/messages) thrown in a specific date >>>>>>> period >>>>>>> 2. New artifact deployed >>>>>>> 3. How long do servers take to start >>>>>>> 4. How long the servers were up >>>>>>> 5. Invalid login attempts >>>>>>> 6. Message processing errors (Number of API failures) >>>>>>> 7. Access token validation errors (not sent, invalid, revoked) >>>>>>> 8. Access token expiration errors >>>>>>> >>>>>>> The attached PDF file elaborates on these use cases. Let me know if >>>>>>> you have any comments on them. >>>>>>> >>>>>>> -- >>>>>>> Thanks, >>>>>>> Miyuru Dayarathna >>>>>>> Senior Technical Lead >>>>>>> Mobile: +94713527783 >>>>>>> Blog: http://miyurublog.blogspot.com >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ============================ >>>>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>>>> Site: http://people.apache.org/~hemapani/ >>>>>> Photos: http://www.flickr.com/photos/hemapani/ >>>>>> Phone: 0772360902 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks, >>>>> Miyuru Dayarathna >>>>> Senior Technical Lead >>>>> Mobile: +94713527783 >>>>> Blog: http://miyurublog.blogspot.com >>>>> >>>> >>>> >>>> >>>> -- >>>> ============================ >>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>> Site: http://home.apache.org/~hemapani/ >>>> Photos: http://www.flickr.com/photos/hemapani/ >>>> Phone: 0772360902 >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Technical Lead - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> Thanks, >> Miyuru Dayarathna >> Senior Technical Lead >> Mobile: +94713527783 >> Blog: http://miyurublog.blogspot.com >> > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ > email: [email protected]; office: (+1 650 745 4499 | +94 11 214 5345) > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva > Lean . Enterprise . Middleware > -- Thanks, Miyuru Dayarathna Senior Technical Lead Mobile: +94713527783 Blog: http://miyurublog.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
