Skip to content

Commit e75726c

Browse files
committed
Added offline volumes; down vservers; down protocol vservers. Took out the matching and excptions option with volume utilization alerts, since it was causing issues with aging out events.
1 parent 4647c39 commit e75726c

File tree

5 files changed

+441
-209
lines changed

5 files changed

+441
-209
lines changed

Monitoring/monitor-ontap-services/README.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -288,6 +288,7 @@ filename, then set the configFilename environment variable to the name of your c
288288
| smRelationshipsFilename | No | No | OntapAdminServer + "-smRelationships" | Set to the filename (S3 object) where you want the program to store the SnapMirror relationships into. This file is used to track the number of bytes transferred so it can detect stalled SnapMirror updates. This file will be created as necessary. |
289289
| storageEventsFilename | No | No | OntapAdminServer + "-storageEvents" | Set to the filename (S3 object) where you want the program to store the Storage Utilization events it has alerted on. This file will be created as necessary. |
290290
| quotaEventsFilename | No | No | OntapAdminServer + "-quotaEvents" | Set to the filename (S3 object) where you want the program to store the Quota Utilization events it has alerted on. This file will be created as necessary. |
291+
| vserverEventsFilename | No | No | OntapAdminServer + "-vserverEvents" | Set to the filename (S3 object) where you want the program to store the vserver events it has alerted on. This file will be created as necessary. |
291292
| systemStatusFilename | No | No | OntapAdminServer + "-systemStatus" | Set to the filename (S3 object) where you want the program to store the overall system status information into. This file will be created as necessary. |
292293
| snsTopicArn | Yes | No | None | Set to the ARN of the SNS topic you want the program to publish alert messages to. |
293294
| cloudWatchLogGroupName | No | No | None | The name of **an existing** CloudWatch log group that the Lambda function will also send alerts to. If left blank, alerts will not be sent to CloudWatch.|
@@ -346,14 +347,6 @@ Each rule should be an object with one, or more, of the following keys:
346347
|healthy|Boolean|If `true` will alert with the relationship is healthy. If `false` will alert with the relationship is unhealthy.|
347348

348349
###### Matching condition schema for Storage Utilization (storage)
349-
The storage schema had two additional keys that can be included before the rules:
350-
|Key Name|Value Type|Notes|
351-
|---|---|---|
352-
|exceptions|Array of objects|Each entry in this array specifies SVM and Volume name combination that should be ignored for the rules specified within its block. The format of the object is: `{"svm": "svm_name", "name": "volume_name"}`|
353-
|matches|Array of objects|Each entry in this array specifies a SVM and Volume name combination that must be matched for the rules specified within its block to be applied. The format of the object is: `{"svm": "svm_name", "name": "volume_name"}`|
354-
355-
The exceptions and matches keys are optional. If they are not specified, then the rules will be applied to all SVMs and volumes.
356-
357350
Each rule should be an object with one, or more, of the following keys:
358351
|Key Name|Value Type|Notes|
359352
|---|---|---|
@@ -363,6 +356,7 @@ Each rule should be an object with one, or more, of the following keys:
363356
|volumeCriticalPercentUsed|Integer|Specifies the maximum allowable volume utilization (between 0 and 100) before an alert is sent.|
364357
|volumeWarnFilesPercentUsed|Integer|Specifies the maximum allowable volume files (inodes) utilization (between 0 and 100) before an alert is sent.|
365358
|volumeCriticalFilesPercentUsed|Integer|Specifies the maximum allowable volume files (inodes) utilization (between 0 and 100) before an alert is sent.|
359+
|offline:|Boolean|If `true` will alert if the volume is offline.|
366360

367361
###### Matching condition schema for Quota (quota)
368362
Each rule should be an object with one, or more, of the following keys:
@@ -373,6 +367,14 @@ Each rule should be an object with one, or more, of the following keys:
373367
|maxSoftQuotaSpacePercentUsed|Integer|Specifies the maximum allowable storage utilization (between 0 and 100) against the soft quota limit before an alert is sent.|
374368
|maxQuotaInodesPercentUsed|Integer|Specifies the maximum allowable inode utilization (between 0 and 100) before an alert is sent.|
375369

370+
###### Matching condition schema for Vserver (vserver)
371+
Each rule should be an object with one, or more, of the following keys:
372+
|Key Name|Value Type|Notes|
373+
|---|---|---|
374+
|vserverState|Boolean|If `true` will alert if the vserver is not in `running` state.|
375+
|nfsProtocolState|Boolean|If `true` will alert if the NFS protocol is not enabled on a vserver.|
376+
|cifsProtocolState|Boolean|If `true` will alert if the CIFS protocol is enabled for a vserver but doesn't have an `online` status.|
377+
376378
###### Example Matching conditions file:
377379
```json
378380
{

Monitoring/monitor-ontap-services/buildLambdaLayer

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,5 @@
33
# This script builds the Lambda Layer required for the monitor_ontap_services to function.
44
rm -rf python lambda_layer.zip
55
mkdir python
6-
pip3 install --target ./python 'cronsim>=2.6'
6+
pip3 install --target ./python 'cronsim>=2.6' pytz
77
zip -r lambda_layer.zip python

0 commit comments

Comments
 (0)