Nagios配置

目录

Object Configuration Overview 对象配置概述................................................................................... 错误！未定义书签。Object Definitions 对象定义 ............................................................................................................... 错误！未定义书签。开发相关 .............................................................................................................................................. 错误！未定义书签。

Object Configuration Overview 对象配置概述

Up To: Contents

See Also: Configuration Overview, Object Definitions

What Are Objects?什么是对象

Objects are all the elements that are involved in the monitoring and notification logic. Types of objects include: 对象是所有在监视和通知逻辑中被处理的元素。对象的类型包含：

?Services 服务

?Service Groups 服务组

?Hosts 主机

?Host Groups 主机组

?Contacts 联系人

?Contact Groups 联系人组

?Commands 命令

?Time Periods 时间段

?Notification Escalations 通知自动调整

?Notification and Execution Dependencies 通知和执行依赖

More information on what objects are and how they relate to each other can be found below. 更多关于对象是什么和对象相互之间如何关联的信息如下。

Where Are Objects Defined?什么地方定义对象

Objects can be defined in one or more configuration files and/or directories that you specify using the cfg_file and/or cfg_dir directives in the main configuration file. 对象可以在一个或多个配置文件（或者目录）中被定义，这些配置文件（或目录）使用cfg_file（或cfg_dir）在主配置文件中指定。

Tip: When you follow quickstart installation guide, several sample object configuration files are placed in /usr/local/nagios/etc/objects/. You can use these sample files to see how

object inheritance works and learn how to define your own object definitions. 提示：如果你按照快速安装向导进行安装，/usr/local/nagios/etc/objects/目录中有一些对象定义的实例文件。你可以使用这些文件来查看对象是如何继承的，学习如何定义你自己的对象。

How Are Objects Defined?对象是如何定义的？

Objects are defined in a flexible template format, which can make it much easier to manage your Nagios configuration in the long term. Basic information on how to define objects in your configuration files can be found here. 对象以一个灵活的模板格式定义，这些模板使得你在很长一个组中更容易地管理你的Nagios配置。关于怎样在你的配置文件中定义对象的基本信息可以在这里找到。

Once you get familiar with the basics of how to define objects, you should read up on object inheritance, as it will make your configuration more robust for the future. Seasoned users can exploit some advanced features of object definitions as described in the documentation on object tricks. 你熟悉了基本对象的定义后，就可以了解对象继承。它会使你的配置在以后更强健。老用户可以利用一些对象定义的高些特性。这些说明在文档的对象技巧章节。

Objects Explained对象解释

Some of the main object types are explained in greater detail below... 下面详细解释一些主要的对象类型。

Hosts are one of the central objects in the monitoring logic.

Important attributes of hosts are as follows: 主机是监控逻辑中的

核心对象。主机重要的属性如下：

?Hosts are usually physical devices on your network (servers,

workstations, routers, switches, printers, etc). 主机通常是

网络中的一个物理的设备（服务器，工作站，路由器，交换机，打

印机等）。

?Hosts have an address of some kind (e.g. an IP or MAC address).

主机会有某种类型的地址（如IP，MAC）

?Hosts have one or more more services associated with them. 主

机有一个或多个服务与之相关联

?Hosts can have parent/child relationships with other hosts,

often representing real-world network connections, which is

used in the network reachability logic. 主机与其它主机存在

父子关系，这种父子关系通常代表真实网络中的连接，这些连接在

网络可达性逻辑中会用到。

Host Groups are groups of one or more hosts. Host groups can make

it easier to (1) view the status of related hosts in the Nagios web

interface and (2) simplify your configuration through the use of

object tricks . 主机组是一个或多个主机的组。主机组可以简化以下操

作：1）在Nagios的web接口中查看相关联的主机状态2）通过对象技巧简

化你的配置过程

Services are one of the central objects in the monitoring logic.

Services are associated with hosts and can be: 服务是监控逻

辑中的重要对象。服务与主机关联并且可以是：

?Attributes of a host (CPU load, disk usage, uptime, etc.)

