+1 for the idea in general, what we need to do is to insert this ID as a MDC value and configure the logging appender pattern to include that ID into the logs printed into the file/console.
We are already working on something similar to this for tracing transactions across the products, for that we are using a correlation id (transaction id) between products. This effort has to work seamlessly with that too, in the case of a request that will be initiated by APIM, there will be a correlation id coming in, in the request (as a HTTP header) so the ID generation logic should look at this header, and generate a new ID only if that is not available. Thanks, Ruwan On Tue, Sep 4, 2018 at 6:38 PM Dulanja Liyanage <[email protected]> wrote: > How can we map a particular request between the wso2carbon.log and the > HTTP access log? > > IMO, we should generate this Correlation ID from a custom valve and add > that as a request attribute, and then extend the Access Log valve to print > that ID in the HTTP Access Log as well. (I haven't tried this, but I > believe this approach is feasible) > > Also, by doing this way you don't have to individually add the filter to > each webapp in the product, because valves get engaged for all the contexts. > > WDYT? > > Thanks, > Dulanja > > On Mon, Aug 20, 2018 at 4:53 PM, Thumilan Mikunthan <[email protected]> > wrote: > >> Hi All, >> *Problem* >> >> Whenever an error occurred, analyzing error log line could not give >> enough information to diagnose the error. A mechanism to track each request >> flow is helpful to diagnose. >> >> *Solution* >> Assign unique id to each request and track it down through log files. >> >> - >> >> Use a Request filter to filter all requests which come to WSO2 IS. >> - >> >> Assign a unique id for each request. >> - >> >> Print the unique id along with log lines in order to diagnose errors. >> >> *Solution Diagram* >> [image: UUID Archi.jpg] >> >> >> *Sample Scenario* >> [1] - Sample Scenario (Correlation ID-sample.jpg) >> We can easily understand that above error occurred because of illegal >> access by tracking the unique id. >> >> Please give feedback regarding this architecture. >> >> Best Regards, >> M.Thumilan >> > > > > -- > Thanks & Regards, > Dulanja Liyanage > Lead, Platform Security Team > WSO2 Inc. > -- Ruwan Linton Director - Delivery, WSO2; https://wso2.com Member, Apache Software Foundation; http://www.apache.org <http://adroitlogic.org/> email: [email protected]; cell: +94 77 341 3097; phone: +94 11 2833 436 linkedin: http://www.linkedin.com/in/ruwanlinton
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
