]>
Commit | Line | Data |
---|---|---|
b6230b30 ER |
1 | ############################################################################## |
2 | # | |
3 | # NAGIOS.CFG - Sample Main Config File for Nagios | |
4 | # | |
5 | # Read the documentation for more information on this configuration | |
6 | # file. I've provided some comments here, but things may not be so | |
7 | # clear without further explanation. | |
8 | # | |
cff08d9a | 9 | # $Id: $ |
b6230b30 ER |
10 | # |
11 | ############################################################################## | |
12 | ||
13 | ||
14 | # LOG FILE | |
15 | # This is the main log file where service and host events are logged | |
16 | # for historical purposes. This should be the first option specified | |
17 | # in the config file!!! | |
18 | ||
19 | log_file=/var/log/nagios/nagios.log | |
20 | ||
21 | ||
22 | ||
23 | # OBJECT CONFIGURATION FILE(S) | |
24 | # This is the configuration file in which you define hosts, host | |
25 | # groups, contacts, contact groups, services, etc. I guess it would | |
26 | # be better called an object definition file, but for historical | |
27 | # reasons it isn't. You can split object definitions into several | |
28 | # different config files by using multiple cfg_file statements here. | |
29 | # Nagios will read and process all the config files you define. | |
30 | # This can be very useful if you want to keep command definitions | |
31 | # separate from host and contact definitions... | |
32 | ||
33 | # Plugin commands (service and host check commands) | |
34 | # Arguments are likely to change between different releases of the | |
35 | # plugins, so you should use the same config file provided with the | |
36 | # plugin release rather than the one provided with Nagios. | |
37 | cfg_file=/etc/nagios/checkcommands.cfg | |
38 | ||
39 | # Misc commands (notification and event handler commands, etc) | |
40 | cfg_file=/etc/nagios/misccommands.cfg | |
41 | ||
42 | # You can split other types of object definitions across several | |
43 | # config files if you wish (as done here), or keep them all in a | |
44 | # single config file. | |
45 | ||
46 | #cfg_file=/etc/nagios/minimal.cfg | |
47 | ||
48 | cfg_file=/etc/nagios/contactgroups.cfg | |
49 | cfg_file=/etc/nagios/contacts.cfg | |
50 | cfg_file=/etc/nagios/dependencies.cfg | |
51 | cfg_file=/etc/nagios/escalations.cfg | |
52 | cfg_file=/etc/nagios/hostgroups.cfg | |
53 | cfg_file=/etc/nagios/hosts.cfg | |
54 | cfg_file=/etc/nagios/services.cfg | |
55 | cfg_file=/etc/nagios/timeperiods.cfg | |
56 | ||
57 | # Extended host/service info definitions are now stored along with | |
58 | # other object definitions: | |
59 | cfg_file=/etc/nagios/hostextinfo.cfg | |
60 | cfg_file=/etc/nagios/serviceextinfo.cfg | |
61 | ||
62 | # You can also tell Nagios to process all config files (with a .cfg | |
63 | # extension) in a particular directory by using the cfg_dir | |
64 | # directive as shown below: | |
65 | ||
66 | #cfg_dir=/etc/nagios/servers | |
67 | #cfg_dir=/etc/nagios/printers | |
68 | #cfg_dir=/etc/nagios/switches | |
69 | #cfg_dir=/etc/nagios/routers | |
70 | ||
71 | ||
72 | ||
73 | # OBJECT CACHE FILE | |
74 | # This option determines where object definitions are cached when | |
75 | # Nagios starts/restarts. The CGIs read object definitions from | |
76 | # this cache file (rather than looking at the object config files | |
77 | # directly) in order to prevent inconsistencies that can occur | |
78 | # when the config files are modified after Nagios starts. | |
79 | ||
80 | object_cache_file=/var/lib/nagios/objects.cache | |
81 | ||
82 | ||
83 | ||
84 | # RESOURCE FILE | |
85 | # This is an optional resource file that contains $USERx$ macro | |
86 | # definitions. Multiple resource files can be specified by using | |
87 | # multiple resource_file definitions. The CGIs will not attempt to | |
88 | # read the contents of resource files, so information that is | |
89 | # considered to be sensitive (usernames, passwords, etc) can be | |
90 | # defined as macros in this file and restrictive permissions (600) | |
91 | # can be placed on this file. | |
92 | ||
93 | resource_file=/etc/nagios/resource.cfg | |
94 | ||
95 | ||
96 | ||
97 | # STATUS FILE | |
98 | # This is where the current status of all monitored services and | |
99 | # hosts is stored. Its contents are read and processed by the CGIs. | |
100 | # The contentsof the status file are deleted every time Nagios | |
101 | # restarts. | |
102 | ||
103 | status_file=/var/lib/nagios/status.dat | |
104 | ||
105 | ||
106 | ||
107 | # NAGIOS USER | |
108 | # This determines the effective user that Nagios should run as. | |
109 | # You can either supply a username or a UID. | |
110 | ||
111 | nagios_user=nagios | |
112 | ||
113 | ||
114 | ||
115 | # NAGIOS GROUP | |
116 | # This determines the effective group that Nagios should run as. | |
117 | # You can either supply a group name or a GID. | |
118 | ||
119 | nagios_group=nagios | |
120 | ||
121 | ||
122 | ||
123 | # EXTERNAL COMMAND OPTION | |
124 | # This option allows you to specify whether or not Nagios should check | |
125 | # for external commands (in the command file defined below). By default | |
126 | # Nagios will *not* check for external commands, just to be on the | |
127 | # cautious side. If you want to be able to use the CGI command interface | |
128 | # you will have to enable this. Setting this value to 0 disables command | |
129 | # checking (the default), other values enable it. | |
130 | ||
131 | check_external_commands=1 | |
132 | ||
133 | ||
134 | ||
135 | # EXTERNAL COMMAND CHECK INTERVAL | |
136 | # This is the interval at which Nagios should check for external commands. | |
137 | # This value works of the interval_length you specify later. If you leave | |
138 | # that at its default value of 60 (seconds), a value of 1 here will cause | |
139 | # Nagios to check for external commands every minute. If you specify a | |
140 | # number followed by an "s" (i.e. 15s), this will be interpreted to mean | |
141 | # actual seconds rather than a multiple of the interval_length variable. | |
142 | # Note: In addition to reading the external command file at regularly | |
143 | # scheduled intervals, Nagios will also check for external commands after | |
144 | # event handlers are executed. | |
145 | # NOTE: Setting this value to -1 causes Nagios to check the external | |
146 | # command file as often as possible. | |
147 | ||
148 | #command_check_interval=1 | |
149 | #command_check_interval=15s | |
150 | command_check_interval=-1 | |
151 | ||
152 | ||
153 | ||
154 | # EXTERNAL COMMAND FILE | |
155 | # This is the file that Nagios checks for external command requests. | |
156 | # It is also where the command CGI will write commands that are submitted | |
157 | # by users, so it must be writeable by the user that the web server | |
158 | # is running as (usually 'nobody'). Permissions should be set at the | |
159 | # directory level instead of on the file, as the file is deleted every | |
160 | # time its contents are processed. | |
161 | ||
162 | command_file=/var/lib/nagios/rw/nagios.cmd | |
163 | ||
164 | ||
165 | ||
166 | # COMMENT FILE | |
167 | # This is the file that Nagios will use for storing host and service | |
168 | # comments. | |
169 | ||
170 | comment_file=/var/lib/nagios/comments.dat | |
171 | ||
172 | ||
173 | ||
174 | # DOWNTIME FILE | |
175 | # This is the file that Nagios will use for storing host and service | |
176 | # downtime data. | |
177 | ||
178 | downtime_file=/var/lib/nagios/downtime.dat | |
179 | ||
180 | ||
181 | ||
182 | # LOCK FILE | |
183 | # This is the lockfile that Nagios will use to store its PID number | |
184 | # in when it is running in daemon mode. | |
185 | ||
186 | lock_file=/var/lib/nagios/nagios.pid | |
187 | ||
188 | ||
189 | ||
190 | # TEMP FILE | |
191 | # This is a temporary file that is used as scratch space when Nagios | |
192 | # updates the status log, cleans the comment file, etc. This file | |
193 | # is created, used, and deleted throughout the time that Nagios is | |
194 | # running. | |
195 | ||
196 | temp_file=/var/lib/nagios/nagios.tmp | |
197 | ||
198 | ||
199 | ||
200 | # EVENT BROKER OPTIONS | |
201 | # Controls what (if any) data gets sent to the event broker. | |
202 | # Values: 0 = Broker nothing | |
203 | # -1 = Broker everything | |
204 | # <other> = See documentation | |
205 | ||
206 | event_broker_options=-1 | |
207 | ||
208 | ||
209 | ||
210 | # EVENT BROKER MODULE(S) | |
211 | # This directive is used to specify an event broker module that should | |
212 | # by loaded by Nagios at startup. Use multiple directives if you want | |
213 | # to load more than one module. Arguments that should be passed to | |
214 | # the module at startup are seperated from the module path by a space. | |
215 | # | |
216 | # Example: | |
217 | # | |
218 | # nebmodule=<modulepath> [moduleargs] | |
219 | ||
220 | #broker_module=/somewhere/module1.o | |
221 | #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0 | |
222 | ||
223 | ||
224 | ||
225 | ||
226 | # LOG ROTATION METHOD | |
227 | # This is the log rotation method that Nagios should use to rotate | |
228 | # the main log file. Values are as follows.. | |
229 | # n = None - don't rotate the log | |
230 | # h = Hourly rotation (top of the hour) | |
231 | # d = Daily rotation (midnight every day) | |
232 | # w = Weekly rotation (midnight on Saturday evening) | |
233 | # m = Monthly rotation (midnight last day of month) | |
234 | ||
235 | log_rotation_method=d | |
236 | ||
237 | ||
238 | ||
239 | # LOG ARCHIVE PATH | |
240 | # This is the directory where archived (rotated) log files should be | |
241 | # placed (assuming you've chosen to do log rotation). | |
242 | ||
243 | log_archive_path=/var/log/nagios/archives | |
244 | ||
245 | ||
246 | ||
247 | # LOGGING OPTIONS | |
248 | # If you want messages logged to the syslog facility, as well as the | |
249 | # NetAlarm log file set this option to 1. If not, set it to 0. | |
250 | ||
251 | use_syslog=1 | |
252 | ||
253 | ||
254 | ||
255 | # NOTIFICATION LOGGING OPTION | |
256 | # If you don't want notifications to be logged, set this value to 0. | |
257 | # If notifications should be logged, set the value to 1. | |
258 | ||
259 | log_notifications=1 | |
260 | ||
261 | ||
262 | ||
263 | # SERVICE RETRY LOGGING OPTION | |
264 | # If you don't want service check retries to be logged, set this value | |
265 | # to 0. If retries should be logged, set the value to 1. | |
266 | ||
267 | log_service_retries=1 | |
268 | ||
269 | ||
270 | ||
271 | # HOST RETRY LOGGING OPTION | |
272 | # If you don't want host check retries to be logged, set this value to | |
273 | # 0. If retries should be logged, set the value to 1. | |
274 | ||
275 | log_host_retries=1 | |
276 | ||
277 | ||
278 | ||
279 | # EVENT HANDLER LOGGING OPTION | |
280 | # If you don't want host and service event handlers to be logged, set | |
281 | # this value to 0. If event handlers should be logged, set the value | |
282 | # to 1. | |
283 | ||
284 | log_event_handlers=1 | |
285 | ||
286 | ||
287 | ||
288 | # INITIAL STATES LOGGING OPTION | |
289 | # If you want Nagios to log all initial host and service states to | |
290 | # the main log file (the first time the service or host is checked) | |
291 | # you can enable this option by setting this value to 1. If you | |
292 | # are not using an external application that does long term state | |
293 | # statistics reporting, you do not need to enable this option. In | |
294 | # this case, set the value to 0. | |
295 | ||
296 | log_initial_states=0 | |
297 | ||
298 | ||
299 | ||
300 | # EXTERNAL COMMANDS LOGGING OPTION | |
301 | # If you don't want Nagios to log external commands, set this value | |
302 | # to 0. If external commands should be logged, set this value to 1. | |
303 | # Note: This option does not include logging of passive service | |
304 | # checks - see the option below for controlling whether or not | |
305 | # passive checks are logged. | |
306 | ||
307 | log_external_commands=1 | |
308 | ||
309 | ||
310 | ||
311 | # PASSIVE CHECKS LOGGING OPTION | |
312 | # If you don't want Nagios to log passive host and service checks, set | |
313 | # this value to 0. If passive service checks should be logged, set | |
314 | # this value to 1. | |
315 | ||
316 | log_passive_checks=1 | |
317 | ||
318 | ||
319 | ||
320 | # GLOBAL HOST AND SERVICE EVENT HANDLERS | |
321 | # These options allow you to specify a host and service event handler | |
322 | # command that is to be run for every host or service state change. | |
323 | # The global event handler is executed immediately prior to the event | |
324 | # handler that you have optionally specified in each host or | |
325 | # service definition. The command argument is the short name of a | |
326 | # command definition that you define in your host configuration file. | |
327 | # Read the HTML docs for more information. | |
328 | ||
329 | #global_host_event_handler=somecommand | |
330 | #global_service_event_handler=somecommand | |
331 | ||
332 | ||
333 | ||
334 | # SERVICE INTER-CHECK DELAY METHOD | |
335 | # This is the method that Nagios should use when initially | |
336 | # "spreading out" service checks when it starts monitoring. The | |
337 | # default is to use smart delay calculation, which will try to | |
338 | # space all service checks out evenly to minimize CPU load. | |
339 | # Using the dumb setting will cause all checks to be scheduled | |
340 | # at the same time (with no delay between them)! This is not a | |
341 | # good thing for production, but is useful when testing the | |
342 | # parallelization functionality. | |
343 | # n = None - don't use any delay between checks | |
344 | # d = Use a "dumb" delay of 1 second between checks | |
345 | # s = Use "smart" inter-check delay calculation | |
346 | # x.xx = Use an inter-check delay of x.xx seconds | |
347 | ||
348 | service_inter_check_delay_method=s | |
349 | ||
350 | ||
351 | ||
352 | # MAXIMUM SERVICE CHECK SPREAD | |
353 | # This variable determines the timeframe (in minutes) from the | |
354 | # program start time that an initial check of all services should | |
355 | # be completed. Default is 30 minutes. | |
356 | ||
357 | max_service_check_spread=30 | |
358 | ||
359 | ||
360 | ||
361 | # SERVICE CHECK INTERLEAVE FACTOR | |
362 | # This variable determines how service checks are interleaved. | |
363 | # Interleaving the service checks allows for a more even | |
364 | # distribution of service checks and reduced load on remote | |
365 | # hosts. Setting this value to 1 is equivalent to how versions | |
366 | # of Nagios previous to 0.0.5 did service checks. Set this | |
367 | # value to s (smart) for automatic calculation of the interleave | |
368 | # factor unless you have a specific reason to change it. | |
369 | # s = Use "smart" interleave factor calculation | |
370 | # x = Use an interleave factor of x, where x is a | |
371 | # number greater than or equal to 1. | |
372 | ||
373 | service_interleave_factor=s | |
374 | ||
375 | ||
376 | ||
377 | # HOST INTER-CHECK DELAY METHOD | |
378 | # This is the method that Nagios should use when initially | |
379 | # "spreading out" host checks when it starts monitoring. The | |
380 | # default is to use smart delay calculation, which will try to | |
381 | # space all host checks out evenly to minimize CPU load. | |
382 | # Using the dumb setting will cause all checks to be scheduled | |
383 | # at the same time (with no delay between them)! | |
384 | # n = None - don't use any delay between checks | |
385 | # d = Use a "dumb" delay of 1 second between checks | |
386 | # s = Use "smart" inter-check delay calculation | |
387 | # x.xx = Use an inter-check delay of x.xx seconds | |
388 | ||
389 | host_inter_check_delay_method=s | |
390 | ||
391 | ||
392 | ||
393 | # MAXIMUM HOST CHECK SPREAD | |
394 | # This variable determines the timeframe (in minutes) from the | |
395 | # program start time that an initial check of all hosts should | |
396 | # be completed. Default is 30 minutes. | |
397 | ||
398 | max_host_check_spread=30 | |
399 | ||
400 | ||
401 | ||
402 | # MAXIMUM CONCURRENT SERVICE CHECKS | |
403 | # This option allows you to specify the maximum number of | |
404 | # service checks that can be run in parallel at any given time. | |
405 | # Specifying a value of 1 for this variable essentially prevents | |
406 | # any service checks from being parallelized. A value of 0 | |
407 | # will not restrict the number of concurrent checks that are | |
408 | # being executed. | |
409 | ||
410 | max_concurrent_checks=0 | |
411 | ||
412 | ||
413 | ||
414 | # SERVICE CHECK REAPER FREQUENCY | |
415 | # This is the frequency (in seconds!) that Nagios will process | |
416 | # the results of services that have been checked. | |
417 | ||
418 | service_reaper_frequency=10 | |
419 | ||
420 | ||
421 | ||
422 | ||
423 | # AUTO-RESCHEDULING OPTION | |
424 | # This option determines whether or not Nagios will attempt to | |
425 | # automatically reschedule active host and service checks to | |
426 | # "smooth" them out over time. This can help balance the load on | |
427 | # the monitoring server. | |
428 | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | |
429 | # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY | |
430 | ||
431 | auto_reschedule_checks=0 | |
432 | ||
433 | ||
434 | ||
435 | # AUTO-RESCHEDULING INTERVAL | |
436 | # This option determines how often (in seconds) Nagios will | |
437 | # attempt to automatically reschedule checks. This option only | |
438 | # has an effect if the auto_reschedule_checks option is enabled. | |
439 | # Default is 30 seconds. | |
440 | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | |
441 | # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY | |
442 | ||
443 | auto_rescheduling_interval=30 | |
444 | ||
445 | ||
446 | ||
447 | ||
448 | # AUTO-RESCHEDULING WINDOW | |
449 | # This option determines the "window" of time (in seconds) that | |
450 | # Nagios will look at when automatically rescheduling checks. | |
451 | # Only host and service checks that occur in the next X seconds | |
452 | # (determined by this variable) will be rescheduled. This option | |
453 | # only has an effect if the auto_reschedule_checks option is | |
454 | # enabled. Default is 180 seconds (3 minutes). | |
455 | # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE | |
456 | # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY | |
457 | ||
458 | auto_rescheduling_window=180 | |
459 | ||
460 | ||
461 | ||
462 | # SLEEP TIME | |
463 | # This is the number of seconds to sleep between checking for system | |
464 | # events and service checks that need to be run. | |
465 | ||
466 | sleep_time=0.25 | |
467 | ||
468 | ||
469 | ||
470 | # TIMEOUT VALUES | |
471 | # These options control how much time Nagios will allow various | |
472 | # types of commands to execute before killing them off. Options | |
473 | # are available for controlling maximum time allotted for | |
474 | # service checks, host checks, event handlers, notifications, the | |
475 | # ocsp command, and performance data commands. All values are in | |
476 | # seconds. | |
477 | ||
478 | service_check_timeout=60 | |
479 | host_check_timeout=30 | |
480 | event_handler_timeout=30 | |
481 | notification_timeout=30 | |
482 | ocsp_timeout=5 | |
483 | perfdata_timeout=5 | |
484 | ||
485 | ||
486 | ||
487 | # RETAIN STATE INFORMATION | |
488 | # This setting determines whether or not Nagios will save state | |
489 | # information for services and hosts before it shuts down. Upon | |
490 | # startup Nagios will reload all saved service and host state | |
491 | # information before starting to monitor. This is useful for | |
492 | # maintaining long-term data on state statistics, etc, but will | |
493 | # slow Nagios down a bit when it (re)starts. Since its only | |
494 | # a one-time penalty, I think its well worth the additional | |
495 | # startup delay. | |
496 | ||
497 | retain_state_information=1 | |
498 | ||
499 | ||
500 | ||
501 | # STATE RETENTION FILE | |
502 | # This is the file that Nagios should use to store host and | |
503 | # service state information before it shuts down. The state | |
504 | # information in this file is also read immediately prior to | |
505 | # starting to monitor the network when Nagios is restarted. | |
506 | # This file is used only if the preserve_state_information | |
507 | # variable is set to 1. | |
508 | ||
509 | state_retention_file=/var/lib/nagios/retention.dat | |
510 | ||
511 | ||
512 | ||
513 | # RETENTION DATA UPDATE INTERVAL | |
514 | # This setting determines how often (in minutes) that Nagios | |
515 | # will automatically save retention data during normal operation. | |
516 | # If you set this value to 0, Nagios will not save retention | |
517 | # data at regular interval, but it will still save retention | |
518 | # data before shutting down or restarting. If you have disabled | |
519 | # state retention, this option has no effect. | |
520 | ||
521 | retention_update_interval=60 | |
522 | ||
523 | ||
524 | ||
525 | # USE RETAINED PROGRAM STATE | |
526 | # This setting determines whether or not Nagios will set | |
527 | # program status variables based on the values saved in the | |
528 | # retention file. If you want to use retained program status | |
529 | # information, set this value to 1. If not, set this value | |
530 | # to 0. | |
531 | ||
532 | use_retained_program_state=1 | |
533 | ||
534 | ||
535 | ||
536 | # USE RETAINED SCHEDULING INFO | |
537 | # This setting determines whether or not Nagios will retain | |
538 | # the scheduling info (next check time) for hosts and services | |
539 | # based on the values saved in the retention file. If you | |
540 | # If you want to use retained scheduling info, set this | |
541 | # value to 1. If not, set this value to 0. | |
542 | ||
543 | use_retained_scheduling_info=0 | |
544 | ||
545 | ||
546 | ||
547 | # INTERVAL LENGTH | |
548 | # This is the seconds per unit interval as used in the | |
549 | # host/contact/service configuration files. Setting this to 60 means | |
550 | # that each interval is one minute long (60 seconds). Other settings | |
551 | # have not been tested much, so your mileage is likely to vary... | |
552 | ||
553 | interval_length=60 | |
554 | ||
555 | ||
556 | ||
557 | # AGGRESSIVE HOST CHECKING OPTION | |
558 | # If you don't want to turn on aggressive host checking features, set | |
559 | # this value to 0 (the default). Otherwise set this value to 1 to | |
560 | # enable the aggressive check option. Read the docs for more info | |
561 | # on what aggressive host check is or check out the source code in | |
562 | # base/checks.c | |
563 | ||
564 | use_aggressive_host_checking=0 | |
565 | ||
566 | ||
567 | ||
568 | # SERVICE CHECK EXECUTION OPTION | |
569 | # This determines whether or not Nagios will actively execute | |
570 | # service checks when it initially starts. If this option is | |
571 | # disabled, checks are not actively made, but Nagios can still | |
572 | # receive and process passive check results that come in. Unless | |
573 | # you're implementing redundant hosts or have a special need for | |
574 | # disabling the execution of service checks, leave this enabled! | |
575 | # Values: 1 = enable checks, 0 = disable checks | |
576 | ||
577 | execute_service_checks=1 | |
578 | ||
579 | ||
580 | ||
581 | # PASSIVE SERVICE CHECK ACCEPTANCE OPTION | |
582 | # This determines whether or not Nagios will accept passive | |
583 | # service checks results when it initially (re)starts. | |
584 | # Values: 1 = accept passive checks, 0 = reject passive checks | |
585 | ||
586 | accept_passive_service_checks=1 | |
587 | ||
588 | ||
589 | ||
590 | # HOST CHECK EXECUTION OPTION | |
591 | # This determines whether or not Nagios will actively execute | |
592 | # host checks when it initially starts. If this option is | |
593 | # disabled, checks are not actively made, but Nagios can still | |
594 | # receive and process passive check results that come in. Unless | |
595 | # you're implementing redundant hosts or have a special need for | |
596 | # disabling the execution of host checks, leave this enabled! | |
597 | # Values: 1 = enable checks, 0 = disable checks | |
598 | ||
599 | execute_host_checks=1 | |
600 | ||
601 | ||
602 | ||
603 | # PASSIVE HOST CHECK ACCEPTANCE OPTION | |
604 | # This determines whether or not Nagios will accept passive | |
605 | # host checks results when it initially (re)starts. | |
606 | # Values: 1 = accept passive checks, 0 = reject passive checks | |
607 | ||
608 | accept_passive_host_checks=1 | |
609 | ||
610 | ||
611 | ||
612 | # NOTIFICATIONS OPTION | |
613 | # This determines whether or not Nagios will sent out any host or | |
614 | # service notifications when it is initially (re)started. | |
615 | # Values: 1 = enable notifications, 0 = disable notifications | |
616 | ||
617 | enable_notifications=1 | |
618 | ||
619 | ||
620 | ||
621 | # EVENT HANDLER USE OPTION | |
622 | # This determines whether or not Nagios will run any host or | |
623 | # service event handlers when it is initially (re)started. Unless | |
624 | # you're implementing redundant hosts, leave this option enabled. | |
625 | # Values: 1 = enable event handlers, 0 = disable event handlers | |
626 | ||
627 | enable_event_handlers=1 | |
628 | ||
629 | ||
630 | ||
631 | # PROCESS PERFORMANCE DATA OPTION | |
632 | # This determines whether or not Nagios will process performance | |
633 | # data returned from service and host checks. If this option is | |
634 | # enabled, host performance data will be processed using the | |
635 | # host_perfdata_command (defined below) and service performance | |
636 | # data will be processed using the service_perfdata_command (also | |
637 | # defined below). Read the HTML docs for more information on | |
638 | # performance data. | |
639 | # Values: 1 = process performance data, 0 = do not process performance data | |
640 | ||
641 | process_performance_data=0 | |
642 | ||
643 | ||
644 | ||
645 | # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS | |
646 | # These commands are run after every host and service check is | |
647 | # performed. These commands are executed only if the | |
648 | # enable_performance_data option (above) is set to 1. The command | |
649 | # argument is the short name of a command definition that you | |
650 | # define in your host configuration file. Read the HTML docs for | |
651 | # more information on performance data. | |
652 | ||
653 | #host_perfdata_command=process-host-perfdata | |
654 | #service_perfdata_command=process-service-perfdata | |
655 | ||
656 | ||
657 | ||
658 | # HOST AND SERVICE PERFORMANCE DATA FILES | |
659 | # These files are used to store host and service performance data. | |
660 | # Performance data is only written to these files if the | |
661 | # enable_performance_data option (above) is set to 1. | |
662 | ||
663 | #host_perfdata_file=/tmp/host-perfdata | |
664 | #service_perfdata_file=/tmp/service-perfdata | |
665 | ||
666 | ||
667 | ||
668 | # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES | |
669 | # These options determine what data is written (and how) to the | |
670 | # performance data files. The templates may contain macros, special | |
671 | # characters (\t for tab, \r for carriage return, \n for newline) | |
672 | # and plain text. A newline is automatically added after each write | |
673 | # to the performance data file. Some examples of what you can do are | |
674 | # shown below. | |
675 | ||
676 | #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$ | |
677 | #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$ | |
678 | ||
679 | ||
680 | ||
681 | ||
682 | # HOST AND SERVICE PERFORMANCE DATA FILE MODES | |
683 | # This option determines whether or not the host and service | |
684 | # performance data files are opened in write ("w") or append ("a") | |
685 | # mode. Unless you are the files are named pipes, you will probably | |
686 | # want to use the default mode of append ("a"). | |
687 | ||
688 | #host_perfdata_file_mode=a | |
689 | #service_perfdata_file_mode=a | |
690 | ||
691 | ||
692 | ||
693 | # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL | |
694 | # These options determine how often (in seconds) the host and service | |
695 | # performance data files are processed using the commands defined | |
696 | # below. A value of 0 indicates the files should not be periodically | |
697 | # processed. | |
698 | ||
699 | #host_perfdata_file_processing_interval=0 | |
700 | #service_perfdata_file_processing_interval=0 | |
701 | ||
702 | ||
703 | ||
704 | # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS | |
705 | # These commands are used to periodically process the host and | |
706 | # service performance data files. The interval at which the | |
707 | # processing occurs is determined by the options above. | |
708 | ||
709 | #host_perfdata_file_processing_command=process-host-perfdata-file | |
710 | #service_perfdata_file_processing_command=process-service-perfdata-file | |
711 | ||
712 | ||
713 | ||
714 | # OBSESS OVER SERVICE CHECKS OPTION | |
715 | # This determines whether or not Nagios will obsess over service | |
716 | # checks and run the ocsp_command defined below. Unless you're | |
717 | # planning on implementing distributed monitoring, do not enable | |
718 | # this option. Read the HTML docs for more information on | |
719 | # implementing distributed monitoring. | |
720 | # Values: 1 = obsess over services, 0 = do not obsess (default) | |
721 | ||
722 | obsess_over_services=0 | |
723 | ||
724 | ||
725 | ||
726 | # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND | |
727 | # This is the command that is run for every service check that is | |
728 | # processed by Nagios. This command is executed only if the | |
729 | # obsess_over_service option (above) is set to 1. The command | |
730 | # argument is the short name of a command definition that you | |
731 | # define in your host configuration file. Read the HTML docs for | |
732 | # more information on implementing distributed monitoring. | |
733 | ||
734 | #ocsp_command=somecommand | |
735 | ||
736 | ||
737 | ||
738 | # ORPHANED SERVICE CHECK OPTION | |
739 | # This determines whether or not Nagios will periodically | |
740 | # check for orphaned services. Since service checks are not | |
741 | # rescheduled until the results of their previous execution | |
742 | # instance are processed, there exists a possibility that some | |
743 | # checks may never get rescheduled. This seems to be a rare | |
744 | # problem and should not happen under normal circumstances. | |
745 | # If you have problems with service checks never getting | |
746 | # rescheduled, you might want to try enabling this option. | |
747 | # Values: 1 = enable checks, 0 = disable checks | |
748 | ||
749 | check_for_orphaned_services=0 | |
750 | ||
751 | ||
752 | ||
753 | # SERVICE FRESHNESS CHECK OPTION | |
754 | # This option determines whether or not Nagios will periodically | |
755 | # check the "freshness" of service results. Enabling this option | |
756 | # is useful for ensuring passive checks are received in a timely | |
757 | # manner. | |
758 | # Values: 1 = enabled freshness checking, 0 = disable freshness checking | |
759 | ||
760 | check_service_freshness=1 | |
761 | ||
762 | ||
763 | ||
764 | # SERVICE FRESHNESS CHECK INTERVAL | |
765 | # This setting determines how often (in seconds) Nagios will | |
766 | # check the "freshness" of service check results. If you have | |
767 | # disabled service freshness checking, this option has no effect. | |
768 | ||
769 | service_freshness_check_interval=60 | |
770 | ||
771 | ||
772 | ||
773 | # HOST FRESHNESS CHECK OPTION | |
774 | # This option determines whether or not Nagios will periodically | |
775 | # check the "freshness" of host results. Enabling this option | |
776 | # is useful for ensuring passive checks are received in a timely | |
777 | # manner. | |
778 | # Values: 1 = enabled freshness checking, 0 = disable freshness checking | |
779 | ||
780 | check_host_freshness=0 | |
781 | ||
782 | ||
783 | ||
784 | # HOST FRESHNESS CHECK INTERVAL | |
785 | # This setting determines how often (in seconds) Nagios will | |
786 | # check the "freshness" of host check results. If you have | |
787 | # disabled host freshness checking, this option has no effect. | |
788 | ||
789 | host_freshness_check_interval=60 | |
790 | ||
791 | ||
792 | ||
793 | # AGGREGATED STATUS UPDATES | |
794 | # This option determines whether or not Nagios will | |
795 | # aggregate updates of host, service, and program status | |
796 | # data. Normally, status data is updated immediately when | |
797 | # a change occurs. This can result in high CPU loads if | |
798 | # you are monitoring a lot of services. If you want Nagios | |
799 | # to only refresh status data every few seconds, disable | |
800 | # this option. | |
801 | # Values: 1 = enable aggregate updates, 0 = disable aggregate updates | |
802 | ||
803 | aggregate_status_updates=1 | |
804 | ||
805 | ||
806 | ||
807 | # AGGREGATED STATUS UPDATE INTERVAL | |
808 | # Combined with the aggregate_status_updates option, | |
809 | # this option determines the frequency (in seconds!) that | |
810 | # Nagios will periodically dump program, host, and | |
811 | # service status data. If you are not using aggregated | |
812 | # status data updates, this option has no effect. | |
813 | ||
814 | status_update_interval=15 | |
815 | ||
816 | ||
817 | ||
818 | # FLAP DETECTION OPTION | |
819 | # This option determines whether or not Nagios will try | |
820 | # and detect hosts and services that are "flapping". | |
821 | # Flapping occurs when a host or service changes between | |
822 | # states too frequently. When Nagios detects that a | |
823 | # host or service is flapping, it will temporarily supress | |
824 | # notifications for that host/service until it stops | |
825 | # flapping. Flap detection is very experimental, so read | |
826 | # the HTML documentation before enabling this feature! | |
827 | # Values: 1 = enable flap detection | |
828 | # 0 = disable flap detection (default) | |
829 | ||
830 | enable_flap_detection=0 | |
831 | ||
832 | ||
833 | ||
834 | # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES | |
835 | # Read the HTML documentation on flap detection for | |
836 | # an explanation of what this option does. This option | |
837 | # has no effect if flap detection is disabled. | |
838 | ||
839 | low_service_flap_threshold=5.0 | |
840 | high_service_flap_threshold=20.0 | |
841 | low_host_flap_threshold=5.0 | |
842 | high_host_flap_threshold=20.0 | |
843 | ||
844 | ||
845 | ||
846 | # DATE FORMAT OPTION | |
847 | # This option determines how short dates are displayed. Valid options | |
848 | # include: | |
849 | # us (MM-DD-YYYY HH:MM:SS) | |
850 | # euro (DD-MM-YYYY HH:MM:SS) | |
851 | # iso8601 (YYYY-MM-DD HH:MM:SS) | |
852 | # strict-iso8601 (YYYY-MM-DDTHH:MM:SS) | |
853 | # | |
854 | ||
855 | date_format=iso8601 | |
856 | ||
857 | ||
858 | ||
859 | # P1.PL FILE LOCATION | |
860 | # This value determines where the p1.pl perl script (used by the | |
861 | # embedded Perl interpreter) is located. If you didn't compile | |
862 | # Nagios with embedded Perl support, this option has no effect. | |
863 | ||
864 | p1_file=/usr/sbin/p1.pl | |
865 | ||
866 | ||
867 | ||
868 | # ILLEGAL OBJECT NAME CHARACTERS | |
869 | # This option allows you to specify illegal characters that cannot | |
870 | # be used in host names, service descriptions, or names of other | |
871 | # object types. | |
872 | ||
873 | illegal_object_name_chars=`~!$%^&*|'"<>?,()= | |
874 | #' | |
875 | ||
876 | # ILLEGAL MACRO OUTPUT CHARACTERS | |
877 | # This option allows you to specify illegal characters that are | |
878 | # stripped from macros before being used in notifications, event | |
879 | # handlers, etc. This DOES NOT affect macros used in service or | |
880 | # host check commands. | |
881 | # The following macros are stripped of the characters you specify: | |
882 | # $HOSTOUTPUT$ | |
883 | # $HOSTPERFDATA$ | |
884 | # $HOSTACKAUTHOR$ | |
885 | # $HOSTACKCOMMENT$ | |
886 | # $SERVICEOUTPUT$ | |
887 | # $SERVICEPERFDATA$ | |
888 | # $SERVICEACKAUTHOR$ | |
889 | # $SERVICEACKCOMMENT$ | |
890 | ||
891 | illegal_macro_output_chars=`~$&|'"<> | |
892 | #' | |
893 | ||
894 | ||
895 | ||
896 | # REGULAR EXPRESSION MATCHING | |
897 | # This option controls whether or not regular expression matching | |
898 | # takes place in the object config files. Regular expression | |
899 | # matching is used to match host, hostgroup, service, and service | |
900 | # group names/descriptions in some fields of various object types. | |
901 | # Values: 1 = enable regexp matching, 0 = disable regexp matching | |
902 | ||
903 | use_regexp_matching=0 | |
904 | ||
905 | ||
906 | ||
907 | # "TRUE" REGULAR EXPRESSION MATCHING | |
908 | # This option controls whether or not "true" regular expression | |
909 | # matching takes place in the object config files. This option | |
910 | # only has an effect if regular expression matching is enabled | |
911 | # (see above). If this option is DISABLED, regular expression | |
912 | # matching only occurs if a string contains wildcard characters | |
913 | # (* and ?). If the option is ENABLED, regexp matching occurs | |
914 | # all the time (which can be annoying). | |
915 | # Values: 1 = enable true matching, 0 = disable true matching | |
916 | ||
917 | use_true_regexp_matching=0 | |
918 | ||
919 | ||
920 | ||
921 | ||
922 | # ADMINISTRATOR EMAIL ADDRESS | |
923 | # The email address of the administrator of *this* machine (the one | |
924 | # doing the monitoring). Nagios never uses this value itself, but | |
925 | # you can access this value by using the $ADMINEMAIL$ macro in your | |
926 | # notification commands. | |
927 | ||
928 | admin_email=nagios | |
929 | ||
930 | ||
931 | ||
932 | # ADMINISTRATOR PAGER NUMBER/ADDRESS | |
933 | # The pager number/address for the administrator of *this* machine. | |
934 | # Nagios never uses this value itself, but you can access this | |
935 | # value by using the $ADMINPAGER$ macro in your notification | |
936 | # commands. | |
937 | ||
938 | admin_pager=pagenagios | |
939 | ||
940 | ||
941 | ||
942 | # DAEMON CORE DUMP OPTION | |
943 | # This option determines whether or not Nagios is allowed to create | |
944 | # a core dump when it runs as a daemon. Note that it is generally | |
945 | # considered bad form to allow this, but it may be useful for | |
946 | # debugging purposes. | |
947 | # Values: 1 - Allow core dumps | |
948 | # 0 - Do not allow core dumps (default) | |
949 | ||
950 | daemon_dumps_core=0 | |
951 | ||
b6230b30 | 952 | # EOF (End of file) |