QOS_POWER_STATE Metric collected for devices but not visible in OC Metric Viewer or CABI Availability Reports
search cancel

QOS_POWER_STATE Metric collected for devices but not visible in OC Metric Viewer or CABI Availability Reports

book

Article ID: 257564

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We currently have a situation on a large number of devices where the QOS_POWER_STATE Metric is not visible in either the OC Metric Viewer or CABI Availability Reports. However, the data is being collected and stored in the UIM database.

select * from s_qos_data where qos like '%power%' and source like '%<source_machine>';

select * from RN_QOS_DATA_1116 where table_id='<table_id#>' order by sampletime DESC, shows the data.

table_id sampletime samplevalue tz_offset samplestdev samplerate
253326 2023-01-06 13:45:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:40:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:35:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:30:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:25:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:20:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:15:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:10:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:05:49.000 1.00 0 300.00 0.00
253326 2023-01-06 13:00:49.000 1.00 0 300.00 0.00
253326 2023-01-06 12:55:49.000 1.00 0 300.00 0.00

But in OC Metrics view, the collected data is not visible.

Environment

  • Release: 20.4

Resolution

Restart of the Secondary hub resolved the issue.

Data flow, probe->Robot->Hub->data_engine to Database, and Database to OC / CABI.

​Metric correlation did not happen due to some issues in niscache processing and that is why a restart of the remote/Secondary ​hub actually kickstarted the data collection once again from ​the ​robot​(s) and​ that resolved the issue.