Program Description

• Prerequisites
• Minimum Requirements
• Product Objectives
• Product Support

Monarch Overview

• Architectural View of Monarch
• Structure of Monarch Concepts
• Monarch User Interface

Monarch Setup Procedures

• Setting Up An Existing Installation
• Setting Up A New Installation

Monarch How-To's

• How Do I Import An Existing Nagios Configuration?
• How Do I Create A New Host?
• How Do I Create A New Service?
• How Do I Add Services To A Host?
• How Do I Create A Service Profile?
• How Do I Create A Host Profile?
• How Do I Setup Dependencies?
• How Do I Setup Notifications?
• How Do I Setup Escalations?
• How Do I Run Commit?

Program Description

The GroundWork Monitor Architect (Monarch) is a program for use in the deployment of the Nagios monitoring component of GroundWork Monitoring. The Monarch web interface consists of a set of tools that allow a user to easily configure and maintain the GroundWork Monitor System. A user can apply templates to the input to generate a set of Nagios configuration files and add or delete configuration options direct from this web interface.

GroundWork Monitor Architect is a component of GroundWork Monitor, GroundWork's open source IT infrastructure monitoring solution. GroundWork Monitor delivers enterprise-class availability and performance monitoring for a fraction of the cost of commercial alternatives. For more information about GroundWork Monitor, please visit www.itgroundwork.com.

Prerequisites

• GroundWork Monitor 3.x or higher
• Or pre-installed software
  • Nagios 1.2 (Nagios 2.0 supported in future version)
  • MySQL 4.1
  • Perl Modules:
    XML-LibXML-Common-0.13
    XML-NamespaceSupport-1.08
    XML-SAX-0.12
    XML-LibXML-1.58
    CGI.pm-3.07
    DBI-1.48
    DBD-mysql-2.9005
    File::Copy

Minimum Requirements

Basic set of Nagios files to include:

• nagios.cfg
• cgi.cfg
• resource.cfg

Product Objectives

• Provide a tool to allow users to easily create and modify GroundWork Monitor/Nagios configuration files.
• Utilize a template oriented configuration thorough extensive use of templates.
• Enable all functions via a web browser interface.
• Support most GroundWork Monitor/Nagios configuration options.

Product Support

• For product support, please email us at: [email protected].
• Professional Product support is available through a GroundWork subscription agreement.
• Monarch was written by Scott Parris of GroundWork Open Source Solutions.
• Information on directives outside the scope of this document can be found in the Nagios Documentation.
• This document is best printed using landscape orientation.

Monarch Overview

Architectural View of Monarch

Monarch is a set of .cgi scripts written in Perl. The three major functions of Monarch are:

• Design which lets you create the configuration files. If you are starting from scratch and in the process of building a new configuration for the GroundWork Monitor you will spend time here creating elements that Monarch uses.
• Manage allows you to modify existing configurations.
• Control allows you to access administration functions such as managing User IDs. You can control the implementation including the loading of Monarch, running of a Pre Flight Test (a verification of the Nagios configuration) and commit files into your production configuration using the Monarch Commit option.

When performing a load operation all of the Nagios config files get loaded into the MySQL Monarch Database, mirroring the entire configuration in the database. Monarch then operates by manipulating this database.

In addition to the Nagios configuration information there are extra data structures that Monarch uses to add functionality, such as; Host and Service Profiles, Escalation Trees, and Monarch Access Rights.

Once you are finished making modifications, you can execute the Pre Flight Test, which is the equivalent of the nagios -v command. This will verify the configuration, and will write the updated nagios configuration files into a Workspace Directory. At this point your current Nagios configuration has still not been affected. You can look at the config files and manually manipulate them if you prefer to.

Monarch gives you the capability to commit the files into your production configuration if you choose to. Commit will: 1) make a backup of your old configuration; 2) Put it into a separate backup directory; 3) Copy the updated configuration files back into your production nagios/etc directory; and 4) Perform a nagios restart thus activating the configuration.

In summary, Monarch provides options for controlling your production configuration. If you just want to see the new changes, you can keep the changed files in your Workspace Directory. Alternatively, the Monarch Commit option provides the option to implement the changes you make.

Structure of Monarch Concepts

Hosts and Services

With Nagios, you can define templates. When defining, for example a Host, you would enter the common definitions in a Host Template. To define a specific Host, you apply the definition using a Template. This is a method that Nagios uses to reduce the number of repetitive entries in its object definitions. You would define Service Templates the same way and apply them when you define Services. A Host, when fully implemented, has a Host Template, a unique Host Definition, and Services. Services have Service Templates and Service Definitions. Monarch takes this concept one step further.

