Changeset 1060


Ignore:
Timestamp:
Apr 4, 2009, 12:59:01 AM (13 years ago)
Author:
quentin
Message:
Update Nagios configuration for Nagios 3
Location:
noc/nagios
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • noc/nagios/cgi.cfg

    r990 r1060  
    1111# data they might need.
    1212
    13 main_config_file=/etc/nagios2/nagios.cfg
     13main_config_file=/etc/nagios3/nagios.cfg
    1414
    1515
     
    2020# and statuswrl CGIs.
    2121
    22 physical_html_path=/usr/share/nagios2/htdocs
     22physical_html_path=/usr/share/nagios3/htdocs
    2323
    2424
     
    3232# (without the quotes).
    3333
    34 url_html_path=/nagios2
     34url_html_path=/nagios3
    3535
    3636
     
    4646
    4747
    48 # NAGIOS PROCESS CHECK COMMAND
    49 # This is the full path and filename of the program used to check
    50 # the status of the Nagios process.  It is used only by the CGIs
    51 # and is completely optional.  However, if you don't use it, you'll
    52 # see warning messages in the CGIs about the Nagios process
    53 # not running and you won't be able to execute any commands from
    54 # the web interface.  The program should follow the same rules
    55 # as plugins; the return codes are the same as for the plugins,
    56 # it should have timeout protection, it should output something
    57 # to STDIO, etc.
    58 #
    59 # Note: The command line for the check_nagios plugin below may
    60 # have to be tweaked a bit, as different versions of the plugin
    61 # use different command line arguments/syntaxes.
    62 
    63 nagios_check_command=/usr/lib/nagios/plugins/check_nagios /var/cache/nagios2/status.dat 5 '/usr/sbin/nagios2'
    64 
     48# PENDING STATES OPTION
     49# This option determines what states should be displayed in the web
     50# interface for hosts/services that have not yet been checked.
     51# Values: 0 = leave hosts/services that have not been check yet in their original state
     52#         1 = mark hosts/services that have not been checked yet as PENDING
     53
     54use_pending_states=1
     55
     56nagios_check_command=/usr/lib/nagios/plugins/check_nagios /var/cache/nagios3/status.dat 5 '/usr/sbin/nagios3'
    6557
    6658
     
    8375
    8476use_authentication=1
     77
     78
     79
     80
     81# x509 CERT AUTHENTICATION
     82# When enabled, this option allows you to use x509 cert (SSL)
     83# authentication in the CGIs.  This is an advanced option and should
     84# not be enabled unless you know what you're doing.
     85
     86use_ssl_authentication=0
     87
    8588
    8689
     
    246249# of various CGIs (status, statusmap, extinfo, and outages). 
    247250
    248 refresh_rate=60
     251refresh_rate=90
     252
     253
     254
     255# ESCAPE HTML TAGS
     256# This option determines whether HTML tags in host and service
     257# status output is escaped in the web interface.  If enabled,
     258# your plugin output will not be able to contain clickable links.
     259
     260escape_html_tags=1
     261
    249262
    250263
  • noc/nagios/nagios.cfg

    r898 r1060  
    11##############################################################################
    22#
    3 # NAGIOS.CFG - Main Config File for Nagios
     3# NAGIOS.CFG - Sample Main Config File for Nagios
     4#
    45#
    56##############################################################################
     
    1112# in the config file!!!
    1213
    13 log_file=/var/log/nagios2/nagios.log
    14 
    15 
    16 
    17 # OBJECT CONFIGURATION FILE(S)
    18 # This is the configuration file in which you define hosts, host
    19 # groups, contacts, contact groups, services, etc.  I guess it would
    20 # be better called an object definition file, but for historical
    21 # reasons it isn't.  You can split object definitions into several
    22 # different config files by using multiple cfg_file statements here.
    23 # Nagios will read and process all the config files you define.
    24 # This can be very useful if you want to keep command definitions
    25 # separate from host and contact definitions...
    26 
    27 # Plugin commands (service and host check commands)
    28 # Arguments are likely to change between different releases of the
    29 # plugins, so you should use the same config file provided with the
    30 # plugin release rather than the one provided with Nagios.
    31 cfg_file=/etc/nagios2/checkcommands.cfg
     14log_file=/var/log/nagios3/nagios.log
    3215
    3316# Debian also defaults to using the check commands defined by the debian
     
    3518cfg_dir=/etc/nagios-plugins/config
    3619
    37 # Misc commands (notification and event handler commands, etc)
    38 cfg_file=/etc/nagios2/misccommands.cfg
    39 
    40 # You can split other types of object definitions across several
    41 # config files if you wish (as done here), or keep them all in a
    42 # single config file.
    43 
    44 cfg_file=/etc/nagios2/base.cfg
    45 cfg_file=/etc/nagios2/contacts.cfg
    46 cfg_file=/etc/nagios2/hostgroups.cfg
    47 cfg_file=/etc/nagios2/hosts.cfg
    48 cfg_file=/etc/nagios2/services.cfg
    49 
    50 cfg_file=/etc/nagios2/xvm.cfg
    51 #cfg_file=/etc/nagios2/test.cfg
    52 
     20# OBJECT CONFIGURATION FILE(S)
     21# These are the object configuration files in which you define hosts,
     22# host groups, contacts, contact groups, services, etc.
     23# You can split your object definitions across several config files
     24# if you wish (as shown below), or keep them all in a single config file.
     25
     26# You can specify individual object config files as shown below:
     27cfg_file=/etc/nagios3/misccommands.cfg
     28cfg_file=/etc/nagios3/contacts.cfg
     29cfg_file=/etc/nagios3/hostgroups.cfg
     30cfg_file=/etc/nagios3/hosts.cfg
     31cfg_file=/etc/nagios3/services.cfg
     32
     33cfg_file=/etc/nagios3/xvm.cfg
    5334
    5435
     
    6041# when the config files are modified after Nagios starts.
    6142
    62 object_cache_file=/var/cache/nagios2/objects.cache
     43object_cache_file=/var/cache/nagios3/objects.cache
     44
     45
     46
     47# PRE-CACHED OBJECT FILE
     48# This options determines the location of the precached object file.
     49# If you run Nagios with the -p command line option, it will preprocess
     50# your object configuration file(s) and write the cached config to this
     51# file.  You can then start Nagios with the -u option to have it read
     52# object definitions from this precached file, rather than the standard
     53# object configuration files (see the cfg_file and cfg_dir options above).
     54# Using a precached object file can speed up the time needed to (re)start
     55# the Nagios process if you've got a large and/or complex configuration.
     56# Read the documentation section on optimizing Nagios to find our more
     57# about how this feature works.
     58
     59precached_object_file=/var/lib/nagios3/objects.precache
    6360
    6461
     
    7370# can be placed on this file.
    7471
    75 resource_file=/etc/nagios2/private/resource.cfg
     72resource_file=/etc/nagios3/private/resource.cfg
    7673
    7774
     
    8380#  restarts.
    8481
    85 status_file=/var/cache/nagios2/status.dat
     82status_file=/var/cache/nagios3/status.dat
     83
     84
     85
     86# STATUS FILE UPDATE INTERVAL
     87# This option determines the frequency (in seconds) that
     88# Nagios will periodically dump program, host, and
     89# service status data.
     90
     91status_update_interval=10
    8692
    8793
     
    108114# Nagios will *not* check for external commands, just to be on the
    109115# cautious side.  If you want to be able to use the CGI command interface
    110 # you will have to enable this.  Setting this value to 0 disables command
    111 # checking (the default), other values enable it.
     116# you will have to enable this.
     117# Values: 0 = disable commands, 1 = enable commands
    112118
    113119check_external_commands=1
     
    128134# command file as often as possible.
    129135
    130 #command_check_interval=1
    131 command_check_interval=1s
    132 #command_check_interval=-1
     136#command_check_interval=15s
     137command_check_interval=-1
    133138
    134139
     
    144149# time to do it.
    145150
    146 command_file=/var/lib/nagios2/rw/nagios.cmd
    147 
    148 
    149 
    150 # COMMENT FILE
    151 # This is the file that Nagios will use for storing host and service
    152 # comments.
    153 
    154 comment_file=/var/lib/nagios2/comments.dat
    155 
    156 
    157 
    158 # DOWNTIME FILE
    159 # This is the file that Nagios will use for storing host and service
    160 # downtime data.
    161 
    162 downtime_file=/var/lib/nagios2/downtime.dat
     151command_file=/var/lib/nagios3/rw/nagios.cmd
     152
     153
     154
     155# EXTERNAL COMMAND BUFFER SLOTS
     156# This settings is used to tweak the number of items or "slots" that
     157# the Nagios daemon should allocate to the buffer that holds incoming
     158# external commands before they are processed.  As external commands
     159# are processed by the daemon, they are removed from the buffer. 
     160
     161external_command_buffer_slots=4096
    163162
    164163
     
    168167# in when it is running in daemon mode.
    169168
    170 lock_file=/var/run/nagios2/nagios2.pid
     169lock_file=/var/run/nagios3/nagios3.pid
    171170
    172171
     
    178177# running.
    179178
    180 temp_file=/var/cache/nagios2/nagios.tmp
     179temp_file=/var/cache/nagios3/nagios.tmp
     180
     181
     182
     183# TEMP PATH
     184# This is path where Nagios can create temp files for service and
     185# host check results, etc.
     186
     187temp_path=/tmp
    181188
    182189
     
    198205# the module at startup are seperated from the module path by a space.
    199206#
     207#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
     208# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
     209#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
     210#
     211# Do NOT overwrite modules while they are being used by Nagios or Nagios
     212# will crash in a fiery display of SEGFAULT glory.  This is a bug/limitation
     213# either in dlopen(), the kernel, and/or the filesystem.  And maybe Nagios...
     214#
     215# The correct/safe way of updating a module is by using one of these methods:
     216#    1. Shutdown Nagios, replace the module file, restart Nagios
     217#    2. Delete the original module file, move the new module file into place, restart Nagios
     218#
    200219# Example:
    201220#
     
    204223#broker_module=/somewhere/module1.o
    205224#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
    206 
    207225
    208226
     
    225243# placed (assuming you've chosen to do log rotation).
    226244
    227 log_archive_path=/var/log/nagios2/archives
     245log_archive_path=/var/log/nagios3/archives
    228246
    229247
     
    231249# LOGGING OPTIONS
    232250# If you want messages logged to the syslog facility, as well as the
    233 # NetAlarm log file set this option to 1.  If not, set it to 0.
     251# Nagios log file set this option to 1.  If not, set it to 0.
    234252
    235253use_syslog=0
     
    396414
    397415
    398 # SERVICE CHECK REAPER FREQUENCY
     416# HOST AND SERVICE CHECK REAPER FREQUENCY
    399417# This is the frequency (in seconds!) that Nagios will process
    400 # the results of services that have been checked.
    401 
    402 service_reaper_frequency=10
    403 
     418# the results of host and service checks.
     419
     420check_result_reaper_frequency=10
     421
     422
     423
     424
     425# MAX CHECK RESULT REAPER TIME
     426# This is the max amount of time (in seconds) that  a single
     427# check result reaper event will be allowed to run before
     428# returning control back to Nagios so it can perform other
     429# duties.
     430
     431max_check_result_reaper_time=30
     432
     433
     434
     435
     436# CHECK RESULT PATH
     437# This is directory where Nagios stores the results of host and
     438# service checks that have not yet been processed.
     439#
     440# Note: Make sure that only one instance of Nagios has access
     441# to this directory! 
     442
     443check_result_path=/var/lib/nagios3/spool/checkresults
     444
     445
     446
     447
     448# MAX CHECK RESULT FILE AGE
     449# This option determines the maximum age (in seconds) which check
     450# result files are considered to be valid.  Files older than this
     451# threshold will be mercilessly deleted without further processing.
     452
     453max_check_result_file_age=3600
     454
     455
     456
     457
     458# CACHED HOST CHECK HORIZON
     459# This option determines the maximum amount of time (in seconds)
     460# that the state of a previous host check is considered current.
     461# Cached host states (from host checks that were performed more
     462# recently that the timeframe specified by this value) can immensely
     463# improve performance in regards to the host check logic.
     464# Too high of a value for this option may result in inaccurate host
     465# states being used by Nagios, while a lower value may result in a
     466# performance hit for host checks.  Use a value of 0 to disable host
     467# check caching.
     468
     469cached_host_check_horizon=15
     470
     471
     472
     473# CACHED SERVICE CHECK HORIZON
     474# This option determines the maximum amount of time (in seconds)
     475# that the state of a previous service check is considered current.
     476# Cached service states (from service checks that were performed more
     477# recently that the timeframe specified by this value) can immensely
     478# improve performance in regards to predictive dependency checks.
     479# Use a value of 0 to disable service check caching.
     480
     481cached_service_check_horizon=15
     482
     483
     484
     485# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
     486# This option determines whether or not Nagios will attempt to execute
     487# checks of hosts when it predicts that future dependency logic test
     488# may be needed.  These predictive checks can help ensure that your
     489# host dependency logic works well.
     490# Values:
     491#  0 = Disable predictive checks
     492#  1 = Enable predictive checks (default)
     493
     494enable_predictive_host_dependency_checks=1
     495
     496
     497
     498# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
     499# This option determines whether or not Nagios will attempt to execute
     500# checks of service when it predicts that future dependency logic test
     501# may be needed.  These predictive checks can help ensure that your
     502# service dependency logic works well.
     503# Values:
     504#  0 = Disable predictive checks
     505#  1 = Enable predictive checks (default)
     506
     507enable_predictive_service_dependency_checks=1
     508
     509
     510
     511# SOFT STATE DEPENDENCIES
     512# This option determines whether or not Nagios will use soft state
     513# information when checking host and service dependencies. Normally
     514# Nagios will only use the latest hard host or service state when
     515# checking dependencies. If you want it to use the latest state (regardless
     516# of whether its a soft or hard state type), enable this option.
     517# Values:
     518#  0 = Don't use soft state dependencies (default)
     519#  1 = Use soft state dependencies
     520
     521soft_state_dependencies=0
     522
     523
     524
     525# TIME CHANGE ADJUSTMENT THRESHOLDS
     526# These options determine when Nagios will react to detected changes
     527# in system time (either forward or backwards).
     528
     529#time_change_threshold=900
    404530
    405531
     
    426552
    427553auto_rescheduling_interval=30
    428 
    429554
    430555
     
    465590notification_timeout=30
    466591ocsp_timeout=5
    467 perfdata_timeout=30
     592perfdata_timeout=5
    468593
    469594
     
    491616# variable is set to 1.
    492617
    493 state_retention_file=/var/lib/nagios2/retention.dat
     618state_retention_file=/var/lib/nagios3/retention.dat
    494619
    495620
     
    525650# value to 1.  If not, set this value to 0.
    526651
    527 use_retained_scheduling_info=0
     652use_retained_scheduling_info=1
     653
     654
     655
     656# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
     657# The following variables are used to specify specific host and
     658# service attributes that should *not* be retained by Nagios during
     659# program restarts.
     660#
     661# The values of the masks are bitwise ANDs of values specified
     662# by the "MODATTR_" definitions found in include/common.h. 
     663# For example, if you do not want the current enabled/disabled state
     664# of flap detection and event handlers for hosts to be retained, you
     665# would use a value of 24 for the host attribute mask...
     666# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
     667
     668# This mask determines what host attributes are not retained
     669retained_host_attribute_mask=0
     670
     671# This mask determines what service attributes are not retained
     672retained_service_attribute_mask=0
     673
     674# These two masks determine what process attributes are not retained.
     675# There are two masks, because some process attributes have host and service
     676# options.  For example, you can disable active host checks, but leave active
     677# service checks enabled.
     678retained_process_host_attribute_mask=0
     679retained_process_service_attribute_mask=0
     680
     681# These two masks determine what contact attributes are not retained.
     682# There are two masks, because some contact attributes have host and
     683# service options.  For example, you can disable host notifications for
     684# a contact, but leave service notifications enabled for them.
     685retained_contact_host_attribute_mask=0
     686retained_contact_service_attribute_mask=0
    528687
    529688
     
    663822
    664823
    665 
    666824# HOST AND SERVICE PERFORMANCE DATA FILE MODES
    667825# This option determines whether or not the host and service
    668826# performance data files are opened in write ("w") or append ("a")
    669 # mode.  Unless you are the files are named pipes, you will probably
    670 # want to use the default mode of append ("a").
     827# mode. If you want to use named pipes, you should use the special
     828# pipe ("p") mode which avoid blocking at startup, otherwise you will
     829# likely want the defult append ("a") mode.
    671830
    672831#host_perfdata_file_mode=a
     
    711870# This is the command that is run for every service check that is
    712871# processed by Nagios.  This command is executed only if the
    713 # obsess_over_service option (above) is set to 1.  The command
     872# obsess_over_services option (above) is set to 1.  The command
    714873# argument is the short name of a command definition that you
    715874# define in your host configuration file. Read the HTML docs for
     
    720879
    721880
    722 # ORPHANED SERVICE CHECK OPTION
    723 # This determines whether or not Nagios will periodically
    724 # check for orphaned services.  Since service checks are not
    725 # rescheduled until the results of their previous execution
     881# OBSESS OVER HOST CHECKS OPTION
     882# This determines whether or not Nagios will obsess over host
     883# checks and run the ochp_command defined below.  Unless you're
     884# planning on implementing distributed monitoring, do not enable
     885# this option.  Read the HTML docs for more information on
     886# implementing distributed monitoring.
     887# Values: 1 = obsess over hosts, 0 = do not obsess (default)
     888
     889obsess_over_hosts=0
     890
     891
     892
     893# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
     894# This is the command that is run for every host check that is
     895# processed by Nagios.  This command is executed only if the
     896# obsess_over_hosts option (above) is set to 1.  The command
     897# argument is the short name of a command definition that you
     898# define in your host configuration file. Read the HTML docs for
     899# more information on implementing distributed monitoring.
     900
     901#ochp_command=somecommand
     902
     903
     904
     905# TRANSLATE PASSIVE HOST CHECKS OPTION
     906# This determines whether or not Nagios will translate
     907# DOWN/UNREACHABLE passive host check results into their proper
     908# state for this instance of Nagios.  This option is useful
     909# if you have distributed or failover monitoring setup.  In
     910# these cases your other Nagios servers probably have a different
     911# "view" of the network, with regards to the parent/child relationship
     912# of hosts.  If a distributed monitoring server thinks a host
     913# is DOWN, it may actually be UNREACHABLE from the point of
     914# this Nagios instance.  Enabling this option will tell Nagios
     915# to translate any DOWN or UNREACHABLE host states it receives
     916# passively into the correct state from the view of this server.
     917# Values: 1 = perform translation, 0 = do not translate (default)
     918
     919translate_passive_host_checks=0
     920
     921
     922
     923# PASSIVE HOST CHECKS ARE SOFT OPTION
     924# This determines whether or not Nagios will treat passive host
     925# checks as being HARD or SOFT.  By default, a passive host check
     926# result will put a host into a HARD state type.  This can be changed
     927# by enabling this option.
     928# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
     929
     930passive_host_checks_are_soft=0
     931
     932
     933
     934# ORPHANED HOST/SERVICE CHECK OPTIONS
     935# These options determine whether or not Nagios will periodically
     936# check for orphaned host service checks.  Since service checks are
     937# not rescheduled until the results of their previous execution
    726938# instance are processed, there exists a possibility that some
    727 # checks may never get rescheduled.  This seems to be a rare
     939# checks may never get rescheduled.  A similar situation exists for
     940# host checks, although the exact scheduling details differ a bit
     941# from service checks.  Orphaned checks seem to be a rare
    728942# problem and should not happen under normal circumstances.
    729943# If you have problems with service checks never getting
    730 # rescheduled, you might want to try enabling this option.
     944# rescheduled, make sure you have orphaned service checks enabled.
    731945# Values: 1 = enable checks, 0 = disable checks
    732946
    733 check_for_orphaned_services=0
     947check_for_orphaned_services=1
     948check_for_orphaned_hosts=1
    734949
    735950
     
    775990
    776991
    777 # AGGREGATED STATUS UPDATES
    778 # This option determines whether or not Nagios will
    779 # aggregate updates of host, service, and program status
    780 # data.  Normally, status data is updated immediately when
    781 # a change occurs.  This can result in high CPU loads if
    782 # you are monitoring a lot of services.  If you want Nagios
    783 # to only refresh status data every few seconds, disable
    784 # this option.
    785 # Values: 1 = enable aggregate updates, 0 = disable aggregate updates
    786 
    787 aggregate_status_updates=1
    788 
    789 
    790 
    791 # AGGREGATED STATUS UPDATE INTERVAL
    792 # Combined with the aggregate_status_updates option,
    793 # this option determines the frequency (in seconds!) that
    794 # Nagios will periodically dump program, host, and
    795 # service status data.  If you are not using aggregated
    796 # status data updates, this option has no effect.
    797 
    798 status_update_interval=15
     992
     993# ADDITIONAL FRESHNESS THRESHOLD LATENCY
     994# This setting determines the number of seconds that Nagios
     995# will add to any host and service freshness thresholds that
     996# it calculates (those not explicitly specified by the user).
     997
     998additional_freshness_latency=15
     999
    7991000
    8001001
     
    8121013#         0 = disable flap detection (default)
    8131014
    814 enable_flap_detection=0
     1015enable_flap_detection=1
    8151016
    8161017
     
    8371038#
    8381039
    839 date_format=us
     1040date_format=iso8601
     1041
     1042
     1043
     1044
     1045# TIMEZONE OFFSET
     1046# This option is used to override the default timezone that this
     1047# instance of Nagios runs in.  If not specified, Nagios will use
     1048# the system configured timezone.
     1049#
     1050# NOTE: In order to display the correct timezone in the CGIs, you
     1051# will also need to alter the Apache directives for the CGI path
     1052# to include your timezone.  Example:
     1053#
     1054#   <Directory "/usr/local/nagios/sbin/">
     1055#      SetEnv TZ "Australia/Brisbane"
     1056#      ...
     1057#   </Directory>
     1058
     1059#use_timezone=US/Mountain
     1060#use_timezone=Australia/Brisbane
     1061
    8401062
    8411063
     
    8461068# Nagios with embedded Perl support, this option has no effect.
    8471069
    848 p1_file=/usr/lib/nagios2/p1.pl
     1070p1_file=/usr/lib/nagios3/p1.pl
     1071
     1072
     1073
     1074# EMBEDDED PERL INTERPRETER OPTION
     1075# This option determines whether or not the embedded Perl interpreter
     1076# will be enabled during runtime.  This option has no effect if Nagios
     1077# has not been compiled with support for embedded Perl.
     1078# Values: 0 = disable interpreter, 1 = enable interpreter
     1079
     1080enable_embedded_perl=1
     1081
     1082
     1083
     1084# EMBEDDED PERL USAGE OPTION
     1085# This option determines whether or not Nagios will process Perl plugins
     1086# and scripts with the embedded Perl interpreter if the plugins/scripts
     1087# do not explicitly indicate whether or not it is okay to do so. Read
     1088# the HTML documentation on the embedded Perl interpreter for more
     1089# information on how this option works.
     1090
     1091use_embedded_perl_implicitly=1
    8491092
    8501093
     
    9031146
    9041147
    905 
    906 # ADMINISTRATOR EMAIL ADDRESS
    907 # The email address of the administrator of *this* machine (the one
    908 # doing the monitoring).  Nagios never uses this value itself, but
    909 # you can access this value by using the $ADMINEMAIL$ macro in your
    910 # notification commands.
    911 
    912 admin_email=nagios
    913 
    914 
    915 
    916 # ADMINISTRATOR PAGER NUMBER/ADDRESS
    917 # The pager number/address for the administrator of *this* machine.
    918 # Nagios never uses this value itself, but you can access this
    919 # value by using the $ADMINPAGER$ macro in your notification
     1148# ADMINISTRATOR EMAIL/PAGER ADDRESSES
     1149# The email and pager address of a global administrator (likely you).
     1150# Nagios never uses these values itself, but you can access them by
     1151# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
    9201152# commands.
    9211153
    922 admin_pager=pagenagios
     1154admin_email=sipb-nagios@mit.edu
     1155admin_pager=sipb-nagios@mit.edu
    9231156
    9241157
     
    9281161# a core dump when it runs as a daemon.  Note that it is generally
    9291162# considered bad form to allow this, but it may be useful for
    930 # debugging purposes.
     1163# debugging purposes.  Enabling this option doesn't guarantee that
     1164# a core file will be produced, but that's just life...
    9311165# Values: 1 - Allow core dumps
    9321166#         0 - Do not allow core dumps (default)
     
    9351169
    9361170
    937 #process_performance_data=1
    938 #service_perfdata_file=/home/noc/ng/log/perfdata
    939 #service_perfdata_file_template=$LASTSERVICECHECK$||$HOSTNAME$||$SERVICEDESC$||$SERVICEOUTPUT$||$SERVICEPERFDATA$
    940 #service_perfdata_file_mode=a
    941 #service_perfdata_file_processing_interval=60
    942 #service_perfdata_file_processing_command=ng-service-perfdata
    943 # EOF (End of file)
     1171
     1172# LARGE INSTALLATION TWEAKS OPTION
     1173# This option determines whether or not Nagios will take some shortcuts
     1174# which can save on memory and CPU usage in large Nagios installations.
     1175# Read the documentation for more information on the benefits/tradeoffs
     1176# of enabling this option.
     1177# Values: 1 - Enabled tweaks
     1178#         0 - Disable tweaks (default)
     1179
     1180use_large_installation_tweaks=0
     1181
     1182
     1183
     1184# ENABLE ENVIRONMENT MACROS
     1185# This option determines whether or not Nagios will make all standard
     1186# macros available as environment variables when host/service checks
     1187# and system commands (event handlers, notifications, etc.) are
     1188# executed.  Enabling this option can cause performance issues in
     1189# large installations, as it will consume a bit more memory and (more
     1190# importantly) consume more CPU.
     1191# Values: 1 - Enable environment variable macros (default)
     1192#         0 - Disable environment variable macros
     1193
     1194enable_environment_macros=1
     1195
     1196
     1197
     1198# CHILD PROCESS MEMORY OPTION
     1199# This option determines whether or not Nagios will free memory in
     1200# child processes (processed used to execute system commands and host/
     1201# service checks).  If you specify a value here, it will override
     1202# program defaults.
     1203# Value: 1 - Free memory in child processes
     1204#        0 - Do not free memory in child processes
     1205
     1206#free_child_process_memory=1
     1207
     1208
     1209
     1210# CHILD PROCESS FORKING BEHAVIOR
     1211# This option determines how Nagios will fork child processes
     1212# (used to execute system commands and host/service checks).  Normally
     1213# child processes are fork()ed twice, which provides a very high level
     1214# of isolation from problems.  Fork()ing once is probably enough and will
     1215# save a great deal on CPU usage (in large installs), so you might
     1216# want to consider using this.  If you specify a value here, it will
     1217# program defaults.
     1218# Value: 1 - Child processes fork() twice
     1219#        0 - Child processes fork() just once
     1220
     1221#child_processes_fork_twice=1
     1222
     1223
     1224
     1225# DEBUG LEVEL
     1226# This option determines how much (if any) debugging information will
     1227# be written to the debug file.  OR values together to log multiple
     1228# types of information.
     1229# Values:
     1230#          -1 = Everything
     1231#          0 = Nothing
     1232#          1 = Functions
     1233#          2 = Configuration
     1234#          4 = Process information
     1235#          8 = Scheduled events
     1236#          16 = Host/service checks
     1237#          32 = Notifications
     1238#          64 = Event broker
     1239#          128 = External commands
     1240#          256 = Commands
     1241#          512 = Scheduled downtime
     1242#          1024 = Comments
     1243#          2048 = Macros
     1244
     1245debug_level=0
     1246
     1247
     1248
     1249# DEBUG VERBOSITY
     1250# This option determines how verbose the debug log out will be.
     1251# Values: 0 = Brief output
     1252#         1 = More detailed
     1253#         2 = Very detailed
     1254
     1255debug_verbosity=1
     1256
     1257
     1258
     1259# DEBUG FILE
     1260# This option determines where Nagios should write debugging information.
     1261
     1262debug_file=/var/lib/nagios3/nagios.debug
     1263
     1264
     1265
     1266# MAX DEBUG FILE SIZE
     1267# This option determines the maximum size (in bytes) of the debug file.  If
     1268# the file grows larger than this size, it will be renamed with a .old
     1269# extension.  If a file already exists with a .old extension it will
     1270# automatically be deleted.  This helps ensure your disk space usage doesn't
     1271# get out of control when debugging Nagios.
     1272
     1273max_debug_file_size=1000000
     1274
     1275
Note: See TracChangeset for help on using the changeset viewer.