File: plugins.html

package info (click to toggle)
nagios2 2.6-2%2Betch5
  • links: PTS
  • area: main
  • in suites: etch
  • size: 6,856 kB
  • ctags: 4,475
  • sloc: ansic: 64,870; sh: 4,676; makefile: 787; perl: 722
file content (99 lines) | stat: -rw-r--r-- 3,010 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>
<head>
<title>Nagios Plugins</title>

<STYLE type="text/css">
<!--
        .Default { font-family: verdana,arial,serif; font-size: 8pt; }
        .PageTitle { font-family: verdana,arial,serif; font-size: 12pt; font-weight: bold; }
-->      
</STYLE>

</head>

<body bgcolor="#FFFFFF" text="black" class="Default">

<p>
<div align="center">
<h2 class="PageTitle">Nagios Plugins</h2>
</div>
</p>
<hr>

<p>
<strong><u>What Are Plugins?</u></strong>
</p>

<p>
Plugins are compiled executables or scripts (Perl, shell, etc.) that can be run from a command line to check the status or a host or service.  Nagios uses the results from plugins to determine the current status or hosts and services on your network.  No, you can't get away without using plugins - Nagios is useless without them.
</p>

<p>
<strong><u>Obtaining Plugins</u></strong>
</p>

<p>
Plugin development for Nagios is being done at SourceForge.  The Nagios plugin development project page (where the latest version of by plugins can always be found) is located at <a href="http://sourceforge.net/projects/nagiosplug/">http://sourceforge.net/projects/nagiosplug/</a>.
</p>

<p>
<strong><u>How Do I Use Plugin <i>X</i>?</u></strong>
</p>

<p>
Documentation on how to use individual plugins is <i>not</i> supplied with the core Nagios distribution.  You should refer to the latest plugin distribution for information on using plugins.  Karl DeBisschop, lead plugin developer/maintainer points out the following:
</p>

<p>
<dir>
All plugins that comply with minimal development guideline for this project include internal documentation.  The documentation can be read executing plugin with the '-h' option ('--help' if long options are enabled).  If the '-h' option does not work, that is a bug.
</dir>
</p>

<p>
For example, if you want to know how the check_http plugin works or what options it accepts, you should try executing one of the following commands:
</p>

<p>
<dir>
<strong>
./check_http --help
</strong>
</dir>
</p>

<p>
or
</p>

<p>
<dir>
<strong>
./check_http -h
</strong>
</dir>
</p>

<p>
<strong><u>Command Definition Examples For Services</u></strong>
</p>

<p>
It is important to note that command definitions found in sample config files in the core Nagios distribution are probably <i>not</i> accurate as to command line parameters, etc when it comes to the plugins.  They are simply provided as examples of how to define commands.
</p>

<a name="howto"></a>
<p>
<strong><u>Creating Custom Plugins</u></strong>
</p>

<p>
Creating your own plugins to perform custom host or service checks is easy.  You can find information on how to write plugins at <a href="http://sourceforge.net/projects/nagiosplug/">http://sourceforge.net/projects/nagiosplug/</a>.  The developer guidelines can be found at <a href="http://nagiosplug.sourceforge.net/developer-guidelines.html">http://nagiosplug.sourceforge.net/developer-guidelines.html</a>.
</p>

<hr>

</body>
</html>