主机的某个属性（CPU占用，磁盘使用，运行时间）

?Services provided by the host (HTTP, POP3, FTP, SSH, etc.)

服务由主机提供（HTTP，POP3，FTP，SSH等）

?Other things associated with the host (DNS records, etc.)

其它与主机相关的事物（DNS记录等）

Service Groups are groups of one or more services. Service groups

can make it easier to (1) view the status of related services

in the Nagios web interface and (2) simplify your configuration

through the use of object tricks. 服务组是一个或多个服务的组。

服务组可以使得以下操作更简单1）在Nagios的WEB界面中查看相关

联的服务2）通过对象技巧简化配置的过程

Contacts are people involved in the notification process: 联系人是在通

知处理中涉及的人

?Contacts have one or more notification methods (cellphone, pager, email, instant messaging, etc.) 联系人有一个或多个通知方式（手机，

页面，邮件，即时通讯等）

?Contacts receive notifications for hosts and service they are responsible for 联系人接收他们负责的主机和服务的通知

Contact Groups are groups of one or more contacts. Contact groups can make

it easier to define all the people who get notified when certain host or service problems occur. 联系人组是一个或多个联系人的组。联系人组可以简

化所有在主机或服务发生故障时被通知的人的定义

?When hosts and services can be monitored 何时主机和服务会被监控

?When contacts can receive notifications 何时联系人会接收通知

Information on how timeperiods work can be found here. 时间段的工作方式可以在这

里找到。

Commands are used to tell Nagios what programs, scripts, etc. it should

execute to perform: 命令用来告诉Nagios（执行）什么程序，脚本等。它会

被执行来处理：

?Host and service checks 主机和服务检查

?Notifications 通知

?Event handlers 事件处理句柄?and more... 和更多

Object Definitions 对象定义

Up To: Contents

See Also: Object Configuration Overview, Object Tricks, Object Inheritance, Custom Object Variables

Introduction介绍

One of the features of Nagios' object configuration format is that you can create object definitions that inherit properties from other object definitions. An explanation of how object inheritence works can be found here. I strongly suggest that you familiarize yourself with object inheritence once you read over the documentation presented below, as it will make the job of creating and maintaining object definitions much easier than it otherwise would be. Also, read up on the object tricks that offer shortcuts for otherwise tedious configuration tasks. Nagios的对象配置格式的其中一个特点是你可以通过继承其它对象定义属性来创建对象定义。对象定义如何工作可以在这里找到。本人强烈建议你先熟悉对象继承再继续下面的文档阅读。这样可以使你创建和维护对象定义的工作变得简化。同时，读一下对象技巧。对象技巧为其它冗长的配置任务提供了捷径。

When creating and/or editing configuration files, keep the following in mind: 当创建和（或）编辑配置文件，请记住以下：

1.Lines that start with a '#' character are taken to be comments and are not processed

以#开关的行为注释，它不会被执行

2.Directive names are case-sensitive 指令名是大小写敏感的

3.Characters that appear after a semicolon (;) in configuration lines are treated as

comments and are not processed 分号;之后的配置行内容为注释将不被执行

Retention Notes

It is important to point out that several directives in host, service, and contact definitions may not be picked up by Nagios when you change them in your configuration files. Object directives that can exhibit this behavior are marked with an asterisk (*). The reason for this

behavior is due to the fact that Nagios chooses to honor values stored in the state retention file over values found in the config files, assuming you have state retention enabled on a program-wide basis and the value of the directive is changed during runtime with an external command. 很重要的一点必须指出的是，主机，服务和联系人定义中的一些指令可能不会被Nagios获得，当你在配置文件中改变它们。那些可能会显示出这种反应的对象指令都被*标注了。出现这种现象的原因是Nagios选择尊从于将值保存在state_retention_file中（配置文件中找到值），如果你将state_retention在一个程序宽度基础层面打开了并且在运行的过程中指令的值被一个外部程序修改了。

