logmon MCS template 'QOS Name' creation without a name doesn't add <Default> in logmon.cfg
search cancel

logmon MCS template 'QOS Name' creation without a name doesn't add <Default> in logmon.cfg

book

Article ID: 278715

calendar_today

Updated On: 04-23-2024

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

In the logmon MCS, when creating "QOS Metric for Variable" the UI lets you create a QOS Metric For a Variable without setting a QOS Name. 

When this happens a variable is created, however, as the QOS Name is empty in the CFG file ("qosname = ") no QOS is collected, so the variable doesn't work when created this way: 

Looking at the probe.cfg, qosname is empty:

 

               <profile>
                  definition = 1
                  operator = eq
                  qosactive = yes
                  threshold = 
                  qosname = 
                  mcs_profileid = 119
                qostarget = var
             </progile>

 

NOTE: When the same is done, from IM, so creating a variable without a QOS Name, the variable is created and it seems similar in the UI, in IM.: 

However, the QOS Name shows as "qosname = <Default>".  When hostname is not empty and it has a <Default> the QOS is then created. So in this case there is no issue. 



               <DefaultfromIM>
                  definition = 1
                  operator = eq
                  qosactive = yes
                  qosname = <Default>
                  qostarget = Default from IM
               </DefaultfromIM>

 

Is there a fix so qosname is set to <Default> in the CFG in MCS as it currently does in IM? 

Environment

DX UIM 20.4.x, DX UIM 23.4

logmon_mcs_template_4.21

Cause

Defect 

Resolution

Attached to this KB is a new logmon_mcs_template_4.22

This template contains the fix for this issue. 

1. Download the 3 files contained in this document, and import them into the UIM archive:

logmon probe version 4.21
logmon templates package 4.21
logmon templates package 4.22

2. Deploy both templates packages in order to the robot running mon_config_service (generally the primary hub)

They will be listed in the database like this:

3 .Migrate profile(s): CTRL+P on mon:config_service

execute:

activate_probe_templates_package

probe_name = logmon

template_package_version: 4.22-SNAPSHOT

If you need to update to 4.21-SNAPSHOT, that should be the first package that is migrated, and then you would check to make sure it has migrated, then update to the 4.22-SNAPSHOT using the same process.

Check if it is migrated: 

 

After this new profiles were created with 4.22 Profile even if we leave an empty qos name in the UI, the probe will print <Default> and QOS will be collected immediately:

            <variables>
               <default_fix_var_test>
                  qosactive = yes
                  threshold = 
                  definition = 1
                  operator = eq
                  mcs_profileid = 150
                  qosname = <Default>
                  qostarget = fix_default_test
               </default_fix_var_test>
            </variables>

Attachments

logmon-4.21-2024.zip get_app
logmon_mcs_templates-4.21-20240110.094358-9_1713893532135.zip get_app
logmon_mcs_templates-4.22-20240201.zip get_app