Nimble Storage Replication Health API Check Script

Submit review Recommend Print

Rating

0 votes

Favoured:

Current Version

1.0

Last Release Date

2020-01-17

Compatible With

Nagios XI

Owner

geekmungus

License

GPL

Hits

4680

Files:

File	Description
check_nimble_repl_api.py	check_nimble_repl_api.py

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Download Now

Monitoring Made Magically Better

Nagios Core on Overdrive
Powerful Monitoring Dashboards
Time-Saving Configuration Wizards
Open Source Powered Monitoring On Steroids
And So Much More!

The script utilises the Nimble Storage API to monitor the state of any lagged volumes, i.e. replicas that are still in a copying state. The user can specify when a lagged volume breaches a specific threshold in seconds to generate an error. Its normal for there to be a small amount of lag when the replication occurs, so you set it to a threshold after which you care. For example if a volume collection normally replicates within about 60 minutes (3600 seconds), then set the threshold for 3600, that way if it goes over that you'll know. The script uses the Nimble Storage API, so setting it to check every 30 minutes is normally sufficient.

The script makes use of the Nimble Storage API, it is recommended to create a read-only account on the Nimble Storage array(s), this can be AD/LDAP or local.

The script is written in Python 2.7, check the shebang line at the start of the file to ensure the path to your interpreter is correct.

Example usage:

./check_nimble_repl_api.py -e https://array.domain.co.uk:5392 -u username -p password -c theshold(in seconds)

Within NagiosXI configuration you can use the -e as an argument and enter the URL as written, NagiosXI appears to deal with the escapes correctly.

You may need to put the password in single quotes (if it contains weird characters).

There is a debug mode, add "-d" to the end of the command string for more detailed output for troubleshooting operation of the script, this is best run from the command line of the NagiosXI server.

Reviews (0)

Be the first to review this listing!

Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner. The files and information on this site are the property of their respective owner(s). Nagios Enterprises makes no claims or warranties as to the fitness of any file or information on this website, for any purpose whatsoever. In fact, we officially disclaim all liability. We do, however, think these community contributions are pretty damn cool. Website Copyright © 2009-2024 Nagios Enterprises, LLC. All rights reserved.