|
|
| (76 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | = Nagios Integration with COSMOS =
| + | This page has been moved to: [[COSMOS Design 188390]] |
| − | | + | |
| − | == Change History ==
| + | |
| − | {|{{BMTableStyle}}
| + | |
| − | !align="left"|Name:
| + | |
| − | !align="left"|Date:
| + | |
| − | !align="left"|Revised Sections:
| + | |
| − | |-
| + | |
| − | |Ali Mehregani
| + | |
| − | |11/19/2007
| + | |
| − | |<ul><li>Initial version</li></ul>
| + | |
| − | |}
| + | |
| − | | + | |
| − | == Workload Estimation ==
| + | |
| − | | + | |
| − | {|{{BMTableStyle}}
| + | |
| − | |+{{BMTableCaptionStyle}}|Rough workload estimate in person weeks
| + | |
| − | |-{{BMTHStyle}}
| + | |
| − | ! Process
| + | |
| − | ! Sizing
| + | |
| − | ! Names of people doing the work
| + | |
| − | |-
| + | |
| − | | align="left" | Design
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | | align="left" | Code
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | | align="left" | Test
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | | align="left" | Documentation
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | | align="left" | Build and infrastructure
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | | align="left" | Code review, etc.*
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |-
| + | |
| − | ! align="right" | TOTAL
| + | |
| − | |
| + | |
| − | |
| + | |
| − | |}
| + | |
| − | | + | |
| − | == Terminologies/Acronyms ==
| + | |
| − | | + | |
| − | The terminologies/acronyms below are commonly used throughout this document. The list below defines each term regarding how it is used in this document:
| + | |
| − | | + | |
| − | == Introduction ==
| + | |
| − | The COSMOS vision is entailed in the definition of what COSMOS is - "The world or universe regarded as an orderly, harmonious system". The intention of the project is to apply an orderly and harmonious behavior to the world of system management. Complementing standards such as CMDBf, SML, and Web2.0 technologies are making this vision a reality. The overall COSMOS vision is to provide an extensible framework, based on a set of acceptable standards, to simplify the task of building an ecosystem of existing system management tooling.
| + | |
| − | | + | |
| − | Inline with that vision, Nagios can help to not only mature the COSMOS framework but it can also provide out-of-the-box value to COSMOS users. This two-folded advantage has many positive implications:
| + | |
| − | | + | |
| − | # It is a step forward to evolving an open source code base to a framework that is usable in a production environment
| + | |
| − | # Makes the COSMOS project an attractable solution that provides value by its own
| + | |
| − | # Simplifies integration of proprietary solutions with Nagios, and
| + | |
| − | # Demonstrates a working example of a well-established system management application in COSMOS framework
| + | |
| − | | + | |
| − | The next section provides more detail about Nagios.
| + | |
| − | | + | |
| − | === What is Nagios? ===
| + | |
| − | Nagios is a system and network monitoring application that is capable of detecting and notifying abnormal behavior. The definition and monitoring behavior is defined by administrators using a set of flat-file configurations. The files indicate <b>what</b> and <b>how</b> things should be monitored. There are three primary atomic entities in Nagios:
| + | |
| − | | + | |
| − | <b>Host</b> - A physical device on a network that is intended to be monitored (e.g. a desktop, printer, router, switch, hub, etc...).
| + | |
| − | <b>Service</b> - Indicates the specific component of a host that should be monitored (e.g. CPU utilization, memory consumption, HTTP, etc...)
| + | |
| − | <b>Command</b> - A utility that allows for a service check. For example, check_CPU can be a command used to monitor the CPU utilization on a particular host.
| + | |
| − | | + | |
| − | An administrator is required to define hosts, services, and commands to effectively monitor a set of resources. The actual monitoring of a host/service is not done by Nagios. The monitoring is done by add-on plug-ins that are defined as individual commands. This architecture provides the capability to virtually monitor any aspect of a system that can be automated. There are already many available plug-ins for monitoring common hosts/services in a typical networking environment. Where limited, administrators can write their own plug-in to accomplish the monitoring of an uncommon host/service.
| + | |
| − | | + | |
| − | Nagios itself runs on Linux but it is capable of monitoring desktops running Windows via its plug-in architecture. As part of its monitoring solution, Nagios also provides an alerting mechanism that broadcasts a problem to sets of contacts or contact groups. A notification handler can also be registered to take certain actions based on incoming events (e.g. storing status information in an RDBMS). The diagram below, extracted from Nagios documentation¹, pictorially depicts the components of Nagios:
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:nagios-architecture.png]] | + | |
| − | | + | |
| − | | + | |
| − | There is also a web-based UI included that provides reporting and limited administration capabilities. An screen shot of the Nagios web-based UI is included below. The next section describes the scope and the value of this enhancement.
| + | |
| − | | + | |
| − | | + | |
| − | [[Image:nagios.png]]
| + | |
| − | | + | |
| − | == Purpose ==
| + | |
| − | The purpose of this document is to outline the initial effort in bringing Nagios closer to COSMOS. The integration points and their related value to the Nagios and COSMOS user base will be covered by subsequent sections.
| + | |
| − | | + | |
| − | === Scope ===
| + | |
| − | There are a number of areas where COSMOS can add value to Nagios. The areas can be summarized into three categories:
| + | |
| − | | + | |
| − | #Data Manager Integration
| + | |
| − | #Administration Capabilities
| + | |
| − | #Reporting
| + | |
| − | | + | |
| − | ==== Data Manager Integration ====
| + | |
| − | The task of defining the required hosts and services in Nagios is cumbersome, time-consuming, and error-prone. It's usually the case that information required to define hosts is stored in other data stores. For example, a subset of configuration items stored in a CMDB can typically serve as the hosts that an administrator may want to monitor. It could also be the case where host information is stored under an asset database.
| + | |
| − | | + | |
| − | COSMOS can significantly ease the task of defining hosts in Nagios by
| + | |
| − | | + | |
| − | ==== Administration Capabilities ====
| + | |
| − | | + | |
| − | ==== Reporting ====
| + | |
| − | | + | |
| − | == Requirements ==
| + | |
| − | | + | |
| − | | + | |
| − | == Use Cases ==
| + | |
| − | | + | |
| − | | + | |
| − | == Implementation Detail ==
| + | |
| − | | + | |
| − | | + | |
| − | == Test Coverage ==
| + | |
| − | | + | |
| − | | + | |
| − | == Task Breakdown ==
| + | |
| − | | + | |
| − | == Open Issues/Questions ==
| + | |
