...
- Where necessary, provide links to switch the dashboards back and forth: e.g., from the violation page to the page displaying its validation info
- Color coding for the critical violations
3. Data Generation
...
The user could take some possible approaches to execute the audits and generate audit results:
...
For the development purpose, we need a certain amount of audit results data which consist of various types of validation and violation cases. Hope the data to be reflecting the production reality.
Approach 1: Execute the audits in the IST lab (or production) and bring the audit results.
- Script A runs to collect a list of info that will be used as arguments in the audit requests: serviceInstanceId, modelINvariantId, modelVersionId, customerId, serviceType
- Script B runs to send audit requests based on the data above: need to distribute the requests over time to be realistic
- Manually collect the elasticsearch dump (which will contain all the audit validation/violation events) and import to dev lab
Approach 2: Collect the components info and copy to dev lab
- Script X runs to GET all info from each component of interest in the IST or production
- Script Y prepares APIs to PUT the info into the components in the dev lab
- Run Script A
- Run Script B
After that, as necessary, we could manipulate the data to generate many different types of violations
- Manually update the data in some components to generate special violation cases
Configurations
- Audit targets selection: which microservices should be included and cross-checked
- Audit rules selection: which rules should be validated for the target services
- Scheduling parameters: when, which rules will be applied
...