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
Dear @Mohan Singh Rathor,
Kindly ensure that the script is executed before applying the patch.
Please ignore the previously attached script and consider the script attached to this email as the correct one to be executed.
Best Regards,
Marwan Kanaan I Software Developer
no more error empty description showing but
I have verified the system status following the recent database script execution and patch updates. Unfortunately, there has been no change in behaviour; discovery tickets have not been generated since November 12, 2025, on either server (10.164.168.11 or 10.164.168.12).
Please find the attached server logs for your review and investigation.
serverlogs_12nov_02Feb.rar
And we got one exceptional discovery ticket IM3577717 but not able to see in the logs on both server.
Dear @Mohan Singh Rathor,
As discussed on Teams, the issue causing the dumps process not to work is related to the nep-server-config.xml configuration.
On the production environment, the dumps trouble ticket flag is currently set to false. Kindly change it to true.
Additionally, please confirm with @Abir whether the engineering flag should be false on .11.
SS
Best Regards,
Marwan Kanaan I Software Developer
Dears
As per previous recommendation from Nazih as per
nep.troubleTicket.executor.isEnabled shall be true only on one node as it is the process responsible to open tickets with UTT for items stored in DB as per my understanding
having it running on both nodes is causing the duplication
Regards
Abir
Still some KQI dumps are not generating which dashboard showing red and needs to be checked with MOhan
Please find below the formal technical guidelines to be strictly adhered to during the process of creating Key Quality Indicators (KQIs) to ensure system consistency and to prevent known issues such as empty description errors.
1. KQI Main Categories
During the KQI creation process, the following three primary KQI categories are to be used:
OutdatedDumpsData
AbnormalDumpsFilesCount
SFTP_SSHConnectionFailure
2. Configuration Guidelines for Each Category
2.1. OutdatedDumpsData
When working under the OutdatedDumpsData category:
The Description Template must be explicitly set to one of the following:
PhyLogNotSeparated
PhyLogSeparated
This is mandatory to avoid empty description generation, as the process relies on the template to determine the description format.
Additional Configuration:
If the template is set to PhyLogSeparated, it is imperative to configure the NEP_DUMPS_KQI_KEY table such that the KQI_FILE_TYPE column is set to either Logical or Physical.
If using PhyLogNotSeparated, this additional configuration is not required.
2.2. SFTP_SSHConnectionFailure
When working under the SFTP_SSHConnectionFailure category:
The Description Template must be one of the following:
CF_Push
CF_Pull
CF_WithAttachment
Note:
There is no requirement to set the KQI_FILE_TYPE column in the NEP_DUMPS_KQI_KEY table for this category.
2.3. AbnormalDumpsFilesCount
When working under the AbnormalDumpsFilesCount category:
The Description Template must be strictly set to:
PhyLogSeparated
Additional Configuration:
As with OutdatedDumpsData, it is mandatory to configure the NEP_DUMPS_KQI_KEY table such that the KQI_FILE_TYPE column is set to either Logical or Physical to ensure proper operation.
3. Important Notes
Failure to comply with the above configuration standards will result in empty descriptions due to the dependency of the description generation process on the correctly set templates and corresponding data in the database.
Please ensure these requirements are reviewed and implemented carefully during each KQI creation to maintain data integrity and prevent processing failures.
Should you require any clarifications or technical assistance regarding these configurations, please do not hesitate to reach out.
No Patch Need For This Bug
Best regards,