One way to get around this problem is to disable the retention of non-status information using the retain_nonstatus_information directive in the host, service, and contact definitions. Disabling this directive will cause Nagios to take the initial values for these directives from your config files, rather than from the state retention file when it (re)starts. 一个避免这种问题的方式是在主机，服务和联系人定义中通过设置retain_nonstatus_information项来关闭无状态的信息的保持。关闭这个指令将会导致Nagios从配置文件中为这些指令获取初始值，而不是从状态保持文件中，当它启动或重启里。

Sample Configuration Files简单配置文件

Note: Sample object configuration files are installed in the /usr/local/nagios/etc/ directory when you follow the quickstart installation guide. 注：一些对象配置文件在

/usr/local/nagios/etc/目录中可以找到，如果你按照快速安装向导安装的话。

Object Types

Host definitions

Host group definitions

Service definitions

Service group definitions

Contact definitions

Contact group definitions

Time period definitions

Command definitions

Service dependency definitions

Service escalation definitions

Host dependency definitions

Host escalation definitions

Extended host information definitions

Extended service information definitions

Host Definition 主机定义

Description: 描述

A host definition is used to define a physical server, workstation, device, etc. that resides on your network. 一个主机定义是用来定义一个物理的服务器，工作站，设备等。这些设备都在你的网络中。

Definition Format: 定义格式

Note: Directives in red are required, while those in black are optional. 注:红色为必须的，黑色为可选的

define host{

host_name host_name

alias alias

display_name display_name

address address

parents host_names

hostgroups hostgroup_names

check_command command_name

initial_state [o,d,u]

max_check_attempts #

check_interval #

retry_interval #

active_checks_enabled [0/1]

passive_checks_enabled [0/1]

check_period timeperiod_name

obsess_over_host [0/1]

check_freshness [0/1]

freshness_threshold #

event_handler command_name

event_handler_enabled [0/1]

low_flap_threshold #

high_flap_threshold #

flap_detection_enabled [0/1]

flap_detection_options [o,d,u]

process_perf_data [0/1]

retain_status_information [0/1]

retain_nonstatus_information [0/1]

contacts contacts

contact_groups contact_groups

notification_interval #

first_notification_delay #

notification_period timeperiod_name

notification_options [d,u,r,f,s]

notifications_enabled [0/1]

stalking_options [o,d,u]

notes note_string

notes_url url

action_url url

icon_image image_file

icon_image_alt alt_string

vrml_image image_file

statusmap_image image_file

2d_coords x_coord,y_coord

3d_coords x_coord,y_coord,z_coord

}

Example Definition: 定义实例

define host{

host_name bogus-router

alias Bogus Router #1

address 192.168.1.254

parents server-backbone

check_command check-host-alive

check_interval 5

retry_interval 1

max_check_attempts 5

check_period 24x7

process_perf_data 0

retain_nonstatus_information 0

contact_groups router-admins

notification_interval 30

notification_period 24x7

notification_options d,u,r

}

Directive Descriptions: 指令描述

host_name: This directive is used to define a short name used to identify

the host. It is used in host group and service definitions to

reference this particular host. Hosts can have multiple services

(which are monitored) associated with them. When used properly,

the $HOSTNAME$ macro will contain this short name. 这个指令

用来定义一个用来指定主机的短的名称。它被用在主机组和服务定义

中来引用这个特定的主机。主机可以有多个关联服务被监控。正确使

用的情况下，$HOSTNAME$宏将包含这个短的名称。

alias: This directive is used to define a longer name or description

used to identify the host. It is provided in order to allow you

to more easily identify a particular host. When used properly,

the $HOSTALIAS$ macro will contain this alias/description. 这

个指令被用来定义一个长的名称来描述指定的主机。提供它是用来允

许你更简单地识别特定主机。正确使用的情况下,$HOSTALIAS$宏包含

这个别名（或称描述）

address: This directive is used to define the address of the host.

Normally, this is an IP address, although it could really be

anything you want (so long as it can be used to check the status

of the host). You can use a FQDN to identify the host instead

of an IP address, but if DNS services are not available this could

