]>
Commit | Line | Data |
---|---|---|
e177e737 | 1 | # Man page created with: |
2 | # | |
3 | # pod2man -s 5 -r "`./check_openmanage -V | head -n 1`" -c 'Nagios plugin' check_openmanage.conf.pod check_openmanage.conf.5 | |
4 | # | |
5 | # $Id: check_openmanage.pod 20039 2011-04-26 09:56:56Z trondham $ | |
6 | ||
7 | =head1 NAME | |
8 | ||
763e1084 | 9 | F<check_openmanage.conf> - Configuration file for check_openmanage |
e177e737 | 10 | |
11 | =head1 FILE FORMAT | |
12 | ||
13 | The file has an ini-style syntax and consists of sections and | |
14 | parameters. A section begins with the name of the section in square | |
15 | brackets and continues until the next section begins. An example of | |
16 | section with two keywords and parameters: | |
17 | ||
763e1084 | 18 | =over 8 |
19 | ||
20 | I<[section]> | |
21 | I<key1> = I<boolean> | |
22 | I<key2> = I<string> | |
23 | ||
24 | =back | |
e177e737 | 25 | |
26 | The data types used are string (no quotes needed) and bool (with | |
27 | values of C<TRUE/FALSE>). For boolean values, C<1>, C<on> and C<true> | |
28 | are equivalent, likewise for C<0>, C<off> and C<false>. They are also | |
29 | case insensitive. | |
30 | ||
31 | The root section or global section has no section name in brackets, | |
32 | example: | |
33 | ||
763e1084 | 34 | key1 = false |
35 | key2 = foo | |
36 | ||
37 | [section] | |
38 | key1 = true | |
39 | key2 = bar | |
e177e737 | 40 | |
41 | The values set in a bracket section will override those set in the | |
42 | root section, in case of conflicts. | |
43 | ||
44 | Lines starting with C<#> or C<;> are considered comments and ignored, as | |
45 | are blank lines. | |
46 | ||
47 | The configuration file must be a regular file. Owner and group does | |
48 | not matter, but the Nagios user must have read access. | |
49 | ||
50 | =head1 SECTIONS AND ORDERING | |
51 | ||
52 | The section name should correspond to the hostname, i.e. the value | |
53 | passed to the C<-H> or C<--hostname> parameter. The section name | |
54 | itself can be either an exact match to the hostname, or a glob | |
55 | pattern, as this example shows: | |
56 | ||
763e1084 | 57 | key1 = true |
58 | key2 = foo | |
59 | ||
60 | [192.168.1.2] | |
61 | key1 = true | |
62 | ||
63 | [192.168.*] | |
64 | key1 = false | |
65 | key2 = bar | |
e177e737 | 66 | |
67 | The sections are read in order of significance. The root section is | |
68 | read first. Then any sections with glob patterns that match the | |
69 | hostname are read (alphabetically). Any section whose name is an exact | |
70 | match to the hostname is read last. | |
71 | ||
72 | For boolean values, any conflicts are resolved by letting the section | |
73 | with the most significance (closest match to the hostname) override | |
74 | any previous definitions. For string values, they are simply added | |
75 | together. | |
76 | ||
763e1084 | 77 | In the example above, for the host C<192.168.1.2> the value of I<key1> |
78 | will be I<true> and I<key2> will be I<bar>. Any other host that | |
79 | matches C<192.168.*> will have I<key1 = false> and I<key2 = bar>. All | |
80 | other hosts will have I<key1 = true> and I<key2 = foo>. | |
81 | ||
82 | Normal shell globbing may be used for the section names. This is | |
83 | limited to C<*>, C<?> and C<[]>. Some examples: | |
84 | ||
85 | [192.168.*] | |
86 | # matches e.g. 192.168.10.20 | |
87 | ||
88 | [192.168.10[34].1] | |
89 | # matches 192.168.103.1 and 192.168.104.1 | |
90 | ||
91 | [login?.example.com] | |
92 | # mathces e.g. login1.example.com | |
93 | ||
94 | CAUTION! Be careful not to have more than one glob pattern section | |
95 | match any single host. This may lead to unpredictable results. | |
e177e737 | 96 | |
97 | =head1 CONFIGURATION | |
98 | ||
763e1084 | 99 | =head2 General |
100 | ||
aae8f5be | 101 | =over 4 |
e177e737 | 102 | |
aae8f5be | 103 | =item Check control |
e177e737 | 104 | |
105 | Any keyword to the C<--check> parameter are accepted in the | |
763e1084 | 106 | configuration file, as C<check_I<KEYWORD>>. These options take boolean |
e177e737 | 107 | values (C<true> or C<false>). The following keywords are accepted for |
108 | check control, listed here with their default values: | |
109 | ||
763e1084 | 110 | check_storage = true |
111 | check_memory = true | |
112 | check_fans = true | |
113 | check_power = true | |
114 | check_temp = true | |
115 | check_cpu = true | |
116 | check_voltage = true | |
117 | check_batteries = true | |
118 | check_amperage = true | |
119 | check_intrusion = true | |
120 | check_sdcard = true | |
121 | check_esmhealth = true | |
122 | check_esmlog = false | |
123 | check_alertlog = false | |
124 | check_everything = false | |
125 | ||
126 | If used together with the C<--check> command line option, the command | |
127 | line option will override the configuration file, if there is a | |
e177e737 | 128 | conflict. |
129 | ||
763e1084 | 130 | The option C<check_everything> is special and turns on all |
131 | checks. Setting this option to "true" will effectively negate any | |
132 | other check options. This option corresponds to the C<-a> or C<--all> | |
133 | command line option. | |
134 | ||
135 | For more information about check control, see | |
136 | L<check_openmanage(8)/CHECK CONTROL>. | |
137 | ||
aae8f5be | 138 | =item Blacklisting |
e177e737 | 139 | |
140 | For blacklisting the keyword C<blacklist> is used, and the value is a | |
141 | string that uses the same syntax as the C<-b> or C<--blacklist> | |
142 | parameter. Example: | |
143 | ||
144 | blacklist = ctrl_fw=all/pdisk=0:0:1 | |
145 | ||
763e1084 | 146 | If used together with the C<-b> or C<--blacklist> command line option, |
147 | the two blacklists from the config file and command line are added | |
148 | together. | |
149 | ||
150 | For more information about blacklisting, including syntax, see | |
151 | L<check_openmanage(8)/BLACKLISTING>. | |
152 | ||
153 | =item Timeout | |
154 | ||
155 | The plugin timeout can be configured with the C<timeout> keyword. The | |
156 | argument is number of seconds and should be a positive | |
157 | integer. Example: | |
158 | ||
159 | timeout = 60 | |
160 | ||
161 | If used together with the command line option C<-t> or C<--timeout>, | |
162 | the command line option takes precedence. | |
e177e737 | 163 | |
c8323c71 | 164 | =item Performance data |
165 | ||
166 | Performance data can be turned on in the configuration file with | |
167 | C<performance_data>. Accepted values are boolean (TRUE/FALSE) or | |
168 | either of the keywords "minimal" and "multiline". Example: | |
169 | ||
170 | performance_data = true | |
171 | ||
172 | The corresponding command line option is C<-p> or <--perfdata>. | |
173 | ||
e177e737 | 174 | =back |
175 | ||
763e1084 | 176 | =head2 SNMP Options |
177 | ||
178 | Several SNMP related options may be set in the configuration file. For | |
179 | each of these, if used together with the corresponding command line | |
180 | option, the latter takes presedence and overrules the option set in | |
181 | the configuration file. The configuration file may contain the | |
182 | following SNMP options: | |
183 | ||
184 | =over 4 | |
185 | ||
186 | =item SNMP community string | |
187 | ||
188 | The SNMP community string can be set with C<snmp_community>. Example: | |
189 | ||
190 | snmp_community = mycommunity | |
191 | ||
192 | Corresponding command line option: C<-C> or C<--community> | |
193 | ||
194 | =item SNMP protocol version | |
195 | ||
196 | The SNMP protocol version can be set with C<snmp_version>. Example: | |
197 | ||
198 | snmp_version = 2 | |
199 | ||
200 | Corresponding command line option: C<-P> or C<--protocol> | |
201 | ||
202 | =item SNMP port number | |
203 | ||
204 | The remote port number used with SNMP can be set with | |
205 | C<snmp_port>. Example: | |
206 | ||
207 | snmp_port = 161 | |
208 | ||
209 | Corresponding command line option: C<--port> | |
210 | ||
211 | =item Use IPv6 instead of IPv4 | |
212 | ||
213 | The option C<snmp_use_ipv6> instructs the plugin to use IPv6 instead | |
214 | of IPv4. This option takes a boolean value. Example: | |
215 | ||
216 | snmp_use_ipv6 = true | |
217 | ||
218 | Corresponding command line option: C<-6> or C<--ipv6> | |
219 | ||
220 | =item Use TCP instead of UDP | |
221 | ||
222 | The option C<snmp_use_ipv6> instructs the plugin to use IPv6 instead | |
223 | of IPv4. This option takes a boolean value. Example: | |
224 | ||
225 | snmp_use_tcp = true | |
226 | ||
227 | Corresponding command line option: C<--tcp> | |
228 | ||
229 | =back | |
230 | ||
231 | =head2 Output control | |
232 | ||
233 | These options all corresponds to command line options. If the | |
234 | configuration file option and the corresponding command line option is | |
235 | used simultaneously, the command line option takes precedence. | |
236 | ||
237 | =over 4 | |
238 | ||
239 | =item Include servicetag in alerts | |
240 | ||
241 | The option C<output_servicetag> will make the plugin include the | |
242 | servers servicetag (serial number) in every alert. This option takes a | |
243 | boolean value. Example: | |
244 | ||
245 | output_servicetag = true | |
246 | ||
247 | Corresponding command line option: C<-i> or C<--info> | |
248 | ||
249 | =item Include service state in alerts | |
250 | ||
251 | The option C<output_servicestate> will make the plugin include the | |
252 | service state in any alerts. This option takes a boolean | |
253 | value. Example: | |
254 | ||
255 | output_servicestate = true | |
256 | ||
257 | Corresponding command line option: C<-s> or C<--state> | |
258 | ||
259 | =item Include abbreviated service state in alerts | |
260 | ||
261 | The option C<output_servicestate_abbr> will make the plugin include | |
262 | the abbreviated service state in any alerts. This option takes a | |
263 | boolean value. Example: | |
264 | ||
265 | output_servicestate_abbr = true | |
266 | ||
267 | Corresponding command line option: C<-S> or C<--short-state> | |
268 | ||
269 | =item Show system info with alerts | |
270 | ||
271 | The option C<output_sysinfo> will make the plugin output some system | |
272 | information with alerts. This option takes a boolean value. Example: | |
273 | ||
274 | output_sysinfo = true | |
275 | ||
276 | Corresponding command line option: C<-e> or C<--extinfo> | |
277 | ||
278 | =item Show blacklistings in OK output | |
279 | ||
280 | The option C<output_blacklist> will make the plugin show any | |
281 | blacklistings in the OK output. This option takes a boolean | |
282 | value. Example: | |
283 | ||
284 | output_blacklist = true | |
285 | ||
286 | Corresponding command line option: C<-B> or C<--show-blacklist> | |
287 | ||
288 | =item Verbosity of OK output | |
289 | ||
290 | The option C<output_ok_verbosity> lets you adjust how much information | |
291 | is shown in the OK output. This option takes a positive integer as | |
292 | parameter. Example: | |
293 | ||
294 | output_ok_verbosity = 3 | |
295 | ||
296 | Corresponding command line option: C<-o> or C<--ok-info> | |
297 | ||
298 | =item HTML output | |
299 | ||
300 | The output C<output_html> makes the plugin produce HTML output. This | |
301 | option takes either a boolean value, or a country or area | |
302 | code. Example: | |
303 | ||
304 | output_html = de | |
305 | ||
306 | Corresponding command line option: C<-I> or C<--htmlinfo> | |
307 | ||
308 | =back | |
309 | ||
310 | =head2 Temperature limits | |
311 | ||
312 | Custom temperature limits may be configured with the options | |
313 | C<temp_threshold_warning> and C<temp_threshold_critical>. These | |
314 | options corresponds to the command line options C<-w> or C<--warning> | |
315 | and C<-c> or C<--critical>, respectively. They take the same arguments | |
316 | as the command line options. Example: | |
317 | ||
318 | temp_threshold_warning = 0=30/10 | |
319 | temp_threshold_critical = 0=35/8 | |
320 | ||
321 | The command line options take precedence over the configuration file | |
322 | options, if used simultaneously. | |
323 | ||
e177e737 | 324 | =head1 SEE ALSO |
325 | ||
03f30077 | 326 | L<check_openmanage(8)> |
e177e737 | 327 | L<http://folk.uio.no/trondham/software/check_openmanage.html> |
328 | ||
329 | =cut |