| 23 |
|
</p> |
| 24 |
|
|
| 25 |
|
<p align="justify"> |
| 26 |
+ |
The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a> |
| 27 |
+ |
are now visible on the web. You may view the latest information |
| 28 |
+ |
about each machine, historical 24-hour reports and alerts for |
| 29 |
+ |
each machine. Please remember that this is work in progress |
| 30 |
+ |
still, so the only data currently viewable is our own data that |
| 31 |
+ |
has been harvested by our own testing. Also note that historical |
| 32 |
+ |
reports are only available for periods during which our server |
| 33 |
+ |
was running. |
| 34 |
+ |
</p> |
| 35 |
+ |
|
| 36 |
+ |
<p align="justify"> |
| 37 |
|
Our current host development allows us to pass machine statistics |
| 38 |
|
to our distributed filter arrangement, which then processes the |
| 39 |
|
data and stores it for later use. An example of such use is the |
| 43 |
|
version and also a command line version that can run in a terminal |
| 44 |
|
window. Alerting mechanisms are being put in place to complete the |
| 45 |
|
i-scream system. |
| 46 |
+ |
</p> |
| 47 |
+ |
|
| 48 |
+ |
<p align="justify"> |
| 49 |
+ |
Builds of the i-scream Distributed Central Monitoring System |
| 50 |
+ |
are now available for <a href="/builds/">download</a> from this |
| 51 |
+ |
website. These are still very much in development and should |
| 52 |
+ |
only be used by people who have been in communication with the |
| 53 |
+ |
development team. |
| 54 |
|
</p> |
| 55 |
|
|
| 56 |
|
<p> </p> |