cause problems. When used properly, the $HOSTADDRESS$ macro will

contain this address. Note: If you do not specify an address

directive in a host definition, the name of the host will be used

as its address. A word of caution about doing this, however -

if DNS fails, most of your service checks will fail because the

plugins will be unable to resolve the host name. 这个指令被

用来定义主机的地址。通常，这是一个IP地址。当然也可以是你想要

的任何值（只要它能被用来检查主机的状态）。你可以使用一个FQDN

（正式域名）代替使用ip地址来指定主机，但是如果DNS服务不可达

时这将会导致问题产生。$HOSTADDRESS$宏包含这个地址。注：如果你

在一个主机定义中不指定一个地址指令，主机的名称将被用来作为它

的地址。这种方式的一个警告：无论如何，如果DNS失败了，你的很

多服务将会失败，因为插件将不能处理主机名称。

display_name: This directive is used to define an alternate name that should

be displayed in the web interface for this host. If not

specified, this defaults to the value you specify for the

host_name directive. Note: The current CGIs do not use this

option, although future versions of the web interface will. 这

个指令被用来指定一个替换名称，它将会在web界面中显示来提示这

个主机。如果不指定，直接使用host_name指令。注：当前的CGI不

使用这个选项，虽然以的版本将会使用。

parents: This directive is used to define a comma-delimited list of short

names of the "parent" hosts for this particular host. Parent

hosts are typically routers, switches, firewalls, etc. that lie

between the monitoring host and a remote hosts. A router, switch,

etc. which is closest to the remote host is considered to be that

host's "parent". Read the "Determining Status and Reachability

of Network Hosts" document located here for more information.

If this host is on the same network segment as the host doing

the monitoring (without any intermediate routers, etc.) the host

is considered to be on the local network and will not have a

parent host. Leave this value blank if the host does not have

a parent host (i.e. it is on the same segment as the Nagios host).

The order in which you specify parent hosts has no effect on how

things are monitored. 这个指令用来指定一个分号分隔的特定的父

主机的短名称。父主机一般为路由器，交换机，防火墙等。它们都位

于监控主机和远端主机之间。这些路由器，交换机等距离远端主机最

近的即为主机的父。读xxxxxx文档来获取更多信息。如果这个主机和

监控主机在同一个网络（没有中间路由器），那么这个主机将没有父

主机。如果主机没有父主机这项留空。你所指定的父主机对如何监控

主机没有影响。

hostgroups: This directive is used to identify the short name(s) of the

hostgroup(s) that the host belongs to. Multiple hostgroups

should be separated by commas. This directive may be used as an

alternative to (or in addition to) using the members directive

in hostgroup definitions. 这个指令被用来指定主机所属的主机组

的短名称。多个主机组可以以逗号分隔。这个指令可以被用来作为主

机组中的members指令的一个替代。

check_command: This directive is used to specify the short name of the command

that should be used to check if the host is up or down. Typically,

this command would try and ping the host to see if it is "alive".

The command must return a status of OK (0) or Nagios will assume

the host is down. If you leave this argument blank, the host will

not be actively checked. Thus, Nagios will likely always assume

the host is up (it may show up as being in a "PENDING" state in

the web interface). This is useful if you are monitoring printers

or other devices that are frequently turned off. The maximum

amount of time that the notification command can run is

controlled by the host_check_timeout option. 这个指令用来指定

一个命令，这个命令用来检测该主机是否启动。通常，这个命令会试

着ping该主机来检查主机是否牌活动状态。这个命令必须返回一个状

态0，否则Nagios假设主机处于关机状态。如果你把这个参数留空，

主机将不会被动态检测。这样一来，Nagios会认为主机一直处于运行

状态（它也可能会在web界面中显示为PENDING状态）。它对于像打

印机或其它经常关闭的设备的监控非常有用。通知命令的最大可运行

时间由host_check_timeout选项控制。

initial_state: By default Nagios will assume that all hosts are in UP states

when it starts. You can override the initial state for a host

