oi_connector 1.55 doesn't send QOS to DX OI but alarms are generated without issue.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

I can see these errors in oi_connector log.

Jun 24 17:33:26:191 [QUEUE_MONITOR_THREAD, oi_connector] QOS Subscription is either null or not Ok so Reconnecting to hub queue...
Jun 24 17:33:26:192 [QUEUE_MONITOR_THREAD, oi_connector] QOS subscription is unavailable on Primary Hub
Jun 24 17:33:26:195 [QUEUE_MONITOR_THREAD, oi_connector] Primary Hub is available: /<domain>/<hub>/<robot>//hub
Jun 24 17:33:26:195 [QUEUE_MONITOR_THREAD, oi_connector] subscribe to queue hub address is /<domain>/<hub>/<robot>//hub
Jun 24 17:33:26:195 [QUEUE_MONITOR_THREAD, oi_connector] inside subscribe to queue hub address is /<domain>/<hub>/<robot>/
Jun 24 17:33:26:637 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total time to execute http request : 20
Jun 24 17:33:26:637 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total time to post metric metadata to nass  : 20
Jun 24 17:33:26:637 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total no of Metrics Metadata posted on NASS via post : 2
Jun 24 17:33:26:673 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total time to execute http request : 36
Jun 24 17:33:26:673 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total no of UIM Alarms posted on jarvis via post : 2
Jun 24 17:33:26:673 [ALARM_PROCESSOR_THREAD-3, oi_connector] Total Time Taken by Thread in AlarmEventProcessor :: 56 ms. [ Total Records :: 2 ]
Jun 24 17:33:27:197 [QUEUE_MONITOR_THREAD, oi_connector] Queue is not subscribe, Nass is not available : axagateway.uimQos
Jun 24 17:33:27:197 [QUEUE_MONITOR_THREAD, oi_connector] New subscriber object constructed for :  Queue[axagateway.uimQos].
Jun 24 17:33:27:843 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:27:948 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:052 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:156 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:261 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:365 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:469 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:574 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:678 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:28:783 [attach_clientsession, oi_connector] Retaining Data in the QoS Queue, as effectiveTaskCount reaches to max limit.
Jun 24 17:33:32:038 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total time to execute http request : 15
Jun 24 17:33:32:039 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total time to post metric metadata to nass  : 16
Jun 24 17:33:32:039 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total no of Metrics Metadata posted on NASS via post : 1
Jun 24 17:33:32:052 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total time to execute http request : 13
Jun 24 17:33:32:052 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total no of UIM Alarms posted on jarvis via post : 1
Jun 24 17:33:32:052 [ALARM_PROCESSOR_THREAD-2, oi_connector] Total Time Taken by Thread in AlarmEventProcessor :: 29 ms. [ Total Records :: 1 ]

I updated oi_connector from 1.52 to 1.55, but the situation stayed the same.

Environment

• oi_connector v1.55

Resolution

Support for NASS reactive client library and API in UIM OI Connector (From oi_connector v1.55)

The oi_connector uses the NASS REST APIs till the previous release. Now, you can use the NASS reactive client library and API to improve the resiliency, performance, and scalability of the NASS metric ingestion pipeline.

By default, the integration uses the NASS Reactive client library to send metric data to DX OI. 

1. Optionally, you can revert to using NASS REST API. To continue to use the NASS REST API, using Raw configure mode, add the enable_reactive_client key in the setup section of oi_connector.cfg file and set the value to false.
2. Deactivate oi_connector
3. Activate oi_connector