Hi Team,
I have configured a bash script to monitor netapp volumes which goes beyond 95%. so any volume which goes beyond 95% nagios will trigger an sms to the concerned number.
Now the issue is say if there are 3 volumes which are beyond 95%, the state will change to critical and all the 3 volumes details will be sent. Imagine the admin is clearing space only in 2 volumes. one volume is still pending. still the state will be critical only in nagios and any other new volumes if it comes beyond 95% will not trigger sms becase state is still critical.
Is there any way we can do even if the state is critical and if any additions are happening still it should send an sms.
Thanks
Venki
Nagios Netapp Monitoring
Re: Nagios Netapp Monitoring
It sounds like BPI (Nagios Business Process Intelligence) would best apply to this scenario.
https://assets.nagios.com/downloads/nag ... BPI_v2.pdf
Basically you would create a 'netapp volume' group (withinin BPI) and then you can set a performance threshold for the group, instead of individual hosts or services. Ex:
Warning Threshold:
If the health percentage of the group drops below the Warning Threshold, the group state changes to "Warning."
Critical Threshold:
If the health percentage of the group drops below the Critical Threshold, the group state changes to "Critical."
Must be a lower number than the Warning Threshold.
A Basic BPI Group
This is a basic group with 5 members. The group has a warning threshold of 60%, and a
critical threshold of 70%. Even though the group has one member in a Warning state, the group state is still 'Ok' because the health percentage is at 75%
Let us know if this is what you're looking for, thanks.
https://assets.nagios.com/downloads/nag ... BPI_v2.pdf
Basically you would create a 'netapp volume' group (withinin BPI) and then you can set a performance threshold for the group, instead of individual hosts or services. Ex:
Warning Threshold:
If the health percentage of the group drops below the Warning Threshold, the group state changes to "Warning."
Critical Threshold:
If the health percentage of the group drops below the Critical Threshold, the group state changes to "Critical."
Must be a lower number than the Warning Threshold.
A Basic BPI Group
This is a basic group with 5 members. The group has a warning threshold of 60%, and a
critical threshold of 70%. Even though the group has one member in a Warning state, the group state is still 'Ok' because the health percentage is at 75%
Let us know if this is what you're looking for, thanks.
Be sure to check out the Knowledgebase for helpful articles and solutions!
Re: Nagios Netapp Monitoring
Hi Wallace,
Thanks for replying.
Sorry to say i am not looking for this.
nagios will execute an event handler only when a state change happens.
pblm is if any volume is going above critical threshold nagios will change the state to critical and sms alert is triggered.
But if we are not clearing the space of that volume and if one more volumes are coming above threshold, nagios will not execute the event handler as the state is still critical.
Is there any way even if the state is critical and any new additional device is coming in that critical threshold, nagios should send an sms.
Regards
Venki
Thanks for replying.
Sorry to say i am not looking for this.
nagios will execute an event handler only when a state change happens.
pblm is if any volume is going above critical threshold nagios will change the state to critical and sms alert is triggered.
But if we are not clearing the space of that volume and if one more volumes are coming above threshold, nagios will not execute the event handler as the state is still critical.
Is there any way even if the state is critical and any new additional device is coming in that critical threshold, nagios should send an sms.
Regards
Venki
Re: Nagios Netapp Monitoring
This is a plugin issue, not a Nagios/Core issue. The plugin itself needs to determine if something is OK/Warning/Critical, and Nagios acts accordingly. You will need to write this logic into your plugin, but honestly with disk checks it's usually best to do one check per partition/disk/mountpoint/etc. to avoid this sort of thing.
Former Nagios employee