Alarms are made invisible automatically: guidance to read nas.log

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are seeing some case of alarms that are being turned into invisible and we don't know who or what is making them invisible. 

Environment

DX UIM 24.3.*

Cause

Guidance

Resolution

Analyzing nas.log would provide indications on who or what is turning the alarms into invisible. 

Some guidance for reding the alarm log.

First set "loglevel = 5, and "debug = 5" 

 

• This is normally logged in nas.log when you manually make an alarm invisible:
  
  Mar  3 09:07:19:718 [12876] 2 nas: NiS bridge: NTS UPDATED VISIBILITY: nimid='#########-######', FALSE
Mar  3 09:07:19:721 [12876] 2 nas: NiS bridge: NA UPDATED VISIBILITY: nimid='#########-######', FALSE

 

• The Below is observed in the nas.log when the alarm is made invisible via an AO that set the visibility:
  
  
  Line 357: Mar  3 09:10:14:958 [11848] 2 nas: ExecEvent: IMMEDIATE rule='set pollagent alarm inviisble', nimid='#########-######', ACTION:set_visibility
Line 358: Mar  3 09:10:14:958 [11848] 3 nas: ExecEvent: Rule='set pollagent alarm inviisble' on nimid=''#########-######'' with ACTION:set_visibility, age:0s, status:OK


• When an alarm is made invisble via UIMAPI / we_services_rest / REST Call / Swagger the followin gis logged: 
  
  

  Mar 12 10:46:31:805 [14740] 2 nas: NiS bridge: NTS UPDATED VISIBILITY: nimid=''#########-######', FALSE
Mar 12 10:46:31:806 [14740] 2 nas: NiS bridge: NA UPDATED VISIBILITY: nimid='#########-######', FALSE