CABI UIM Summary dashboard never loads - Devices data missing
search cancel

CABI UIM Summary dashboard never loads - Devices data missing

book

Article ID: 205454

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Opened the UIM Summary dashboard logged directly on the JasperReports machine, but the dashboard never loads successfully, it keeps trying to update the Devices panel.

If we manually run the SQL query for the Devices panel, the query takes less than 2 minutes to display the result.

select * from (select 'total_device_count' as type, count(*) as device_count       from cm_computer_system 
               union 
       select 'active_device_count' as type, count(DISTINCT(CASE WHEN sqs.sampletime is not NULL THEN ccs.cs_id ELSE NULL END)) as device_count
from cm_computer_system ccs 
       join cm_device cd 
               on ccs.cs_id = cd.cs_id 
       join cm_configuration_item cci 
               on cd.dev_id = cci.dev_id 
       join cm_configuration_item_metric ccim 
               on cci.ci_id = ccim.ci_id 
       join s_qos_data sqd 
               on ccim.ci_metric_id = sqd.ci_metric_id 
               and sqd.origin IN (select * from (select distinct sqd.origin from S_QOS_DATA sqd union select distinct ccso.origin from CM_COMPUTER_SYSTEM_ORIGIN ccso union select distinct na.origin from NAS_ALARMS na) alias) 
       join s_qos_snapshot sqs 
               on sqd.table_id = sqs.table_id 
               and CAST(sqs.sampletime as datetime) >= DATEADD(MINUTE, -30, CURRENT_TIMESTAMP)) src 
  pivot (sum(device_count) for type in (total_device_count,active_device_count))piv

The cabi_external probe was deployed on the same machine where the UMP was installed on.

The CABI 7.1.1 is using an external MS-SQL 2016 database instead of an embedded Postgres database.

Environment

Release : 20.1

Component : UIM - CABI

Resolution

After removed the defaultTransactionIsolation="READ_UNCOMMITTED" parameter from the /opt/CA/CABI/apache-tomcat/webapps/jasperserver-pro/META-INF/context.xml file the issue was resolved. Then bounce the apache-tomcat service.