Search Exchange

Search All Sites

Nagios Log Server Now Available - Download Now

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)

Featured Project

check_cisco_wlc - Cisco WLC Checks

check_cisco_wlc - Cisco WLC Checks

/Category: Cisco
Views: 28272

Popular Projects

Jump to the most requested...

Nagios XI Addons:
General Addons:

Project Stats

There are 4964 listings in 442 categories on Nagios Exchange!

Newest Nagios Projects

  • check_freebsd_version

    Checks whether there are updates available for the installed version of FreeBSD. For FreeBSD version 10.0 or later.

  • Send nagios report as pdf file via email

    With the help of this script we can send Nagios Report as pdf file via email.

  • IBM Storwize v7000 Performance

    Plugin to check storage's performance. It doesn't need any extra libraries.

  • check_mariadb_slaves

    A Nagios plugin written in Python to monitor Maria DB slave metrics. Specifically: Replication Lag Slave IO running Slave SQL running

  • box293_check_message_queue

    This Plugin is for checking the kernel message queues. Will return a critical result if more than 1 queue of the same owner exists. WARNING and/or CRITICAL thresholds can be defined on the number of message found in the queue. These need to be the second and/or third arguments of the plugin in the format w_nm:integer for warning and c_nm:integer for critical. Critical does not require warning and vice versa however critical value must be larger than warning value. Example: w_nm:1000 c_nm:5000 The plugin is just a bash script. Usage: box293_check_message_queue [owner_name] [w_nm:integer] [c_nm:integer] Example: box293_check_message_queue nagios w_nm:1000 c_nm:5000 CRITICAL: 3 message queues for the user nagios detected (CRITICAL > 1), Number Of Messages (Total) = 0, Used Bytes (Total) = 0B|Queues=3;;2 Queue_Messages_Total=0 Queue_Used_Bytes_Total=0B;;;0;131072000 Notes: If you don't know what a kernel message queue is or if you use them, this command will show you: ipcs -q ------ Message Queues -------- key msqid owner perms used-bytes messages 0xbd000002 1736704 nagios 600 0 0 Also, if you want to rely on being alerted when there is more than 1 queue for the owner then you will need to run this plugin from another Nagios instance (like via NPRE or check_by_ssh).

  • Check Bandwidth, with vnstat (by Nestor@Toronto)

    Using vnstat to check current bandwidth. vnstat will provide slightly faster checking but it can only do per NIC/interface, instead of over all bandwidth. Script were written in BASH, tested on CentOS 6.X, Nagios 3.X # Dependency: vnstat

  • Check Bandwidth, with iftop (by Nestor@Toronto)

    Using iftop to check current bandwidth. Script were written in BASH, tested on CentOS 6.X, Nagios 3.X # Dependency: iftop

  • Check Bandwidth, with iftop, for single interface (by Nestor@Toronto)

    Using iftop to check current bandwidth for ONLY one NIC. Script were written in BASH, tested on CentOS 6.X, Nagios 3.X # Dependency: iftop

  • Check Bandwidth for PPTP/PPP VPN (by Nestor@Toronto)

    This script will check how many PPTP user is currently logged and check each users' speed, it will send out alert if any user is over usage from input value. Check IO Wait for Linux. Return IO wait in percentage Script were written in BASH, tested on CentOS 6.X, Nagios 3.X # Dependency: vnstat,

  • Check Speedtest (by Nestor@Toronto)

    Using '', written by Matt Martz, to check server max bandwidth using speedtest method. It return alert if server bandwidth is slower than given speed. Note: While managing few hundreds VM/VPS from different VPS vendors, I found that sometime bandwidth slow down without notice. Best practice would be running this speedtest at least daily. If monitoring is required perhaps hourly. You may also want to make sure re-try is more than 3 minutes. Or perhaps one retry. # Dependency: - Python (tested with Python 2.6) - - Speedtest may require upto 150 seconds to finish the test. Please make sure you set the timeout alert accordingly. # KNOWN Bug: some server may return time out.