ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/cms/features.xhtml
(Generate patch)

Comparing web/www/cms/features.xhtml (file contents):
Revision 1.1 by tdb, Fri May 25 18:00:32 2001 UTC vs.
Revision 1.3 by tdb, Sun Mar 21 23:58:13 2004 UTC

# Line 1 | Line 1
1 < <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
1 > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2 >   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3  
3 <!--
4    features.shtml
5    Created by tdb1 30/10/2000
6    Last edited 10/05/2001
7 -->
8
9
4   <html>
5  
6   <head>
7 < <title>Overview and Features</title>
8 < <meta name="description" content="The i-scream Project is a central monitoring system for Unix, Linux and NT servers.">
15 < <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, server, alert">
16 < <meta name="generator" content="notepad on acid, aye.">
7 > <title>CMS Features</title>
8 > <!--#include virtual="/style.inc" -->
9   </head>
10  
11 < <body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
11 > <body>
12  
13 < <table border="0" cellpadding="2" cellspacing="2">
22 < <tr>
23 <  <td valign="top">
24 < <!--#include virtual="left.inc" -->
25 <  </td>
26 <  <td valign="top">
27 < <!--#include virtual="title.inc" -->
13 > <div id="container">
14  
15 <    <table border="0" width="500">
16 <     <tr>
17 <      <td>
18 <       <font size="2" face="arial,sans-serif">
15 > <div id="main">
16 >
17 > <!--#include virtual="/header.inc" -->
18 >
19 > <div id="contents">
20 >
21 >  <h1 class="top">CMS Features</h1>
22 >
23 >  <h2>Problem Specification</h2>
24 >
25 >       <h3>Original Problem</h3>
26 >
27 >       <p>
28 >        This is the original specification given to us when we
29 >        started the project. The i-scream central monitoring
30 >        system meets this specification, and aims to extend it
31 >        further. This is, however, where it all began.
32 >       </p>
33        
34 <       <center><h3>Key Features of The System</h3></center>
34 >       <h3>Centralised Machine Monitoring</h3>
35 >
36 >       <p>
37 >        The Computer Science department has a number of different machines
38 >        running a variety of different operating systems. One of the tasks
39 >        of the systems administrators is to make sure that the machines
40 >        don't run out of resources. This involves watching processor loads,
41 >        available disk space, swap space, etc.
42 >       </p>
43        
44 +       <p>
45 +        It isn't practicle to monitor a large number of machines by logging
46 +        on and running commands such as 'uptime' on the unix machines, or
47 +        by using performance monitor for NT servers. Thus this project is
48 +        to write monitoring software for each platform supported which
49 +        reports resource usage back to one centralized location. System
50 +        Administrators would then be able to monitor all machines from this
51 +        centralised location.
52 +       </p>
53 +
54 +       <p>
55 +        Once this basic functionality is implemented it could usefully be
56 +        expanded to include logging of resource usage to identify longterm
57 +        trends/problems, alerter services which can directly contact
58 +        sysadmins (or even the general public) to bring attention to problem
59 +        areas. Ideally it should be possible to run multiple instances of
60 +        the reporting tool (with all instances being updated in realtime)
61 +        and to to be able to run the reporting tool as both as stand alone
62 +        application and embeded in a web page.
63 +       </p>
64 +
65 +       <p>
66 +        This project will require you to write code for the unix and Win32
67 +        APIs using C and knowledge of how the underlying operating systems
68 +        manage resources. It will also require some network/distributed
69 +        systems code and a GUI front end for the reporting tool. It is
70 +        important for students undertaking this project to understand the
71 +        importance of writing efficient and small code as the end product
72 +        will really be most useful when machines start run out of processing
73 +        power/memory/disk.
74 +       </p>
75 +
76 +       <p>
77 +        John Cinnamond (email jc) whose idea this is, will provide technical
78 +        support for the project.
79 +       </p>
80 +
81 +  <h2>Features</h2>
82 +
83 +       <h3>Key Features of The System</h3>
84 +      
85         <ul>
86          <li>A centrally stored, dynamically reloaded, system wide configuration system</li>
87          <li>A totally extendable monitoring system, nothing except the Host (which
# Line 59 | Line 108
108          <li>Large overhead monitor Helpdesk style displays for latest Alerting information</li>
109         </ul>
110        
111 <       <center><h3>An Overview of the i-scream Central Monitoring System</h3></center>
111 >       <h3>An Overview of the i-scream Central Monitoring System</h3>
112  
113 <       <p align="left">
113 >       <p>
114          The i-scream system monitors status and performance information
115          obtained from machines feeding data into it and then displays
116          this information in a variety of ways.
117         </p>
118        
119 <       <p align="left">
119 >       <p>
120          This data is obtained through the running of small applications
121          on the reporting machines.  These applications are known as
122          "Hosts".  The i-scream system provides a range of hosts which are
# Line 82 | Line 131
131          to the server that they are still alive.
132         </p>
133        
134 <       <p align="left">
134 >       <p>
135          It is then fed into the i-scream server.  The server then splits
136          the data two ways.  First it places the data in a database system,
137          typically MySQL based, for later extraction and processing by the
# Line 99 | Line 148
148          as it flows through the system.
149         </p>
150        
151 <       <p align="left">
151 >       <p>
152          The final section of the system links the Local Client Monitors to
153          an alerting system.  These Monitors can be configured to detect
154          changes in the data past threshold levels.  When a threshold is
# Line 109 | Line 158
158          when a certain level is reached, certain alerting mechanisms fire
159          through whatever medium they are configured to send.
160         </p>
161 <       </font>
113 <      </td>
114 <     </tr>  
115 <    </table>
161 > </div>
162  
163 < <!--#include virtual="bottom.inc" -->
118 <  </td>
119 < </tr>
120 < </table>
163 > <!--#include virtual="/footer.inc" -->
164  
165 < </body>
165 > </div>
166  
167 + <!--#include virtual="/menu.inc" -->
168 +
169 + </div>
170 +
171 + </body>
172   </html>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines