These are some steps to help review if UIM is successfully sending data to OI. This includes checking the UIM queues which was not stated as part of this problem, but should be checked.
1) From IM open hub and click on Status
2) Under Subscribers/Queues please check following queues
axagateway.alarms
axagateway.uimQos
If the metrics are in queued then something wrong with OI connector please check the OI connector logs.
In the OI connector if it is posting to NASS you will see something like below
Feb 16 15:57:41:701 [QOS_PROCESSOR_THREAD, oi_connector] Total Time Taken by Thread in QosEventProcessorNASS :: 0 ms. [ Total Records :: 10 ]
Feb 16 15:57:49:824 [QOS_PROCESSOR_THREAD, oi_connector] Total time to execute http request : 11
Feb 16 15:57:49:824 [QOS_PROCESSOR_THREAD, oi_connector] Total time to post metric values to nass : 11
Feb 16 15:57:49:824 [QOS_PROCESSOR_THREAD, oi_connector] Total no of Qos values posted on NASS via post : 14
Feb 16 15:57:49:824 [QOS_PROCESSOR_THREAD, oi_connector] Total Time Taken by Thread in QosEventProcessorNASS :: 12 ms. [ Total Records :: 14 ]
Feb 16 15:57:57:922 [QOS_PROCESSOR_THREAD, oi_connector] Total Time Taken by Thread in QosEventProcessorNASS :: 0 ms. [ Total Records :: 1 ]
With no errors, investigation on OI SaaS side needs to happen.
If it is not able to post it will throw some errors, based on that it would be suitable to raise a support ticket with the error message provided.