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.

purestorage probe and self-monitoring alarms

book

Article ID: 226623

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

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

Cause

Self-monitoring alarms are generated when a profile resource item is no longer available as can be seen from this log copy:
Oct 17 23:18:26:824 [Data Collector - PUREARRAY01, purestorage] Data point lookup failed for '"ESC:pureStorageArray:PUREARRAY01::PureStorageArray::10.10.10.10"."writespersec"', will attempting to use raw data value for display
Oct 17 23:18:26:824 [Data Collector - PUREARRAY01, purestorage] Failed to collect data for monitor '10.10.10.10.Writes Per Second'. Updated value will not be available.: Lookup failed for value of monitor '"ESC:pureStorageArray:PUREARRAY01::PureStorageArray::10.10.10.10"."writespersec"'. 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: 
Oct 17 23:18:26:833 [Data Collector - PUREARRAY01, purestorage] PERF: DONE:  Updating monitors in graph   {Seconds=0.015}

Finally the self-monitoring alarms are sent:
Oct 17 23:18:26:834 [Data Collector - PUREARRAY01, purestorage] SENDING_ALARM: Self-Monitoring Failures for 'PUREARRAY01:pureStorageArray.readspersec': Data Collection (1 of 1 failed).  See purestorage.log for more details

Environment

Release : 20.3

Component : UIM - PURESTORAGE

Resolution

Available in purestorage-1.23T4 and later. 

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