Adding Robot IP and QOS Mapping to Alarm Payload via Alarm Enrichment (Use Case Example)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

A user needs to enrich DX UIM alarm payloads by adding the Robot IP address and QOS mapping information into custom alarm fields (e.g., custom_4 and custom_5). This allows for better downstream processing and visibility in the Alarm Console.

Environment

• Product: DX Unified Infrastructure Management (UIM)
• Probe: nas (Alarm Enrichment)
• Database: Microsoft SQL Server (UIM Database)

Resolution

1. Create a Custom Lookup Table (needed for QOS enrichment)

To ensure high performance and prevent locking on core tables, create a custom lookup table in the UIM database. This table should be periodically refreshed to include new sources.

-- Create a lookup table for QOS metrics

SELECT DISTINCT ci_metric_id, qos INTO custom_qos_mapping FROM S_QOS_DATA WHERE target IS NOT NULL AND probe = 'cdm';

 

2. Configure the enrichment-sources via raw configure (database login information needs to be updated here as well)

    enrichement-source > cmdbs 

Add the following enrichment-source configurations to define where the nas probe retrieves the data.

  enrichement-source > cmdbs > os_enricher (for IP) 

• query: select name, ip, os_type from cm_computer_system where name=?

• population_query: select name, ip, os_type from cm_computer_system

 enrichement-source > cmdbs > qos_enricher (for QOS metadata)

• query: SELECT qos FROM custom_qos_mapping WHERE ci_metric_id = ?

• population_query: SELECT ci_metric_id, qos FROM custom_qos_mapping

 

3. Define Enrichment Rules in nas.cfg via raw configure

enrichment-rules > 1 (for IP)

Set up rules to map the retrieved database values to the alarm custom fields.

• use_enricher: os_enricher

• match_alarm_regex: (cdm) (or desired probe)

• match_alarm_field: prid

• lookup_by_alarm_field: robot

enrichment-rules > 1 > overwrite-rules

• udata.custom_4 = [cmdb.ip]

 

enrichment-rules > 2 (for QOS metadata)         

• use_enricher: qos_enricher

• match_ alarm_regex: (cdm)

• lookup_by_regexp: .* 

• match_alarm_field: prid

• lookup_by_alarm_field: met_id

 enrichment-rules > 2 > overwrite-rules       

• overwrite-rules: udata.custom_5 = [cmdb.qos]

---

Verification

1. Restart the nas probe to apply changes.

2. Trigger a test alarm from the cdm probe.

3. Check the Alarm Console (Operator Console or Infrastructure Manager) and verify that the Custom 4 field contains the IP address and Custom 5 contains the QOS name.