...
- Any change of the validation/violation data being pushed to elasticsearch?
- violationDetails (which tells what is really different) need to be parsed (using logstash) or sent/stored by search-service (see the sample event below)? Kibana cannot use such nested info in the visualizations.
- Any other meta-data useful? e.g., who invoked the validation (user, dept)
- "(audit) Time elapsed from orchestration time" would be useful? to get an idea when the instance content would drift from the intended info.
(Note) Below are the sample validation and violation events currently stored in ES.
2. Dashboard Ideas
...
(Note) One dashboard type could need multiple dashboard pages depending on the amount of visualizations.
Dashboard Type | Description (What To Want to See) | Required Information To Show (Visualizations) | |
---|---|---|---|
1 | Overall Audit Monitor | As a general admin, I want to see the whole platform integrity - health status in terms of all validation rules configured |
|
| |||
2 | Overall Audit Analysis | What kind of validations mostly executed against which models What kind of violations mostly occur in which components |
|
3 | Individual Audit Analysis | Given a validation job, the user wants to see and quickly recognize all relevant violations detected by POMBA |
|
|
4 | Violation Analysis |
- violation stats by validation type
- violation stats by validation rule
for Network Discovery | For the specific use cases of Network Discovery, the user wants to see the audit stats |
| |
5 | Violation Summary Report | Provide a list of summary list for the validation and violation cases for any potential fixes |
|
Supportable Features
- Provide links to move back and forth across the dashboards: e.g., from the violation page to the page displaying its validation info
...