Details
-
Type:
Bug
-
Status:
Reopened
(View Workflow)
-
Priority:
Normal
-
Resolution: Not Fixed
-
Component/s: NEP
-
Labels:None Labels
-
Customer:OMAN-Tel
-
Product:NEP
Description
Dear @Abir Messaikeh, @Khaled Khalil,
We've found that some vendor tickets aren't being created because of an "Empty Description" error. We inserted CF_Pull into the Description template in the NEP_KQI table when these KQIs were created. Please review and let us know your recommendations.
Logs and NEP_KQI table exported sheet attached in link for your reference.
server.log.2025-06-30.gz
server.log.2025-06-30.gz:2025-06-30 22:22:05,549 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5) Error While Creating UttTicket for kqi name Huawei CPE Outdated dumps data, Diplay Name Huawei IP CPE Outdated dumps data , Empty Description
server.log.2025-06-30.gz:2025-06-30 22:21:21,773 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-5) Error While Creating UttTicket for kqi name Cisco CPE Outdated dumps data, Diplay Name Cisco IP CPE Outdated dumps data , Empty Description
server.log.2025-06-30.gz:2025-06-30 20:20:58,480 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-4) Error While Creating UttTicket for kqi name Cisco CPE Outdated dumps data, Diplay Name Cisco IP CPE Outdated dumps data , Empty Description
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 4 hours
-
Exploring DB + implemented logic
-
- Time Spent:
- 4 hours
-
Investigating the issue further by querying data from the PROD and resolving the connection issue with the BI platform.
-
- Time Spent:
- 2 hours
-
discuess with hassan and still blocked because the data and trying to solve the issue
-
- Time Spent:
- 1 day
-
investigate the code and realise the logic and making a documentation about the kqi and bi
-
- Time Spent:
- 4 hours
-
invistigate the issue and fixed bi data not coming issue
-
- Time Spent:
- 4 hours
-
fixed data issue not coming and start working on a fix
-
- Time Spent:
- 1 day
-
find the root cause and prevent the empty desc to generate anymore and provide a clean up for kqi tables
-
- Time Spent:
- 4 hours
-
investigate why the process of kqi dumps not working and replay the same to L2 to fix the configuration on prod
