Sponsored Content
Full Discussion: Nagios plugins
Special Forums UNIX and Linux Applications Infrastructure Monitoring Nagios plugins Post 302969587 by MadeInGermany on Thursday 24th of March 2016 08:33:08 AM
Old 03-24-2016
Nagios plugins

I don't like the standard monitoring plugins for Nagios. After hours of checking out alternatives, I finally decided to develop some own alternatives (and spend days Smilie).
The goal was to make system monitoring simple. (And not: getting as many details as possible.)
The plugins are written in standard shell. They work on Linux and Solaris and many other Unixes. They work well with nrpe (Nagios Remote Plugin Executor).
The attached zip file contains a text file DESCRIPTION that shortly describes the functions.
With some shell writing skills it should be easy to port the plugins to other monitoring tools.

Last edited by MadeInGermany; 10-30-2018 at 10:49 AM.. Reason: updated attached zip file
These 4 Users Gave Thanks to MadeInGermany For This Post:
 

5 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Nagios aka Netsaint plugins

Hi guys, I'm looking for a Nagios plugin which monitors selected processes and if they die, restarts them. Does anyone have such a plugin\script, or could anyone point me in the right direction? Cheers Jamie (3 Replies)
Discussion started by: JayC89
3 Replies

2. Infrastructure Monitoring

creating nagios plugins and defining services

Hello friends, i have essential nagios documents and some basic configuration documents but they dont meet my needs, so i would like to have a detailed, comprehensive documents that refers to pluggins, how to configure a complex nagios script as a service, maybe even how to trigger another... (0 Replies)
Discussion started by: EAGL€
0 Replies

3. Solaris

nagios-plugins-1.4.15 Install Problem on Solaris 10

I am trying to install nagios-plugins-1.4.15 on a Solaris 10 box and when I run the ./configure script I get this error: checking for grep that handles long lines and -e... configure: error: no acceptable grep could be found in... (2 Replies)
Discussion started by: thatwaseasy
2 Replies

4. Infrastructure Monitoring

Nagios check dependent on second nagios server

We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side. I was wondering if there is any way to setup cross dependencies... (1 Reply)
Discussion started by: eugenes18t
1 Replies

5. Shell Programming and Scripting

Creating additional plugins for nagios

Team would like to know if anyone here had created a basic nagios plugin. I did write a simple postfix service checker. Then add it in nagios nrpe.cfg then restart nrpe and nagios and it is not working, its like i cant receive email if the service is stopped or running. #!/bin/bash... (0 Replies)
Discussion started by: kenshinhimura
0 Replies
COLLECTD-NAGIOS(1)						     collectd							COLLECTD-NAGIOS(1)

NAME
collectd-nagios - Nagios plugin for querying collectd SYNOPSIS
collectd-nagios -s socket -n value_spec -H hostname [options] DESCRIPTION
This small program is the glue between collectd and nagios. collectd collects various performance statistics which it provides via the "unixsock plugin", see collectd-unixsock(5). This program is called by Nagios, connects to the UNIX socket and reads the values from collectd. It then returns OKAY, WARNING or CRITICAL depending on the values and the ranges provided by Nagios. ARGUMENTS AND OPTIONS
The following arguments and options are required and understood by collectd-nagios. The order of the arguments generally doesn't matter, as long as no argument is passed more than once. -s socket Path of the UNIX socket opened by collectd's "unixsock plugin". -n value_spec The value to read from collectd. The argument is in the form "plugin[-instance]/type[-instance]". -H hostname Hostname to query the values for. -d data_source Each value_spec may be made of multiple "data sources". With this option you can select one or more data sources. To select multiple data sources simply specify this option again. If multiple data sources are examined they are handled according to the consolidation function given with the -g option. -g none|average|sum When multiple data sources are selected from a value spec, they can be handled differently depending on this option. The values of the following meaning: none No consolidation if done and the warning and critical regions are applied to each value independently. average The warning and critical ranges are applied to the average of all values. sum The warning and critical ranges are applied to the sum of all values. percentage The warning and critical ranges are applied to the ratio (in percent) of the first value and the sum of all values. A warning is returned if the first value is not defined or if all values sum up to zero. -c range -w range Set the critical (-c) and warning (-w) ranges. These options mostly follow the normal syntax of Nagios plugins. The general format is "min:max". If a value is smaller than min or bigger than max, a warning or critical status is returned, otherwise the status is success. The tilde sign (~) can be used to explicitly specify infinity. If ~ is used as a min value, negative infinity is used. In case of max, it is interpreted as positive infinity. If the first character of the range is the at sign (@), the meaning of the range will be inverted. I. e. all values within the range will yield a warning or critical status, while all values outside the range will result in a success status. min (and the colon) may be omitted, min is then assumed to be zero. If max (but not the trailing colon) is omitted, max is assumed to be positive infinity. -m If this option is given, "Not a Number" (NaN) is treated as critical. By default, the none consolidation reports NaNs as warning. Other consolidations simply ignore NaN values. RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status message to STDOUT and signals success or failure with it's return value. It exits with a return value of 0 for success, 1 for warning and 2 for critical. If the values are not available or some other error occurred, it returns 3 for unknown. SEE ALSO
collectd(1), collectd.conf(5), collectd-unixsock(5), <http://nagios.org/> AUTHOR
Florian Forster <octo at verplant.org> 5.1.0 2012-04-02 COLLECTD-NAGIOS(1)
All times are GMT -4. The time now is 06:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy