--- web/www/contents.inc 2001/03/30 08:08:46 1.12
+++ web/www/contents.inc 2001/12/09 18:06:07 1.27
@@ -13,26 +13,35 @@
Current Status
- All i-scream components are now functioning to initial
- design parameters and our system is regarded to be complete.
- Documentation is available to assist third party programmers
- in producing Hosts for use with the i-scream server.
+ 
+ The "project" stage of i-scream has finished, leaving the
+ system in a completed state. Since then the goals have
+ changed from completing a project to producing a useful
+ and functional product.
+ Documentation is
+ available for people wanting to try out the i-scream
+ system, and our code is availabel via CVS.
Our progress during the project can be found in the meeting minutes.
- Code is viewable via CVS to UKC users only.
+ Work is still continuing to adapt and improve the i-scream central
+ monitoring system as a product for use in networked environments.
- The i-scream Distributed Central Monitoring System Reports
- are now visible on the web. You may view the latest information
- about each machine, historical 24-hour reports and alerts for
- each machine. Please remember that this is work in progress
- still, so the only data currently viewable is our own data that
- has been harvested by our own testing. Also note that historical
- reports are only available for periods during which our server
- was running.
+ 
+ The i-scream Distributed Central Monitoring System Reports
+ are no longer visible on the web. You may view some of the
+ output in the screen shots
+ section or you can sample some static example content on the
+ Reports Demo pages.
+ You may view the latest information about each machine,
+ historical 24-hour reports and alerts for each machine. If
+ you would like your i-scream web reports to be linked from this
+ site, then please email us at
+ dev@i-scream.org.uk
+ 
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
@@ -43,55 +52,87 @@
+ 
Builds of the i-scream Distributed Central Monitoring System
- are now available for download from this
- website. These are still very much in development and should
- only be used by people who have been in communication with the
- development team. Please email us if you wish to use any i-scream
- software, as we are interested to know who is using it and we may
- be able to help you out with any problems you encounter.
+ are now available for download 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 dev@i-scream.org.uk
Project Completion
- The project deadline was 4pm on 29 March 2001. Most of the group
+ 
+ The i-scream Distributed Central Monitoring System started off as
+ a final year project for a group of Computer Science students at
+ the University of Kent at Canterbury, 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,
+ 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,
- development and enhancements to the system shall be continued
- in the near future.
+ the project is still being developed by the core development team
+ 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.
- As can be seen in the "problem domain" document, the project
+ 
+ As can be seen in our "problem domain" document, the project
was aimed at the UKC Computer Science department, and as such
- we believe a demonstration to the "customer" is important. The
+ 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 our project may now be of great
- interest to anybody who wishes to monitor a number of machines
- on their network using a central configuration.
+ anticipated. We believe that the system may now be of interest
+ to anybody who wishes to monitor a number of machines on their
+ network using a central configuration. The i-scream central
+ monitoring system is now being used by the UKC Computer Science
+ department, and their feedback is being used to further improve
+ the product.
Naming History
- The name i-scream arose from a meeting whereupon one member
- of our group randomly chose to draw an ice cream on the white board.
+ 
+ The name i-scream arose from a meeting whereupon one member
+ of the development team 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 i-scream. And thus, we were left with a cunning
+ so we had to settle for i-scream. And thus, we were left with a cunning
play on words - it still sounded like ice cream, yet also
- served as a functional decription of our system - namely, one which
+ served as a functional description of our system - namely, one which
screams at somebody if something has gone wrong...
-
+
+
+ Searching
+
+
+
+
+
+
+