| Jira | ||||||
|---|---|---|---|---|---|---|
|
1. Upgrade of ELK & Potential
...
Feature Development (
...
AAI search-
...
data-
...
service)
- Current ELK versions: elasticsearch 2.4, kibana 4.6 (no logstash is being used)
- To better create the dashboards with enhanced features and look, upgrading to version 5.6 is desired. (note: Logging project is using 5.5)
- Upgrade from 2.x to 5.x needs "Full Cluster-restart Upgrade".
2.
...
Dashboard Ideas
The visualizations and dashboards will need to be designed and created according to the current and any potential purposes use cases of the POMBA services - what the users want/need to knowcheck, how the system could help improve the whole platform integrity. We want the POMBA reporting to be informative, insightful, and intuitive from the user's perspective.
Challenges
- We have created a few sample validation rules and do but do not know all the rules to be created by the users in the production. That means most likely we can create and provide some high-level dashboards - for the specific rules and details, we could only provide some sample dashboards to give an idea so that how the end users could create their own dashboards customized for their use cases.
- For the Network Discovery, what specific audits will be executed and what kinds of audit results are expected
Visualization List Dashboard List
| Dashboard |
|---|
...
| What To Want to See | Required Information To Show (Visualizations) | ||
|---|---|---|---|
| 1 | Audit Overview |
| |
| 2 | Audit Analysis | Given a validation job triggered, the user wants to see all related violations found by POMBA |
|
| 3 | |||
| 4 | Violation Analysis | what kind of violations mostly occur |
|
| 5 | Violation Analysis for Network Discovery |
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
3. Data Generation based on Audit Use Cases
...
Generally two approaches to execute the audits and generate audit results:
- Event-Driven Auditing: e.g., Post-orchestration audit trigger by system or user with a specific service instance
- Continuous or Scheduled Auditing: targeting a pre-configured set of service instances (existing and/or new). It could be against all the deployed artifacts.
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