How to change the displayed component name for polled metrics in DX NetOps Performance Management
search cancel

How to change the displayed component name for polled metrics in DX NetOps Performance Management

book

Article ID: 434831

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

  • Users want to display custom names for metrics (e.g., "NGD Analog 1" changed to "TANK 3") in reports or dashboards.
  • The desired descriptive value is not available in any MIB table on the monitored device.
  • Changing the Vendor Certification is not an option because the data is not on the device.

Environment

  • DX NetOps Performance Management (all supported releases)

Cause

By default, DX NetOps displays the component name as defined in the Vendor Certification or as discovered from the device MIB. When the device does not store the specific descriptive name required for reporting, a manual alias must be applied at the Performance Center level.

Resolution

You can manually override component names using the update_alias_name.sh utility. This allows you to map custom strings to existing internal Item IDs.

  1. Log in to the Performance Center server.
  2. Navigate to the tools directory:
    bash
    cd /opt/CA/PerformanceCenter/Tools/bin
  3. Generate a list of current components to identify their internal IDs:
    bash
    ./update_alias_name.sh -h <PC_Host> -u <User> -p <Pass> -T component -S 8182
    This creates a ComponentsList.csv file.
  4. Create a new file named Input.csv containing the IDs and your new custom names. The format must be: SourceID,ItemID,NewName Example: 1330255,1330260,TANK 3
  5. Apply the custom aliases using the input file:
    bash
    ./update_alias_name.sh -h <PC_Host> -u <User> -p <Pass> -T component -S 8182 -i Input.csv
  6. Enable the aliases in the NetOps Portal UI:
    • Go to My Settings (or User Settings).
    • Locate Item Name Display Setting.
    • Change the value to Use Item Name Alias.

Note: If the UI does not update immediately, you may need to wait for the next synchronization cycle between the Data Aggregator and Performance Center.