Difference between revisions of "Set up Nagios monitoring of the ARM farm"
(→Project Description) |
|||
Line 5: | Line 5: | ||
== Project Description == | == Project Description == | ||
− | + | "Nagios monitors your entire IT infrastructure to ensure systems, applications, services, and business processes are functioning properly. In the event of a failure, Nagios can alert technical staff of the problem, allowing them to begin remediation processes before outages affect business processes, end-users, or customers. With Nagios you'll never be left having to explain why a unseen infrastructure outage hurt your organization's bottom line. " | |
+ | |||
+ | Setting up Nagios for the Fedora-ARM build farm will make it easier to get notification of system issues. | ||
== Project Leader(s) == | == Project Leader(s) == |
Revision as of 07:07, 8 October 2010
Contents
Project Name
Set Up Nagios monitoring of the ARM farm
Project Description
"Nagios monitors your entire IT infrastructure to ensure systems, applications, services, and business processes are functioning properly. In the event of a failure, Nagios can alert technical staff of the problem, allowing them to begin remediation processes before outages affect business processes, end-users, or customers. With Nagios you'll never be left having to explain why a unseen infrastructure outage hurt your organization's bottom line. "
Setting up Nagios for the Fedora-ARM build farm will make it easier to get notification of system issues.
Project Leader(s)
Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki
Project Contributor(s)
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.
Project Details
Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.
Project Plan
Goals for each release:
- 0.1
- 0.2
- 0.3
Project News
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.
Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.