by using this directive. Valid options are: o = UP, d = DOWN,

and u = UNREACHABLE. Nagios在启动时默认假设所有主机都为启动

状态。你可以使用这个指令重写这个初始状态。可用的选项是o= UP,

d = DOWN, u = UNREACHABLE

max_check_attempts: This directive is used to define the number of times that Nagios

will retry the host check command if it returns any state other

than an OK state. Setting this value to 1 will cause Nagios to

generate an alert without retrying the host check. Note: If you

do not want to check the status of the host, you must still set

this to a minimum value of 1. To bypass the host check, just leave

the check_command option blank. 这个指令被用来定义主机检测命

令的重试次数，如果它返回一个非OK的状态的话。设置这个值为1

将会导致Nagios在不重试的情况下产生一个警告。注：如果你不想检

查主机的状态，你必须保持这个设置为最小值1.要绕过主机检测，请

保持check_command选项为空。

check_interval: This directive is used to define the number of "time units"

between regularly scheduled checks of the host. Unless you've

changed the interval_length directive from the default value of

60, this number will mean minutes. More information on this value

can be found in the check scheduling documentation. 这个指令

用来定义一个时间单位的数量（来指定时间），在这个时间内定期执

行检测主机操作。如果你没有修改interval_length指令的默认值60，

这个数量代表多少分钟。

retry_interval: This directive is used to define the number of "time units" to

wait before scheduling a re-check of the hosts. Hosts are

rescheduled at the retry interval when they have changed to a

non-UP state. Once the host has been retried max_check_attempts

times without a change in its status, it will revert to being

scheduled at its "normal" rate as defined by the check_interval

value. Unless you've changed the interval_length directive from

the default value of 60, this number will mean minutes. More

information on this value can be found in the check scheduling

documentation. 这个指令被用来定义等待重新检测主机的时间单位

数量。当主机状态变为一个非启动状态时，主机会被计划一个重试定

时。当主机被重试次数达到max_check_attempts而主机的状态仍然没

有改变，它将会切换到一个由check_interval指定的计划任务在它的

normal级别。如果你没有修改interval_length指令的默认值60，这

个值代表分钟数。

active_checks_enabled *: This directive is used to determine whether or not active checks

(either regularly scheduled or on-demand) of this host are

enabled. Values: 0 = disable active host checks, 1 = enable

active host checks (default). 这个指令用来决定主动主机检查

（无论是定期任务还是基于询问的）是否开启。

passive_checks_enabled *: This directive is used to determine whether or not passive checks

are enabled for this host. Values: 0 = disable passive host

checks, 1 = enable passive host checks (default). 被动主机检

测

check_period: This directive is used to specify the short name of the time

period during which active checks of this host can be made. 主

动检测被构造的时间。

obsess_over_host *: This directive determines whether or not checks for the host will

be "obsessed" over using the ochp_command.

check_freshness *: This directive is used to determine whether or not freshness

checks are enabled for this host. Values: 0 = disable freshness

checks, 1 = enable freshness checks (default).

freshness_threshold: This directive is used to specify the freshness threshold (in

seconds) for this host. If you set this directive to a value of

0, Nagios will determine a freshness threshold to use

automatically. ？

event_handler: This directive is used to specify the short name of the command

that should be run whenever a change in the state of the host

is detected (i.e. whenever it goes down or recovers). Read the

documentation on event handlers for a more detailed explanation

of how to write scripts for handling events. The maximum amount

of time that the event handler command can run is controlled by

the event_handler_timeout option. 这个指令用来指定一个命令的

短名字，这个命令会在主机状态被改变时运行（无论是主机down掉或

恢复）。命令的超时时间由event_handler_timeout选项控制。event_handler_enabled *: This directive is used to determine whether or not the event

handler for this host is enabled. Values: 0 = disable host event

handler, 1 = enable host event handler. 这个指令用来决定这个

主机的事件处理是否被启用。0不起用，1起用。

low_flap_threshold: This directive is used to specify the low state change threshold

used in flap detection for this host. More information on flap

