| 1 |
|
| 2 |
<!-- |
| 3 |
$Author: tdb $ |
| 4 |
$Id: contents.inc,v 1.31 2002/06/01 13:29:25 tdb Exp $ |
| 5 |
--> |
| 6 |
|
| 7 |
<table border="0" width="500"> |
| 8 |
<tr> |
| 9 |
<td> |
| 10 |
<font size="2" face="arial,sans-serif"> |
| 11 |
|
| 12 |
<center><h3>Project News</h3></center> |
| 13 |
|
| 14 |
<p align="justify"> |
| 15 |
<b>Saturday 1 June 2002</b><br><br> |
| 16 |
Work has now been finished on a new ihost written in C. This has |
| 17 |
been in the pipeline for a long time, and we're glad to finally |
| 18 |
see an efficient native host! Credit goes to our new developer |
| 19 |
<a href="/who.shtml">Pete</a>. Until we update the downloads |
| 20 |
pages you can download the new ihost |
| 21 |
<a href="http://ukc.i-screma.org.uk/snapshots/ihost-1.0rc1.tar.gz"> |
| 22 |
here</a>. |
| 23 |
</p> |
| 24 |
|
| 25 |
<p align="justify"> |
| 26 |
<b>Tuesday 21 May 2002</b><br><br> |
| 27 |
We've finally put the finishing touches to the new |
| 28 |
<a href="http://rrdtool.eu.org">RRDtool</a> based graphing system. |
| 29 |
It's working well, and has done away with the MySQL database |
| 30 |
backend which took up far too many resources. This new system |
| 31 |
generates the graphs in a more realtime nature, allowing more |
| 32 |
flexible graphs to be generated. This is currently only available |
| 33 |
through <a href="http://www.i-scream.org.uk/cgi-bin/cvs/viewcvs.cgi/cms/source/reports/rrdgraphing/"> |
| 34 |
CVS</a>. |
| 35 |
</p> |
| 36 |
|
| 37 |
<p align="justify"> |
| 38 |
<b>Saturday 18 May 2002</b><br><br> |
| 39 |
The i-scream central monitoring system is now <a href="/license.shtml"> |
| 40 |
licensed under the GNU Public License. We are currently working |
| 41 |
to make full downloads, including source, available on this site. |
| 42 |
</p> |
| 43 |
|
| 44 |
<p align="justify"> |
| 45 |
<b>Thursday 7 Feb 2002</b><br><br> |
| 46 |
The alerting section of the i-scream central monitoring system |
| 47 |
now makes full use of an externally developed IRC bot for it's IRC |
| 48 |
connectivity. To find out more about this IRC bot, please visit |
| 49 |
the author's website at <a href="http://www.jibble.org"> |
| 50 |
http://www.jibble.org</a>. |
| 51 |
</p> |
| 52 |
|
| 53 |
<p align="justify"> |
| 54 |
<b>Tuesday 8 Jan 2002</b><br><br> |
| 55 |
Java ACL (Access Control List) code has been added to the util |
| 56 |
package of the i-scream server. This code will ultimately allow |
| 57 |
the server to be more secure when exposed to the Internet. More |
| 58 |
details can be found <a href="http://www.cs.ukc.ac.uk/people/staff/tdb/#acl"> |
| 59 |
here</a> on the author's website. |
| 60 |
</p> |
| 61 |
|
| 62 |
<p> </p> |
| 63 |
<center><h3>About i-scream</h3></center> |
| 64 |
|
| 65 |
<p align="justify"> |
| 66 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="left"></a> |
| 67 |
Details of the i-scream central monitoring system can be found |
| 68 |
on the <b><a href="features.shtml">features and overview</a></b> page. |
| 69 |
A variety of <b><a href="screenshots">screen shots</a></b> from the |
| 70 |
system show some of the key features in use. The <b><a href="reports">reports demo</a></b> |
| 71 |
page provides a static example of what the i-scream reports (alerts, |
| 72 |
historical graphs, and live data) could look like on a production system. |
| 73 |
</p> |
| 74 |
|
| 75 |
<p align="justify"> |
| 76 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-main.gif" width="100" height="107" align="right"></a> |
| 77 |
The latest source code is available in the <b><a href="cvs.shtml">CVS</a></b> |
| 78 |
repository, with binary downloads on the downloads page. The |
| 79 |
<b><a href="documentation">documentation</a></b> page has details of |
| 80 |
installation, use and maintenance for the end user and developer. |
| 81 |
We value feedback and comments from you, so please drop us an e-mail |
| 82 |
to <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>. |
| 83 |
</p> |
| 84 |
|
| 85 |
<p> </p> |
| 86 |
<center><h3>Current Work</h3></center> |
| 87 |
|
| 88 |
<p align="justify"> |
| 89 |
<b>Extending monitoring facilites</b><br><br> |
| 90 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a> |
| 91 |
Work is continuing, in conjunction with the new ihost, to extend |
| 92 |
the range of i-scream's monitoring. Currently we are adding new |
| 93 |
features to more accurately monitoring memory and swap usage, |
| 94 |
along with more disk statistics. We are also planning to improve |
| 95 |
the rather basic service monitors which are currently in place. |
| 96 |
There are also many more subtle changes that need to be made to |
| 97 |
improve the reliability and usefulness of i-scream's monitoring. |
| 98 |
</p> |
| 99 |
|
| 100 |
<p align="justify"> |
| 101 |
<b>Server security</b><br><br> |
| 102 |
Security was something mostly overlooked in the original stage |
| 103 |
of this project (due to the academic nature of the work). However, |
| 104 |
once in production use this has become an issue, and is being |
| 105 |
addressed. Initially the plan is to lock down the external points |
| 106 |
of access (TCP & UDP) in the server to specific hosts. In the |
| 107 |
longer term, encryption of data would be nice, but would take a |
| 108 |
lot more time and work. |
| 109 |
</p> |
| 110 |
|
| 111 |
<p align="justify"> |
| 112 |
<b>Testing and Development</b><br><br> |
| 113 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a> |
| 114 |
The i-scream system is being tested and developed within the |
| 115 |
Univeristy of Kent Computer Science department by the Systems |
| 116 |
Group. This has led to many bug fixes and minor feature |
| 117 |
enhancements, and will hopefully help to aid the long term |
| 118 |
development of the system. |
| 119 |
</p> |
| 120 |
|
| 121 |
<p> </p> |
| 122 |
<center><h3>Project History</h3></center> |
| 123 |
|
| 124 |
<p align="justify"> |
| 125 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a> |
| 126 |
The i-scream Distributed Central Monitoring System started off as |
| 127 |
a final year project for a group of <a href="http://www.cs.ukc.ac.uk"> |
| 128 |
Computer Science</a> students at the <a href="http://www.ukc.ac.uk"> |
| 129 |
University of Kent at Canterbury</a>, UK. The project was completed at |
| 130 |
4pm on 29 March 2001. It consisted of five lever-arch folders containing |
| 131 |
mostly source code and documentation. The CVS repository was tagged to |
| 132 |
signify this even, however, the project is still being developed by the |
| 133 |
<a href="acknowledgements.shtml">core development team</a>. |
| 134 |
</p> |
| 135 |
|
| 136 |
<p align="justify"> |
| 137 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a> |
| 138 |
As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" document, the project |
| 139 |
was aimed at the UKC Computer Science department, and as such |
| 140 |
we believed that a demonstration to the "customer" was important. The |
| 141 |
feedback from our demonstation was more positive than we had |
| 142 |
anticipated. We believe that the system may now be of interest |
| 143 |
to anybody who wishes to monitor a number of machines on their |
| 144 |
network using a central configuration. The i-scream central |
| 145 |
monitoring system is now being used by the UKC Computer Science |
| 146 |
department, and their feedback is being used to further improve |
| 147 |
the product. |
| 148 |
</p> |
| 149 |
|
| 150 |
<p align="justify"> |
| 151 |
<a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a> |
| 152 |
The name <i>i-scream</i> arose from a meeting whereupon one member |
| 153 |
of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board. |
| 154 |
It later became apparent that we had no name for our project (other |
| 155 |
than 'The Project'). It seemed only natural to name our project after |
| 156 |
the ice cream that had been oh-so-randomly drawn on the white board. |
| 157 |
Copyright issues immediately ruled out anything involving Mr Whippy, |
| 158 |
so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning |
| 159 |
play on words - it still sounded like <i>ice cream</i>, yet also |
| 160 |
served as a functional description of our system - namely, one which |
| 161 |
screams at somebody if something has gone wrong... |
| 162 |
</p> |
| 163 |
<p align="justify"> |
| 164 |
|
| 165 |
<p> </p> |
| 166 |
<center><h3>Searching i-scream</h3></center> |
| 167 |
|
| 168 |
<!-- Search Google --> |
| 169 |
<center> |
| 170 |
<FORM method=GET action=http://www.google.com/custom> |
| 171 |
<TABLE bgcolor=#FFFFFF cellspacing=0 border=0> |
| 172 |
<tr> |
| 173 |
<td valign="middle"> |
| 174 |
<A HREF=http://www.google.com/search> |
| 175 |
<IMG SRC=http://www.google.com/logos/Logo_40wht.gif border=0 ALT=Google align=middle width="128" height="53"></A> |
| 176 |
</td> |
| 177 |
<td valign="middle"> |
| 178 |
<input type=hidden name=domains value="i-scream.org.uk"> |
| 179 |
<input type=hidden name=sitesearch value="i-scream.org.uk"> |
| 180 |
<INPUT TYPE=text name=q size=35 maxlength=255 value=""> |
| 181 |
<INPUT type=submit name=sa VALUE="Search"> |
| 182 |
<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;"> |
| 183 |
</td> |
| 184 |
</tr> |
| 185 |
</TABLE> |
| 186 |
</FORM> |
| 187 |
</center> |
| 188 |
<!-- Search Google --> |
| 189 |
|
| 190 |
</p> |
| 191 |
</font> |
| 192 |
</td> |
| 193 |
</tr> |
| 194 |
</table> |
