...
- The violation event need to add more fields from the field "violations" available in the validation info including: modelName, errorMessage, violationDetails, indicator for manual vs automatic trigger
- The field violationDetails (which would tell the exact discrepancies; see the sample event below inside the '?violations') need to be parsed and stored in separate fields. Such nested data cannot be directly used in the kibana visualizations (? mark indicates it).
- We could further parse out the ONAP components involved with the violations to see the violation stats factored by component (from violationDetails)
- "Audit duration" stats would be useful? time taken for the auditing itself (from trigger to result).
- Any other meta-data that would be useful? e.g., who invoked the validation (user, dept), manual vs automatic trigger
2. Dashboard Ideas
...