- 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.
+ 
+ All i-scream components now function 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 local users only.
- 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.
+ 
+
+ The i-scream Distributed Central Monitoring System Reports
+ are now visible on the web. If you are not a local user, then you may
+ view some of the output in the screen shots section or you may view 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. 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 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
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.
+ 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.
- 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.
+ 
+ The latest 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
- 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 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.
- 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 great
+ interest to anybody who wishes to monitor a number of machines
+ on their network using a central configuration.
- 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
screams at somebody if something has gone wrong...
- + +
+