-
Story
-
Resolution: Done
-
Medium
-
None
Refer the attachment for the requirement mapping against the feedback for KPI computation MS. In summary, below are noted.
1. Define KPIs that span multiple resources using policy
2. Maintain time alignment between the data source(producer) and the KPI computation MS i.e, between reporting period and granularity period
3. KPI computation logic should be configurable, need not be fixed
4. Any changes to the computation formula should be notified to the consumer
5. Apply validation on the input PM data against the KPIs such as the counters allowed for a specific KPI or a resource
6. Handle the policy failures at KPI level. It is implementation dependent to handle
i) partial failure in computation of kpis
ii) failed to compute all kpis
7. Handle the failures at counter level like the temporary unavailability of counters
8. Figure out the consumers for KPI computation MS and the NFs producing the counters
9. Allow more than one operation for a KPI
10. Set limits for number of KPIs and counters per NF/data producer
11. Policies for KPIs and counters should be configurable.
- is blocked by
-
DCAEGEN2-2835 Configurable KPI computation formula
- Submitted
- is cloned by
-
DCAEGEN2-3193 Enhancements to KPI Computation MS for Kohn Release
- Closed
- relates to
-
DCAEGEN2-2972 Improvements to kpi-computation-ms Microservice
- Closed
-
DCAEGEN2-2989 Enhance (KPI-MS) KpiComputation for SUM-RATIO operation.
- Submitted
- mentioned in
-
Page Loading...