...
- High-Level Requirements
- Dashboard views of Service lists
- Filtering capabilities based on search criteria
- Configurable search criteria
- Dashboard views of statistics (donuts, pie charts, etc.) for filtered service instances
- Service Instance Rendering and detail panel views
- with sub-service instance drill-drown and drill-up capabilities
- A service instance could be realized by multiple process instances
- with process / task detail
- Topology (workflow) views during/after orchestration
- with sub-service instance drill-drown and drill-up capabilities
- Input/output data views for process/task/service task (messages, parameters)
- Display on service / task detail panel
- Provide message log views (could be on a pop-up widget)
- Color coding/visual indication of statistic and service type and status
- Troubleshooting capabilities by manipulating the workflow during orchestration for troubleshooting and retry from the current location (stretch goal)
- TOSCA orchestration monitoring (stretch goal)
- Dashboard views of Service lists
- Required UI Widgets
- Service List
- Service Statistic
- Service Instance Rendering and Detail
- Widget Requirements and Design
- Service List Widget
- Capabilities
- Provides monitoring capabilities for processed services based on search criteria
- Configurable Search Criteria filtering: Service ID, Operation Type, Status, User Id, Date/Time range
- Actual filtering criteria fields could be changed based on configuration
- The Service List panel will display the filtered Service list.
- This widget can be triggered from other UIs (VID, UUI, external applications).
- Provides monitoring capabilities for processed services based on search criteria
- Design
- The search criteria fields will be defined in a search criteria field configuration file (e.g., so-monitoring-config.yaml). So, they can be customized and support internationalization.
- Based on the fields and buttons configuration, the Service List widget will render the corresponding fields and buttons.
- The search criteria fields support the field validation based on the field type; e.g., length, date format, time format.
- The wild characters are supported for the String field.
- Example of so-monitoring-config.yaml
- Capabilities
- Service List Widget
...
- Estimates
- Note:
- It is a rough estimate - to be refined
- Estimate includes development and unit testing time
- As mentioned in the above section, the components can be built in parallel.
- 5 hours / day
- Note:
Priority | Component | Development Estimate | Comments |
---|---|---|---|
Priority | Component | Development Estimate | Comments |
1 | REST APIs for providing data to UIs | 80 hours / Java developer |
|
2 | SO Service List widget | 80 hours / UI developer |
|
3 | Service Instance Rendering and Detail Panel | 120 hours / UI developer |
|
4 | Statistic Dashboard (stretch goal) | 40 hours / UI developer |
|
5 | Custom History Producer (stretch goal) | 40 hours / Java developer |
|