please provide more details about the issue as it's not clear the scenario and what you are expecting?

Dear Hassan,
i have added the SS from naming convnetion and attchament from KQI. We have tried to change the naming rule from counter to alphacounter. but still same nodes are reporting.

Please check.

as discussed with marwan , we need to check if we can add more options in preferences to cover our cases

tx

dear @aurobinda kindly share a sample xml for the nodes above for test purpose

Asked Integration to generate an XML

Dear @Aurobinda Panda,

note that I checked the rules locally and, after testing, the issue is within the rule itself, as the nodes are ending with zone names.

Therefore, I suggest applying the following rule:
s(D)<>siteID<>counter<>s<>s(Metro6040V2)<>s<>zone

Additionally, for the rest of the rules, please add zone instead of counter or AlphaCounter and verify the rule afterward.

Best Regards,
Marwan Kanaan I Software Developer

Naming convention changed as suggested. Will check the result.

@Marwan, As checked, still same issue occurred. Please check again.

Dear @Aurobinda Panda,

The names and zone names don’t match. Either the zone names should be in uppercase for Sohar, Saham, and Suwaiq, or you can choose to ignore the mismatched ones as this is a normal case due to naming convention variations for these nodes.

Also, how do you expect SUW to match SUWAIQ_3G?

Best Regards,
Marwan Kanaan I Software Developer

Dear @marwan,
As per your suggestions naming convention rules changed. But if still issue is not resolved, so the suggestions are not relevant. atleast one of the NEs should have updated with the suggested rule. but it didn't happen.

So instead of Zone, can't we use counter as a static value.

Kindly confirm.

dear @aurobinda

kindly know that you can set counter as a static value but non of the above names going to be working.

regards,