detection can be found here. If you set this directive to a value

of 0, the program-wide value specified by the

low_host_flap_threshold directive will be used. 这个指令用来

指定一个抖动检测的最小阀值。如果指定该值为0，则使用程序级的

low_host_flap_threshold指令值。

high_flap_threshold: This directive is used to specify the high state change threshold

used in flap detection for this host. More information on flap

detection can be found here. If you set this directive to a value

of 0, the program-wide value specified by the

high_host_flap_threshold directive will be used. 同上。指定

最大值。

flap_detection_enabled *: This directive is used to determine whether or not flap detection

is enabled for this host. More information on flap detection can

be found here. Values: 0 = disable host flap detection, 1 = enable

host flap detection. 是否启用抖动检测

flap_detection_options: This directive is used to determine what host states the flap

detection logic will use for this host. Valid options are a

combination of one or more of the following: o = UP states, d

= DOWN states, u = UNREACHABLE states. 这个指令用来决定该主

机的flap_detection_logic将使用的主机状态。o = UP states, d =

DOWN states, u = UNREACHABLE states.

process_perf_data *: This directive is used to determine whether or not the processing

of performance data is enabled for this host. Values: 0 = disable

performance data processing, 1 = enable performance data

processing. 这个指令用来决定主机是否使用性能处理数据。0为禁

用性能数据处理，1为启用。

retain_status_information: This directive is used to determine whether or not

status-related information about the host is retained across

program restarts. This is only useful if you have enabled state

retention using the retain_state_information directive. Value:

0 = disable status information retention, 1 = enable status

information retention. 这个指令用来决定程序重启时是否保持主

机状态相关信息。这一项只有使用retain_state_information指令启

用了状态保持时才可用。0为禁用，1为启用

retain_nonstatus_information: This directive is used to determine whether or not non-status

information about the host is retained across program restarts.

This is only useful if you have enabled state retention using

the retain_state_information directive. Value: 0 = disable

non-status information retention, 1 = enable non-status

information retention. 这个指令用来决定当程序重启时是否保持

主机的非状态信息。这一项只有使用retain_state_information指令

启用了状态保持时才可用。0为禁用，1为启用

contacts: This is a list of the short names of the contacts that should

be notified whenever there are problems (or recoveries) with

this host. Multiple contacts should be separated by commas.

Useful if you want notifications to go to just a few people and

don't want to configure contact groups. You must specify at least

one contact or contact group in each host definition. 这是一

个列表，当主机出现问题或恢复时通知的列表中的联系人。多个联系

人用逗号分隔。如果不想配置contact_groups选项或者要通知很少部

分人的情况下这个指令很有用。在每个主机定义中，你必须为主机指

定至少一个联系人或联系人组。

contact_groups: This is a list of the short names of the contact groups that

should be notified whenever there are problems (or recoveries)

with this host. Multiple contact groups should be separated by

commas. You must specify at least one contact or contact group

in each host definition. 主机出问题或恢复时通知的联系人组。多

个联系人组用逗号分隔。每个主机至少指定一个联系人或联系人组。notification_interval: This directive is used to define the number of "time units" to

wait before re-notifying a contact that this service is still

down or unreachable. Unless you've changed the interval_length

directive from the default value of 60, this number will mean

minutes. If you set this value to 0, Nagios will not re-notify

contacts about problems for this host - only one problem

notification will be sent out.

first_notification_delay: This directive is used to define the number of "time units" to

wait before sending out the first problem notification when this

host enters a non-UP state. Unless you've changed the

interval_length directive from the default value of 60, this

number will mean minutes. If you set this value to 0, Nagios will

start sending out notifications immediately.

notification_period: This directive is used to specify the short name of the time

period during which notifications of events for this host can

be sent out to contacts. If a host goes down, becomes

unreachable, or recoveries during a time which is not covered

by the time period, no notifications will be sent out. notification_options: This directive is used to determine when notifications for the

host should be sent out. Valid options are a combination of one

or more of the following: d= send notifications on a DOWN state,

