--- web/www/contents.inc 2001/12/09 18:06:07 1.27 +++ web/www/contents.inc 2002/02/09 15:00:42 1.28 @@ -1,8 +1,7 @@
- Current StatusProject News
-
- 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.
- Work is still continuing to adapt and improve the i-scream central
- monitoring system as a product for use in networked environments.
+ Thursday 7 Feb 2002
-
- 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
+ Tuesday 8 Jan 2002
-
- 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.
+ Tuesday 18 Dec 2001 + About i-scream- - Builds of the i-scream Distributed Central Monitoring System - 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 + + Details of the i-scream central monitoring system can be found + on the features and overview page. + A variety of screen shots from the + system show some of the key features in use. The reports demo + page provides a static example of what the i-scream reports (alerts, + historical graphs, and live data) could look like on a production system. - + ++ + The latest source code is available in the CVS + repository, with binary downloads on the downloads page. The + documentation page has details of + installation, use and maintenance for the end user and developer. + We value feedback and comments from you, so please drop us an e-mail + to dev@i-scream.org.uk. + +- Project CompletionCurrent Work
+ Historical/Realtime graphing package
+ Server security
+ Testing and Development + Project HistoryThe 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, - 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 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. + a final year project for a group of + Computer Science students at the + University of Kent at Canterbury, UK. The project was completed at + 4pm on 29 March 2001. It consisted of five lever-arch folders containing + mostly source code and documentation. The CVS repository was tagged to + signify this even, however, the project is still being developed by the + core development team. @@ -94,9 +128,6 @@ the product. -- Naming HistoryThe name i-scream arose from a meeting whereupon one member @@ -113,23 +144,27 @@
- SearchingSearching i-scream |