DX Unified Infrastructure Management

Hello all,

We are trying to create some custom QOS for counting something.

As testing, we are using this commands below:

nimqosdefinition -q QOS_TOTAL -d "Generic count" -g QOS_GENERIC -u count -s count

nimqos -q QOS_TOTAL -s "10.22.50.11" -t "Total Devices" -v 10 -i 1800 -T "11.10" -N "Total" -M "11.10:2" -R "10.22.50.11"

The tables in CA_UIM database about the device is ok for S_QOS_DEFINITION, S_QOS_DATA, CM_COMPUTER_SYSTEM, CM_DEVICE, but no association for CM_CONFIGURATION_ITEM_METRIC.

What is the problem to associate the device with metric?

This is because we need to show this information in USM for this device, but I see that without CM_CONFIGURATION_ITEM_METRIC association, the information is not showed.

Regards,

Paulo

It would be fabulous if CA/Broadcom could share an official procedure for populating these tables so that custom QoS generated at the scripting level could be integrated into the UMP portlets fully. 

Hello all,

Any idea? Can not we create remote monitoring metrics by nimqos?

Regards,

Paulo

ump > slm > quality of service > expand down click the down arrow in the black circle > new and it provides the ability to create a new qos. But you still need a custom probe to do the monitoring. restmon maybe what you are looking for, it will turn a json schema file into a monitoring probe.

Is there any way to do this for a QOS that already exists?

The SLM portlet lets you edit the properties of an existing QoS but unfortunately the only thing that's editable at that point is the description. 

What would be really nice, I suppose, would be that data_engine, when seeing a new QOS created using the old ways, would create the underpinning data that would make these QOS values work with some of the "new" features - like the performance reports portlet.

restmon is limited to valid CI and Metric types supported, and that list is downloadable from the restmon page in OC.

Is the goal just to create some new QoS for the fun of it, or is the need to do a new type of monitoring that requires new QoS metrics. If the latter then isn't this just a part of developing a new probe and the SDK is the place to go:

Probe Software Developer Kit - CA Unified Infrastructure Management Probes - CA Technologies Documentation 

In the event that you want to use a new Metric Type ID, you can use the 9.1.1:1 series.  This will allow the metrics to be displayed in USM.

I think that you brought up restmon - not sure why exactly but that's not the issue.

If you create a QOS the way the original poster did, using the command line utilities, you will be unable to see that value in a performance report. You will be able to see it in a list view though. The issue is that while it's creating a valid QOS, it's not creating the underlying CI/DI definitions in the tables. These are used in part of the join that the performance report portlet issues to get data and so it results in nothing.

You get the same behavior if you capture a variable in logmon and assign it to a QoS for instance.