Service Names

Monarch introduces a concept called a Service Name, which is a combination of a Service Template and a Service Definition. The Service Name is generic which means it has not yet been applied to a specific Host. It contains all the information except the Host name. Monarch creates Service Names out of all defined Services when you import your existing nagios configuration.

Service Profiles

Once you have a Service Name you can define a Service Profile. A Service Profile is a collection of multiple Service Names. Here is an example:

You have a web server on which you will want to monitor CPU, memory, disk, http, and apache processes. You will have 50 of these web servers. Instead of creating 50 definitions you would create a Service Name for each of the Services (CPU, memory, disk). You can then create a Service Profile called web monitoring and include all of the Service Names in the Service Profile. You would then associate this Service Profile with each of the 50 servers. Monarch does this with a Host Profile.

Host Profiles

Once you have the Service Profiles defined you can combine them with a Host Template and create a Host Profile. These Profiles are not associated with a specific Host. Once you have the Host Profile you can apply this combined definition to each of your 50 specific web servers. This concept will allow you to generically define the different roles of the different devices you are monitoring and easily apply them.

Application of Host Profiles

Once the above steps are complete, if you want to change one of the parameters and apply it to all 50 of your web servers, you can make a change to either the Host Profile, the Service Profile, or in the Service Name, which will then be applied to all 50 web servers.

Monarch's User Interface

When you start Monarch you will see the Design, Manage, and Control options. Each of the option's elements are listed below (the Overview tab displays this documentation).

Monarch Setup Procedures

Setting Up An Existing Installation

If you are working with an existing database and only want to update the distribution follow these steps:

1. Run monarch_setup.pl.
2. In Monarch, select Control>Nagios Configuration>Load from: /etc/nagios/nagios.cfg option.
3. You can then run a Pre Flight Test or Commit.

Setting Up A New Installation

Prerequisites to installing Monarch

• MySQL 4.1
• Modules: (downloadable from CPAN)
  XML-LibXML-Common-0.13
  XML-NamespaceSupport-1.08
  XML-SAX-0.12
  XML-LibXML-1.58
  CGI.pm-3.07
  DBI-1.48
  DBD-mysql-2.9005
  File::Copy

Note: If you wish to use Monarch to run pre-flight tests, your web server account will need to be a member of the Nagios Group.

Create the database

Example

• # mysql
• Your MySQL connection ID is 4974 to server version: 4.1.9-standard.
• Type help or \h for help.
• Type \c to clear the buffer.
• mysql> create database <database name>;

Note: default = monarch

Run monarch_setup.pl

This monarch_setup.pl script will help you setup Monarch on your system. You will be prompted with the following questions: [examples are displayed in these square brackets]. Note: If you need to rerun monarch_setup.pl use monarch_setup.pl 1.

1. What is the name of the user that will have access to the database?: [root]
2. What is the password for user root to access the database: [ ]
3. What is the name of the database you will use for your Monarch installation?: [monarch]
4. Enter your web server's user account: [apache]
5. Enter your web server's user group: [apache]
6. What is your web server's document root: [/var/www/html]
7. Enter the full path of your cgi-bin directory: [/var/www/cgi-bin]
8. Enter the full installation path for Monarch: [/usr/local/groundwork/monarch]
9. Would you like to set permissions so that Monarch can read your nagios cfg files including resource.cfg?: [yes]. Note: You will need to manage this manually if your answer is no.
10. Enter the full path to your nagios.cfg file:[/etc/nagios]

Notes

Be absolutely certain these values are correct. Otherwise, permissions will be set incorrectly and Monarch will not work. Make sure you webserver user is a member of the Nagios Group. Nagios .cfgs need read/write permissions for Group and Parent directories need to be searchable (i.e. rwx) for Group.

Log into Monarch

1. In your browser enter: http:// <hostname|address>/cgi-bin/monarch.cgi.
2. Login account: super_user password: password.

Setup the nagios.cfg directory

1. In Monarch, select Control.
2. Select Setup.
3. In the Setup Options screen make sure the Nagios nagios.cfg directory is set to /etc/nagios.

Nagios configuration

1. Select Control.
2. Select Nagios Configuration.

If you already have a Nagios config and you want to import it, choose Load from: /etc/nagios/nagios.cfg to start from an existing Nagios configuration.

If you are building a Nagios config from scratch, select Set default configuration to start a new Nagios installation.

