Hi All, While we are at it, can we add a known(and agreed) context property for correlation Id.
e.g. "X-WSO2-CorrelationId" HTTP header(on inbound) -> context-property -> X-WSO2-CorrelationId HTTP header(on outbound) This ID needs to be generated if not received and should be present in all the transports (if technically allows) This will allow us to trace a request across different products. Cheers, Ruwan On Fri, Jul 22, 2016 at 11:28 AM, Kasun Indrasiri <ka...@wso2.com> wrote: > Hi, > > We need to improve ESB 5 logging, so that we can easily identify errors > and different states. > > - Timeouts : What timeout applies in a given error condition (global, EP, > or socket TO) > - Correlate connections, request, callbacks > - Add additional information such as endpoint that failed and the target > URL. > - Use different use cases that we can think of by considering error codes > > Isuru wrote a great troubleshooting guide for ESB[1]. I think its a good > starting point to understand different errors that can occur and our log > must reflect the exact reason for a given error condition. > > Need to do this before ESB 5 GA. > > [1] > http://wso2.com/library/articles/2014/05/wso2-esb-a-guide-to-troubleshoot/ > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ruwan Abeykoon* *Associate Director/Architect**,* *WSO2, Inc. http://wso2.com <https://wso2.com/signature> * *lean.enterprise.middleware.*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
