search cancel

duplicate metrics and can't tell which metric is which in CABI reports

book

Article ID: 215036

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When scheduling CABI reports we get presented with multiple "copies" of a metric with no way to differentiate the target.

 

Environment

Release : 20.3

Component : UIM OPERATOR CONSOLE - CABI REPORTS AND INTEGRATION

Resolution

This is a limitation of the CABI interface.

For now, you can run the following SQL Query and keep a copy of the results handy when designing reports:

MSSQL/MySQL:

 

 

SELECT DISTINCT(ccimd.met_description),
cim.ci_metric_type,
sqd.qos met_type,
sqdef.unit_short,
ccimd.unit_type,
sqdef.description
FROM  CM_CONFIGURATION_ITEM_METRIC cim
LEFT JOIN CM_CONFIGURATION_ITEM_METRIC_DEFINITION ccimd ON ccimd.met_type = cim.ci_metric_type
JOIN S_QOS_DATA sqd on sqd.ci_metric_id = cim.ci_metric_id and sqd.origin IN (select distinct origin from S_QOS_DATA)
JOIN s_qos_definition sqdef ON sqd.qos_def_id = sqdef.qos_def_id
JOIN CM_CONFIGURATION_ITEM ci ON cim.ci_id = ci.ci_id
JOIN CM_DEVICE cd ON cd.dev_id = ci.dev_id
JOIN CM_COMPUTER_SYSTEM_ORIGIN ccso ON cd.cs_id = ccso.cs_id
JOIN CM_GROUP_MEMBER cgm ON ccso.cs_id = cgm.cs_id
ORDER BY ccimd.met_description

 

 

Oracle:

SELECT DISTINCT(ccimd.met_description),
cim.ci_metric_type,
sqd.qos met_type,
sqdef.unit_short,
ccimd.unit_type,
sqdef.description
FROM  CM_CONFIGURATION_ITEM_METRIC cim
LEFT JOIN CM_CONFIGURATION_ITEM_METRIC_D ccimd ON ccimd.met_type = cim.ci_metric_type
JOIN S_QOS_DATA sqd on sqd.ci_metric_id = cim.ci_metric_id and sqd.origin IN (select distinct origin from S_QOS_DATA)
JOIN s_qos_definition sqdef ON sqd.qos_def_id = sqdef.qos_def_id
JOIN CM_CONFIGURATION_ITEM ci ON cim.ci_id = ci.ci_id
JOIN CM_DEVICE cd ON cd.dev_id = ci.dev_id
JOIN CM_COMPUTER_SYSTEM_ORIGIN ccso ON cd.cs_id = ccso.cs_id
JOIN CM_GROUP_MEMBER cgm ON ccso.cs_id = cgm.cs_id
ORDER BY ccimd.met_description

 

This query outputs a list of all QoS's in the system in the same order they would appear in CABI.   You can then refer to the list to determine which metric is which.

For example, the initial screenshot above shows 4 "versions" of "AvgResponseTime" and in the query output they will appear as follows:

This is not ideal but can be used as a "cheat sheet" to differentiate the metrics when designing CABI reports.

 

 

 

Additional Information

You can take the following steps to permanently change the metric selector to use more descriptive QoS names:

1. Login via superuser in cabijs via browser.
2. From View Menu select Repository.
3. In Left Tree Go To Root --> Public --> ca --> UIM --> resources --> library --> health --> input_controls.
4. Click on input_controls, in right panel search for "Metric Query". Right click and select Edit option.
5. Edit Query: Metric Query page comes up --> Name the Query and then click on Next button.
6. This page is for "Link Data Source", click on Next.
7. Now, In "Define the Query" page replace the content of "Query String" with this query:

SELECT DISTINCT COALESCE(ccimd.met_description,'...') ccimd_description,
                $P!{concat_hidden} met_type,
                sqdef.unit_short,
    COALESCE(ccimd.unit_type,'...') unit_type, 
                sqdef.description sqdef_description
FROM  CM_CONFIGURATION_ITEM_METRIC cim  
LEFT JOIN $P!{ccimd_table} ccimd ON ccimd.met_type = cim.ci_metric_type 
JOIN S_QOS_DATA sqd on sqd.ci_metric_id = cim.ci_metric_id  
JOIN s_qos_definition sqdef ON sqd.qos_def_id = sqdef.qos_def_id 
JOIN CM_CONFIGURATION_ITEM ci ON cim.ci_id = ci.ci_id 
JOIN S_QOS_SNAPSHOT sqs ON sqd.table_id = sqs.table_id
JOIN CM_DEVICE cd ON cd.dev_id = ci.dev_id 
JOIN CM_COMPUTER_SYSTEM_ORIGIN ccso ON cd.cs_id = ccso.cs_id $P!{devices_in_clause_hidden} $X{IN, cd.cs_id, select_members}
JOIN CM_GROUP_MEMBER cgm ON ccso.cs_id = cgm.cs_id 
AND cgm.grp_id = $P{group} $P!{MetricTime}
ORDER BY ccimd_description 

8. Click on the Save Button and Exit.
9. Then please verify the issue again and share the results with us.

 

This article will be updated in the future with MSSQL-based instructions as they become available.

 

Attachments