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</a> 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 monitoring system now makes |
47 |
< |
full use of an externally developed IRC bot for it's IRC |
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>. |
59 |
|
here</a> on the author's website. |
60 |
|
</p> |
61 |
|
|
32 |
– |
<p align="justify"> |
33 |
– |
<b>Tuesday 18 Dec 2001</b><br><br> |
34 |
– |
The i-scream ihost package has undergone significant changes to |
35 |
– |
make it more flexible and modular. It now incorporates plugins |
36 |
– |
which can be written in any language, and automatically XML |
37 |
– |
encodes data it is given (as opposed to the hardcoded approach |
38 |
– |
in the old version). It has also been made more robust, and |
39 |
– |
where possible optimised to reduce the load on the host system. |
40 |
– |
</p> |
41 |
– |
|
62 |
|
<p> </p> |
63 |
|
<center><h3>About i-scream</h3></center> |
64 |
|
|
86 |
|
<center><h3>Current Work</h3></center> |
87 |
|
|
88 |
|
<p align="justify"> |
89 |
< |
<b>Historical/Realtime graphing package</b><br><br> |
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 |
< |
The current system for graphing i-scream data from the i-scream |
92 |
< |
system is good, but proving to be unscalable and very resource |
93 |
< |
hungry. This is mostly due to the MySQL database backend, |
94 |
< |
and the vast quantity of data recorded. The new system |
95 |
< |
in development makes use of <a href="http://rrdtool.eu.org/"> |
96 |
< |
RRDtool</a> to generate the graphs in realtime. This reduces |
97 |
< |
the peak loads of the system, and allows generation of more |
78 |
< |
flexible graphs. This work is nearing completetion. |
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 |
< |
|
99 |
> |
|
100 |
|
<p align="justify"> |
101 |
|
<b>Server security</b><br><br> |
102 |
|
Security was something mostly overlooked in the original stage |