As a consumer of POMBA reporting, I would like POMBA to enrich the data being used to generate reports in order to provide more useful and richer reporting. 

In particular, the following additional information must be included int the report

• Overview

• • request-id from X-ONAP-RequestID
  • client information from X-FromAppId

In addition, reporting should avoid overloading a field in order to report specific information.  The report should be well-defined and predictable.

Note I also want this additional information or additional formatting of information to be available in the DMaaP message that gets sent with the audit report results.

Background and Implementation Hints

See the attached snapshots for the current validation/violation data events stored in elasticsearch.

Base on the POA-AUDIT-RESULT message, the data router service should deal with the following enrichment jobs while storing the validation/violation events into elasticsearch through the search-data-service. 

• The field violationDetails (which indicate the exact discrepancies between the components) need to be parsed and stored in separate fields. Note that the current nested object cannot be directly used in the kibana visualizations (? mark indicates it when looking at output). The actual field names found in there will be dynamic and need to reflect the common model names in Context Builders Mapping to Common Model.

Value

Enabler for creating useful and data-rich dashboards.

Success Criteria

• Compliant to the ask above
• Support for all ONAP best practices
• Code checked in, use documented on Wiki
  • Alignment with (by updating story or page)
    • https://wiki.onap.org/display/DW/POMBA+Reporting
• Demo to working group