vRNI-Node_Group_Profile_TN you should see a huge number of profiles created. Collector logs at location /var/log/arkin/collector below error are seen:
2025-05-28T17:26:42.271Z INFO nsxt.tasks.ManageNSXTLatencyTask NSXT_<NSXT IPAddress/FQDN>_Config_OpMgr-0 createNSGroupForTNs:613 New Child NSGroup added, id /infra/domains/default/groups/vRNI-Node_Group_Profile_TN_829###ef-###-###-8453-#######362, member count 40
2025-05-28T17:26:42.326Z ERROR dataprovider.utils.HttpUtils NSXT_<NSXT IP Address/FQDN>_Config_OpMgr-0 checkCodeAndThrow:53 Could not get response for /policy/api/v1/infra/domains/default/groups/vRNI-Node_Group_Profile_RFF####==, status 400
2025-05-28T17:26:42.326Z ERROR dataprovider.utils.HttpUtils NSXT_<NSXT IPAddress/FQDN>_Config_OpMgr-0 checkStatusAndThrow:41 API /policy/api/v1/infra/domains/default/groups/vRNI-Node_Group_Profile_RFF####== error response {
"httpStatus" : "BAD_REQUEST",
"error_code" : 500127,
"module_name" : "Policy",
"error_message" : "Cannot create an object with path=[/infra/domains/default/groups/vRNI-Node_Group_Profile_RFF####==] as it already exists."
}
An investigation of collector logs revealed that improper cleanup procedures resulted in the removal of vRNI_Groups from the vRNI KV Store, while corresponding entries were not deleted from NSX-T.
Consequently, during latency enablement, while TN_Groups were successfully created, an exception was encountered during the creation of vRNI_Group, indicating a pre-existing group.
During this time the Watcher task operates continuously in the background, generating a substantial number of TN_Groups. Because of which we saw a high number of TN_Groups.
Issue is with NSX-T Latency statistics profile state entries which needs to be cleaned up using script(s) available with support team.
If you believe you have have encountered this issue then to investigate this further