Hi Kasun, Implemented the scenario, now it works fine other than below limitations
* need to add a debug point in where ever we need to see wirelogs (for example if we need to see wirelogs for some send mediator, we need to put a debug point to that mediator) * need to right click on the mediator and click "show wirelogs" to view the wirelogs for that mediator( In the code review , it was suggested to change wirelog view so that it shows the corresponding wirelogs when ever we clicked on a mediator, didn't had time to do this yet) * flow is not implemented in nhttp transport * flow is not implemented in case we use clone mediator in the flow (need to clone the log holder object which reside inside message context and need to think of a way to aggregate that later) * have to test with some complex flows Other than that, now we can correlate and see wire logs for mediators (for example if there is a send mediator in the flow, we can see the wirelog sent to back end from the send mediator and the response for it, faced some difficulties when relating those information with the corresponding mediator when the messages are large, and was able to overcome them by introducing some locking mechanism in wirelevel. Thanks, On Tue, May 3, 2016 at 12:14 PM, Kasun Indrasiri <[email protected]> wrote: > @Rajith : Can you please update the progress on this? > > On Mon, Apr 4, 2016 at 9:52 PM, Viraj Rajaguru <[email protected]> wrote: > >> Hi Rajith, >> >> With the current implementation, we can only see the wire logs from >> Developer Studio while debugging without any correlation with the mediator. >> This might be acceptable when we have a simple message flow to debug with >> one or two back-end calls etc. But it comes to scenarios with large number >> of back-end calls, service chaining, scatter-gather etc.. the way we >> showing the wire logs might not be useful for users since we do not have >> any correlation. >> >> At the initial discussion we had with Kasun, we thought of having this >> correlation with mediators for wire logs. What we thought is to have a new >> view in Developer Studio to show the wire logs and show only the associated >> wire logs for a particular mediator(call, send etc.) once we click on the >> relevant mediator while debugging. >> >> As per the discussion we are having currently, it is not straightforward >> to have this correlation with mediators. But it might be really useful if >> we can implement this. >> >> Thanks, >> Viraj. >> >> On Tue, Apr 5, 2016 at 9:30 AM, Isuru Udana <[email protected]> wrote: >> >>> Hi Kasun, >>> >>> TRANSPORT_HEADERS case is somewhat different, because we have access to >>> the all the transport level headers from the HttpRequest coming from Http >>> Core level, but for the entire message we won't be able to take that >>> approach. >>> >>> Thanks. >>> >>> On Tue, Apr 5, 2016 at 9:24 AM, Isuru Udana <[email protected]> wrote: >>> >>>> Hi Kasun, >>>> >>>> It is not possible to make it a part of the message context as we don't >>>> have access to any context at the Wire level (Not even the http core level >>>> context). >>>> >>>> >>>> On Tue, Apr 5, 2016 at 9:11 AM, Kasun Indrasiri <[email protected]> wrote: >>>> >>>>> Can we have wire level message information as part of the message >>>>> context (Of course we have to do this only if debugging is enabled or >>>>> something), so that we can correlate message and its wire level message >>>>> while debugging. >>>>> >>>>> >>>>> On Fri, Apr 1, 2016 at 9:46 AM, Rajith Vitharana <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I was able to simply show the wire log (what is just written to the >>>>>> wire) as a property when a debug point get hits, But in that case there >>>>>> are >>>>>> some drawbacks, such as we can't see back end call wire logs because we >>>>>> can't set debug point just after back end call happens, (we can see back >>>>>> end response but not back end request) and also we can't see the final >>>>>> response to the client as well(due to the same reason). >>>>>> >>>>>> But if we can just print the wire logs (as already doing when wire >>>>>> logs are enabled in ESB) in Developer studio side when something gets >>>>>> written to the wire, IMO that would be more usable, If we are going to do >>>>>> that, we will have to figure out a way to filter the wire logs for that >>>>>> specific service only(which is being debugged) otherwise it will show >>>>>> everything which get's written to the wire. >>>>>> WDYT? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> On Thu, Mar 31, 2016 at 10:54 AM, Kasun Indrasiri <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> We came across a sort of a mandatory requirement for debugger : >>>>>>> debugging wire level message from the visual editor. We need to >>>>>>> figure out how to represent this visually + implement this at the core >>>>>>> engine level (probably propagate these transport level information to >>>>>>> the >>>>>>> mediation level). >>>>>>> >>>>>>> With this feature, the debugger can be used to design/debug >>>>>>> complete end to end message flows in ESB. >>>>>>> >>>>>>> Thanks, >>>>>>> -- >>>>>>> Kasun Indrasiri >>>>>>> Software Architect >>>>>>> WSO2, Inc.; http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> cell: +94 77 556 5206 >>>>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rajith Vitharana >>>>>> >>>>>> Software Engineer, >>>>>> WSO2 Inc. : wso2.com >>>>>> Mobile : +94715883223 >>>>>> Blog : http://lankavitharana.blogspot.com/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Kasun Indrasiri >>>>> Software Architect >>>>> WSO2, Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> >>>>> cell: +94 77 556 5206 >>>>> Blog : http://kasunpanorama.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> *Isuru Udana* >>>> Associate Technical Lead >>>> WSO2 Inc.; http://wso2.com >>>> email: [email protected] cell: +94 77 3791887 >>>> blog: http://mytecheye.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> *Isuru Udana* >>> Associate Technical Lead >>> WSO2 Inc.; http://wso2.com >>> email: [email protected] cell: +94 77 3791887 >>> blog: http://mytecheye.blogspot.com/ >>> >> >> >> >> -- >> Viraj Rajaguru >> Senior Software Engineer >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
