cohesity_monitor probe and self-monitoring alarms

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

What are the self-monitoring alarms and how can they be disabled? 

Environment

Release : 20.3

Component : UIM COHESITY_MONITOR PROBE

Cause

Self-monitoring alarms are generated when a profile resource item is no longer available as can be seen from this log copy:
Dec 06 18:59:41:936 [Data Collector - Cohesity, cohesity_monitor] Data point lookup failed for '"ESC:CLUSTER:TEST Cohesity::CohesityP"."numServiceAlerts"', will attempt to use raw data value for display
Dec 06 18:59:41:936 [Data Collector - Cohesity, cohesity_monitor] Failed to collect data for monitor 'TEST Cohesity/CohesityP.Number of active service Alerts'. Updated value will not be available.: Lookup failed for value of monitor '"ESC:CLUSTER:TEST Cohesity::CohesityP"."numServiceAlerts"'. GUI will not display current value or severity. Will try again next polling cycle.

Then the graph file graphDump.txt which contains the list of resource items is updated: 
Dec 06 18:59:41:994 [Data Collector - Cohesity, cohesity_monitor] PERF: DONE:  Updating monitors in graph   {Seconds=0.058}

Finally the self-monitoring alarms are sent:
Dec 06 18:59:41:994 [Data Collector - Cohesity, cohesity_monitor] SENDING_ALARM: Self-Monitoring Failures for 'Cohesity:CLUSTER.numServiceCriticalAlerts': Data Collection (2 of 2 failed).  See cohesity_monitor.log for more details

Resolution

open the cohesity_monitor raw configure
go to setup 
New Key 
key name: enable_self_monitoring_alarm 
value: false
OK 
Apply
OK

Additional Information

When enabled the log will show:
Dec 08 11:58:59:832 [Data Collector - Cohesity, cohesity_monitor] Self monitoring alarms are disabled. Skipping sending alarm for: CLEAR: No Self-Monitoring Failures for 'Cohesity:CLUSTER.totalLogicalUsageBytes'.