...
- automatic deployment of kibana (version 6.1.2) through oom (currently, it is manually installed), configure/install all POMBA dashboards
- if necessary for any audit results parsing, automatic deployment of logstash (version 6.1.2) through oom
Feature Enhancements (Questions)
- Any change of enhancement (add more fields) is desired for the validation/violation data being pushed to elasticsearch?
- violationDetails (which would tell the exact discrepancies; see the sample event below in the '?violations') need to be sent/stored by data-router in separate fields or parsed (using logstash)? Such nested info cannot be used in the kibana visualizations.
- We could parse out the components involved with the violations to see the violation stats factored by component
- "Elapsed time after orchestration" would be useful? if the result could change for the same audit requests at different times since orchestration
- "Audit duration" stats would be useful? time taken for the auditing (from trigger to result)
- Any other meta-data that would be useful? e.g., who invoked the validation (user, dept) "Elapsed time after orchestration" would be useful? to get an idea when the instance content would drift from the intended info if it can happen.
(Note) Below are the sample validation and violation events currently stored in ES that will be the data source for the Kibana dashboards.
...