25 |
|
<p align="justify"> |
26 |
|
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a> |
27 |
|
|
28 |
< |
The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a> |
28 |
> |
The i-scream Distributed Central Monitoring System Reports |
29 |
|
are now visible on the web. If you are <b>not</b> a local user, then you may |
30 |
< |
view some of the output in the <b><a href="screenshots/">screenshots</a></b> section. |
30 |
> |
view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some |
31 |
> |
static example content on the <a href="reports/"><b>Reports Demo</b></a> pages. |
32 |
|
You may view the latest information about each machine, historical 24-hour |
33 |
|
reports and alerts for each machine. Our own i-scream server is running constantly, |
34 |
|
along with several hosts to enable plenty of data harvesting. If you would |
80 |
|
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a> |
81 |
|
As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project |
82 |
|
was aimed at the UKC Computer Science department, and as such |
83 |
< |
we believed that a demonstration to the "customer" was important. The |
83 |
> |
we believed that a demonstration to the "customer" was important. The |
84 |
|
feedback from our demonstation was more positive than we had |
85 |
|
anticipated. We believe that the system may now be of great |
86 |
|
interest to anybody who wishes to monitor a number of machines |