<center><h3>Current Status</h3></center>
<p align="justify">
- <img src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="left">
- All i-scream components now function to initial
- design parameters and our system is regarded to be complete.
- <b><a href="worddocs/">Documentation</a></b> is available to assist third party programmers
- in producing Hosts for use with the i-scream server.
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
+ 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.
+ <b><a href="documentation/">Documentation</a></b> is
+ available for people wanting to try out the i-scream
+ system, and our code is availabel via <a href="cvs.shtml">CVS</a>.
Our progress during the project can be found in the meeting minutes.
- Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users users only.
+ Work is still continuing to adapt and improve the i-scream central
+ monitoring system as a product for use in networked environments.
</p>
<p align="justify">
- <img src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="right">
- The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
- are now visible on the web. If you are <b>not</b> a local user, then you may
- view some of the output in the <b><a href="screenshots/">screenshots</a></b> section.
- 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 <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
+ The i-scream Distributed Central Monitoring System Reports
+ are no longer visible on the web. You may view some of the
+ output in the <b><a href="screenshots/">screen shots</a></b>
+ section or you can sample some static example content on the
+ <a href="reports/"><b>Reports Demo</b></a> 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
+ <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
</p>
<p align="justify">
- <img src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a>
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
</p>
<p align="justify">
- <img src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right">
- The latest builds of the i-scream Distributed Central Monitoring System
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
+ Builds of the i-scream Distributed Central Monitoring System
are now available for <b><a href="/downloads/">download</a></b> 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
<center><h3>Project Completion</h3></center>
<p align="justify">
- <img src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
The i-scream Distributed Central Monitoring System started off as
a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
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 <a href="acknowledgments.shtml">core development team</a>
+ the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
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.
</p>
<p align="justify">
- <img src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right">
- As can be seen in our "<a href="worddocs/">problem domain</a>" document, the project
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
+ As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project
was aimed at the UKC Computer Science department, and as such
- we believed that a demonstration to the "customer" was 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 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.
+ 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.
</p>
<p> </p>
<center><h3>Naming History</h3></center>
<p align="justify">
- <img src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
The name <i>i-scream</i> arose from a meeting whereupon one member
of the <a href="acknowledgements.shtml">development team</a> 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
Copyright issues immediately ruled out anything involving Mr Whippy,
so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
play on words - it still sounded like <i>ice cream</i>, 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...
</p>
<p align="justify">
-
+
+ <p> </p>
+ <center><h3>Searching</h3></center>
+
+ <!-- Search Google -->
+ <center>
+ <FORM method=GET action=http://www.google.com/custom>
+ <TABLE bgcolor=#FFFFFF cellspacing=0 border=0>
+ <tr valign=top><td>
+ <A HREF=http://www.google.com/search>
+ <IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A>
+ </td>
+ <td>
+ <font face=arial,sans-serif size=-1><input type=hidden name=domains value="i-scream.org.uk"><input type=radio name=sitesearch value="i-scream.org.uk" checked> search i-scream <input type=radio name=sitesearch value=""> search google </font><br>
+ <INPUT TYPE=text name=q size=35 maxlength=255 value="">
+ <INPUT type=submit name=sa VALUE="Search">
+ <INPUT type=hidden name=cof VALUE="T:#000066;LW:502;ALC:#3333cc;L:http://www.i-scream.org.uk/i-scream.gif;LC:#0000ff;LH:37;BGC:#ffffff;AH:left;VLC:#3333cc;AWFID:d646a9fd69e7d9cb;">
+ </td></tr></TABLE>
+ </FORM>
+ </center>
+ <!-- Search Google -->
+
</p>
</font>
</td>
i-scream / www.i-scream.org.git / blobdiff