UIM - What does the qos_processor probe do?

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

This KB provides a brief detail on the functionality of the qos_processor probe 

Environment

component: qos_processor

version : 20.4.x

Resolution

Documentation for the qos_processor probe can be found here.

qos_processor

Overview

The qos_processor probe works with the data_engine probe and the NIS database to:

Maintain correct origin after changes at robot and hub

Prior to NMS 6.0, the origin field of S_QOS_DATA table was not updated if an origin reassignment occurred at the robot or hub.

Modify origin and other select QoS monitor attributes using script-based enrichment.

 

This option allows you to assign the origin field of the S_QOS_DATA table based on the outcome of applying rules to monitor attributes such as QOS, SOURCE, TARGET.

 

If an enrichment script exists for QOS_MESSAGE it will override an origin change done on the hub.

Changes to the enrichment_rb (Ruby Scripting language) script are dynamically loaded by the qos_processor probe.

 

Note: An enrichment script is not required. If an enrichment script does not exist only origin changes will be made.

These changes allow UMP portlets such as list viewer to reflect the correct origin associated with QoS data sent from the probes.

The S_QOS_DATA table in the NIS database contains records that represent instances of specific probe monitors that generate QoS data.

The qos_processor probe listens for QOS_MESSAGE subjects on the hub, evaluates and potentially modifies some non-key attributes of the record corresponding to the monitor. The evaluation and modification of the attributes is done with the use of an enrichment script (enrichment.rb). This script should be located in <Nimsoft>/probes/slm/qos_processor/scripts/<enrichment.rb>.

 

The probe can modify the fields:

 

ORIGIN

HOST

ROBOT

PROBE

 

All fields will be bound into the script environment as member fields of a script object named "monitor." There is also a logging object named "logger" available for writing messages to the probe log file.

 

Important!

This probe cannot modify the QOS, SOURCE or TARGET fields as these are the keys that uniquely identify the data in the entire system.

 

WARNING: This probe will reduce the overall throughput of your system, if you encounter performance issues please contact Broadcom UIM  Support for assistance.