The categories of all possible Nagios alerts

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
ranjitw
Posts: 175
Joined: Tue Sep 01, 2015 1:52 am

The categories of all possible Nagios alerts

Post by ranjitw »

Hi All,

Can anyone please share me the list of all possible Nagios alerts for check_nt and check_nrpe plugins ?

Regards,
Ranjit w
Regards,
Ranjit W
jdalrymple
Skynet Drone
Posts: 2620
Joined: Wed Feb 11, 2015 1:56 pm

Re: The categories of all possible Nagios alerts

Post by jdalrymple »

check_nt is self documented.

Code: Select all

check_nt v2.0.3 (nagios-plugins 2.0.3)
Copyright (c) 2000 Yves Rubin ([email protected])
Copyright (c) 2000-2014 Nagios Plugin Development Team
        <[email protected]>

This plugin collects data from the NSClient service running on a
Windows NT/2000/XP/2003 server.


Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]

Options:
 -h, --help
    Print detailed help screen
 -V, --version
    Print version information
 --extra-opts=[section][@file]
    Read options from an ini file. See
    https://www.nagios-plugins.org/doc/extra-opts.html
    for usage and examples.
Options:
 -H, --hostname=HOST
   Name of the host to check
 -p, --port=INTEGER
   Optional port number (default: 1248)
 -s, --secret=<password>
   Password needed for the request
 -w, --warning=INTEGER
   Threshold which will result in a warning status
 -c, --critical=INTEGER
   Threshold which will result in a critical status
 -t, --timeout=INTEGER
   Seconds before connection attempt times out (default:  -l, --params=<parameters>
   Parameters passed to specified check (see below) -d, --display={SHOWALL}
   Display options (currently only SHOWALL works) -u, --unknown-timeout
   Return UNKNOWN on timeouts10)
 -h, --help
   Print this help screen
 -V, --version
   Print version information
 -v, --variable=STRING
   Variable to check

Valid variables are:
 CLIENTVERSION = Get the NSClient version
  If -l <version> is specified, will return warning if versions differ.
 CPULOAD =
  Average CPU load on last x minutes.
  Request a -l parameter with the following syntax:
  -l <minutes range>,<warning threshold>,<critical threshold>.
  <minute range> should be less than 24*60.
  Thresholds are percentage and up to 10 requests can be done in one shot.
  ie: -l 60,90,95,120,90,95
 UPTIME =
  Get the uptime of the machine.
  -l <unit>
  <unit> = seconds, minutes, hours, or days. (default: minutes)
  Thresholds will use the unit specified above.
 USEDDISKSPACE =
  Size and percentage of disk use.
  Request a -l parameter containing the drive letter only.
  Warning and critical thresholds can be specified with -w and -c.
 MEMUSE =
  Memory use.
  Warning and critical thresholds can be specified with -w and -c.
 SERVICESTATE =
  Check the state of one or several services.
  Request a -l parameters with the following syntax:
  -l <service1>,<service2>,<service3>,...
  You can specify -d SHOWALL in case you want to see working services
  in the returned string.
 PROCSTATE =
  Check if one or several process are running.
  Same syntax as SERVICESTATE.
 COUNTER =
  Check any performance counter of Windows NT/2000.
        Request a -l parameters with the following syntax:
        -l "\\<performance object>\\counter","<description>
        The <description> parameter is optional and is given to a printf
  output command which requires a float parameter.
  If <description> does not include "%%", it is used as a label.
  Some examples:
  "Paging file usage is %%.2f %%%%"
  "%%.f %%%% paging file used."
 INSTANCES =
  Check any performance counter object of Windows NT/2000.
  Syntax: check_nt -H <hostname> -p <port> -v INSTANCES -l <counter object>
  <counter object> is a Windows Perfmon Counter object (eg. Process),
  if it is two words, it should be enclosed in quotes
  The returned results will be a comma-separated list of instances on
   the selected computer for that object.
  The purpose of this is to be run from command line to determine what instances
   are available for monitoring without having to log onto the Windows server
    to run Perfmon directly.
  It can also be used in scripts that automatically create Nagios service
   configuration files.
  Some examples:
  check_nt -H 192.168.1.1 -p 1248 -v INSTANCES -l Process

Notes:
 - The NSClient service should be running on the server to get any information
   (http://nsclient.ready2run.nl).
 - Critical thresholds should be lower than warning thresholds
 - Default port 1248 is sometimes in use by other services. The error
   output when this happens contains "Cannot map xxxxx to protocol number".
   One fix for this is to change the port to something else on check_nt
   and on the client service it's connecting to.

Send email to [email protected] if you have questions regarding use
of this software. To submit patches or suggest improvements, send email to
[email protected]
check_nrpe has no similar constructs, check_nrpe does whatever you tell it to based upon plugins you install and configure. The nsclient++ daemon has some built in modules that allow you to check some system metrics without writing/executing your own plugins, those are documented here at http://www.nsclient.org.
ranjitw
Posts: 175
Joined: Tue Sep 01, 2015 1:52 am

Re: The categories of all possible Nagios alerts

Post by ranjitw »

Hi ,

By default in Nagios XI when we add a server to monitoring with default thresholds alarms would be generated with different messages based on the service type being monitored.

Is there way to get list of all possible alarm messages which will be generated with the default commands

Regards,
Ranjit W
Regards,
Ranjit W
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: The categories of all possible Nagios alerts

Post by hsmith »

You would have to look at the code of the plugin itself, if I'm understanding your question right.

You're saying you want a list of every possible output of every possible plugin in Nagios XI? What 'default commands' are you talking about here?
Former Nagios Employee.
me.
User avatar
eloyd
Cool Title Here
Posts: 2190
Joined: Thu Sep 27, 2012 9:14 am
Location: Rochester, NY
Contact:

Re: The categories of all possible Nagios alerts

Post by eloyd »

Is there way to get list of all possible alarm messages which will be generated with the default commands
No.

Especially since thousands of plugins have been developed and distributed via the Nagios Exchange, and probably hundreds of thousands of custom plugins have been written that were never released to the public.

However, all Nagios plugins return a single number for the status of the check: 0=OK, 1=WARNING, and 2=CRITICAL (anything else is treated as UNKNOWN). So I don't know why you want to know what you're asking for, but you don't need to know all possible results, just the 0, 1, or 2 from a properly configured plugin.
Image
Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoyd
I'm a Nagios Fanatic! • Join our public Nagios Discord Server!
jdalrymple
Skynet Drone
Posts: 2620
Joined: Wed Feb 11, 2015 1:56 pm

Re: The categories of all possible Nagios alerts

Post by jdalrymple »

In addition to eloyd's comments you may find this useful: https://nagios-plugins.org/doc/guidelines.html
ranjitw
Posts: 175
Joined: Tue Sep 01, 2015 1:52 am

Re: The categories of all possible Nagios alerts

Post by ranjitw »

Thank you. Please close the post.
Regards,
Ranjit W
Locked