X-Git-Url: http://git.i-scream.org/?a=blobdiff_plain;f=www%2Fcontents.inc;h=328fcb8ae7db52f350dc1f0645200da34b6ff5fb;hb=c5247ffd12bbb233b14ff41012b40d45c12e50d1;hp=e9c31a28d5834956f6f672652fe92afbc41ddd46;hpb=91f328627111f72cdfd9919a8411b3e881bc000c;p=www.i-scream.org.git diff --git a/www/contents.inc b/www/contents.inc index e9c31a2..328fcb8 100644 --- a/www/contents.inc +++ b/www/contents.inc @@ -1,8 +1,7 @@
- Current StatusProject News
+ Tuesday 4 February 2003
+ Saturday 1 June 2002
- 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.
- Our progress during the project can be found in the meeting minutes.
- Code is viewable via CVS to UKC users only.
+ Tuesday 21 May 2002
- 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.
+ Saturday 18 May 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.
+ Thursday 7 Feb 2002
+ 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. - 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. + + 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 was 4pm on 29 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, - development and enhancements to the system shall be continued - in the near future. + + 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. 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 i-scream |