Well, the server is blantly not monitored by i-scream :-) This banner is more

[www.i-scream.org.git] / www / contents.inc

diff --git a/www/contents.inc b/www/contents.inc
index 09a5c83fb439a1d2cb5f047582cc3afc84b82cef..73e6bc4ee4711e0a62f2409213e3d5ad2cd16fad 100644 (file)
--- a/www/contents.inc
+++ b/www/contents.inc
@@ -22,6 +22,17 @@
         to UKC users only.
        </p>
 
+       <p align="justify">
+        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
+        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.
+       </p>
+
        <p align="justify">
         Our current host development allows us to pass machine statistics
         to our distributed filter arrangement, which then processes the
@@ -33,6 +44,14 @@
         window. Alerting mechanisms are being put in place to complete the
         i-scream system.
        </p>
+       
+       <p align="justify">
+        Builds of the i-scream Distributed Central Monitoring System
+        are now available for <a href="/builds/">download</a> 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.
+       </p>
 
        <p>&nbsp;</p>
        <center><h3>Project Completion</h3></center>