12/14/2023 0 Comments Dcommands def![]() ![]() A word of caution about doing this, however. Note: If you do not specify anĪddress directive in a host definition, the name of the host will be When used properly, the $HOSTADDRESS$ macro Services are not available this could cause problems. Use a FQDN to identify the host instead of an IP address, but if DNS (so long as it can be used to check the status of the host). This is an IP address, although it could really be anything you want This directive is used to define the address of the host. When used properly, the $HOSTALIAS$ macro will contain this alias/description. It is provided in order to allow you to more easily identify a particular host. This directive is used to define a longer name or description used to identify the host. When used properly, the $HOSTNAME$ macro will contain this short name. Hosts can have multiple services (which are monitored) associated with them. It is used in host group and service definitions to reference this particular host. This directive is used to define a short name used to identify the host. Note: Directives in red are required, while those in black are optional. This can be useful when certain objects are dynamic but need to pull in a number of configs or when certain configs files grow to an unmanageable size.Įxtended host information definitions (Deprecated)Įxtended service information definitions (Deprecated)Ī host definition is used to define a physical server, workstation, device, etc. an object definition file included from the main configuration file with a cfg_file= or cfg_dir= directive can use include_file= or include_dir= to include another object definition file, which in turn can also use include_file= or include_dir= to include yet another object definition file, and so on. They are closely related to the cfg_file= and cfg_dir= directives in the main configuration file. The directives are not allowed within the actual definition of an object, and should appear before, after, or in between any object definitions. These directives may be repeated to include multiple files/directories. cfg extension in the directory specified. The former includes the single file specified, the latter will process all files ending in the. Note: Sample object configuration files are installed in the /usr/local/nagios/etc/ directory when you follow the quickstart installation guide.įile Inclusions, Cascading Configs, and the 'include_file' DirectiveĪn object definition file can include other object definition files with the use of the include_file= and include_dir= directives. 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. 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. 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. ![]() Object directives that can exhibit this behavior are marked with an asterisk ( *). 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. Inquire today and let our Quickstart team help you get started with Nagios XI ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |