<html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 10 (filtered)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Can someone tell me how to verify the settings for the CGI? It still seems to read from files, and the main program is logging to mySQL? Enclosing my config info. nagios@argus:/usr/local/nagios/etc$ cat nagios.cfg resource.cfg cgi.cfg ############################################################################## # # NAGIOS.CFG - Sample Main Config File for Nagios 1.0b6 # # Read the documentation for more information on this configuration # file. I've provided some comments here, but things may not be so # clear without further explanation. # # Last Modified: 07-04-2002 # ############################################################################## # LOG FILE # This is the main log file where service and host events are logged # for historical purposes. This should be the first option specified # in the config file!!! log_file=/usr/local/nagios/var/nagios.log # OBJECT CONFIGURATION FILE(S) # This is the configuration file in which you define hosts, host # groups, contacts, contact groups, services, etc. I guess it would # be better called an object definition file, but for historical # reasons it isn't. You can split object definitions into several # different config files by using multiple cfg_file statements here. # Nagios will read and process all the config files you define. # This can be very useful if you want to keep command definitions # separate from host and contact definitions... # Plugin commands (service and host check commands) # Arguments are likely to change between different releases of the # plugins, so you should use the same config file provided with the # plugin release rather than the one provided with Nagios. cfg_file=/usr/local/nagios/etc/checkcommands.cfg # Misc commands (notification and event handler commands, etc) cfg_file=/usr/local/nagios/etc/misccommands.cfg # You can split other types of object definitions across several # config files if you wish (as done here), or keep them all in a # single config file. cfg_file=/usr/local/nagios/etc/contactgroups.cfg cfg_file=/usr/local/nagios/etc/contacts.cfg cfg_file=/usr/local/nagios/etc/dependencies.cfg cfg_file=/usr/local/nagios/etc/escalations.cfg cfg_file=/usr/local/nagios/etc/hostgroups.cfg cfg_file=/usr/local/nagios/etc/hosts.cfg cfg_file=/usr/local/nagios/etc/services.cfg cfg_file=/usr/local/nagios/etc/timeperiods.cfg # RESOURCE FILE # This is an optional resource file that contains $USERx$ macro # definitions. Multiple resource files can be specified by using # multiple resource_file definitions. The CGIs will not attempt to # read the contents of resource files, so information that is # considered to be sensitive (usernames, passwords, etc) can be # defined as macros in this file and restrictive permissions (600) # can be placed on this file. resource_file=/usr/local/nagios/etc/resource.cfg # STATUS FILE # This is where the current status of all monitored services and # hosts is stored. Its contents are read and processed by the CGIs. # The contentsof the status file are deleted every time Nagios # restarts. status_file=/usr/local/nagios/var/status.log # NAGIOS USER # This determines the effective user that Nagios should run as. # You can either supply a username or a UID. nagios_user=nagios # NAGIOS GROUP # This determines the effective group that Nagios should run as. # You can either supply a group name or a GID. nagios_group=nagios # EXTERNAL COMMAND OPTION # This option allows you to specify whether or not Nagios should check # for external commands (in the command file defined below). By default # Nagios will *not* check for external commands, just to be on the # cautious side. If you want to be able to use the CGI command interface # you will have to enable this. Setting this value to 0 disables command # checking (the default), other values enable it. check_external_commands=0 # EXTERNAL COMMAND CHECK INTERVAL # This is the interval at which Nagios should check for external commands. # This value works of the interval_length you specify later. If you leave # that at its default value of 60 (seconds), a value of 1 here will cause # Nagios to check for external commands every minute. If you specify a # number followed by an "s" (i.e. 15s), this will be interpreted to mean # actual seconds rather than a multiple of the interval_length variable. # Note: In addition to reading the external command file at regularly # scheduled intervals, Nagios will also check for external commands after # event handlers are executed. # NOTE: Setting this value to -1 causes Nagios to check the external # command file as often as possible. #command_check_interval=1 #command_check_interval=15s command_check_interval=-1 # EXTERNAL COMMAND FILE # This is the file that Nagios checks for external command requests. # It is also where the command CGI will write commands that are submitted # by users, so it must be writeable by the user that the web server # is running as (usually 'nobody'). Permissions should be set at the # directory level instead of on the file, as the file is deleted every # time its contents are processed. command_file=/usr/local/nagios/var/rw/nagios.cmd # COMMENT FILE # This is the file that Nagios will use for storing host and service # comments. comment_file=/usr/local/nagios/var/comment.log # DOWNTIME FILE # This is the file that Nagios will use for storing host and service # downtime data. downtime_file=/usr/local/nagios/var/downtime.log # LOCK FILE # This is the lockfile that Nagios will use to store its PID number # in when it is running in daemon mode. lock_file=/usr/local/nagios/var/nagios.lock # TEMP FILE # This is a temporary file that is used as scratch space when Nagios # updates the status log, cleans the comment file, etc. This file # is created, used, and deleted throughout the time that Nagios is # running. temp_file=/usr/local/nagios/var/nagios.tmp # LOG ROTATION METHOD # This is the log rotation method that Nagios should use to rotate # the main log file. Values are as follows.. # n = None - don't rotate the log # h = Hourly rotation (top of the hour) # d = Daily rotation (midnight every day) # w = Weekly rotation (midnight on Saturday evening) # m = Monthly rotation (midnight last day of month) log_rotation_method=d # LOG ARCHIVE PATH # This is the directory where archived (rotated) log files should be # placed (assuming you've chosen to do log rotation). log_archive_path=/usr/local/nagios/var/archives # LOGGING OPTIONS # If you want messages logged to the syslog facility, as well as the # NetAlarm log file set this option to 1. If not, set it to 0. use_syslog=1 # NOTIFICATION LOGGING OPTION # If you don't want notifications to be logged, set this value to 0. # If notifications should be logged, set the value to 1. log_notifications=1 # SERVICE RETRY LOGGING OPTION # If you don't want service check retries to be logged, set this value # to 0. If retries should be logged, set the value to 1. log_service_retries=1 # HOST RETRY LOGGING OPTION # If you don't want host check retries to be logged, set this value to # 0. If retries should be logged, set the value to 1. log_host_retries=1 # EVENT HANDLER LOGGING OPTION # If you don't want host and service event handlers to be logged, set # this value to 0. If event handlers should be logged, set the value # to 1. log_event_handlers=1 # INITIAL STATES LOGGING OPTION # If you want Nagios to log all initial host and service states to # the main log file (the first time the service or host is checked) # you can enable this option by setting this value to 1. If you # are not using an external application that does long term state # statistics reporting, you do not need to enable this option. In # this case, set the value to 0. log_initial_states=0 # EXTERNAL COMMANDS LOGGING OPTION # If you don't want Nagios to log external commands, set this value # to 0. If external commands should be logged, set this value to 1. # Note: This option does not include logging of passive service # checks - see the option below for controlling whether or not # passive checks are logged. log_external_commands=1 # PASSIVE SERVICE CHECKS LOGGING OPTION # If you don't want Nagios to log passive service checks, set this # value to 0. If passive service checks should be logged, set this # value to 1. log_passive_service_checks=1 # GLOBAL HOST AND SERVICE EVENT HANDLERS # These options allow you to specify a host and service event handler # command that is to be run for every host or service state change. # The global event handler is executed immediately prior to the event # handler that you have optionally specified in each host or # service definition. The command argument is the short name of a # command definition that you define in your host configuration file. # Read the HTML docs for more information. #global_host_event_handler=somecommand #global_service_event_handler=somecommand # INTER-CHECK DELAY METHOD # This is the method that Nagios should use when initially # "spreading out" service checks when it starts monitoring. The # default is to use smart delay calculation, which will try to # space all service checks out evenly to minimize CPU load. # Using the dumb setting will cause all checks to be scheduled # at the same time (with no delay between them)! This is not a # good thing for production, but is useful when testing the # parallelization functionality. # n = None - don't use any delay between checks # d = Use a "dumb" delay of 1 second between checks # s = Use "smart" inter-check delay calculation # x.xx = Use an inter-check delay of x.xx seconds inter_check_delay_method=s # SERVICE CHECK INTERLEAVE FACTOR # This variable determines how service checks are interleaved. # Interleaving the service checks allows for a more even # distribution of service checks and reduced load on remote # hosts. Setting this value to 1 is equivalent to how versions # of Nagios previous to 0.0.5 did service checks. Set this # value to s (smart) for automatic calculation of the interleave # factor unless you have a specific reason to change it. # s = Use "smart" interleave factor calculation # x = Use an interleave factor of x, where x is a # number greater than or equal to 1. service_interleave_factor=s # MAXIMUM CONCURRENT SERVICE CHECKS # This option allows you to specify the maximum number of # service checks that can be run in parallel at any given time. # Specifying a value of 1 for this variable essentially prevents # any service checks from being parallelized. A value of 0 # will not restrict the number of concurrent checks that are # being executed. max_concurrent_checks=0 # SERVICE CHECK REAPER FREQUENCY # This is the frequency (in seconds!) that Nagios will process # the results of services that have been checked. service_reaper_frequency=10 # SLEEP TIME # This is the number of seconds to sleep between checking for system # events and service checks that need to be run. I would recommend # *not* changing this from its default value of 1 second. sleep_time=1 # TIMEOUT VALUES # These options control how much time Nagios will allow various # types of commands to execute before killing them off. Options # are available for controlling maximum time allotted for # service checks, host checks, event handlers, notifications, the # ocsp command, and performance data commands. All values are in # seconds. service_check_timeout=60 host_check_timeout=30 event_handler_timeout=30 notification_timeout=30 ocsp_timeout=5 perfdata_timeout=5 # RETAIN STATE INFORMATION # This setting determines whether or not Nagios will save state # information for services and hosts before it shuts down. Upon # startup Nagios will reload all saved service and host state # information before starting to monitor. This is useful for # maintaining long-term data on state statistics, etc, but will # slow Nagios down a bit when it (re)starts. Since its only # a one-time penalty, I think its well worth the additional # startup delay. retain_state_information=1 # STATE RETENTION FILE # This is the file that Nagios should use to store host and # service state information before it shuts down. The state # information in this file is also read immediately prior to # starting to monitor the network when Nagios is restarted. # This file is used only if the preserve_state_information # variable is set to 1. state_retention_file=/usr/local/nagios/var/status.sav # RETENTION DATA UPDATE INTERVAL # This setting determines how often (in minutes) that Nagios # will automatically save retention data during normal operation. # If you set this value to 0, Nagios will not save retention # data at regular interval, but it will still save retention # data before shutting down or restarting. If you have disabled # state retention, this option has no effect. retention_update_interval=60 # USE RETAINED PROGRAM STATE # This setting determines whether or not Nagios will set # program status variables based on the values saved in the # retention file. If you want to use retained program status # information, set this value to 1. If not, set this value # to 0. use_retained_program_state=0 # INTERVAL LENGTH # This is the seconds per unit interval as used in the # host/contact/service configuration files. Setting this to 60 means # that each interval is one minute long (60 seconds). Other settings # have not been tested much, so your mileage is likely to vary... interval_length=60 # AGRESSIVE HOST CHECKING OPTION # If you don't want to turn on agressive host checking features, set # this value to 0 (the default). Otherwise set this value to 1 to # enable the agressive check option. Read the docs for more info # on what agressive host check is or check out the source code in # base/checks.c use_agressive_host_checking=0 # SERVICE CHECK EXECUTION OPTION # This determines whether or not Nagios will actively execute # service checks when it initially starts. If this option is # disabled, checks are not actively made, but Nagios can still # receive and process passive check results that come in. Unless # you're implementing redundant hosts or have a special need for # disabling the execution of service checks, leave this enabled! # Values: 1 = enable checks, 0 = disable checks execute_service_checks=1 # PASSIVE CHECK ACCEPTANCE OPTION # This determines whether or not Nagios will accept passive # service checks results when it initially (re)starts. # Values: 1 = accept passive checks, 0 = reject passive checks accept_passive_service_checks=1 # NOTIFICATIONS OPTION # This determines whether or not Nagios will sent out any host or # service notifications when it is initially (re)started. # Values: 1 = enable notifications, 0 = disable notifications enable_notifications=1 # EVENT HANDLER USE OPTION # This determines whether or not Nagios will run any host or # service event handlers when it is initially (re)started. Unless # you're implementing redundant hosts, leave this option enabled. # Values: 1 = enable event handlers, 0 = disable event handlers enable_event_handlers=1 # PROCESS PERFORMANCE DATA OPTION # This determines whether or not Nagios will process performance # data returned from service and host checks. If this option is # enabled, host performance data will be processed using the # host_perfdata_command (defined below) and service performance # data will be processed using the service_perfdata_command (also # defined below). Read the HTML docs for more information on # performance data. # Values: 1 = process performance data, 0 = do not process performance data process_performance_data=0 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS # These commands are run after every host and service check is # performed. These commands are executed only if the # enable_performance_data option (above) is set to 1. The command # argument is the short name of a command definition that you # define in your host configuration file. Read the HTML docs for # more information on performance data. #host_perfdata_command=process-host-perfdata #service_perfdata_command=process-service-perfdata # OBSESS OVER SERVICE CHECKS OPTION # This determines whether or not Nagios will obsess over service # checks and run the ocsp_command defined below. Unless you're # planning on implementing distributed monitoring, do not enable # this option. Read the HTML docs for more information on # implementing distributed monitoring. # Values: 1 = obsess over services, 0 = do not obsess (default) obsess_over_services=0 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND # This is the command that is run for every service check that is # processed by Nagios. This command is executed only if the # obsess_over_service option (above) is set to 1. The command # argument is the short name of a command definition that you # define in your host configuration file. Read the HTML docs for # more information on implementing distributed monitoring. #ocsp_command=somecommand # ORPHANED SERVICE CHECK OPTION # This determines whether or not Nagios will periodically # check for orphaned services. Since service checks are not # rescheduled until the results of their previous execution # instance are processed, there exists a possibility that some # checks may never get rescheduled. This seems to be a rare # problem and should not happen under normal circumstances. # If you have problems with service checks never getting # rescheduled, you might want to try enabling this option. # Values: 1 = enable checks, 0 = disable checks check_for_orphaned_services=0 # SERVICE FRESHNESS CHECK OPTION # This option determines whether or not Nagios will periodically # check the "freshness" of service results. Enabling this option # is useful for ensuring passive checks are received in a timely # manner. # Values: 1 = enabled freshness checking, 0 = disable freshness checking check_service_freshness=1 # FRESHNESS CHECK INTERVAL # This setting determines how often (in seconds) Nagios will # check the "freshness" of service check results. If you have # disabled service freshness checking, this option has no effect. freshness_check_interval=60 # AGGREGATED STATUS UPDATES # This option determines whether or not Nagios will # aggregate updates of host, service, and program status # data. Normally, status data is updated immediately when # a change occurs. This can result in high CPU loads if # you are monitoring a lot of services. If you want Nagios # to only refresh status data every few seconds, disable # this option. # Values: 1 = enable aggregate updates, 0 = disable aggregate updates aggregate_status_updates=1 # AGGREGATED STATUS UPDATE INTERVAL # Combined with the aggregate_status_updates option, # this option determines the frequency (in seconds!) that # Nagios will periodically dump program, host, and # service status data. If you are not using aggregated # status data updates, this option has no effect. status_update_interval=15 # FLAP DETECTION OPTION # This option determines whether or not Nagios will try # and detect hosts and services that are "flapping". # Flapping occurs when a host or service changes between # states too frequently. When Nagios detects that a # host or service is flapping, it will temporarily supress # notifications for that host/service until it stops # flapping. Flap detection is very experimental, so read # the HTML documentation before enabling this feature! # Values: 1 = enable flap detection # 0 = disable flap detection (default) enable_flap_detection=0 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES # Read the HTML documentation on flap detection for # an explanation of what this option does. This option # has no effect if flap detection is disabled. low_service_flap_threshold=5.0 high_service_flap_threshold=20.0 low_host_flap_threshold=5.0 high_host_flap_threshold=20.0 # DATE FORMAT OPTION # This option determines how short dates are displayed. Valid options # include: # us (MM-DD-YYYY HH:MM:SS) # euro (DD-MM-YYYY HH:MM:SS) # iso8601 (YYYY-MM-DD HH:MM:SS) # strict-iso8601 (YYYY-MM-DDTHH:MM:SS) # date_format=us # ILLEGAL OBJECT NAME CHARACTERS # This options allows you to specify illegal characters that cannot # be used in host names, service descriptions, or names of other # object types. illegal_object_name_chars=`~!$%^&*|'"<>?,()= # ILLEGAL MACRO OUTPUT CHARACTERS # This options allows you to specify illegal characters that are # stripped from macros before being used in notifications, event # handlers, etc. This DOES NOT affect macros used in service or # host check commands. # The following macros are stripped of the characters you specify: # $OUTPUT$, $PERFDATA$ illegal_macro_output_chars=`~$&|'"<> # ADMINISTRATOR EMAIL ADDRESS # The email address of the administrator of *this* machine (the one # doing the monitoring). Nagios never uses this value itself, but # you can access this value by using the $ADMINEMAIL$ macro in your # notification commands. admin_email=nagios # ADMINISTRATOR PAGER NUMBER/ADDRESS # The pager number/address for the administrator of *this* machine. # Nagios never uses this value itself, but you can access this # value by using the $ADMINPAGER$ macro in your notification # commands. admin_pager=pagenagios # EOF (End of file) ########################################################################### # # RESOURCE.CFG - Sample Resource File for Nagios 1.0b6 # # You can define $USERx$ macros in this file, which can in turn be used # in command definitions in your host config file(s). $USERx$ macros are # useful for storing sensitive information such as usernames, passwords, # etc. They are also handy for specifying the path to plugins and # event handlers - if you decide to move the plugins or event handlers to # a different directory in the future, you can just update one or two # $USERx$ macros, instead of modifying a lot of command definitions. # # The CGIs will not attempt to read the contents of resource files, so # you can set restrictive permissions (600 or 660) on them. # # Nagios supports up to 32 $USERx$ macros ($USER1$ through $USER32$) # # Resource files may also be used to store configuration directives for # external data sources like MySQL... # ########################################################################### # Sets $USER1$ to be the path to the plugins $USER1$=/usr/local/nagios/libexec # Sets $USER2$ to be the path to event handlers #$USER2$=/usr/local/nagios/libexec/eventhandlers # Store some usernames and passwords (hidden from the CGIs) #$USER3$=someuser #$USER4$=somepassword # DB STATUS DATA # Note: These config directives are only used if you compiled # in database support for status data! # The user you specify here needs SELECT, INSERT, UPDATE, and # DELETE privileges on the 'programstatus', 'hoststatus', # and 'servicestatus' tables in the database. xsddb_host=localhost xsddb_port=3306 xsddb_database=nagios xsddb_username=nagios xsddb_password=nagios xsddb_optimize_data=1 xsddb_optimize_interval=3600 # DB COMMENT DATA # Note: These config directives are only used if you compiled # in database support for comment data! # The user you specify here needs SELECT, INSERT, UPDATE, and # DELETE privileges on the 'hostcomments' and 'servicecomments' # tables in the database. xcddb_host=localhost xcddb_port=3306 xcddb_database=nagios xcddb_username=nagios xcddb_password=nagios xcddb_optimize_data=1 # DB DOWNTIME DATA # Note: These config directives are only used if you compiled # in database support for downtime data! # The user you specify here needs SELECT, INSERT, UPDATE, and # DELETE privileges on the 'hostdowntime' and 'servicedowntime' # tables in the database. xdddb_host=localhost xdddb_port=3306 xdddb_database=nagios xdddb_username=nagios xdddb_password=nagios xdddb_optimize_data=1 # DB RETENTION DATA # Note: These config directives are only used if you compiled # in database support for retention data! # The user you specify here needs SELECT, INSERT, UPDATE, and # DELETE privileges on the 'programretention', 'hostretention', # and 'serviceretention' tables in the database. xrddb_host=localhost xrddb_port=3306 xrddb_database=nagios xrddb_username=nagios xrddb_password=nagios xrddb_optimize_data=1 ################################################################# # # CGI.CFG - Sample CGI Configuration File for Nagios 1.0b6 # # Last Modified: 05-30-2002 # ################################################################# # MAIN CONFIGURATION FILE # This tells the CGIs where to find your main configuration file. # The CGIs will read the main and host config files for any other # data they might need. main_config_file=/usr/local/nagios/etc/nagios.cfg # PHYSICAL HTML PATH # This is the path where the HTML files for Nagios reside. This # value is used to locate the logo images needed by the statusmap # and statuswrl CGIs. physical_html_path=/usr/local/nagios/share # URL HTML PATH # This is the path portion of the URL that corresponds to the # physical location of the Nagios HTML files (as defined above). # This value is used by the CGIs to locate the online documentation # and graphics. If you access the Nagios pages with an URL like # http://www.myhost.com/nagios, this value should be '/nagios' # (without the quotes). url_html_path=/nagios # CONTEXT-SENSITIVE HELP # This option determines whether or not a context-sensitive # help icon will be displayed for most of the CGIs. # Values: 0 = disables context-sensitive help # 1 = enables context-sensitive help show_context_help=0 # NAGIOS PROCESS CHECK COMMAND # This is the full path and filename of the program used to check # the status of the Nagios process. It is used only by the CGIs # and is completely optional. However, if you don't use it, you'll # see warning messages in the CGIs about the Nagios process # not running and you won't be able to execute any commands from # the web interface. The program should follow the same rules # as plugins; the return codes are the same as for the plugins, # it should have timeout protection, it should output something # to STDIO, etc. # # Note: If you are using the check_nagios plugin here, the first # argument should be the physical path to the status log, the # second argument is the number of minutes that the status log # contents should be "fresher" than, and the third argument is the # string that should be matched from the output of the 'ps' # command in order to locate the running Nagios process. That # process string is going to vary depending on how you start # Nagios. Run the 'ps' command manually to see what the command # line entry for the Nagios process looks like. #nagios_check_command=/usr/local/nagios/libexec/check_nagios /usr/local/nagios/var/status.log 5 '/usr/local/nagios/bin/nagios' # AUTHENTICATION USAGE # This option controls whether or not the CGIs will use any # authentication when displaying host and service information, as # well as committing commands to Nagios for processing. # # Read the HTML documentation to learn how the authorization works! # # NOTE: It is a really *bad* idea to disable authorization, unless # you plan on removing the command CGI (cmd.cgi)! Failure to do # so will leave you wide open to kiddies messing with Nagios and # possibly hitting you with a denial of service attack by filling up # your drive by continuously writing to your command file! # # Setting this value to 0 will cause the CGIs to *not* use # authentication (bad idea), while any other value will make them # use the authentication functions (the default). use_authentication=0 # DEFAULT USER # Setting this variable will define a default user name that can # access pages without authentication. This allows people within a # secure domain (i.e., behind a firewall) to see the current status # without authenticating. You may want to use this to avoid basic # authentication if you are not using a sercure server since basic # authentication transmits passwords in the clear. # # Important: Do not define a default username unless you are # running a secure web server and are sure that everyone who has # access to the CGIs has been authenticated in some manner! If you # define this variable, anyone who has not authenticated to the web # server will inherit all rights you assign to this user! #default_user_name=guest # SYSTEM/PROCESS INFORMATION ACCESS # This option is a comma-delimited list of all usernames that # have access to viewing the Nagios process information as # provided by the Extended Information CGI (extinfo.cgi). By # default, *no one* has access to this unless you choose to # not use authorization. You may use an asterisk (*) to # authorize any user who has authenticated to the web server. #authorized_for_system_information=nagiosadmin,theboss,jdoe # CONFIGURATION INFORMATION ACCESS # This option is a comma-delimited list of all usernames that # can view ALL configuration information (hosts, commands, etc). # By default, users can only view configuration information # for the hosts and services they are contacts for. You may use # an asterisk (*) to authorize any user who has authenticated # to the web server. #authorized_for_configuration_information=nagiosadmin,jdoe # SYSTEM/PROCESS COMMAND ACCESS # This option is a comma-delimited list of all usernames that # can issue shutdown and restart commands to Nagios via the # command CGI (cmd.cgi). Users in this list can also change # the program mode to active or standby. By default, *no one* # has access to this unless you choose to not use authorization. # You may use an asterisk (*) to authorize any user who has # authenticated to the web server. #authorized_for_system_commands=nagiosadmin # GLOBAL HOST/SERVICE VIEW ACCESS # These two options are comma-delimited lists of all usernames that # can view information for all hosts and services that are being # monitored. By default, users can only view information # for hosts or services that they are contacts for (unless you # you choose to not use authorization). You may use an asterisk (*) # to authorize any user who has authenticated to the web server. #authorized_for_all_services=nagiosadmin,guest #authorized_for_all_hosts=nagiosadmin,guest # GLOBAL HOST/SERVICE COMMAND ACCESS # These two options are comma-delimited lists of all usernames that # can issue host or service related commands via the command # CGI (cmd.cgi) for all hosts and services that are being monitored. # By default, users can only issue commands for hosts or services # that they are contacts for (unless you you choose to not use # authorization). You may use an asterisk (*) to authorize any # user who has authenticated to the web server. #authorized_for_all_service_commands=nagiosadmin #authorized_for_all_host_commands=nagiosadmin # EXTENDED HOST INFORMATION # This is all entirely optional. If you don't enter any extended # information, nothing bad will happen - I promise... Its basically # just used to have pretty icons and such associated with your hosts. # This is especially nice when you're using the statusmap and # statuswrl CGIs. You can also specify an URL that links to a document # containing more information about the host (location details, contact # information, etc). # # hostextinfo[<host_name>]=<notes_url>;<icon_image>;<vrml_image>;<gd2_image>;\ # <image_alt>;<x_2d>,<y_2d>;<x_3d>,<y_3d>,<z_3d>; # # <notes_url> = Optional URL that points to a document of # some type containing information on the host. # The information (and the document type) can # be anything you want. Examples include details # on the physical location of the server, info # on how to contact the admins in case of an # emergency, etc. Relative URLs start in the # same path that is used to access the CGIs. # The link that is created for the host's notes # notes is found in the extinfo CGI. # Note: You may use the $HOSTNAME$ and # $HOSTADDRESS$ macros in this URL. # <icon_image> = A GIF, PNG, or JPG image to associate with # the host. This is used in the status and # extinfo CGIs. # <vrml_image> = An image to use in the statuswrl CGI in the # VRML generation. Transparent images don't # work so great.. # <gd2_image> = A GD2 format image used by the statusmap CGI # to represent the host. PNG images can be # converted to GD2 format by using the 'pngtogd2' # utility supplied with Boutell's gd library. # <image_alt> = ALT tag used with PNG, GIF, and GD2 images # in the status, statusmap, and extinfo CGIs # <x_2d>,<y_2d> = X and Y coordinates used when drawing the # host in the statusmap CGI. (0,0) is located # in the upper left corner of the screen and is # considered to be the origin. The coordinates # you supply here are used as the coords of the # upper left hand corner of host icon. Both # numbers should be positive integers. # <x_3d>,<y_3d>,<z_3d> = X, Y, and Z coordinates used when drawing # the host in the statuswrl (VRML) CGI. All # numbers can be positive or negative (anywhere # in 3-D space). The coordinates are used to # determine the center of the host "cube" that # is drawn. Host "cubes" are drawn with a # height, width, and depth of 0.5 (meters). # # Note: All images must be placed in the /logos subdirectory under # the HTML images path (i.e. /usr/local/nagios/share/images/logos/). # This path is automatically determined by appending "/images/logos" # to the path specified by the 'physical_html_path' directive. #hostextinfo[es-eds]=/serverinfo/es-eds.html;novell40.gif;novell40.jpg;novell40.gd2;IntranetWare 4.11;100,50;3.5,0.0,-1.5; #hostextinfo[rosie]=/serverinfo/rosie.html;win40.gif;win40.jpg;win40.gd2;NT Server 4.0;;; # EXTENDED SERVICE INFORMATION # This is all entirely optional. If you don't enter any extended # information, nothing bad will happen - I promise... Its basically # just used to have pretty icons and such associated with your services. # You can also specify an URL that links to a document containing more # information about the service (location details, contact information, # etc). # # serviceextinfo[<host_name>;<svc_description>]=<notes_url>;<icon_image>;<image_alt> # # <notes_url> = Optional URL that points to a document of # some type containing information on the service. # The information (and the document type) can # be anything you want. Examples include details # on the physical location of the server, info # on how to contact the admins in case of an # emergency, etc. Relative URLs start in the # same path that is used to access the CGIs. # The link that is created for the service's # notes URL is found in the extinfo CGI. # Note: You may use the $HOSTNAME$, $HOSTADDRESS$, # and $SERVICEDESC$ macros in this URL. # <icon_image> = A GIF, PNG, or JPG image to associate with # the service. This is used in the status and # extinfo CGIs. # <image_alt> = ALT tag used with image # # Note: All images must be placed in the /logos subdirectory under # the HTML images path (i.e. /usr/local/nagios/share/images/logos/). # This path is automatically determined by appending "/images/logos" # to the path specified by the 'physical_html_path' directive. #serviceextinfo[es-eds;PING]=http://www.somewhere.com?tracerouteto=$HOSTADDRESS$;;PING rate #serviceextinfo[rosie;Security Alerts]=;security.gif;Security alerts # STATUSMAP BACKGROUND IMAGE # This option allows you to specify an image to be used as a # background in the statusmap CGI. It is assumed that the image # resides in the HTML images path (i.e. /usr/local/nagios/share/images). # This path is automatically determined by appending "/images" # to the path specified by the 'physical_html_path' directive. # Note: The image file must be in GD2 format! #statusmap_background_image=smbackground.gd2 # DEFAULT STATUSMAP LAYOUT METHOD # This option allows you to specify the default layout method # the statusmap CGI should use for drawing hosts. If you do # not use this option, the default is to use user-defined # coordinates. Valid options are as follows: # 0 = User-defined coordinates # 1 = Depth layers # 2 = Collapsed tree # 3 = Balanced tree # 4 = Circular # 5 = Circular (Marked Up) default_statusmap_layout=5 # DEFAULT STATUSWRL LAYOUT METHOD # This option allows you to specify the default layout method # the statuswrl (VRML) CGI should use for drawing hosts. If you # do not use this option, the default is to use user-defined # coordinates. Valid options are as follows: # 0 = User-defined coordinates # 2 = Collapsed tree # 3 = Balanced tree # 4 = Circular default_statuswrl_layout=4 # STATUSWRL INCLUDE # This option allows you to include your own objects in the # generated VRML world. It is assumed that the file # resides in the HTML path (i.e. /usr/local/nagios/share). #statuswrl_include=myworld.wrl # PING SYNTAX # This option determines what syntax should be used when # attempting to ping a host from the WAP interface (using # the statuswml CGI. You must include the full path to # the ping binary, along with all required options. The # $HOSTADDRESS$ macro is substituted with the address of # the host before the command is executed. ping_syntax=/bin/ping -n -U -c 5 $HOSTADDRESS$ # REFRESH RATE # This option allows you to specify the refresh rate in seconds # of various CGIs (status, statusmap, extinfo, and outages). refresh_rate=90 # SOUND OPTIONS # These options allow you to specify an optional audio file # that should be played in your browser window when there are # problems on the network. The audio files are used only in # the status CGI. Only the sound for the most critical problem # will be played. Order of importance (higher to lower) is as # follows: unreachable hosts, down hosts, critical services, # warning services, and unknown services. If there are no # visible problems, the sound file optionally specified by # 'normal_sound' variable will be played. # # # <varname>=<sound_file> # # Note: All audio files must be placed in the /media subdirectory # under the HTML path (i.e. /usr/local/nagios/share/media/). #host_unreachable_sound=hostdown.wav #host_down_sound=hostdown.wav #service_critical_sound=critical.wav #service_warning_sound=warning.wav #service_unknown_sound=warning.wav #normal_sound=noproblem.wav # DG EXTENDED DATA # Note: These config directives are only used if you compiled # in database support for extended data! # The user you specify here only needs SELECT privileges on the # 'hostextinfo' table in the database. xeddb_host=localhost xeddb_port=3306 xeddb_database=nagios xeddb_username=nagios xeddb_password=nagios # DB STATUS DATA (Read-Only For CGIs) # Note: These config directives are only used if you compiled # in database support for status data! # The user you specify here only needs SELECT privileges on the # 'programstatus', 'hoststatus', and 'servicestatus' tables # in the database, as these values are only used by the CGIs. # The core program will read the directives you specify in # in a resource file. xsddb_host=localhost xsddb_port=3306 xsddb_database=nagios xsddb_username=nagios xsddb_password=nagios # DB COMMENT DATA (Read-Only For CGIs) # Note: These config directives are only used if you compiled # in database support for comment data! # The user you specify here only needs SELECT privileges on the # 'hostcomments', and 'servicecomments' tables in the database, # as these values are only used by the CGIs. The core program # will read the directives you specify in a resource file. xcddb_host=localhost xcddb_port=3306 xcddb_database=nagios xcddb_username=nagios xcddb_password=nagios # DB DOWNTIME DATA (Read-Only For CGIs) # Note: These config directives are only used if you compiled # in database support for downtime data! # The user you specify here only needs SELECT privileges on the # 'hostdowntime', and 'servicedowntime' tables in the database, # as these values are only used by the CGIs. The core program # will read the directives you specify in a resource file. xdddb_host=localhost xdddb_port=3306 xdddb_database=nagios xdddb_username=nagios xdddb_password=nagios nagios@argus:/usr/local/nagios/etc$ </div> </body> </html>