Populate the database (optional)

1. Select Control.
2. Select Load to populate the database with an existing configuration. If the parser hasn't stumbled on any anomalies, you should be good to go.

Nagios 2.0 Support

If you would like files written in the Nagios version 2.0 format, login to MySQL and issue the following statement: update setup set value = '2.x' where name = 'nagios_version'. Full Nagios 2.0 Support will be available in the near future.

Monarch How-To's

How do I import an existing Nagios Configuration?

This How To will step you through how to import an existing Nagios configuration after running the setup script. This process will warn you that it will drop all previous Nagios records from Monarch and load your etc/nagios/nagios.cfg file.

Verify Nagios directory definitions

1. Select Control.
2. Select Setup.
3. In the Setup Options screen, verify the nagios.cfg, resource file, and cgi.cfg directories.
   Note: The initial setup script should have entered the appropriate files here for you. You should not have to make changes unless you want to use a different set of files and directories.
4. Select Save to save any changes.

Drop all Nagios records and load nagios.cfg

1. Select Control.
2. Select Load.
3. In the Confirm Drop Records screen, answer Yes to the prompted question: Are you sure you want to drop all Nagios records from Monarch and load etc/nagios/nagios.cfg?
4. The load status will display and you can check refresh periodically to update the status. The import is finished when the load status indicates completed. Any error messages will be displayed in red. Not all errors mean that something is wrong, as Monarch removes parts of the existing configs that are unused. Make a note of any errors and check your configuration with the Manage screen to be sure Monarch imported everything.
5. Select Continue to return to the main screen.

How do I create a new Host in Monarch?

This How To will take you through the steps to create a new Host. You will be required to configure a Host Template, if one doesn't exist, before creating a Host. This is the minimum required configuration to add a Host. You should consider creating a Host Profile first, especially if you have several Hosts for which monitoring is the same or similar.

To create a Host you will then continue through several steps including defining Host Vitals, Host Attributes 1 and 2, and Selecting Host Services to add specific Services to this Host. A Host Template does not need to be created for each Host. Templates store common properties of Hosts which are often used over when creating new Hosts. When creating a new Host if a Host Profile is chosen the fields Parents, Host Groups, Extended Host Info, Host Escalation Tree, and Service Escalation Tree will be automatically populated and can be modified.

Verify Prerequisites

• Host Template (required)
• Host Groups (optional)
• Extended Host Info Template (optional)
• Host Escalation Tree (optional)
• Service Escalation Tree (optional)
• Service Profile (optional)

Configure a Host Template

1. Select Design.
2. Select Host Templates.
3. Select Copy from an existing Host Template or New Host Template.
4. In the Host Template Properties screen, fill in the properties.
5. Select Add to add the new Host Template.

Create a new Host - Host Vitals

1. Select Design.
2. Select Hosts.
3. Select New Host Wizard.
4. In the Host Vitals screen, enter a new Host Name.
5. Enter an Alias.
6. Enter an Address.
7. Enter a Host Profile (if one is defined).
8. Select Next to go to the Host Attributes 1 screen.

Create a New Host - Host Attributes 1

1. Select a required Host Template.
2. Add to the Host one or more Parents (optional).
3. Select a Configuration File;
   This indicates the configuration file where the Host Definition will be stored after executing a Pre Flight Test or Commit. You might want to store Hosts of different types in different files, i.e. UNIX Hosts in hosts_unix.cfg, network Hosts in hosts_network.cfg, etc. If you need to add a file to the config you can do so under the Control tab in the main window without closing the Host Wizard window.
4. Select Next to go to the Host Attributes 2 screen.

Create a New Host - Host Attributes 2 screen

1. Assign this Host one or more Host Groups;
   This directive is optional but recommended.
   Note: You will get a warning message during Commit or Pre Flight Test if a Host is not a member of any Host Group. You can define a Host Group now but it must have one or more members, so it may be better to finish with the Host first.
2. Select an Extended Host Info Template (optional).
3. Enter map coordinates for 2D and 3D Status Map Coordinates (optional).
4. Select a Host Escalation Tree; This directive is optional. Select if the escalation of Host notifications is required.
5. Select a Service Escalation Tree (optional). Select if escalation of Service Notifications for Services on this Host is required.
6. Select a Service Profile for this Host (optional). Service Profiles assign a pre-defined set of Services to a Host.
7. Select Next to go to the Select Host Services screen.

Create a New Host - Select Host Services

