As a user of POMBA, I want the transaction Id and application id to be logged as they are defined in the ONAP Logging Guideline by all POMBA components, including network discovery.  to be used throughout the entire POMBA audit, including calls to Context Builders and their data sources (SDC, SDNC, A&AI, etc).

The clarify,  throughout the POMBA audit means that whatever gets passed in the audit trigger (REST API) will get used throughout. This means that if an application like MSO is calling POMBA and using the header fields of transaction id and application in a way that makes sense to them, we will honour these values throughout our audit and log the fields.

Note that these header fields get logged using different names (transaction id and partner), as per the logging guidelines can be found at

https://wiki.onap.org/pages/viewpage.action?pageId=28378955#ONAPApplicationLoggingSpecificationv1.2(Casablanca)-MDC-RequestID

The following information shall be supported in the header

• X-ONAP-RequestID - some-transaction-id
• X-FromAppId: some-app-id (SDC, VID, etc)

This information

• Accepted as header information on all REST API
• Included in appropriate log messages for a given Microservice
• Passed on as part of any REST calls that the Microservice itself makes.

The scope of this requirement includes

• POMBA audit initiation
• All Context Builder and Data Dictionary integration
• Network Discovery API

Success Criteria

• Above features are supported
• Code tested and checked in
• Relevant wiki pages are updated

Exclusions

• Complete compliance to the Logging Guidelines