u = send notifications on an UNREACHABLE state, r = send

notifications on recoveries (OK state), f= send notifications

when the host starts and stops flapping, and s = send

notifications when scheduled downtime starts and ends. If you

specify n(none) as an option, no host notifications will be sent

out. If you do not specify any notification options, Nagios will

assume that you want notifications to be sent out for all

possible states. Example: If you specify d,r in this field,

notifications will only be sent out when the host goes DOWN and

when it recovers from a DOWN state.

notifications_enabled *: This directive is used to determine whether or not notifications

for this host are enabled. Values: 0 = disable host

notifications, 1 = enable host notifications.

stalking_options: This directive determines which host states "stalking" is

enabled for. Valid options are a combination of one or more of

the following: o= stalk on UP states, d= stalk on DOWN states,

and u = stalk on UNREACHABLE states. More information on state

stalking can be found here.

notes: This directive is used to define an optional string of notes

pertaining to the host. If you specify a note here, you will see

the it in the extended information CGI (when you are viewing

information about the specified host).

notes_url: This variable is used to define an optional URL that can be used

to provide more information about the host. If you specify an

URL, you will see a red folder icon in the CGIs (when you are

viewing host information) that links to the URL you specify here.

Any valid URL can be used. If you plan on using relative paths,

the base path will the the same as what is used to access the

CGIs (i.e. /cgi-bin/nagios/). This can be very useful if you want

to make detailed information on the host, emergency contact

methods, etc. available to other support staff.

action_url: This directive is used to define an optional URL that can be used

to provide more actions to be performed on the host. If you

specify an URL, you will see a red "splat" icon in the CGIs (when

you are viewing host information) that links to the URL you

specify here. Any valid URL can be used. If you plan on using

relative paths, the base path will the the same as what is used

to access the CGIs (i.e. /cgi-bin/nagios/).

icon_image: This variable is used to define the name of a GIF, PNG, or JPG

image that should be associated with this host. This image will

be displayed in the various places in the CGIs. The image will

look best if it is 40x40 pixels in size. Images for hosts are

assumed to be in the logos/ subdirectory in your HTML images

directory (i.e. /usr/local/nagios/share/images/logos).

icon_image_alt: This variable is used to define an optional string that is used

in the ALT tag of the image specified by the

argument.

vrml_image: This variable is used to define the name of a GIF, PNG, or JPG

image that should be associated with this host. This image will

be used as the texture map for the specified host in the statuswrl

CGI. Unlike the image you use for the variable, this

one should probably not have any transparency. If it does, the

host object will look a bit wierd. Images for hosts are assumed

to be in the logos/ subdirectory in your HTML images directory

(i.e. /usr/local/nagios/share/images/logos).

statusmap_image: This variable is used to define the name of an image that should

be associated with this host in the statusmap CGI. You can

specify a JPEG, PNG, and GIF image if you want, although I would

strongly suggest using a GD2 format image, as other image formats

will result in a lot of wasted CPU time when the statusmap image

is generated. GD2 images can be created from PNG images by using

the pngtogd2utility supplied with Thomas Boutell's gd library.

The GD2 images should be created in uncompressed format in order

to minimize CPU load when the statusmap CGI is generating the

network map image. The image will look best if it is 40x40 pixels

in size. You can leave these option blank if you are not using

the statusmap CGI. Images for hosts are assumed to be in the

logos/ subdirectory in your HTML images directory (i.e.

/usr/local/nagios/share/images/logos).

2d_coords: This variable is used to define coordinates to use when drawing

the host in the statusmap CGI. Coordinates should be given in

positive integers, as they correspond to physical pixels in the

generated image. The origin for drawing (0,0) is in the upper

left hand corner of the image and extends in the positive x

direction (to the right) along the top of the image and in the

positive y direction (down) along the left hand side of the

image. For reference, the size of the icons drawn is usually

about 40x40 pixels (text takes a little extra space). The

coordinates you specify here are for the upper left hand corner

of the host icon that is drawn. Note: Don't worry about what the

