13 |
|
<center><h3>Current Status</h3></center> |
14 |
|
|
15 |
|
<p align="justify"> |
16 |
< |
All i-scream components are now functioning to initial |
17 |
< |
design parameters and our system is regarded to be complete. |
18 |
< |
Documentation is available to assist third party programmers |
19 |
< |
in producing Hosts for use with the i-scream server. |
16 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a> |
17 |
> |
The "project" stage of i-scream has finished, leaving the |
18 |
> |
system in a completed state. Since then the goals have |
19 |
> |
changed from completing a project to producing a useful |
20 |
> |
and functional product. |
21 |
> |
<b><a href="documentation/">Documentation</a></b> is |
22 |
> |
available for people wanting to try out the i-scream |
23 |
> |
system, and our code is availabel via <a href="cvs.shtml">CVS</a>. |
24 |
|
Our progress during the project can be found in the meeting minutes. |
25 |
< |
Code is viewable via CVS to UKC users only. |
25 |
> |
Work is still continuing to adapt and improve the i-scream central |
26 |
> |
monitoring system as a product for use in networked environments. |
27 |
|
</p> |
28 |
|
|
29 |
|
<p align="justify"> |
30 |
< |
The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a> |
31 |
< |
are now visible on the web. You may view the latest information |
32 |
< |
about each machine, historical 24-hour reports and alerts for |
33 |
< |
each machine. Please remember that this is work in progress |
34 |
< |
still, so the only data currently viewable is our own data that |
35 |
< |
has been harvested by our own testing. Also note that historical |
36 |
< |
reports are only available for periods during which our server |
37 |
< |
was running. |
30 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a> |
31 |
> |
The i-scream Distributed Central Monitoring System Reports |
32 |
> |
are no longer visible on the web. You may view some of the |
33 |
> |
output in the <b><a href="screenshots/">screen shots</a></b> |
34 |
> |
section or you can sample some static example content on the |
35 |
> |
<a href="reports/"><b>Reports Demo</b></a> pages. |
36 |
> |
You may view the latest information about each machine, |
37 |
> |
historical 24-hour reports and alerts for each machine. If |
38 |
> |
you would like your i-scream web reports to be linked from this |
39 |
> |
site, then please email us at |
40 |
> |
<a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a> |
41 |
|
</p> |
42 |
|
|
43 |
|
<p align="justify"> |
44 |
+ |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="left"></a> |
45 |
|
Our current host development allows us to pass machine statistics |
46 |
|
to our distributed filter arrangement, which then processes the |
47 |
|
data and stores it for later use. An example of such use is the |
52 |
|
</p> |
53 |
|
|
54 |
|
<p align="justify"> |
55 |
+ |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a> |
56 |
|
Builds of the i-scream Distributed Central Monitoring System |
57 |
< |
are now available for <a href="/builds/">download</a> from this |
58 |
< |
website. These are still very much in development and should |
59 |
< |
only be used by people who have been in communication with the |
60 |
< |
development team. Please email us if you wish to use any i-scream |
61 |
< |
software, as we are interested to know who is using it and we may |
52 |
< |
be able to help you out with any problems you encounter. |
57 |
> |
are now available for <b><a href="/downloads/">download</a></b> from this |
58 |
> |
website. To assist in our addition of features to the system, we |
59 |
> |
would be extremely grateful to receive feedback from anybody who has |
60 |
> |
any comments about the system. You may email the development team |
61 |
> |
at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a> |
62 |
|
</p> |
63 |
|
|
64 |
|
<p> </p> |
65 |
|
<center><h3>Project Completion</h3></center> |
66 |
|
|
67 |
|
<p align="justify"> |
68 |
< |
The project deadline was 4pm on 29 March 2001. Most of the group |
68 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a> |
69 |
> |
The i-scream Distributed Central Monitoring System started off as |
70 |
> |
a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at |
71 |
> |
the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK. |
72 |
> |
The project deadline was 4pm on 29th March 2001. Most of the group |
73 |
|
met very early that morning to compile the project into five |
74 |
< |
lever arch folders. The project, consisting of source code, user, |
74 |
> |
lever arch folders. The project, consisting of source code, user, |
75 |
|
maintenance and other documents, was handed in at 3pm. The CVS |
76 |
|
repository was tagged to signify the project's completion, however, |
77 |
< |
development and enhancements to the system shall be continued |
78 |
< |
in the near future. |
77 |
> |
the project is still being developed by the <a href="acknowledgements.shtml">core development team</a> |
78 |
> |
as we have found the system to be very useful in practice. We would |
79 |
> |
love to hear of ideas for extra features that we may include in the |
80 |
> |
next builds. |
81 |
|
</p> |
82 |
|
|
83 |
|
<p align="justify"> |
84 |
< |
As can be seen in the "problem domain" document, the project |
84 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a> |
85 |
> |
As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project |
86 |
|
was aimed at the UKC Computer Science department, and as such |
87 |
< |
we believe a demonstration to the "customer" is important. The |
87 |
> |
we believed that a demonstration to the "customer" was important. The |
88 |
|
feedback from our demonstation was more positive than we had |
89 |
< |
anticipated. We believe that our project may now be of great |
90 |
< |
interest to anybody who wishes to monitor a number of machines |
91 |
< |
on their network using a central configuration. |
89 |
> |
anticipated. We believe that the system may now be of interest |
90 |
> |
to anybody who wishes to monitor a number of machines on their |
91 |
> |
network using a central configuration. The i-scream central |
92 |
> |
monitoring system is now being used by the UKC Computer Science |
93 |
> |
department, and their feedback is being used to further improve |
94 |
> |
the product. |
95 |
|
</p> |
96 |
|
|
97 |
|
<p> </p> |
98 |
|
<center><h3>Naming History</h3></center> |
99 |
|
|
100 |
|
<p align="justify"> |
101 |
< |
The name <b>i-scream</b> arose from a meeting whereupon one member |
102 |
< |
of our group randomly chose to draw an ice cream on the white board. |
101 |
> |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a> |
102 |
> |
The name <i>i-scream</i> arose from a meeting whereupon one member |
103 |
> |
of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board. |
104 |
|
It later became apparent that we had no name for our project (other |
105 |
|
than 'The Project'). It seemed only natural to name our project after |
106 |
|
the ice cream that had been oh-so-randomly drawn on the white board. |
107 |
|
Copyright issues immediately ruled out anything involving Mr Whippy, |
108 |
< |
so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning |
108 |
> |
so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning |
109 |
|
play on words - it still sounded like <i>ice cream</i>, yet also |
110 |
< |
served as a functional decription of our system - namely, one which |
110 |
> |
served as a functional description of our system - namely, one which |
111 |
|
screams at somebody if something has gone wrong... |
112 |
|
</p> |
113 |
|
<p align="justify"> |
114 |
< |
|
114 |
> |
|
115 |
> |
<p> </p> |
116 |
> |
<center><h3>Searching</h3></center> |
117 |
> |
|
118 |
> |
<!-- Search Google --> |
119 |
> |
<center> |
120 |
> |
<FORM method=GET action=http://www.google.com/custom> |
121 |
> |
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0> |
122 |
> |
<tr valign=top><td> |
123 |
> |
<A HREF=http://www.google.com/search> |
124 |
> |
<IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A> |
125 |
> |
</td> |
126 |
> |
<td> |
127 |
> |
<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> |
128 |
> |
<INPUT TYPE=text name=q size=35 maxlength=255 value=""> |
129 |
> |
<INPUT type=submit name=sa VALUE="Search"> |
130 |
> |
<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;"> |
131 |
> |
</td></tr></TABLE> |
132 |
> |
</FORM> |
133 |
> |
</center> |
134 |
> |
<!-- Search Google --> |
135 |
> |
|
136 |
|
</p> |
137 |
|
</font> |
138 |
|
</td> |