...
| Field Name | Description |
|---|---|
| validationId | A unique identifier for the validation. Each validation has a non-deterministic UUID. Consequently, each validationId is different even if the contents of the validation are the same. |
validationTimestamp | UTC timestamp for the validation event in the format:
|
| transaction-id | A user provided transaction id. This will allow for tracing of the audit through its various operations. If the same transaction id is used as the operation that is being audited related to this service instance id, then this provides even greater traceability. In the case of POMBA, this is X-ONAP-RequestID from the REST header. |
| client | client information from X-FromAppId |
| model-version-id | The model-version-id field provided to initiate the audit |
| model-invariant-id | The model-invariant-id field provided to initiate the audit.service-instance-id |
| serviceInstanceId | Identifier of this service instance, which was provided to initiate the audit. |
| status | "Pass" or "Fail", depending on whether any violations were found |
| dataQuality | A field that reports any issues found during the audit that prevented the audit from fully being successfully run. status = "ok" or "error"; error = error message related to specific data quality issues encountered. |
| requestId | |
| modelName | |
| violations | Array of violations. See below. |
Violations
If rule violations are found, then for each violation, the following will be reported
...