Getting Started with GroundWork Monitor

1. Getting Started with GroundWork Monitor GroundWork Monitor Enterprise Edition 6.2

2. Getting Started with GroundWork Monitor Course Objectives for this Module Configuration • Nagios Configuration Schema • Configuration Tool Overview • Setting Up Hosts

3. GroundWork Monitor Enterprise Edition 6.2Module 3 : Configuration

4. Configuration Nagios Configuration Objects • Nagios is configured from a set of configuration files • The main configuration file (nagios.cfg) contains the global settings for the Nagios application • Ancillary files called the object files contain the configuration objects which describe the monitoring configuration • These object files are comprised of data structures called configuration objects: define host { host_namelocalhost alias Linux Server #1 address 127.0.0.1 use generic-host check_command check-host-alive max_check_attempts 10 notification_interval 480 } define host { name generic-host process_perf_data 1 retain_status_information 1 flap_detection_enabled 1 retain_nonstatus_information 1 active_checks_enabled 1 passive_checks_enabled 1 check_period 24x7 obsess_over_host 0 check_freshness 0 check_command check-host-alive max_check_attempts 3 check_interval 0 event_handler_enabled 1 notifications_enabled 1 notification_interval 60 notification_period 24x7 notification_optionsd,u,r contact_groupsnagiosadmin register 0 }

5. Configuration Nagios Configuration Objects • Nagios is an extremely flexible framework that is controlled through its configuration objects • Nagios configuration objects can be in one file or spread across multiple files • They are comprised of directives (label=value pairs) • They are structured objects and can inherit directives from other Nagios objects (i.e. templates) • They are relational (i.e. hosts incorporate services and services incorporate commands) • They can describe devices (hosts) • They can define relationships (dependencies or groups) • They can control procedures (escalations or event handlers) • They can be used to control UI behavior (extended info) • They define how devices will be checked (services, commands)

6. Configuration Nagios Configuration Object Relationships Templates Any Nagios Object Host Dependencies Host Extended Info Hosts Host Groups Host Escalations Contact Groups Contacts Service Escalations Service Extended Info Services Service Groups Hosts Services Contacts Host Escalations Service Escalations Service Dependencies Timeperiods Commands

7. Configuring Hosts and Services Rationale Behind the Monarch Design • Host Deletion Example • When a host is retired from the network it will cause Host Alarms in Nagios, so it must be removed from Nagios • One could start by deleting the host object for that host in the hosts.cfg file • Then the preflight check would fail because services.cfg contains service objects referencing the missing host • If the service objects are then located and deleted, there will still broken service dependency objects • So one would need to delete all service dependencies referencing services deleted because the host went away • Then there would still be references to the host in hostgroups which would cause preflight failures • There could also be residual extended_host_info objects referencing the host • And extended_service_info objects referencing each of the deleted services • What is needed is a tool that understands not only the configuration data and object syntax but the relationships

8. Configuration Tool Overview Architectural View of Monarch Configuration UI Hosts, Services, Contacts, Escalations Etc. Monarch DB Nagios configuration objects Database Tables | Relationships hosts hosts services services contacts contacts escalations escalations Nagios Configuration files

9. Configuration Tool Overview Architectural View of Monarch Configuration UI Services, Profiles, Hosts, Contacts, Escalations, Commands, Time Periods, Groups, Control, Tools Nagios configuration files nagios/etc Workspace directory M Pre Flight Test Monarch DB Hosts, Services, Contacts… Load Backup directory Commit • Monarch Operation • Edit the data using the GUI • Test configuration using Preflight Test • Backup the data • Create new config files using Commit

10. Configuration Tool Overview Nagios Host and Service Objects • Host and Service Templates Service Definition Host Definition Service Definition Host Definition Service Definition Service Template Host Template Host Definition

11. Configuration Tool Overview Nagios Host and Service Objects • Fully Implemented Host Service Definition Host Alive Service Template generic-service Host Template generic-host Host Definition domain_controller Service Template generic-service Service Definition DNS_Server Host Service Implemented Host

12. Configuration Tool Overview Monarch Services and Service Profiles • Service Profiles Service CPU Inside the Monarch database we can take liberties with how we store the configuration data. Inside the database preconfigured services are stored in the services table. The entries In this table, unlike the services objects in the Nagios configuration files, are NOT associated with hosts. That association happens in another table. This allows us to ship a library of pre-configured, pre-tested services in the GroundWork product. These “unassigned” services can also be grouped Into logical groups called Service Profiles. Each Service Profile contains a collection of Services that would be appropriate for monitoring a particular device architecture Service memory Service disk Service Profile web monitoring Service httpd Service URL get

13. Configuration Tool Overview Monarch Host Profiles • Host Profiles In the Monarch database Service Profiles can also be associated with host templates to make Host Profiles. A host profile contains everything you need to configure a device other than a hostname, IP Address and an alias. Host Template generic-host Host Profile Service Profile web monitoring

14. Configuration Tool Overview Monarch Configuration Objects • Comparison of Nagios and Monarch Configuration Objects

15. Thank you GroundWork Open Source, Inc. 139 Townsend Street, Suite 500 San Francisco, CA 94107 Phone: 415.992.4500 Website:www.gwos.com Email: info@gwos.com GroundWork Subscription Support: support.gwos.com Confidential - Do not distribute