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,

Dear @Mohan Singh Rathor,

I hope this message finds you well.
I would like to inform you that the issue has been identified and will be resolved in the upcoming patch, version 3.7.0.1325. The root cause of the problem has been traced to unnecessary validation, which has now been addressed.
Please let me know if you require any further details or assistance.

Best Regards,

a regression has been shown as KQI with 0 Outdated files is generating now -LS-569 is created for same

so we are reverting this change and will check empty description status accordingly

related logs

https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EfTeuKk2M3hPhCshILR8wykBiHWvMVaxngXMgL38tQ8NLw

2025-09-16 03:22:02,713 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei U2000 RAN Outdated dumps data, Diplay Name Huawei U2000 RAN Outdated dumps data , Empty Description
2025-09-16 03:23:39,074 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei Core Outdated dumps data, Diplay Name Huawei Core Outdated dumps data , Empty Description
2025-09-16 03:24:37,502 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name IntraCom MW Outdated dumps data, Diplay Name IntraCom MW Outdated dumps data , Empty Description
2025-09-16 03:26:19,936 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Fiber-Home Fixed Access Outdated dumps data, Diplay Name Fiber-Home Fixed Access Outdated dumps data , Empty Description
2025-09-16 03:27:16,751 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name SDWAN IP Outdated dumps data, Diplay Name SDWAN IP Outdated dumps data , Empty Description
2025-09-16 03:28:45,205 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Redline MW Outdated dumps data, Diplay Name Redline MW Outdated dumps data , Empty Description
2025-09-16 03:29:11,949 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-9) Error While Creating UttTicket for kqi name Huawei NCE FAN Outdated dumps data, Diplay Name Huawei NCE FAN Outdated dumps data , Empty Description

2025-12-08 03:59:49,953 ERROR [com.mobinets.nep.model.uttticket.controller.TroubleTicketsProcessingHandler] (org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-10) Error While Creating UttTicket for kqi name Tellabs DXX Outdated dumps data, Diplay Name Tellabs DXX Outdated dumps data , Empty Description

Dear @Mohan Singh Rathor,

Kindly find the solution for the reported issue included in patch 3.7.0.1411.

Please note that the attached script must be executed prior to applying the patch to ensure proper behavior.

Best Regards,
Marwan Kanaan I Software Developer

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