Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Nagios Integration with COSMOS
Contents
Nagios Integration with COSMOS
Change History
| Name: | Date: | Revised Sections: |
|---|---|---|
| Ali Mehregani | 11/19/2007 |
|
Workload Estimation
| Process | Sizing | Names of people doing the work |
|---|---|---|
| Design | ||
| Code | ||
| Test | ||
| Documentation | ||
| Build and infrastructure | ||
| Code review, etc.* | ||
| 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