--- web/www/contents.inc 2001/02/28 16:53:17 1.9 +++ web/www/contents.inc 2003/06/08 12:16:28 1.42 @@ -1,8 +1,7 @@
- Current StatusProject News
- Most i-scream components are now functioning to initial
- design parameters and data can now be passed through the
- system and displayed successfully. Documentation is still
- being generated, to allow for future development of the
- i-scream project. Detailed information can usually be
- found in the meeting minutes. Code is viewable via CVS
- to UKC users only.
+ Sunday 8 June 2003
- The i-scream Distributed Central Monitoring System Reports
- are now visible on the web. You may view all reports
- available for each day, but 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.
+ Wednesday 7 May 2003
+ Tuesday 4 February 2003
- 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 (viewable in a web browser). Realtime
- clients are also currently being developed - one Java Swing GUI
- version and also a command line version that can run in a terminal
- window. Alerting mechanisms are being put in place to complete the
- i-scream system.
+ Saturday 1 June 2002
+ Tuesday 21 May 2002
+ Saturday 18 May 2002
+ Thursday 7 Feb 2002
- Builds of the i-scream Distributed Central Monitoring System
- are now available for download from this
- website. These are still very much in development, are should
- only be used by people who have been in communication with the
- development team.
+ Tuesday 8 Jan 2002 + About i-scream+ + 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. + + ++ Current Work
+ Extending monitoring facilites
+ Server security
+ Testing and Development - Project CompletionProject History- The project deadline is 4pm on 29 March. As such, we plan to - complete the coding process by (at the latest) the end of the - project week (26/2 - 2/3). This allows time for documentation - to be tidied up and completed, and printing of the project. + + 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 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. - 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. We - plan to do this over the next two weeks, and the feedback given - will allow any "last minute" alterations to be completed. + 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 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 i-scream |