1. Select the Service Configuration file; This is the location where these Service Definitions will be stored.
   Note: If you selected a Service Profile in the previous page (Host Attributes 2), the Service Names in that Service Profile will show in the form.
2. Select Add to List to add Services to this Host;
   Select the Services to remove by selecting the Discard radio button. Select Services to modify by selecting the Modify radio button. Select Services to modify by selecting the Modify radio button. If you selected Modify for any Services, a form with the check command and command line for each selected Service will be displayed for modifying. If you need to change any of these definitions, use Manage>Hosts to select and modify the settings.
3. Select Next to complete the Host Wizard.
4. In the Completed screen, select Save as Profile to save this new Host as a Host Profile or select Continue to complete the definition of this Host.

How do I create a Service?

This How To will take you though several steps to create a new Service including; Adding a New Command Line, Creating a Service Template, and Creating a Service Name. You will want to create a Service Template if you are going to use common attributes for multiple Services. Service Names incorporate multiple definitions in one place.

Example:
If the command def is: $USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v USEDDISKSPACE -l $ARG1$ -w $ARG2$ -c $ARG3$ in a Service Template named check_nt_disk it translates to: check_nt_disk!C!85!95 which becomes the default Command Line value for a Service Name check_disk_c. Now, if you want to create the Service Name check_disk_d, you can select Service Template check_nt_disk, uncheck 'use template command', and replace the C parameter with D.

Add a new Command

1. Select Design.
2. Select Commands.
3. Select Copy an Existing Command or New Command;
   Note: If the command you are creating has a format similar to an existing command, or if it will be calling a plugin program with different parameters, the copy option will be easiest to use.
4. In the Command Properties screen, enter the Name for the command.
5. Select a command Type.
   For a Host or Service command, select Check
6. Enter the Command Line that will be used to execute the plugin program.
   Note: The command line should also match how it will be executed at a command prompt. You may use Nagios macros here. These are substituted by Nagios before the command is executed. Typical macros include: $HOSTADDRESS$ - the Host's IP Address; $USER1$ - the Nagios plugin directory. See the Nagios documentation for the complete list of macros.
7. Select Add to create the command.
   Note: Be sure the plugin for the command line exists in the plugin folder.

Verify Prerequisites

• Time Periods for the Check
• Time Periods for the Notification
• Event Handlers
• Check Command
• Contact Groups (required if notifications are specified)

Create a Service Template

1. Select Design.
2. Select Service Templates.
3. You have 3 options:
   Copy from an Existing Service Template an exact copy in which you can modify the settings;
   Create a New Service Template from scratch;
   Use an Existing Service Template inherits properties of the Parent Template in which you can modify the settings. The template will use the Nagios use directive for the existing template. These definitions will override the existing template.
4. In the Service Template Properties screen, enter the parameters.
5. Select Add to add the new Service Template.

Verify Prerequisites

• Time Periods for the Check
• Service Template (required)
• Check Command (required unless defined in the template)
• Service Dependency Template
• Extended Info template
• Service Escalation Trees

Creating a Service Name

1. Select Design.
2. Select Profiles.
3. Select Design/Manage Service Names.
4. Select Add New Service Name.
5. In the Service Name screen, enter the properties.
   Note: If you check the Use Template Command, the Service will use the command in the Service Template. If you change the Command in the Service Template, this will change the Command for Hosts using this Service Name Profile. If you do not check the Use Template Command, the Command Line defined in this Service Name Profile will be used.
6. Enter the Command Line that will be used to execute the plugin program.
   Note: Macros are used by the command definition. Here you enter $ARGx$ values separated by '!' Ex check_disk!75!90 for $ARG1$ $ARG2$
7. Select Save to add the new Service Name.

How do I add Services to an Existing Host?

This How To will take you though several steps to add Services to a Host including; Verifying prerequisites, Applying Services to an Existing Host, Changing a Service by applying a different Service Profile, and Changing Services by Modifying the Service definition for this Host. You can apply or modify Services for a Host while creating a new Host in the Host Wizard.

Verify Prerequisites

• Create a Service Name to add

Change a Service by applying a different Service Profile

1. Select Manage.
2. Select Hosts.
3. Select the option to find the Host:
   Find by IP address: Enter the full or partial IP address.
   Find by Host Group: Select a Host Group then a Host Name.
   Find by Host Name: Enter the full or partial Host name.
4. Select Profile.
5. You may either: Select a Host Profile in which the Service Profile associated with that Host Profile will be applied, or select a Service Profile to be applied.
6. Select Save.
   Note: You will then have the option to select Apply Profile to Host which will apply the newly saved Profile to the Host.

