<!--
contents.inc
Created by pjm2 14/10/2000
- Last edited 14/10/2000
+ Last edited 16/01/2001
-->
<table border="0" width="500">
<center><h3>Current Status</h3></center>
<p align="justify">
- The project is currently undergoing planning decisions.
- The implementation of this central monitoring system is
- expected to completed before Easter.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
+ All i-scream components now function to initial
+ design parameters and our system is regarded to be complete.
+ <b><a href="documentation/">Documentation</a></b> is available to assist third party programmers
+ in producing Hosts for use with the i-scream server.
+ Our progress during the project can be found in the meeting minutes.
+ Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users users only.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
+
+ The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
+ are now visible on the web. If you are <b>not</b> a local user, then you may
+ view some of the output in the <b><a href="screenshots/">screenshots</a></b> section.
+ You may view the latest information about each machine, historical 24-hour
+ reports and alerts for each machine. Our own i-scream server is running constantly,
+ along with several hosts to enable plenty of data harvesting. If you would
+ like your i-scream web reports to be linked from this site, then please email us
+ at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
+ Our current host development allows us to pass machine statistics
+ to our distributed filter arrangement, which then processes the
+ data and stores it for later use. An example of such use is the
+ historical report generator which produces graphs of machine
+ usage over periods of time. A real-time
+ client is also available (Conient) and alert information can be
+ displayed to the public via dynamic web pages.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
+ The latest builds of the i-scream Distributed Central Monitoring System
+ are now available for <b><a href="/downloads/">download</a></b> from this
+ website. To assist in our addition of features to the system, we
+ would be extremely grateful to receive feedback from anybody who has
+ any comments about the system. You may email the development team
+ at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
</p>
<p> </p>
- <center><h3>Presentations</h3></center>
+ <center><h3>Project Completion</h3></center>
<p align="justify">
- Our project presentations will run on Monday 16th and
- Tuesday 17th October. Good luck, everybody.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
+ The i-scream Distributed Central Monitoring System started off as
+ a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
+ the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
+ The project deadline was 4pm on 29th March 2001. Most of the group
+ met very early that morning to compile the project into five
+ lever arch folders. The project, consisting of source code, user,
+ maintenance and other documents, was handed in at 3pm. The CVS
+ repository was tagged to signify the project's completion, however,
+ the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
+ as we have found the system to be very useful in practice. We would
+ love to hear of ideas for extra features that we may include in the
+ next builds.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
+ As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project
+ was aimed at the UKC Computer Science department, and as such
+ we believed that a demonstration to the "customer" was important. The
+ feedback from our demonstation was more positive than we had
+ anticipated. We believe that the system may now be of great
+ interest to anybody who wishes to monitor a number of machines
+ on their network using a central configuration.
</p>
- <p align="justify">
- For those who are interested you can view an online version
- of our presentation <a href="documentation/presentation/i-scream-web.htm">here</a>.
- <br>
- Alternatively you can download a powerpoint version from
- <a href="documentation/presentation/i-scream-web.ppt"> here</a>.
- </p>
<p> </p>
<center><h3>Naming History</h3></center>
<p align="justify">
- The name <b>i-scream</b> arose from a meeting whereupon one member
- of our group randomly chose to draw an ice cream on the white board.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
+ The name <i>i-scream</i> arose from a meeting whereupon one member
+ of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.
It later became apparent that we had no name for our project (other
than 'The Project'). It seemed only natural to name our project after
the ice cream that had been oh-so-randomly drawn on the white board.
Copyright issues immediately ruled out anything involving Mr Whippy,
- so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
+ so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
play on words - it still sounded like <i>ice cream</i>, yet also
served as a functional decription of our system - namely, one which
screams at somebody if something has gone wrong...
i-scream / www.i-scream.org.git / blobdiff