Notes
When creating and/or editing configuration files, keep the following in mind:
Sample Configuration
A sample CGI configuration file can be created by running the 'make config' command. The default name of the CGI configuration file is cgi.cfg.
Index
Main configuration file location
Physical HTML path
URL HTML path
Nagios process check command
Authentication usage
Default user name
System/process information access
System/process command access
Configuration information access
Global host information access
Global host command access
Global service information access
Global service command access
Statusmap CGI background image
Default statusmap layout method
Statuswrl CGI include world
Default statuswrl layout method
CGI refresh rate
Audio alerts
Ping syntax
| Main Configuration File Location |
| Format: | main_config_file=<file_name> |
| Example: | main_config_file=/usr/local/nagios/etc/nagios.cfg |
This specifies the location of your main configuration file. The CGIs need to know where to find this file in order to get information about configuration information, current host and service status, etc.
| Physical HTML Path |
| Format: | physical_html_path=<path> |
| Example: | physical_html_path=/usr/local/nagios/share |
This is the physical path where the HTML files for Nagios are kept on your workstation or server. Nagios assumes that the documentation and images files (used by the CGIs) are stored in subdirectories called docs/ and images/, respectively.
| URL HTML Path |
| Format: | url_html_path=<path> |
| Example: | url_html_path=/nagios |
If, when accessing Nagios via a web browser, you point to an URL like http://www.myhost.com/nagios, this value should be /nagios. Basically, its the path portion of the URL that is used to access the Nagios HTML pages.
| Nagios Process Check Command |
| Format: | nagios_check_command=<command_line> |
| Example: | nagios_check_command=/usr/local/nagios/libexec/check_nagios /usr/local/nagios/var/status.log 5 '/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg' |
This is an optional command that the CGIs can use to check the status of the Nagios process. This provides the CGIs (as well as yourself) with some idea of whether or not Nagios is still running. If you do not specify a command to be run, the CGIs will assume that the Nagios process is running. If you do define a process check command, it should follow the same guidelines that are required of standard plugins. If the command returns a non-OK status, the CGIs will think the Nagios process is not running and will refuse to allow you to commit any commands via the command CGI.
| Authentication Usage |
| Format: | use_authentication=<0/1> |
| Example: | use_authentication=1 |
This option controls whether or not the CGIs will use the authentication and authorization functionality when determining what information and commands users have access to. I would strongly suggest that you use the authentication functionality for the CGIs. If you decide not to use authentication, make sure to remove the command CGI to prevent unauthorized users from issuing commands to Nagios. The CGI will not issue commands to Nagios if authentication is disabled, but I would suggest removing it altogether just to be on the safe side. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Default User Name |
| Format: | default_user_name=<username> |
| Example: | default_user_name=guest |
Setting this variable will define a default username that can access the CGIs. This allows people within a secure domain (i.e., behind a firewall) to access the CGIs without necessarily having to authenticate to the web server. You may want to use this to avoid having to use basic authentication if you are not using a secure server, as basic authentication transmits passwords in clear text over the Internet.
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!
| System/Process Information Access |
| Format: | authorized_for_system_information=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_system_information=nagiosadmin,theboss |
This is a comma-delimited list of names of authenticated users who can view system/process information in the extended information CGI. Users in this list are not automatically authorized to issue system/process commands. If you want users to be able to issue system/process commands as well, you must add them to the authorized_for_system_commands variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| System/Process Command Access |
| Format: | authorized_for_system_commands=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_system_commands=nagiosadmin |
This is a comma-delimited list of names of authenticated users who can issue system/process commands via the command CGI. Users in this list are not automatically authorized to view system/process information. If you want users to be able to view system/process information as well, you must add them to the authorized_for_system_information variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Configuration Information Access |
| Format: | authorized_for_configuration_information=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_configuration_information=nagiosadmin |
This is a comma-delimited list of names of authenticated users who can view configuration information in the configuration CGI. Users in this list can view information on all configured hosts, host groups, services, contacts, contact groups, time periods, and commands. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Global Host Information Access |
| Format: | authorized_for_all_hosts=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_all_hosts=nagiosadmin,theboss |
This is a comma-delimited list of names of authenticated users who can view status and configuration information for all hosts. Users in this list are also automatically authorized to view information for all services. Users in this list are not automatically authorized to issue commands for all hosts or services. If you want users able to issue commands for all hosts and services as well, you must add them to the authorized_for_all_host_commands variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Global Host Command Access |
| Format: | authorized_for_all_host_commands=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_all_host_commands=nagiosadmin |
This is a comma-delimited list of names of authenticated users who can issue commands for all hosts via the command CGI. Users in this list are also automatically authorized to issue commands for all services. Users in this list are not automatically authorized to view status or configuration information for all hosts or services. If you want users able to view status and configuration information for all hosts and services as well, you must add them to the authorized_for_all_hosts variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Global Service Information Access |
| Format: | authorized_for_all_services=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_all_services=nagiosadmin,theboss |
This is a comma-delimited list of names of authenticated users who can view status and configuration information for all services. Users in this list are not automatically authorized to view information for all hosts. Users in this list are not automatically authorized to issue commands for all services. If you want users able to issue commands for all services as well, you must add them to the authorized_for_all_service_commands variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Global Service Command Access |
| Format: | authorized_for_all_service_commands=<user1>,<user2>,<user3>,...<usern> |
| Example: | authorized_for_all_service_commands=nagiosadmin |
This is a comma-delimited list of names of authenticated users who can issue commands for all services via the command CGI. Users in this list are not automatically authorized to issue commands for all hosts. Users in this list are not automatically authorized to view status or configuration information for all hosts. If you want users able to view status and configuration information for all services as well, you must add them to the authorized_for_all_services variable. More information on how to setup authentication and configure authorization for the CGIs can be found here.
| Statusmap CGI Background Image |
| Format: | statusmap_background_image=<gd2_image> |
| Example: | statusmap_background_image=statusmapbg.gd2 |
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 (preferably in uncompressed format)!
| Default Statusmap Layout Method |
| Format: | default_statusmap_layout=<layout_number> |
| Example: | default_statusmap_layout=4 |
This option allows you to specify the default layout method used by the statusmap CGI. Valid options are:
| <layout_number> Value | Layout Method |
|---|---|
| 0 | User-defined coordinates |
| 1 | Depth layers |
| 2 | Collapsed tree |
| 3 | Balanced tree |
| 4 | Circular |
| 5 | Circular (Marked Up) |
| 6 | Circular (Balloon) |
| Statuswrl CGI Include World |
| Format: | statuswrl_include=<vrml_file> |
| Example: | statuswrl_include=myworld.wrl |
This option allows you to include your own objects in the generated VRML world. It is assumed that the file resides in the path specified by the physical_html_path directive. Note: This file must be a fully qualified VRML world (i.e. you can view it by itself in a VRML browser).
| Default Statuswrl Layout Method |
| Format: | default_statuswrl_layout=<layout_number> |
| Example: | default_statuswrl_layout=4 |
This option allows you to specify the default layout method used by the statuswrl CGI. Valid options are:
| <layout_number> Value | Layout Method |
|---|---|
| 0 | User-defined coordinates |
| 2 | Collapsed tree |
| 3 | Balanced tree |
| 4 | Circular |
| CGI Refresh Rate |
| Format: | refresh_rate=<rate_in_seconds> |
| Example: | refresh_rate=90 |
This option allows you to specify the number of seconds between page refreshes for the status, statusmap, and extinfo CGIs.
| Audio Alerts |
| Formats: |
host_unreachable_sound=<sound_file> host_down_sound=<sound_file> service_critical_sound=<sound_file> service_warning_sound=<sound_file> service_unknown_sound=<sound_file> |
| Examples: |
host_unreachable_sound=hostu.wav host_down_sound=hostd.wav service_critical_sound=critical.wav service_warning_sound=warning.wav service_unknown_sound=unknown.wav |
These options allow you to specify an audio file that should be played in your browser if there are problems when you are viewing the status CGI. If there are problems, the audio file for the most critical type of problem will be played. The most critical type of problem is on or more unreachable hosts, while the least critical is one or more services in an unknown state (see the order in the example above). Audio files are assumed to be in the media/ subdirectory in your HTML directory (i.e. /usr/local/nagios/share/media).
| Ping Syntax |
| Format: | ping_syntax=<command> |
| Example: | ping_syntax=/bin/ping -n -U -c 5 $HOSTADDRESS$ |
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.