Custom metric family is not available in the view setting for a group context in CA Performance Management (CAPM)
search cancel

Custom metric family is not available in the view setting for a group context in CA Performance Management (CAPM)

book

Article ID: 437504

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

We are using custom certification where component-level information is collected via APIs using Mediation Manager. For these devices, polling and discovery are handled separately.

It’s important to note that we have customer-level groups where the devices themselves are not owned by the customers, but the associated custom metrics are mapped to customers.

To simplify the requirement:
For interfaces, the device is not owned by the customer, but the interfaces are. Therefore, in this view, we do not want to display devices—we only want to display the interfaces associated with the customer.

 

Environment

DX NetOps CAPM all currently supported releases

Cause

This can occur if the custom metric family is not yet fully associated with the items in that specific group or if the metrics are restricted by the current SD-WAN tenancy configuration.

 

Resolution

Do the following:

  1. Verify the Vendor Certification (VC) by checking that the "Versa Access Circuit" metric family has an active Vendor Certification assigned and that it is successfully discovered for the devices in your group. You can check this in the Metric Families section of the Data Aggregator monitoring configuration.

    If it isn't then review the following KB as it outlines how to associate custom metrics/Metric Families with VCs:

    KB : How to assign a Vendor Certification to a new, custom Metric Family in Performance Management(NetOps Portal)

  2. Review Group Membership: Confirm that the group context you are clicking into contains items that support the custom OIDs defined in your new metric family. The group context does not need to directly contain devices, but at least include the device-level components within that context.

  3. Ensure that you deploy the DP to the DA, i.e upload the MF/VC/component XMLs, then check for the updates for the CAMM DP via GET request to:

    http[s]://<DA_HOST>:8581/typecatalog/metricfamilies/typecatalog/certifications/camm/typecatalog/components