maximum x and y coordinates that you can use are. The CGI will

automatically calculate the maximum dimensions of the image it

creates based on the largest x and y coordinates you specify. 3d_coords: This variable is used to define coordinates to use when drawing

the host in the statuswrl CGI. Coordinates can be positive or

negative real numbers. The origin for drawing is (0.0,0.0,0.0).

For reference, the size of the host cubes drawn is 0.5 units on

each side (text takes a little more space). The coordinates you

specify here are used as the center of the host cube.

Host Group Definition

Description:

A host group definition is used to group one or more hosts together for simplifying configuration with object tricks or display purposes in the CGIs.

Definition Format:

Note: Directives in red are required, while those in black are optional.

define hostgroup{

hostgroup_name hostgroup_name

alias alias

members hosts

hostgroup_members hostgroups

notes note_string

notes_url url

action_url url

}

Example Definition:

define hostgroup{

hostgroup_name novell-servers

alias Novell Servers

members netware1,netware2,netware3,netware4

}

Directive Descriptions:

hostgroup_name: This directive is used to define a short name used to identify the host group. alias: This directive is used to define is a longer name or description used to identify the host group. It is provided in order to allow you to more easily

identify a particular host group.

members: This is a list of the short names of hosts that should be included in this group. Multiple host names should be separated by commas. This directive

may be used as an alternative to (or in addition to) the hostgroups directive

in host definitions.

hostgroup_members: This optional directive can be used to include hosts from other "sub" host groups in this host group. Specify a comma-delimited list of short names

of other host groups whose members should be included in this group. notes: This directive is used to define an optional string of notes pertaining to the host. If you specify a note here, you will see the it in the extended

information CGI (when you are viewing information about the specified host). notes_url: This variable is used to define an optional URL that can be used to provide more information about the host group. If you specify an URL, you will see

a red folder icon in the CGIs (when you are viewing hostgroup information)

that links to the URL you specify here. Any valid URL can be used. If you

plan on using relative paths, the base path will the the same as what is

used to access the CGIs (i.e. /cgi-bin/nagios/). This can be very useful

if you want to make detailed information on the host group, emergency contact

methods, etc. available to other support staff.

action_url: This directive is used to define an optional URL that can be used to provide more actions to be performed on the host group. If you specify an URL, you

will see a red "splat" icon in the CGIs (when you are viewing hostgroup

information) that links to the URL you specify here. Any valid URL can be

used. If you plan on using relative paths, the base path will the the same

as what is used to access the CGIs (i.e. /cgi-bin/nagios/).

Service Definition

Description:

A service definition is used to identify a "service" that runs on a host. The term "service" is used very loosely. It can mean an actual service that runs on the host (POP, SMTP, HTTP, etc.) or some other type of metric associated with the host (response to a ping, number of logged in users, free disk space, etc.). The different arguments to a service definition are outlined below.

Definition Format:

Note: Directives in red are required, while those in black are optional.

define service{

host_name host_name

hostgroup_name hostgroup_name

service_description service_description

display_name display_name

servicegroups servicegroup_names

is_volatile [0/1]

check_command command_name

initial_state [o,w,u,c]

max_check_attempts #

check_interval #

retry_interval #

active_checks_enabled [0/1]

passive_checks_enabled [0/1]

check_period timeperiod_name

obsess_over_service [0/1]

check_freshness [0/1]

freshness_threshold #

event_handler command_name

event_handler_enabled [0/1]

low_flap_threshold #

high_flap_threshold #

flap_detection_enabled [0/1]

flap_detection_options [o,w,c,u]

process_perf_data [0/1]

retain_status_information [0/1]

retain_nonstatus_information [0/1]

notification_interval #

first_notification_delay #

notification_period timeperiod_name

notification_options [w,u,c,r,f,s]

notifications_enabled [0/1]

contacts contacts

contact_groups contact_groups

stalking_options [o,w,u,c]

notes note_string

notes_url url

action_url url

icon_image image_file

icon_image_alt alt_string

}

Example Definition:

define service{