search cancel

How to handle loss of $expand=qosclassmaps for interface and qosclassmaps endpoints from Odata OpenAPI?

book

Article ID: 201095

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

In the latest r20.2.2 based Release Notes there is a section documenting OpenAPI OData changes.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/20-2/Performance-Monitoring-with-DX-Performance-Management/release-notes/openapi-changes.html

It refers to the disassociation between the interfaces and qosclassmaps endpoints with the $expand= options for qosclassmaps and qosreds. It states:

  • Impact: The QoS elements hierarchy is no longer supported.
  • Examples:
    • odata/api/interfaces?&$expand=qosclassmaps
    • odata/api/qosclassmaps?&$expand= qosreds

If we're using the $expand=qosclassmaps or $expand= qosreds options in existing scripted queries, will they work if using different endpoints?

Environment

Performance Management r2.8 and newer releases.

The change documented began with the r2.8 release.

Resolution

The suggested alternative endpoint is the specific metric family the data is sought from.

Most often that would be http://<DA_HOST>:8581/odata/api/qosclassmapmfs.

Use of the odata/api/interfaces or odata/api/qosclassmaps are the only ones that won't work with the referenced expand values.