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
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
Introduction/Notes
==================
This modules was inspired and based on the work of David Schmitt
The immerda project group adapted and improved this module.
Mainly we made it using the new native puppet nagios commands
as well we made it more modular to fit for multidistro usage.
In it's current form, this module can be used on CentOS and Debian.
Overview
========
To use the nagios resources, activate storeconfigs on the puppetmaster.
Monitor
-------
On one node the "nagios" class has to be included. By default this installs
apache using the "apache" module. To use lighttpd instead, include
"nagios::lighttpd", or, if the web server is not to be managed by puppet,
include "nagios::headless".
Hosts
-----
On a node which shall be monitored with nagios, include the "nagios::target".
This just creates a host declaration for this host's "$ipaddress" fact. If
the $ipaddress of your target is not the one you wish to modify, you can use
"nagios::target::fqdn" instead, which will use the $fqdn fact of the host instead.
Set the $nagios_parent variable in the node scope for enabling the reachability
features of nagios. If a node needs more customisation, use the
native "@@nagios_host" type directly (the double-ampersand declares the object
as an exported resource).
To monitor hosts not managed by puppet, add "nagios_host" objects to the
monitoring node. The required parameters are "alias", "address" and "use". If
you don't specify a proper nagios template with the "use" parameter, some extra
parameters are needed. You may look up the nagios documentation for this.
Services
--------
Services can be monitored by using the "nagios::service" component.
The simplest form is::
nagios::service { 'check_http':
check_command => 'http_port!80',
}
The intention being obviously to put such declarations into a component defining
a service, thereby being automatically applied together with all instances of
the service.
Obviously, the check command must either be defined using nagios_command objects
(some are supplied in nagios::defaults::commands) or in the nagios configuration
files directly.
Upgrade Notes
=============
The nagios::target bits have been reworked, the notable changes that
may affect an upgrade are:
. previous versions had nagios::target::nat which used the $fqdn for
the address part of nagios::target, this has been renamed to
nagios::target::fqdn to be more clear. if you were using
nagios::target::nat then you will need to change those references to
::fqdn
. previous versions of this module used $fqdn for the nagios::target
address, now it is using $ipaddress. If you need $fqdn, use
nagios::target::fqdn instead of nagios::target
. previous versions of nagios_host used the parameter named 'ip', that
has been changed to 'address'
Caveats
=======
Consistency/Validation/Verification
-----------------------------------
After convergance of the configuration, the system is obviously consistent.
That is, all defined services are monitored. The problem is though, that it is
neither automatically valid - it is not guaranteed that all components declare a
nagios::service - and even if the configuration is valid it definitly is
unverified, since that is always a judgment call for an external observer.
Removal of nagios objects
-------------------------
This module does not automatically purge nagios objects such as hosts and
services that become absent from the manifests. One must set ensure => absent
to guarantee the removal of nagios objects from the configuration as desired.
Templates not supported using native types
------------------------------------------
Templates of hosts and services cannot yet be defined using native types. In
this module, they are provided using a file resource by the class
nagios::defaults::templates
See : http://projects.reductivelabs.com/issues/1180
Variables
=========
Options to change the behavior of the nagios module:
- nagios_allow_external_cmd: Set to true, if you'd like to ensure that your http
daemon can write to the external command file. You
may also need to flip "check_external_commands" in
"nagios.cfg" to enable this functionality.
Examples
========
Usage example:
node nagios {
include nagios::apache
include nagios::defaults
# Declare another nagios command
nagios::command { http_port: command_line
=> '/usr/lib/nagios/plugins/check_http -p $ARG1$ -H $HOSTADDRESS$ -I
$HOSTADDRESS$'
# Declare unmanaged hosts
nagios_host {
'router01.mydomain.com':
alias => 'router01',
notes => 'MyDomain Gateway',
address => "10.0.0.1",
use => 'generic-host';
"router02.mydomain.com":
alias => 'router02',
address => '192.168.0.1',
parents => 'router01',
use => 'generic-host';
}
}
node target {
# Monitor this host
$nagios_parent = 'router01'
include nagios::target
# monitor a service
$apache2_port = 8080
include apache2
# This actually does this somewhere:
#nagios::service { "http_${apache2_port}":
# check_command => "http_port!${apache2_port}"
#}
}
TODO
====
- Provide a default http vhost
- Add facility to deploy nagios plugins
- Add more useful commands and services
- When Puppet will support them, supply nagios templates using native types
License
=======
Copyright (C) 2007 David Schmitt <david@schmitt.edv-bus.at>
See the file LICENSE in the top directory for the full license.
Copyright (C) 2010 Riseup Networks <micah@riseup.net>
|
