ONAP Logging Guidelines (https://wiki.onap.org/download/attachments/1015849/ONAP%20application%20logging%20guidelines.pdf?api=v2) 
talks about having a Request ID as a "a universally unique value that identifies a single transaction request within the ONAP platform" and using it for "tracing of the flow of processing that tells what ONAP components and sub components are involved in its processing". 

Currently, when SO calls A&AI REST APIs, it creates a new Request ID. This will break the tracking of transaction flow across the systems. 

Fix proposed is: 
REST API from SO to A&AI, should first check the MDC for Request ID. If found, then pass the same. Otherwise create new Request ID (UUID), pass it to A&AI and set it in MDC.