20200318 Discussion
Date
Mar 18, 2020
Participants
@LIN MENG
@Seshu Kumar Mudiganti
@Swaminathan Seetharaman
@Guobiao Mo
@LUKAI
@guochuyi
@Zhang Min
@Chuanyu Chen
@Borislav Glozman
Notes and Actions
1.Datalake based solution was discussed during the call, material can be found here:
20200318 KPI discussion material
2. Datalake KPI monitoring only covers partial requirements of KPI, to be more specific, it only satisfied the monitoring from the portal side, KPI calculation is not suitable to be in Datake.
3. functions of datalake was discussion, big data storage. it can provide data for modeling trianing.
4. workflow when using a KPI calculation micro service was discussed, need to be further investigated when the rquirements of KPIs are determined.
NO. | Actions | Responsibles |
---|---|---|
20200318_1 | Lin to sort out all the requirement of KPI for Guilin Release | Lin |
20200318_2 | Analysis how datalake can support different scenarios of KPI usage | Guobiao |
20200318_3 | Analysis all the KPI scenarios and high level solution design | Lukai |