Change Services by modifying the Service definition for this Host

1. Select Manage.
2. Select Hosts.
3. Select the option to find the Host:
   Find by IP address: Enter the full or partial IP address.
   Find by Host Group: Select a Host Group then a Host Name.
   Find by Host Name: Enter the full or partial Host name.
4. Select Services.
5. Choose a Service and select Add Service(s).
   Note: If you have assigned Service Profiles to Hosts, you can add a Service by updating the Service Profile, then applying it to all Hosts.

How do I create a Service profile?

This How To will step you through creating a Service Profile. Service Profiles store Service Names. Once you have a Service Profile you can combine this with a Host Template and create a Host Profile.

Verify Prerequisites

• Service Names must be defined
• Service files must be defined

Add a Service Profile

1. Select Design.
2. Select Profiles.
3. Select Design/Manage Service Profiles.
4. Select Add New Profile.
5. In the Service Profile screen, enter the following:
   Service Profile Name,
   Description of the Service Profile,
   Services to include using Add and Remove
   Note: To select multiple Services Names, use the CTRL key while selecting; or to select a range, click on the first item, press the SHIFT key and select the last item.
6. Select the File where these Service Definitions will be saved.
7. Select Add to create the Service Profile.

How do I create a host profile?

This How To will step you through creating a Host Profile. Host Profiles store Host Templates and Service Profiles. Once you have a Host Profile you can apply this combined definition for example to 50 specific web servers.

Verify Prerequisites

• Service Profiles (if used)
• Host Files
• Host Templates (applied to this Host Profile)
• Host Groups (applied to this Host Profile)

Name the Profile

1. Select Design.
2. Select Profiles.
3. Select Design/Manage Host Profiles.
4. Select Add New Profile.
5. In the Host Profile screen, enter the name of the new Host Profile.
6. Select Add to add the new Host Profile and continue on to the various Host Profile screens.

Define the Profile

1. In the Host Profile screen you can define the following information under each of the displayed tabs:
   Profile: Enter the Extended Host Info Template and the Host file to store the configuration statements.
   Template: Select the Host Template to apply.
   Parents: Add the Parent Hosts.
   Host Groups: Add the Host Groups to this Host Profile.
   Escalations: Enter Host or Service Escalation Trees.
   Services: Enter Service Profile for this Host Profile.
2. Select Save to create the new Host Profile

How do I setup Dependencies?

This How To will step you through setting up Host and Service Dependencies. Host Dependencies allow you to suppress notifications for Hosts based on the status of one or more other Hosts. Service Dependencies allow you to suppress notifications and active checks of Services based on the status of one or more other Services.

Setup Host Dependencies

1. Select Design.
2. Select Host Dependencies.
3. In the Host Dependency Properties screen, select the Host.
4. Select the Parent for the Host.
5. Select the Notification Failure Criteria.
6. Select Add to create the dependency.

Setup Service Dependencies

1. Select Design.
2. Select Service Dependency Templates.
3. Select Copy from an existing Service Dependency Template or New Service Dependency Template.
4. In the Service Dependency Properties screen, select the Service Name (the Service Dependency Template).
5. Select the Execution and Notification Criteria associated with a Service Name.
6. Select Add to save the setup.

How do I setup Notifications?

This How To will review the steps to take to setup Service and Host Notifications. Since you cannot create a Service Name without specifying a Template the only place you need to go to modifiy a Notification is the Template. A change to the Notification Criteria in a Template will be carried to all Services which use the specific Template. One might also consider using a Parent Template so that these type of changes are propagated to all Templates using the Parent.

Verify Prerequisites

• Time Periods are defined
• Contacts Groups are defined

Modify the Notification parameters in the Service Template

1. Select Manage.
2. Select Service Templates.
3. Select the Service Template to modify.
4. Enable the Notifications Enabled checkbox.
5. Set the Notification Interval.
6. Select the Notification Period from the defined Time Periods.
7. Check the desired Notification Options (Unreachable, Critical, Warning and Recovery).
8. Select Contact Groups to be contacted.
9. Select Save to save the modification.

Verify prerequisites for Host Notifications

• Time Periods are defined
• Contacts Groups are defined

Modify the Notification parameters in the Host Template

1. Select Manage.
2. Select Host Templates.
3. Select the Host Template to modify.
4. Enable the Notifications Enabled checkbox.
5. Set the Notification Interval.
6. Select the Notification Period from the defined Time Periods.
7. Check the desired Notification Options (Unreachable, Critical, Warning and Recovery).

