ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM - Logmon QOS not visible for new Alarm Policy creation at Group or Device Level

book

Article ID: 222927

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction


This article documents a known issue where logmon probe QOS from Enhanced MCS templates is not visible to create Group or Device level alarm policies. 

Environment

Release : 20.3

Component : UIM LOGMON

Resolution

This will be fixed as part of the August Patch (ETA first week of Sept). 

If required, the following workaround can be used to resolve this issue before the patch: 

1.  Access the OC server Wasp Raw Configuration and navigate to: "webapps/operator_console/custom/uncrypted/"

2. Add logmon to value for "probeWhiteListSTB"

Example: 

probeWhiteListSTB = processes,aws,azure,apache,windows,unix,vmware,docker_monitor,office365,sap_basis,mysql,oracle,dirscan,snmpget,db2,sqlserver,url_response,ldap_response,ad_response,dns_response,ntservices,email_response,ews_response,cdm,adevl,ntevl,elasticsearch,marklogic,ecs,logstash,paloalto,jarvis,tandberg_cseries,tandberg_ex90,tandberg_mxp,restmon,vmax,iis,weblogic,rsp,websphere,net_connect,nic_monitor,nutanix_monitor,ntperf, ntperf64,logmon

3. Apply the changes and restart the OC wasp.