Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1


Remember Me

Nagios Exchange

Nagios Exchange

NagiosĀ® Exchange is the central place where you'll find all types of Nagios projects - plugins, addons, documentation, extensions, and more. This site is designed for the Nagios Community to share its Nagios creations.

Have a new project for Nagios that you'd like to share? Just create an account and add it to the directory. (Read the FAQ)

Random Project



/Category: Themes and Skins
Views: 663017

Popular Projects

Jump to the most requested...

Nagios XI Addons:
Nagios Log Server Addons:

General Addons:

Project Stats

There are 5843 listings in 458 categories on Nagios Exchange!

Newest Nagios Projects

  • Check AWS CloudWatch Alarms

    check-cloudwatch is a simple CLI program, utilising the AWS SDK, to check the status of a specified CloudWatch alarm.

  • check_aws_events

    Check current event logs information from the AWS Service Health Dashboard The endpoint for the API is: (provides event data for all regions) usage: -s EC2|RDS -r us-east-1|us-west-1|us-west-2


    Simple python script to run checks on ifconfig or /proc/net/dev data

  • Check vplex

    This plugin permit to check the helth of a vplex of the DELL / EMC. It check with the API rest of the vplex.

  • Send Nagios service problem as mail

    A python script which can be used as an event handler for services within Nagios to automatically send mail to a targeted mail address when a service problem occurs. The script is called by creating a command within Nagios and passing the parameters required in the script from the Nagios macros available. There is a option to have an acknowledge list where service problem ID from Nagios can be listed on seperate lines. The script will go through the file, with the search path specefied in the variable ackFile, line-by-line to see if the service problem already have been sent as an mail. Just point this variable to an empty file to exclude this functionality. There is another option to have an exclusion list of service problems to not be sent by mail. This is done by having strings of text of the problem description to be excluded on seperate lines within the file pointed to by the variable exclFile. There is also a debug functionality which can be used to track down errors or formatting problems of the mails sent. Required variables to be set within the script are the following: * sendToMail (mail address to send service problems to) * fromMailAddress (the mail address listed as sender of the mails) * sendToMail_DEBUG (only required if DEBUG is defined as true) * ackFile (just point this to an empty file if not used) * exclFile (just point this to an empty file if not used) * flapThreshold (the percentage of state change during last checks which a service needs to have to be considered flapping and thus prevent mail from being transmitted for the specific service)

  • Local AD check for Azure AD Synchronization

    A simple script which checks the local server that Azure AD Connect runs on for the following: * Time since successful synchronization with Azure AD * Time since successful password synchronization with Azure AD * Errors in event log indicating problems with synchronization Parameters: 1: [Int] $allowedMinutesSinceSync (Default: 90): Time (in minutes) since last successful synchronization before a critical alert is raised. 2: [bool] $disableOutput (Default: $false): Toggles the status of $disableOutput and determines whether the script should generate any output. 3: [bool] $checkPasswordSync (Default: $true) Toggles whether password synchronization is synchronized between local AD and AAD. The checks are performed using the following powershell commands: * Get-ADSyncPartitionPasswordSyncState * Get-ADSyncScheduler * Get-WinEvent The script has only been tested using NSClient++ on Windows 2016 servers and Nagios Core 4.4.5 and the check_nrpe command.

  • Environmental monitoring with BME680

    Environmental monitoring with Raspberry Pi and BME680 and Nagios / NRPE Python3 script run by NRPE. Assumes the BME680 device is already attached to the Raspberry Pi. Software setup Install the required library: sudo pip3 install adafruit-circuitpython-bme680 Enable i2c: sudo raspi-config Use the down arrow to select 5 Interfacing Options. Arrow down to P5 I2C . Select yes when it asks you to enable I2C. Also select yes if it asks about automatically loading the kernel module. Use the right arrow to select the Finish button. To correct permission error you need to add your user to i2c group: sudo usermod -a -G i2c and also nagios / NRPE user: sudo usermod -a -G i2c nagios Log out and back in for group change to take effect and/or reboot the Raspberry Pi: sudo reboot Add NRPE check Save file to /usr/lib/nagios/plugins/ Add to NRPE (/etc/nagios/nrpe.cfg): command[check_environ]=python3 /usr/lib/nagios/plugins/ 12 28 18 25 10 100 20 80 10000 10000000 500000 9000000 900 1070 920 1060 5 1 and restart NRPE: sudo /etc/init.d/nagios-nrpe-server restart Add Nagios service (with optional nagiosgraph) On Nagios server (e.g. add the service definition on frp-nagios01): define service{ use rp3-service host_name frp-nagios01 service_description Enviromental Monitoring BME680 check_command check_nrpe!check_environ -t 90 -n #action_url /nagiosgraph/cgi-bin/show.cgi?host=$HOSTNAME$&service=$SERVICEDESC$&geom=1000x200'$..... }

  • sqldelete

    sqldelete is a C program used to remove multiple Hosts from the Nagios XI server's nagiosql MYSQL database quickly.

  • check_azservicehealth

    This is a Nagios plugin designed to query and give status of Azure Tenant Services (aka Office365 applications). It can be used to report on whether a given service is available to end users, and give a quick report on why it may not be- similar to the health summary available in the Azure tenant administration portal. It requires that an Enterprise Application be registered and be given Office365 Service Health permissions. Parameters require your Tenant GUID as well as the Application ID for the check. It will run in linux powershell, and very likely windows powershell from NCPA/NSClient++ (not tested).

  • Nimble Storage Hardware Pool Disk Space API Check Script

    The script utilises the Nimble Storage API to provide some basic disk space usage monitoring. Although the Nimble Storage alerting system via Infosight is very good, we all know the warm fuzzy feeling of seeing a nice green service status in NagiosXI. The script only really needs to be scheduled to run once every 30 minutes or so. 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. The script monitors the chosen pool, typically this will be the "default" pool, but you can specify to monitor different pools if you have them on your array. Example usage: ./ -e -u username -p password -w warningthreshold -c criticalthreshold -q poolname The warning and critical thresholds should be given as integers of unit TB. And the pool name as the pool name as it appears in the Nimble Storage GUI or CLI, typically this is "default". 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. # Version History # 1.0 - 20/01/2020 - First Release # 1.1 - 20/01/2020 - Feature Added - Added the performance monitoring statistics for Free space, so NagiosXI can graph these metrics overtime. # 1.2 - 02/02/2020 - Feature Added - Added the performance monitoring for all the ouputs, so NagiosXI can graph these metrics overtime; thanks to "42bios" for the suggestion and code.