Define the Contacts in the Host Group for this Host

1. Select Manage.
2. Select Host Groups.
3. Select Host Group that contains the Host for the Notification.
4. In the Host Group Properties screen, select the Contact Groups to be used for Notifications.
5. Select Save to save the Host Group Definitions.

How do I setup Escalations?

This How To will review the steps to take to setup Escalations. For Service and Host Escalations you will first Define the Service or Host Escalation Template, Define the Service or Host Escalation Tree, and then Assign the Service or Host Escalation Tree. For Host Group Escalations you will Define the Host Group Escalation Template and then Define the Host Group Escalation Tree. Service and Host Escalations are completely optional and are used to escalate Notifications for a particular Service or Host.

Define the Service Escalation Template

1. Select Design.
2. Select Escalations.
3. Select Escalation Template.
4. Select the Escalation Type (Service).
5. Select Next to go to the Service Escalation Properties screen.
6. Enter a Name for the Escalation.
7. Select Contact Groups.
8. Assign a First Notification (a number which identifies the first notification for which this escalation is effective).
9. Assign a Last Notification (a number which identifies the last notification for which this escalation is effective).
10. Assign a Notification Interval (indicates the interval in which notifications should be made while this escalation is valid).
11. Select Add to create the escalation.

Define the Service Escalation Tree

1. Select Design.
2. Select Escalations.
3. Select Escalation Tree.
4. Select the Escalation Type (Service).
5. Enter a Name for the Escalation.
6. Select Next to go to the Design Escalation Tree screen.
7. Add an Escalation Template to this Escalation Tree
   Note: You can modify the list of Contact Groups associated with the Escalation by selecting the Modify Groups link.
8. Select Close.

Assign the Service Escalation Tree (to any of the following)

1. To a Service Name, then a Service Profile or Host Profile, then assign the Profile to Hosts using the Host Wizard or by modifying an existing Host Definition.
2. To a Host Profile, then assign the Profile to the Hosts using the Host Wizard or by modifying an Existing Host Definition.
3. To a Host Group.

Define the Host Escalation Template

1. Select Escalations.
2. Select Escalation Template.
3. Select the Escalation Type (Host).
4. Select Next to go to the Host Escalation Properties screen.
5. Enter a Name for the Escalation.
6. Select Contact Groups.
7. Assign a First Notification (a number which identifies the first notification for which this escalation is effective).
8. Assign a Last Notification (a number which identifies the last notification for which this escalation is effective).
9. Assign a Notification Interval (indicates the interval in which notifications should be made while this escalation is valid).
10. Select Add to create the escalation.

Define the Host Escalation Tree

1. Select Escalations.
2. Select Escalation Template.
3. Select the Escalation Type (Host).
4. Enter a Name for the Escalation.
5. Select Next to go to the Design Escalation Tree screen.
6. Add an Escalation Template to this Escalation Tree. Note: You can modify the list of Contact Groups associated with the Escalation by selecting the Modify Groups link.
7. Select Close.

Assign the Host Escalation Tree

1. Go to the Host Profile, then assign the Tree, then assign the Profile to Hosts using the Host Wizard or by modifying an existing Host Definition.

Define the Host Group Escalation Template

1. Select Escalations.
2. Select Escalation Template.
3. Select the Escalation Type (Host Group).
4. Select Next to go to the Host Group Escalation Properties screen.
5. Enter a Name for the Escalation.
6. Select Contact Groups.
7. Assign a First Notification (a number which identifies the first notification for which this escalation is effective).
8. Assign a Last Notification (a number which identifies the last notification for which this escalation is effective).
9. Assign a Notification Interval (indicates the interval in which notifications should be made while this escalation is valid).
10. Select Add to create the escalation.

Define the Host Group Escalation Tree

1. Select Escalations.
2. Select Escalation Template.
3. Select the Escalation Type (Host Group).
4. Enter a Name for the Escalation.
5. Select Next to go to the Design Escalation Tree screen.
6. Add an Escalation Template to this Escalation Tree
   Note: You can modify the list of Contact Groups associated with the Escalation by selecting the Modify Groups link.
7. Select Close.

How do I run a Commit?

This How To will review the steps to commit files into your production configuration using the Monarch Commit option.

Run the Commit command

1. Select Control.
2. Select Commit.
   Nagios commit results, success notes, and any errors will be displayed.
   Note: Commit creates a backup of your config and stores this in the backup directory specified in Control>Setup backup dir.