From: Tim Bishop Date: Sun, 21 Mar 2004 23:59:32 +0000 (+0000) Subject: Commit new website. The old site is tagged, so this won't change the live X-Git-Url: http://git.i-scream.org/?a=commitdiff_plain;h=044ce3d999326b8748cd8f2821ed593298bb07ba;hp=28fd2cb88214745644a1b92687899e6739de7289;p=www.i-scream.org.git Commit new website. The old site is tagged, so this won't change the live site... but it does move HEAD on to the new site. Too many changes to list really. General points are: - Moved to a XHTML CSS compliant site. - Reorganised the site into a more multi-project based look. - Removed a lot of cruft. Still to do: - Fix all the zillions of bugs stopping the whole site from validating :-) - Tidy up the HTML in terms of layout and indentation. Thanks to AJ for his help this weekend in doing this. --- diff --git a/cgi-bin/cvslog.cgi b/cgi-bin/cvslog.cgi index 0f86725..337bc05 100755 --- a/cgi-bin/cvslog.cgi +++ b/cgi-bin/cvslog.cgi @@ -1,5 +1,7 @@ #!/usr/bin/perl -w +# TODO: remove tables, and use CSS instead + use CGI; $query=new CGI; my($period)=$query->param('period'); @@ -48,38 +50,41 @@ my($cvs2clargs) = "--stdout --no-wrap --no-common-dir -r -t -w -S -U $cvsroot/CV my($updatecmd) = "/home/iscream/bin/fullcvsupdate.sh $modulelist"; my($logcmd) = "cd /tmp/i-scream/cvstmp && $cvs2clpath $cvs2clargs"; -my ($left) = "../htdocs/left.inc" ; -my ($title) = "../htdocs/title.inc"; -my ($bottom) = "../htdocs/bottom.inc"; +my ($menu) = "../nwww/menu.inc" ; +my ($header) = "../nwww/header.inc"; +my ($footer) = "../nwww/footer.inc"; +my ($style) = "../nwww/style.inc"; print "Content-type: text/html\n\n"; print <<"END"; - + - The i-scream Project Commit Log - - - - - - - - - -
+ i-scream CVS Commit Logs END -&print_html($left); +&print_html($style); print <<"END"; - + + + + +
+ +
END -&print_html($title); +&print_html($header); print <<"END"; +
+

i-scream CVS Commit Logs

+

$heading

END @@ -90,7 +95,7 @@ my(@modules) = split (/\s+/, $modulelist); foreach my $module (@modules) { print "\n\n"; - print "\n\n"; + print "\n\n"; print "
\n$module module\n
\n$module module\n
\n"; my(@lines) = `$logcmd $module 2>&1`; @@ -152,13 +157,13 @@ foreach my $module (@modules) { print HTML_encode($rev); } print HTML_encode($ext); - print "
\n" + print "
\n" } else { chomp $line; print ""; print HTML_encode($line); - print "
\n" + print "
\n" } } } @@ -167,16 +172,18 @@ foreach my $module (@modules) { print "

\n\n"; } -&print_html($bottom); +print "

"; -print <<"END"; +&print_html($footer); -
+print ""; - +&print_html($menu); +print <<"END"; + + + END diff --git a/cgi-bin/docs.cgi b/cgi-bin/docs.cgi index 8c60667..402c9e5 100755 --- a/cgi-bin/docs.cgi +++ b/cgi-bin/docs.cgi @@ -1,22 +1,15 @@ #!/usr/bin/perl -w -#------------------------------------------------------------ -# docs.cgi -# -# Web-based text file viewer. -# Copyright Paul Mutton, 2000. -#------------------------------------------------------------ - use strict; use CGI; $| = 1; # Settings -my ($left) = "../htdocs/left.inc" ; -my ($title) = "../htdocs/title.inc"; -my ($bottom) = "../htdocs/bottom.inc"; - +my ($menu) = "../nwww/menu.inc" ; +my ($header) = "../nwww/header.inc"; +my ($footer) = "../nwww/footer.inc"; +my ($style) = "../nwww/style.inc"; my ($query) = new CGI; @@ -34,57 +27,57 @@ unless (defined $doc) { # Prevent hackers from supplying a malformed document string. # I.e. only allow normal characters, slashes and dots. unless ($doc =~ /^[a-zA-Z_\-0-9\.\/]+$/) { - print "Malformed request"; + print "Malformed request."; exit; } $doc = "../htdocs/documentation/".$doc; -print <<"END"; - +my($docname) = $doc =~ /\/([^\/]+)$/; - +print <<"END"; + - The i-scream Project Documentation Viewer - - - + i-scream plain text documentation viewer +END + +&print_html($style); + +print <<"END"; - + - - - - - -
+
+ +
END -&print_html($left); +&print_html($header); print <<"END"; +
+

i-scream documentation viewer

-
+

$docname

END -&print_html($title); &print_file($doc); -&print_html($bottom); +print ""; -print <<"END"; +&print_html($footer); -
+print ""; - +&print_html($menu); + +print <<"END"; + + END @@ -92,22 +85,22 @@ exit 0; # Print a file, whilst escaping HTML: - sub print_file ($) { - my ($urls) = '(' . join ('|', qw{ - http - telnet - gopher - file - wais - ftp - } ) - . ')'; - - my ($ltrs) = '\w'; - my ($gunk) = '/#~:.?+=&%@!\-'; - my ($punc) = '.:?\-'; - my ($any) = "${ltrs}${gunk}${punc}"; - my ($filename) = @_; - open(FILE, $filename) or die "Cannot open $filename: $!\n"; +my ($urls) = '(' . join ('|', qw{ + http + telnet + gopher + file + wais + ftp + } ) + . ')'; + +my ($ltrs) = '\w'; +my ($gunk) = '/#~:.?+=&%@!\-'; +my ($punc) = '.:?\-'; +my ($any) = "${ltrs}${gunk}${punc}"; +my ($filename) = @_; +if(open(FILE, $filename)) { print "
\n";
     # Use $_ implicitly throughout.
     while () {
@@ -121,9 +114,13 @@ sub print_file ($) {
     }
     print "
"; } +else { + print "Failed to open $docname."; +} +} # Print a file without escaping HTML: - sub print_html ($) { - my ($filename) = @_; - print `cat $filename 2>&1`; +my ($filename) = @_; +print `cat $filename 2>&1`; } diff --git a/cgi-bin/logo.jpg b/cgi-bin/logo.jpg new file mode 100755 index 0000000..d598438 --- /dev/null +++ b/cgi-bin/logo.jpg @@ -0,0 +1,16 @@ +#!/usr/local/bin/perl -w + +use strict; +$| = 1; + +# Directory to find images in +my($dir) = "/web/i-scream/nwww/logos"; +# Pattern to match images - remember to escape +my($pattern) = "\\.jpg\$"; + +# Where the setbg command is +my($setbg) = "/web/i-scream/nwww.bin/setbg.pl"; + +# Code... +print "Content-type: image/jpeg\n\n"; +exec "$setbg -r -p \'$pattern\' -b cat -f \' \' $dir"; diff --git a/www/acknowledgements.shtml b/www/acknowledgements.shtml deleted file mode 100644 index 639bd12..0000000 --- a/www/acknowledgements.shtml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - - - i-scream acknowledgements and credits - - - - - - - - - - - -
- - - - - - - -
-
- - - - -
-

Acknowledgements

- -

We would like to thank all of - those who have made the i-scream distributed central monitoring system - possible, namely the programmers and those who have assisted in - development by testing our software and offering feedback.

-

The i-scream central - monitoring system started off as a final year Computer Science group - project at the University of Kent at Canterbury, UK.  Since finishing - their degrees, the main programmers have continued to develop the - system 

-
-

The Server

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

ihost

-

Paul Mutton
- Pete Saunders
- Tim Bishop

-

WinHost

-

Paul Mutton

-

Web Reports

-

Paul Mutton
- Tim Bishop

-

Conient

-

Alex Moore

-

Website

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Historical Reports

-

Paul Mutton
- Tim Bishop

-

System-wide - Utilities

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Testing and Feedback

-

Adam Sampson
- Alex Moore
- Ash Beeson
- Fred Barnes
- Ian Utting
- John Cinnamond
- Mark Wheadon
- Paul Mutton
- Phill Camp
- Tim Bishop

-

Ideas and Support

-

John Cinnamond
- Phill Camp
- Mark Wheadon
- Ian Utting

-

 

-

We would also like to thank - the UKC Computer Science department and the UKC Templeman Library for - allowing us to run and test the project on their machines, and all those - people that have supported us along the way.

- Finally we wish to commend the creators of - JacORB, without which, the project would not have achieved the goals we set - out to reach.

-
- - - -
- - - - diff --git a/www/atsign.gif b/www/atsign.gif deleted file mode 100644 index a5d0412..0000000 Binary files a/www/atsign.gif and /dev/null differ diff --git a/www/bottom.inc b/www/bottom.inc deleted file mode 100644 index 66ac39f..0000000 --- a/www/bottom.inc +++ /dev/null @@ -1,18 +0,0 @@ - - - -

 

-

 

-

- - http://www.i-scream.org
- Copyright 2001-2003 The i-scream Project
- dev@i-scream.org - -

-

- -

diff --git a/www/cms/acknowledgements.shtml b/www/cms/acknowledgements.shtml deleted file mode 100644 index 639bd12..0000000 --- a/www/cms/acknowledgements.shtml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - - - i-scream acknowledgements and credits - - - - - - - - - - - -
- - - - - - - -
-
- - - - -
-

Acknowledgements

- -

We would like to thank all of - those who have made the i-scream distributed central monitoring system - possible, namely the programmers and those who have assisted in - development by testing our software and offering feedback.

-

The i-scream central - monitoring system started off as a final year Computer Science group - project at the University of Kent at Canterbury, UK.  Since finishing - their degrees, the main programmers have continued to develop the - system 

-
-

The Server

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

ihost

-

Paul Mutton
- Pete Saunders
- Tim Bishop

-

WinHost

-

Paul Mutton

-

Web Reports

-

Paul Mutton
- Tim Bishop

-

Conient

-

Alex Moore

-

Website

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Historical Reports

-

Paul Mutton
- Tim Bishop

-

System-wide - Utilities

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Testing and Feedback

-

Adam Sampson
- Alex Moore
- Ash Beeson
- Fred Barnes
- Ian Utting
- John Cinnamond
- Mark Wheadon
- Paul Mutton
- Phill Camp
- Tim Bishop

-

Ideas and Support

-

John Cinnamond
- Phill Camp
- Mark Wheadon
- Ian Utting

-

 

-

We would also like to thank - the UKC Computer Science department and the UKC Templeman Library for - allowing us to run and test the project on their machines, and all those - people that have supported us along the way.

- Finally we wish to commend the creators of - JacORB, without which, the project would not have achieved the goals we set - out to reach.

-
- - - -
- - - - diff --git a/www/cms/documentation/gettingstarted.shtml b/www/cms/documentation/gettingstarted.shtml index 9230179..ef417bf 100644 --- a/www/cms/documentation/gettingstarted.shtml +++ b/www/cms/documentation/gettingstarted.shtml @@ -1,29 +1,23 @@ - - - + - Getting Started with the i-scream Central Monitoring System +Getting Started with the i-scream Central Monitoring System + - - + - - - - - -
- - - +
- +
+ + + +
+

Getting Started

Getting Started with the i-scream Central Monitoring System

@@ -142,13 +136,16 @@ again, please let us know.

Finally, we'd like to thank you for trying this i-scream product. We realise that it's still at an early stage, and we therefore appreciate you taking the time to try it out.

-

The i-scream team. +

The i-scream team.

+
- + + +
+ + -
+ diff --git a/www/cms/documentation/gettingstarted.xhtml b/www/cms/documentation/gettingstarted.xhtml index 9230179..ef417bf 100644 --- a/www/cms/documentation/gettingstarted.xhtml +++ b/www/cms/documentation/gettingstarted.xhtml @@ -1,29 +1,23 @@ - - - + - Getting Started with the i-scream Central Monitoring System +Getting Started with the i-scream Central Monitoring System + - - + - - - - - -
- - - +
- +
+ + + +
+

Getting Started

Getting Started with the i-scream Central Monitoring System

@@ -142,13 +136,16 @@ again, please let us know.

Finally, we'd like to thank you for trying this i-scream product. We realise that it's still at an early stage, and we therefore appreciate you taking the time to try it out.

-

The i-scream team. +

The i-scream team.

+
- + + +
+ + -
+ diff --git a/www/cms/documentation/index.shtml b/www/cms/documentation/index.shtml index 6ff0e53..720eb8d 100644 --- a/www/cms/documentation/index.shtml +++ b/www/cms/documentation/index.shtml @@ -1,29 +1,23 @@ - - - + - i-scream documentation +i-scream CMS documentation + - - - - - - - - -
- - - - -

i-scream documentation

+ + +
+ +
+ + + +
+

i-scream documentation

This is the offical documentation for the i-scream central monitoring system. They should be considered "correct" over any other older documentation that still exists on the website. They are currently only @@ -34,52 +28,53 @@ from this website. However, there may be changes in the CVS version which are not documented in the code. The link below shows what changes have been made since the project completion date.

- + Commits to the "cms" CVS module since project completion (29/03/2001) -
-

User guides

-(HTML) Getting Started with the i-scream Central Monitoring System
-(Word|PDF) Unix/Linux ihost user guide
-(Word|PDF) Windows WinHost user guide
-(Word|PDF) Conient client user guide
-(Word|PDF) Server user guide
-(Word|PDF) CORBA Services user guide
-(Word|PDF) Web reports user guide
-(Word|PDF) Database reporter user guide
- -

Maintenance documentation for developers

-(Word|PDF) Unix/Linux ihost maintenance
-(Word|PDF) Windows WinHost maintenance
-(Word|PDF) Conient maintenance
-(Word|PDF) Server maintenance
-(Word|PDF) Web reports maintenance
-(Word|PDF) Database reporter maintenance
- -

Specification documents

-(Word|PDF) Original specification & problem domain
-(Word|PDF) TCP Protocol specifications
-(Word|PDF) Expected XML data from host to server
-(Word|PDF) XML recommendations for host to server UDP packets
-(Word|PDF) Document standards
-(Word|PDF) Java coding standards
- -

Other documents

-(Word|PDF) Risk analysis
-(Word|PDF) Estimated time allocation
-(Word|PDF) Implementation phases for our plan
-(Word|PDF) Estimated time allocation (revised)
-(Word|PDF) Meeting Minutes
-(Word|PDF) Use of the website
-(Word|PDF) Use of CVS and automated software builds
-(Word|PDF) Comparison to Big Brother
-
- - - -
+

User guides

+(HTML) Getting Started with the i-scream Central Monitoring System
+(Word|PDF) Unix/Linux ihost user guide
+(Word|PDF) Windows WinHost user guide
+(Word|PDF) Conient client user guide
+(Word|PDF) Server user guide
+(Word|PDF) CORBA Services user guide
+(Word|PDF) Web reports user guide
+(Word|PDF) Database reporter user guide
+ +

Maintenance documentation for developers

+(Word|PDF) Unix/Linux ihost maintenance
+(Word|PDF) Windows WinHost maintenance
+(Word|PDF) Conient maintenance
+(Word|PDF) Server maintenance
+(Word|PDF) Web reports maintenance
+(Word|PDF) Database reporter maintenance
+ +

Specification documents

+(Word|PDF) Original specification & problem domain
+(Word|PDF) TCP Protocol specifications
+(Word|PDF) Expected XML data from host to server
+(Word|PDF) XML recommendations for host to server UDP packets
+(Word|PDF) Document standards
+(Word|PDF) Java coding standards
+ +

Other documents

+(Word|PDF) Risk analysis
+(Word|PDF) Estimated time allocation
+(Word|PDF) Implementation phases for our plan
+(Word|PDF) Estimated time allocation (revised)
+(Word|PDF) Meeting Minutes
+(Word|PDF) Use of the website
+(Word|PDF) Use of CVS and automated software builds
+(Word|PDF) Comparison to Big Brother
+ + + + + + + + + diff --git a/www/cms/documentation/index.xhtml b/www/cms/documentation/index.xhtml index 6ff0e53..720eb8d 100644 --- a/www/cms/documentation/index.xhtml +++ b/www/cms/documentation/index.xhtml @@ -1,29 +1,23 @@ - - - + - i-scream documentation +i-scream CMS documentation + - - - - - - - - -
- - - - -

i-scream documentation

+ + +
+ +
+ + + +
+

i-scream documentation

This is the offical documentation for the i-scream central monitoring system. They should be considered "correct" over any other older documentation that still exists on the website. They are currently only @@ -34,52 +28,53 @@ from this website. However, there may be changes in the CVS version which are not documented in the code. The link below shows what changes have been made since the project completion date.

- + Commits to the "cms" CVS module since project completion (29/03/2001) -
-

User guides

-(HTML) Getting Started with the i-scream Central Monitoring System
-(Word|PDF) Unix/Linux ihost user guide
-(Word|PDF) Windows WinHost user guide
-(Word|PDF) Conient client user guide
-(Word|PDF) Server user guide
-(Word|PDF) CORBA Services user guide
-(Word|PDF) Web reports user guide
-(Word|PDF) Database reporter user guide
- -

Maintenance documentation for developers

-(Word|PDF) Unix/Linux ihost maintenance
-(Word|PDF) Windows WinHost maintenance
-(Word|PDF) Conient maintenance
-(Word|PDF) Server maintenance
-(Word|PDF) Web reports maintenance
-(Word|PDF) Database reporter maintenance
- -

Specification documents

-(Word|PDF) Original specification & problem domain
-(Word|PDF) TCP Protocol specifications
-(Word|PDF) Expected XML data from host to server
-(Word|PDF) XML recommendations for host to server UDP packets
-(Word|PDF) Document standards
-(Word|PDF) Java coding standards
- -

Other documents

-(Word|PDF) Risk analysis
-(Word|PDF) Estimated time allocation
-(Word|PDF) Implementation phases for our plan
-(Word|PDF) Estimated time allocation (revised)
-(Word|PDF) Meeting Minutes
-(Word|PDF) Use of the website
-(Word|PDF) Use of CVS and automated software builds
-(Word|PDF) Comparison to Big Brother
-
- - - -
+

User guides

+(HTML) Getting Started with the i-scream Central Monitoring System
+(Word|PDF) Unix/Linux ihost user guide
+(Word|PDF) Windows WinHost user guide
+(Word|PDF) Conient client user guide
+(Word|PDF) Server user guide
+(Word|PDF) CORBA Services user guide
+(Word|PDF) Web reports user guide
+(Word|PDF) Database reporter user guide
+ +

Maintenance documentation for developers

+(Word|PDF) Unix/Linux ihost maintenance
+(Word|PDF) Windows WinHost maintenance
+(Word|PDF) Conient maintenance
+(Word|PDF) Server maintenance
+(Word|PDF) Web reports maintenance
+(Word|PDF) Database reporter maintenance
+ +

Specification documents

+(Word|PDF) Original specification & problem domain
+(Word|PDF) TCP Protocol specifications
+(Word|PDF) Expected XML data from host to server
+(Word|PDF) XML recommendations for host to server UDP packets
+(Word|PDF) Document standards
+(Word|PDF) Java coding standards
+ +

Other documents

+(Word|PDF) Risk analysis
+(Word|PDF) Estimated time allocation
+(Word|PDF) Implementation phases for our plan
+(Word|PDF) Estimated time allocation (revised)
+(Word|PDF) Meeting Minutes
+(Word|PDF) Use of the website
+(Word|PDF) Use of CVS and automated software builds
+(Word|PDF) Comparison to Big Brother
+ + + + + + + + + diff --git a/www/cms/downloads/index.shtml b/www/cms/downloads/index.shtml deleted file mode 100644 index 4c19706..0000000 --- a/www/cms/downloads/index.shtml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - - - - - - i-scream software builds - - - - - - - - - - -
- - - - - - - - - - - - - - - - -
-

i-scream software builds

- -

All downloads are licensed under the GPL.

-

All new builds will be signed with our PGP key.

- -
-

current builds

- -

These builds are the latest development working copies. They are much - more developed than the downloads you'll find below. We recommend you - start here. This is the codebase from which we'll make a proper release - sometime in the future.

-

Snapshot Server

- -
-

old (but unchanging) builds

- -

These builds are from the end of the project. Development is still - continuing and can be found in the section above. These downloads are - not changing, and will not be updated until a release is made. Unless - you are really sure you want this version, get the one above. - -

Full documentation can be found by following the "Documentation" - link on the left-hand bar. Downloads below are the same, apart from - the archive format - with one exception being the host application.

- -

You will be asked to enter some basic information before - downloading, although this is purely optional. We value feedback - from people testing the i-scream products, so please feel free to - contact us at dev@i-scream.org.

- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build nameWindows downloads
(.zip format)		Unix downloads
(.tar.gz format)
i-scream Conient (GUI client)download download
i-scream host applicationdownload download
i-scream serverdownload download
i-scream PHP web reportsdownload download
i-scream historical database reporterdownload download
CORBA services managerdownload download
- - -
- - - diff --git a/www/cms/features.shtml b/www/cms/features.shtml index 99dc0ba..f96ed15 100644 --- a/www/cms/features.shtml +++ b/www/cms/features.shtml @@ -1,36 +1,86 @@ - - - - + - Overview and Features - - - +CMS Features + - + + +
+ +
+ + + +
+ +

CMS Features

- - - - - -
- - - +

Problem Specification

- - - - -
- +

Original Problem

+ +

+ This is the original specification given to us when we + started the project. The i-scream central monitoring + system meets this specification, and aims to extend it + further. This is, however, where it all began. +

-

Key Features of The System

+

Centralised Machine Monitoring

+ +

+ The Computer Science department has a number of different machines + running a variety of different operating systems. One of the tasks + of the systems administrators is to make sure that the machines + don't run out of resources. This involves watching processor loads, + available disk space, swap space, etc. +

+ +

+ It isn't practicle to monitor a large number of machines by logging + on and running commands such as 'uptime' on the unix machines, or + by using performance monitor for NT servers. Thus this project is + to write monitoring software for each platform supported which + reports resource usage back to one centralized location. System + Administrators would then be able to monitor all machines from this + centralised location. +

+ +

+ Once this basic functionality is implemented it could usefully be + expanded to include logging of resource usage to identify longterm + trends/problems, alerter services which can directly contact + sysadmins (or even the general public) to bring attention to problem + areas. Ideally it should be possible to run multiple instances of + the reporting tool (with all instances being updated in realtime) + and to to be able to run the reporting tool as both as stand alone + application and embeded in a web page. +

+ +

+ This project will require you to write code for the unix and Win32 + APIs using C and knowledge of how the underlying operating systems + manage resources. It will also require some network/distributed + systems code and a GUI front end for the reporting tool. It is + important for students undertaking this project to understand the + importance of writing efficient and small code as the end product + will really be most useful when machines start run out of processing + power/memory/disk. +

+ +

+ John Cinnamond (email jc) whose idea this is, will provide technical + support for the project. +

+ +

Features

+ +

Key Features of The System

  • A centrally stored, dynamically reloaded, system wide configuration system
    • @@ -58,15 +108,15 @@
  • Large overhead monitor Helpdesk style displays for latest Alerting information
-

An Overview of the i-scream Central Monitoring System

+

An Overview of the i-scream Central Monitoring System

-

+

The i-scream system monitors status and performance information obtained from machines feeding data into it and then displays this information in a variety of ways.

-

+

This data is obtained through the running of small applications on the reporting machines. These applications are known as "Hosts". The i-scream system provides a range of hosts which are @@ -81,7 +131,7 @@ to the server that they are still alive.

-

+

It is then fed into the i-scream server. The server then splits the data two ways. First it places the data in a database system, typically MySQL based, for later extraction and processing by the @@ -98,7 +148,7 @@ as it flows through the system.

-

+

The final section of the system links the Local Client Monitors to an alerting system. These Monitors can be configured to detect changes in the data past threshold levels. When a threshold is @@ -108,16 +158,15 @@ when a certain level is reached, certain alerting mechanisms fire through whatever medium they are configured to send.

- -
+ - -
+ - +
+ + +
+ + diff --git a/www/cms/features.xhtml b/www/cms/features.xhtml index 99dc0ba..f96ed15 100644 --- a/www/cms/features.xhtml +++ b/www/cms/features.xhtml @@ -1,36 +1,86 @@ - - - - + - Overview and Features - - - +CMS Features + - + + +
+ +
+ + + +
+ +

CMS Features

- - - - - -
- - - +

Problem Specification

- - - - -
- +

Original Problem

+ +

+ This is the original specification given to us when we + started the project. The i-scream central monitoring + system meets this specification, and aims to extend it + further. This is, however, where it all began. +

-

Key Features of The System

+

Centralised Machine Monitoring

+ +

+ The Computer Science department has a number of different machines + running a variety of different operating systems. One of the tasks + of the systems administrators is to make sure that the machines + don't run out of resources. This involves watching processor loads, + available disk space, swap space, etc. +

+ +

+ It isn't practicle to monitor a large number of machines by logging + on and running commands such as 'uptime' on the unix machines, or + by using performance monitor for NT servers. Thus this project is + to write monitoring software for each platform supported which + reports resource usage back to one centralized location. System + Administrators would then be able to monitor all machines from this + centralised location. +

+ +

+ Once this basic functionality is implemented it could usefully be + expanded to include logging of resource usage to identify longterm + trends/problems, alerter services which can directly contact + sysadmins (or even the general public) to bring attention to problem + areas. Ideally it should be possible to run multiple instances of + the reporting tool (with all instances being updated in realtime) + and to to be able to run the reporting tool as both as stand alone + application and embeded in a web page. +

+ +

+ This project will require you to write code for the unix and Win32 + APIs using C and knowledge of how the underlying operating systems + manage resources. It will also require some network/distributed + systems code and a GUI front end for the reporting tool. It is + important for students undertaking this project to understand the + importance of writing efficient and small code as the end product + will really be most useful when machines start run out of processing + power/memory/disk. +

+ +

+ John Cinnamond (email jc) whose idea this is, will provide technical + support for the project. +

+ +

Features

+ +

Key Features of The System

  • A centrally stored, dynamically reloaded, system wide configuration system
    • @@ -58,15 +108,15 @@
  • Large overhead monitor Helpdesk style displays for latest Alerting information
-

An Overview of the i-scream Central Monitoring System

+

An Overview of the i-scream Central Monitoring System

-

+

The i-scream system monitors status and performance information obtained from machines feeding data into it and then displays this information in a variety of ways.

-

+

This data is obtained through the running of small applications on the reporting machines. These applications are known as "Hosts". The i-scream system provides a range of hosts which are @@ -81,7 +131,7 @@ to the server that they are still alive.

-

+

It is then fed into the i-scream server. The server then splits the data two ways. First it places the data in a database system, typically MySQL based, for later extraction and processing by the @@ -98,7 +148,7 @@ as it flows through the system.

-

+

The final section of the system links the Local Client Monitors to an alerting system. These Monitors can be configured to detect changes in the data past threshold levels. When a threshold is @@ -108,16 +158,15 @@ when a certain level is reached, certain alerting mechanisms fire through whatever medium they are configured to send.

- -
+ - -
+ - +
+ + +
+ + diff --git a/www/cms/index.shtml b/www/cms/index.shtml new file mode 100644 index 0000000..f92ad18 --- /dev/null +++ b/www/cms/index.shtml @@ -0,0 +1,185 @@ + + + + + +i-scream CMS homepage + + + + + +
+ +
+ + + +
+

i-scream CMS homepage

+ + + +

Overview

+

+ The i-scream central monitoring system provides a free, centrally + configurable distributed server to monitor the status and + performance of Solaris, Linux, FreeBSD and Windows machines + on a network. The server can raise alerts using email, IRC or + a large public information display. Information may also be + browsed interactively via the web or using our multi-platform + client. +

+ +

+ Follow the link above for the original problem specification + we were given to develop the i-scream CMS, and the feature set + of the CMS after it was finished. +

+ +

Screen Shots

+ +

+ These screenshots were taken at the end of the project, and + therefore show the old build given below, and none of our new + features. +

+ +

Reports Demo

+ +

+ This is a demo of the web-based reports that the i-scream system + can do. It's taken from the old builds, so doesn't show any of + the new RRDTool based features. +

+ +

Downloads

+ +

Snapshot Builds

+ +

+ Since the project was completed various changes have happened + in the CMS. These are undocumented, but fairly straightforward. + We'd strongly suggest you use this version of the CMS rather + than the builds from the end of the project. +

+

+ We've done a fair amount of work on the graphing/database side + of the CMS, and fixed numerous bugs. Also, the new ihost/libstatgrab + combination requires the snapshot builds. +

+ +

Old Builds (from project completion)

+ +

+ These builds were completed at the end of the project itself. + They match with the documentation below, and work. But we've + done a fair amount of work since creating them. +

+ +

Documentation

+ +

Product documentation

+ +

+ This documentation was written as the CMS project was completed. + It therefore applies to the downloads available from the time + the project finished. There will definately be descrepences + between this documentation and the snapshot builds. +

+ +

Javadoc documentation

+ +

+ Each component of the CMS written in java has fairly extensive + javadoc documentation that helps to explain the code and API's. +

+ +

Process documentation

+ +

+ Various pieces of documentation were generated during the project + that were intended for internal use. They're not required reading + for running the CMS, but might be interesting if you're curious + about the project itself. +

+ +

Project History

+ +

+ The i-scream Distributed Central Monitoring System started off + as a final year project for a group of Computer Science students + at the University of Kent, + UK. The project was completed at 4pm on 29 March 2001. It + consisted of five lever-arch folders containing mostly source + code and documentation. The CVS repository was tagged to signify + this event, however. +

+

+ As can be seen in our "problem + domain" document, the project was aimed at the UKC + Computer Science department, and as such we believed that a + demonstration to the "customer" was important. The + feedback from our demonstation was more positive than we had + anticipated. We believe that the system may now be of interest + to anybody who wishes to monitor a number of machines on their + network using a central configuration. The i-scream central + monitoring system is now being used by the UKC Computer Science + department, and their feedback is being used to further improve + the product. +

+

+ The name i-scream arose from a meeting whereupon one + member of the development team felt a strange urge to draw an + ice cream on the discussion board. It later became apparent + that we had no name for our project (other than 'The Project'). + It seemed only natural to name our project after the ice cream + that had been oh-so-randomly drawn on the white board. Copyright + issues immediately ruled out anything involving Mr Whippy, so + we had to settle for i-scream. And thus, we were left + with a cunning play on words - it still sounded like ice + cream, yet also served as a functional description of our + system - namely, one which screams at somebody if something has + gone wrong... +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/cms/index.xhtml b/www/cms/index.xhtml new file mode 100644 index 0000000..f92ad18 --- /dev/null +++ b/www/cms/index.xhtml @@ -0,0 +1,185 @@ + + + + + +i-scream CMS homepage + + + + + +
+ +
+ + + +
+

i-scream CMS homepage

+ + + +

Overview

+

+ The i-scream central monitoring system provides a free, centrally + configurable distributed server to monitor the status and + performance of Solaris, Linux, FreeBSD and Windows machines + on a network. The server can raise alerts using email, IRC or + a large public information display. Information may also be + browsed interactively via the web or using our multi-platform + client. +

+ +

+ Follow the link above for the original problem specification + we were given to develop the i-scream CMS, and the feature set + of the CMS after it was finished. +

+ +

Screen Shots

+ +

+ These screenshots were taken at the end of the project, and + therefore show the old build given below, and none of our new + features. +

+ +

Reports Demo

+ +

+ This is a demo of the web-based reports that the i-scream system + can do. It's taken from the old builds, so doesn't show any of + the new RRDTool based features. +

+ +

Downloads

+ +

Snapshot Builds

+ +

+ Since the project was completed various changes have happened + in the CMS. These are undocumented, but fairly straightforward. + We'd strongly suggest you use this version of the CMS rather + than the builds from the end of the project. +

+

+ We've done a fair amount of work on the graphing/database side + of the CMS, and fixed numerous bugs. Also, the new ihost/libstatgrab + combination requires the snapshot builds. +

+ +

Old Builds (from project completion)

+ +

+ These builds were completed at the end of the project itself. + They match with the documentation below, and work. But we've + done a fair amount of work since creating them. +

+ +

Documentation

+ +

Product documentation

+ +

+ This documentation was written as the CMS project was completed. + It therefore applies to the downloads available from the time + the project finished. There will definately be descrepences + between this documentation and the snapshot builds. +

+ +

Javadoc documentation

+ +

+ Each component of the CMS written in java has fairly extensive + javadoc documentation that helps to explain the code and API's. +

+ +

Process documentation

+ +

+ Various pieces of documentation were generated during the project + that were intended for internal use. They're not required reading + for running the CMS, but might be interesting if you're curious + about the project itself. +

+ +

Project History

+ +

+ The i-scream Distributed Central Monitoring System started off + as a final year project for a group of Computer Science students + at the University of Kent, + UK. The project was completed at 4pm on 29 March 2001. It + consisted of five lever-arch folders containing mostly source + code and documentation. The CVS repository was tagged to signify + this event, however. +

+

+ As can be seen in our "problem + domain" document, the project was aimed at the UKC + Computer Science department, and as such we believed that a + demonstration to the "customer" was important. The + feedback from our demonstation was more positive than we had + anticipated. We believe that the system may now be of interest + to anybody who wishes to monitor a number of machines on their + network using a central configuration. The i-scream central + monitoring system is now being used by the UKC Computer Science + department, and their feedback is being used to further improve + the product. +

+

+ The name i-scream arose from a meeting whereupon one + member of the development team felt a strange urge to draw an + ice cream on the discussion board. It later became apparent + that we had no name for our project (other than 'The Project'). + It seemed only natural to name our project after the ice cream + that had been oh-so-randomly drawn on the white board. Copyright + issues immediately ruled out anything involving Mr Whippy, so + we had to settle for i-scream. And thus, we were left + with a cunning play on words - it still sounded like ice + cream, yet also served as a functional description of our + system - namely, one which screams at somebody if something has + gone wrong... +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/cms/javadoc/index.shtml b/www/cms/javadoc/index.shtml index 87189ba..34f3957 100644 --- a/www/cms/javadoc/index.shtml +++ b/www/cms/javadoc/index.shtml @@ -1,25 +1,23 @@ - - - + - i-scream javadoc pages +i-scream CMS javadoc + - + + +
+ +
+ + - - - - - -
- - - +
+

i-scream CMS javadoc

Java Source code documentation

@@ -27,15 +25,19 @@ The whole of the server, and parts of the rest of the system have been written in Java. Making use of the javadoc tool the following pages of documentation have been automatically generated. -

Server javadoc pages

-

Conient javadoc pages

-

Corba Service Manager javadoc pages

-

Util Package javadoc pages

+

Server javadoc pages

+

Conient javadoc pages

+

Corba Service Manager javadoc pages

+

Util Package javadoc pages

+
+ + + + + + - -
+
diff --git a/www/cms/javadoc/index.xhtml b/www/cms/javadoc/index.xhtml index 87189ba..34f3957 100644 --- a/www/cms/javadoc/index.xhtml +++ b/www/cms/javadoc/index.xhtml @@ -1,25 +1,23 @@ - - - + - i-scream javadoc pages +i-scream CMS javadoc + - + + +
+ +
+ + - - - - - -
- - - +
+

i-scream CMS javadoc

Java Source code documentation

@@ -27,15 +25,19 @@ The whole of the server, and parts of the rest of the system have been written in Java. Making use of the javadoc tool the following pages of documentation have been automatically generated. -

Server javadoc pages

-

Conient javadoc pages

-

Corba Service Manager javadoc pages

-

Util Package javadoc pages

+

Server javadoc pages

+

Conient javadoc pages

+

Corba Service Manager javadoc pages

+

Util Package javadoc pages

+
+ + + + + + - -
+
diff --git a/www/cms/minutes.shtml b/www/cms/minutes.shtml index dc73cb2..af3c511 100644 --- a/www/cms/minutes.shtml +++ b/www/cms/minutes.shtml @@ -1,27 +1,23 @@ - - - + - i-scream meeting minutes +i-scream meeting minutes + - - + + +
+ +
- - - -
- - - + +
+

i-scream meeting minutes

i-scream meeting minutes

These are the minutes from all the meetings that took @@ -85,11 +81,15 @@ development of they i-scream central monitoring system.

+
+ + - - - - +
+ + + +
diff --git a/www/cms/minutes.xhtml b/www/cms/minutes.xhtml index dc73cb2..af3c511 100644 --- a/www/cms/minutes.xhtml +++ b/www/cms/minutes.xhtml @@ -1,27 +1,23 @@ - - - + - i-scream meeting minutes +i-scream meeting minutes + - - + + +
+ +
- - - -
- - - + +
+

i-scream meeting minutes

i-scream meeting minutes

These are the minutes from all the meetings that took @@ -85,11 +81,15 @@ development of they i-scream central monitoring system.

+
+ + - - - - +
+ + + +
diff --git a/www/cms/oldtodo.shtml b/www/cms/oldtodo.shtml deleted file mode 100644 index 4e96379..0000000 --- a/www/cms/oldtodo.shtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

(old) i-scream central monitoring system TODO list

- -This is the TODO list to be achieved by the end of the "project" period. -A -newer TODO list now exists to cover the future things -we plan to do with the development of the i-scream central monitoring system.

-Server

-
LocalClient Monitors: Users.
-
-Completed:
-----------
-22/03/2001 - FIX the major memory leak and deadlock issues.
-             LocalClient Monitors: Load, Processes, Queues.
-18/03/2001 - LocalClient Monitors: Disks/Memory need MB threshold
-15/03/2001 - Alert dumping needs to be organised better.
-             Running on Windows InetAddress.getHostName() doesn't return the FQDN.
-13/03/2001 - Thread naming, at least at a "what class it is" level.
-             Utilise the ConfigurationProxy throughout the server.
-             Sort out GC & Configuration objects (and CorbaHandlers).
-09/03/2001 - WebFeeder needs to dump Alerts to disk.
-08/03/2001 - WebFeeder needs to dump XML to disk
-             LocalClient Monitors: Disks, Service Checks
-07/03/2001 - Service Checks: FTP, POP3, IMAP, SSH, Telnet
-01/03/2001 - Make it easy to change flags to the java compiler.
-             Configuration groups need implementing.
-28/02/2001 - Queue identification ? Use a hash of the Queue ?
-             Fix the Queue "unlimited" size problem.
-27/02/2001 - (not needed) ClientInterface/DBInterface need to "pull" data ?
-             Builds on the website ?
-             Change build scripts to make iscream-server.java/tar.gz/zip
-25/02/2001 - Move checking of logging verbosity to the servant.
-23/02/2001 - print verbosity level with logging messages
-             functionality added to the LoggerServant
-23/02/2001 - Startup of components - eg. running DBInterface on another machine.
-             Now catches any problems relating to not finding a component if
-             a component has a dependancy.  The component manager will then
-             retry it after a given timeout.
-12/02/2001 - Logging of Queue.status() somehow.
-06/02/2001 - Make use of the PrintWriter "autoflush" feature :)
-28/01/2001 - Add dependency checking for the DOCOPY Makefile target.
-             Client Interface needs more functionality.
-             SQL Driver doesn't work in Windows.
-18/01/2001 - Heartbeats are still dropped.
-             CVS directories get added to build tar/zip file.
-             Problem on FreeBSD with zip file adding more files than it should.
-             Remove Component from util package -> ComponentManager.
-             Remove ReferenceManager from util package -> ComponentManager.
-             Add status methods to the Queue that return just values.
-             Clean up the util package, it shouldn't do logging etc.
-               -- done with the exception of ReferenceManager.
-16/01/2001 - Build a util package JAR file seperately.
-14/01/2001 - Javadoc pages on website ?
-               -- done for the server at least.
-12/01/2001 - Investigate the use of a Queue in the Filter, to replace the
-             current FilterThread setup.
-07/01/2001 - Makefile needs to copy non-java files to JAR (eg. images).
-02/01/2001 - Add making of Javadoc pages to make scripts.
-             Queuing system in the root filter.
-
- -

Conient

-
Completed:
-----------
-18/03/2001 - Switch to using the StringUtil class for the firewall command stuff.
-             Fix bug where it can take up to two packets to display
-             correct information.  This is most visible in service
-             checks, but can also be seen on disk, memory and anything
-             else that uses two data items from the packet for one
-             component.
-01/03/2001 - re-work host display and choosing mechanism (ie, make us 1.1 protocol)
-26/02/2001 - Rework system displaying of components for Swing Event Handling
-             Allow config to be written back to a local file
-             Allow local file config to be changed via the GUI
-05/02/2001 - allow disk components to alter their units
-             have some icons and the i-scream logo on display
-             show errors in windows rather than on the console
-             Fix error in packet stopping update of ALL hosts
-04/02/2001 - Write LOADS more data components
-03/02/2001 - Allow config to be obtained from the server
-30/01/2001 - Add option to handle firewalls
-29/01/2001 - Allow config to be obtained from a local file
-             Fix problem with memory display showing negative values at start
-             Ensure all Swing updates use the Swing Event Handling thread (partial - only data components)
-28/01/2001 - Tidy up network comms and link handling
-
- -

statgrab

-
Completed:
-----------
-20/03/2001 - Linux - CPU %'s not always right, 2 repititions ?
-19/03/2001 - Odd behaviour with more than 1000 processes, on Solaris at least
-             FreeBSD - grabbing memory total
-11/03/2001 - Solaris - If free memory changes to < 10Mb (?) it changes to K rather than M (thus not matched)
-
- -

C++ Host

-
UDP Packet size to 8Kb
-Porting to Linux/FreeBSD (Windows?)
-
- -

Winhost

-
Completed:
-----------
-19/03/2001 - Still needs to send the true uptime.
-             Processor ID should be packet.os.platform
-             Minor version joined with packet.os.version
-             Logo ? Pink icon ?
-             Solve OCX problem
-
- -

ihost

-
Completed:
-----------
-12/03/2001 - Produce a very quick "check script" which can be run by cron.
-
- -

Web Reports

-
Completed:
-----------
-22/03/2001 - Alert/System Summary Page (incl. helpdesk style)
-15/03/2001 - Individual Host Alert Summary Page(s)
-14/03/2001 - Individual Host Lastest Data Page(s) (including service checks)
-
- - -
- - - \ No newline at end of file diff --git a/www/cms/probdomain.shtml b/www/cms/probdomain.shtml deleted file mode 100644 index e62b53a..0000000 --- a/www/cms/probdomain.shtml +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - - The i-scream Project Problem Domain - - - - - - - - - - - - -
- - - - - - - - -
- - -

Original Problem

- -

- This is the original specification given to us when we - started the project. The i-scream central monitoring - system meets this specification, and aims to extend it - further. This is, however, where it all began. -

- -

Centralised Machine Monitoring

- -

- The Computer Science department has a number of different machines - running a variety of different operating systems. One of the tasks - of the systems administrators is to make sure that the machines - don't run out of resources. This involves watching processor loads, - available disk space, swap space, etc. -

- -

- It isn't practicle to monitor a large number of machines by logging - on and running commands such as 'uptime' on the unix machines, or - by using performance monitor for NT servers. Thus this project is - to write monitoring software for each platform supported which - reports resource usage back to one centralized location. System - Administrators would then be able to monitor all machines from this - centralised location. -

- -

- Once this basic functionality is implemented it could usefully be - expanded to include logging of resource usage to identify longterm - trends/problems, alerter services which can directly contact - sysadmins (or even the general public) to bring attention to problem - areas. Ideally it should be possible to run multiple instances of - the reporting tool (with all instances being updated in realtime) - and to to be able to run the reporting tool as both as stand alone - application and embeded in a web page. -

- -

- This project will require you to write code for the unix and Win32 - APIs using C and knowledge of how the underlying operating systems - manage resources. It will also require some network/distributed - systems code and a GUI front end for the reporting tool. It is - important for students undertaking this project to understand the - importance of writing efficient and small code as the end product - will really be most useful when machines start run out of processing - power/memory/disk. -

- -

- John Cinnamond (email jc) whose idea this is, will provide technical - support for the project. -

- - -
- - -
- - - - \ No newline at end of file diff --git a/www/cms/projectpapers.shtml b/www/cms/projectpapers.shtml index 4f81b07..866a38a 100644 --- a/www/cms/projectpapers.shtml +++ b/www/cms/projectpapers.shtml @@ -1,26 +1,23 @@ - - - + - i-scream project papers & documentation +project papers + - - + + +
+ +
- - - -
- - - + + +
+

project papers

i-scream project papers & documentation

@@ -77,11 +74,15 @@ left to find the official documentation.

+
- - - - + + + + + + + - \ No newline at end of file + diff --git a/www/cms/projectpapers.xhtml b/www/cms/projectpapers.xhtml index 4f81b07..866a38a 100644 --- a/www/cms/projectpapers.xhtml +++ b/www/cms/projectpapers.xhtml @@ -1,26 +1,23 @@ - - - + - i-scream project papers & documentation +project papers + - - + + +
+ +
- - - -
- - - + + +
+

project papers

i-scream project papers & documentation

@@ -77,11 +74,15 @@ left to find the official documentation.

+
- - - - + + + + + + + - \ No newline at end of file + diff --git a/www/cms/quotes.shtml b/www/cms/quotes.shtml deleted file mode 100644 index c1a14dc..0000000 --- a/www/cms/quotes.shtml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - Memorable Project Quotes - - - - - - - - - - -
- - - - - -

Memorable Project Quotes

- -

-These are all genuine quotes that came about during our time -developing the i-scream server, hosts, clients and reporting -system. -

- -

-AJ doc'ing and taking the i-scream pun too far -

- "An i-scream client connects to the i-scream and ...." -
-

- -

-AJ -

- "I'm gonna be raptor! grr!" -
-

- -

-Tim -

- "I'm not going to draw on the board with some fizzy jerks." -
-

- -

-Tim -

- "It's just programming, innit?" -
-

- -

-Paul -

- "Let's sell one sock... Quality." -
-

- -

-Tim -

- "Break my hand... arghhh." -
-

- -

-AJ -

- "But we haven't got any children yet..." -
-

- -

-Tim -

- "Do you like my gender?" -
-

- -

-Paul -

- "Do away with the vowels, damnit. Oh, it's got a 'u' in it, hasn't it..." -
-

- -

-Tim -

- "Long is, in fact, long long." -
-

- -

-Paul -

- "And the fish do their little funky shit." -
-

- -

-Tim -

- "Bloody hell, what are your feet doing over here?!" -
-

- -

-Paul -

- "There's an 'L' in XML, isn't there?" -
-

- -

-AJ -

- "Yeah, we're not paying anything for it, either... we just pay them once a month." -
-

- -

-Ash -

- "Do you want some tissues now?" -
-

- - -

- - - - \ No newline at end of file diff --git a/www/cms/screenshots/index.shtml b/www/cms/screenshots/index.shtml index ef073f7..c7fbed9 100644 --- a/www/cms/screenshots/index.shtml +++ b/www/cms/screenshots/index.shtml @@ -1,42 +1,31 @@ - - - + - i-scream screenshots / overview - - - +CMS Screen Shots + - - + - - - -
- - - - +
+
+ +
+

CMS Screen Shots

- -
-

i-scream - screenshots

+

i-scream + screenshots

(or the two minute tour)

@@ -230,12 +219,15 @@ + + - -
+
+ + + +
diff --git a/www/cms/screenshots/index.xhtml b/www/cms/screenshots/index.xhtml index ef073f7..c7fbed9 100644 --- a/www/cms/screenshots/index.xhtml +++ b/www/cms/screenshots/index.xhtml @@ -1,42 +1,31 @@ - - - + - i-scream screenshots / overview - - - +CMS Screen Shots + - - + - - - -
- - - - +
+
+ +
+

CMS Screen Shots

- -
-

i-scream - screenshots

+

i-scream + screenshots

(or the two minute tour)

@@ -230,12 +219,15 @@ + + - -
+
+ + + +
diff --git a/www/cms/todo.shtml b/www/cms/todo.shtml deleted file mode 100644 index f706cfd..0000000 --- a/www/cms/todo.shtml +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

i-scream central monitoring system TODO list

- -

This page lists the things we plan to do with the -i-scream central monitoring system in the future.

- -

TODO: -

    -
  • monitoring of users logging in & out
    • -
  • web-based configuration system
    • -
  • cleaner separation of some of the CORE functions (such as configuration - and logging) as independent services
    • -
  • grouping of hosts in frontends using server config groups
    • -
  • security of filters - ACL's
    • -
- -

To view the older TODO list from the project -please click here.

- - -
- - - diff --git a/www/contents.inc b/www/contents.inc deleted file mode 100644 index 5b6e4b5..0000000 --- a/www/contents.inc +++ /dev/null @@ -1,213 +0,0 @@ - - - - - - - -
- - -

Project News

- -

- Wednesday 10 March 2004

- libstatgrab 0.9 has been released. -

- -

- Tuesday 15 July 2003

- We have moved the i-scream support and bug tracking to a new - facility on the i-scream server. For further details please - see this page. -

- -

- Sunday 8 June 2003

- The i-scream website, email, and cvs facilities are now all - run from a FreeBSD server.
- - Powered By FreeBSD - -

- -

- Tuesday 4 February 2003

- Over the coming week we will be making snapshot builds of the - i-scream central monitoring system from the CVS repository. - These builds will have quite a few changes from the downloads - currently available (a document detailing them will be - released later on), so please give them a whirl. We would be - grateful if you contacted - us with any questions or bugs.

- The downloads will be available on our snapshot server :-
- - http://snapshots.i-scream.org/. -

- -

- Saturday 1 June 2002

- Work has now been finished on a new ihost written in C. This has - been in the pipeline for a long time, and we're glad to finally - see an efficient native host! Credit goes to our new developer - Pete. Until we update the downloads - pages you can download the new ihost - - here. -

- -

- Tuesday 21 May 2002

- We've finally put the finishing touches to the new - RRDtool based graphing system. - It's working well, and has done away with the MySQL database - backend which took up far too many resources. This new system - generates the graphs in a more realtime nature, allowing more - flexible graphs to be generated. This is currently only available - through - CVS. -

- -

- Tuesday 8 Jan 2002

- Java ACL (Access Control List) code has been added to the util - package of the i-scream server. This code will ultimately allow - the server to be more secure when exposed to the Internet. More - details can be found - here on the author's website. -

- -

 

-

About i-scream

- -

- - Details of the i-scream central monitoring system can be found - on the features and overview page. - A variety of screen shots from the - system show some of the key features in use. The reports demo - page provides a static example of what the i-scream reports (alerts, - historical graphs, and live data) could look like on a production system. -

- -

- - The latest source code is available in the CVS - repository, with binary downloads on the downloads page. The - documentation page has details of - installation, use and maintenance for the end user and developer. - We value feedback and comments from you, so please drop us an e-mail - to dev@i-scream.org. -

- -

 

-

Current Work

- -

- Extending monitoring facilites

- - Work is continuing, in conjunction with the new ihost, to extend - the range of i-scream's monitoring. Currently we are adding new - features to more accurately monitoring memory and swap usage, - along with more disk statistics. We are also planning to improve - the rather basic service monitors which are currently in place. - There are also many more subtle changes that need to be made to - improve the reliability and usefulness of i-scream's monitoring. -

- -

- Server security

- Security was something mostly overlooked in the original stage - of this project (due to the academic nature of the work). However, - once in production use this has become an issue, and is being - addressed. Initially the plan is to lock down the external points - of access (TCP & UDP) in the server to specific hosts. In the - longer term, encryption of data would be nice, but would take a - lot more time and work. -

- -

- Testing and Development

- - The i-scream system is being tested and developed within the - Univeristy of Kent Computer Science department by the Systems - Group. This has led to many bug fixes and minor feature - enhancements, and will hopefully help to aid the long term - development of the system. -

- -

 

-

Project History

- -

- - The i-scream Distributed Central Monitoring System started off as - a final year project for a group of - Computer Science students at the - University of Kent at Canterbury, UK. The project was completed at - 4pm on 29 March 2001. It consisted of five lever-arch folders containing - mostly source code and documentation. The CVS repository was tagged to - signify this even, however, the project is still being developed by the - core development team. -

- -

- - As can be seen in our "problem domain" document, the project - was aimed at the UKC Computer Science department, and as such - we believed that a demonstration to the "customer" was important. The - feedback from our demonstation was more positive than we had - anticipated. We believe that the system may now be of interest - to anybody who wishes to monitor a number of machines on their - network using a central configuration. The i-scream central - monitoring system is now being used by the UKC Computer Science - department, and their feedback is being used to further improve - the product. -

- -

- - The name i-scream arose from a meeting whereupon one member - of the development team felt a strange urge to draw an ice cream on the discussion board. - It later became apparent that we had no name for our project (other - than 'The Project'). It seemed only natural to name our project after - the ice cream that had been oh-so-randomly drawn on the white board. - Copyright issues immediately ruled out anything involving Mr Whippy, - so we had to settle for i-scream. And thus, we were left with a cunning - play on words - it still sounded like ice cream, yet also - served as a functional description of our system - namely, one which - screams at somebody if something has gone wrong... -

-

- -

 

-

Searching i-scream

- - -
-
- - - - - -
- - Google - - - - - - -
-
-
- - -

- -
diff --git a/www/cvs.shtml b/www/cvs.shtml index 90ff671..abb81f4 100644 --- a/www/cvs.shtml +++ b/www/cvs.shtml @@ -1,31 +1,23 @@ - - - - + - i-scream cvs repository - - +i-scream cvs repository + - + + +
+ +
- - - - - -
- - - + - -

i-scream CVS Repository

+
+

i-scream CVS Repository

The i-scream CVS Repository contains all code, documentation, and other files pertaining to all i-scream projects.

@@ -45,10 +37,10 @@ versions. There is also a link to download the latest version of any section.

We also have a facility to allow people to keep tabs on what's changed recently. The following are available:

-

Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
-Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
-Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
-Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29

+

Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
+Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
+Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
+Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29

Anonymous CVS Access (read-only)

@@ -56,12 +48,12 @@ Commits made since 29/03/2001:

When asked for a password, simply press enter. Replace [module] with the section you wish to checkout.

@@ -70,12 +62,12 @@ Replace [module] with the section you wish to checkout.

The i-scream development team have full write access to the CVS repository. This is only available over SSH, and can be done on most clients. First the following environment variables need to be set.

- -
CVS_RSH = ssh
-CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
+
+CVS_RSH = ssh
+CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
+
-

You should know your username and password already. After setting these you will need to enter your password each time you use a CVS command. Obviously this is a time wasting event, so an RSA key can be @@ -87,20 +79,21 @@ normal.

Other means of accessing CVS

-

We currently provide CVSup access to the repository, either for mirroring or -for maintaining an up-to-date local copy. You will probably want to create a -supfile that looks something like this;

- +

We currently provide CVSup access to +the repository, either for mirroring or for maintaining an up-to-date local +copy. You will probably want to create a supfile that looks something like +this;

-
*default host=cvsup.i-scream.org
+
+*default host=cvsup.i-scream.org
 *default base=/home/user/sup
 *default prefix=/home/user/i-scream
 *default release=cvs
 *default delete use-rel-suffix
 *default compress
-i-scream.cms.source tag=.

+i-scream.cms.source tag=.
+
-

The last item in that list is the collection you which to get. The collection "i-scream" is simply the whole repository, and is best used with no tag specified for mirroring. It is most likely that you will want to do that @@ -113,15 +106,18 @@ repository, generated by cvsplot, that allow you to see the progress of development. They're not that exciting, but do show when the work was done.

-

http://www.i-scream.org/cvsplot

+

+http://www.i-scream.org/cvsplot/ +

+
- + - -
+
- + + +
+ diff --git a/www/cvs.xhtml b/www/cvs.xhtml index 90ff671..abb81f4 100644 --- a/www/cvs.xhtml +++ b/www/cvs.xhtml @@ -1,31 +1,23 @@ - - - - + - i-scream cvs repository - - +i-scream cvs repository + - + + +
+ +
- - - - - -
- - - + - -

i-scream CVS Repository

+
+

i-scream CVS Repository

The i-scream CVS Repository contains all code, documentation, and other files pertaining to all i-scream projects.

@@ -45,10 +37,10 @@ versions. There is also a link to download the latest version of any section.

We also have a facility to allow people to keep tabs on what's changed recently. The following are available:

-

Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
-Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
-Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
-Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29

+

Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
+Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
+Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
+Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29

Anonymous CVS Access (read-only)

@@ -56,12 +48,12 @@ Commits made since 29/03/2001:

When asked for a password, simply press enter. Replace [module] with the section you wish to checkout.

@@ -70,12 +62,12 @@ Replace [module] with the section you wish to checkout.

The i-scream development team have full write access to the CVS repository. This is only available over SSH, and can be done on most clients. First the following environment variables need to be set.

- -
CVS_RSH = ssh
-CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
+
+CVS_RSH = ssh
+CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
+
-

You should know your username and password already. After setting these you will need to enter your password each time you use a CVS command. Obviously this is a time wasting event, so an RSA key can be @@ -87,20 +79,21 @@ normal.

Other means of accessing CVS

-

We currently provide CVSup access to the repository, either for mirroring or -for maintaining an up-to-date local copy. You will probably want to create a -supfile that looks something like this;

- +

We currently provide CVSup access to +the repository, either for mirroring or for maintaining an up-to-date local +copy. You will probably want to create a supfile that looks something like +this;

-
*default host=cvsup.i-scream.org
+
+*default host=cvsup.i-scream.org
 *default base=/home/user/sup
 *default prefix=/home/user/i-scream
 *default release=cvs
 *default delete use-rel-suffix
 *default compress
-i-scream.cms.source tag=.

+i-scream.cms.source tag=.
+
-

The last item in that list is the collection you which to get. The collection "i-scream" is simply the whole repository, and is best used with no tag specified for mirroring. It is most likely that you will want to do that @@ -113,15 +106,18 @@ repository, generated by cvsplot, that allow you to see the progress of development. They're not that exciting, but do show when the work was done.

-

http://www.i-scream.org/cvsplot

+

+http://www.i-scream.org/cvsplot/ +

+
- + - -
+
- + + +
+ diff --git a/www/cvsplot/index.html b/www/cvsplot/index.shtml similarity index 71% rename from www/cvsplot/index.html rename to www/cvsplot/index.shtml index 8fbf0f3..227a5b6 100644 --- a/www/cvsplot/index.html +++ b/www/cvsplot/index.shtml @@ -1,13 +1,23 @@ + + i-scream cvs statistics + -

-

i-scream cvs statistics

+
+ +
+ + + +
+

i-scream cvs statistics

This webpage shows a graphical representation of the file count and line count for the source files.
Only the files in the cms module of cvs are listed. @@ -24,7 +34,15 @@ repository.

credits

These images were generated using the cvsplot program, which can be found here.

+
- + +
+ + + +
+ + diff --git a/www/cvsplot/index.xhtml b/www/cvsplot/index.xhtml new file mode 100644 index 0000000..227a5b6 --- /dev/null +++ b/www/cvsplot/index.xhtml @@ -0,0 +1,48 @@ + + + + + +i-scream cvs statistics + + + + + +
+ +
+ + + +
+

i-scream cvs statistics

+

This webpage shows a graphical representation of the file count and line +count for the source files.
+Only the files in the cms module of cvs are listed. +This page is updated at 7am daily.

+

You can also browse the cvs +repository.

+

file count

+

Count of the number of files since the start of the project.

+

Textual representation: filedata.txt

+

+

line count

+

Count of the number of lines of code and documentation since the start of the project.

+

Textual representation: linedata.txt

+

+

credits

+

These images were generated using the cvsplot program, which can be found here.

+
+ + + +
+ + + +
+ + + diff --git a/www/documentation/gettingstarted.shtml b/www/documentation/gettingstarted.shtml deleted file mode 100644 index 9230179..0000000 --- a/www/documentation/gettingstarted.shtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - Getting Started with the i-scream Central Monitoring System - - - - - - - - - - -
- - - - - - -

Getting Started with the i-scream Central Monitoring System

- -

1. Installing the corba services (pre-requisite for the server)

-

The server requires a CORBA Naming Service to run. It may be that you already -have such a system running, in which case you can use that. Simply edit the -jacorb.properties file to point to your Naming service. If you don't have a -naming service running you could just set up your own manually, but if like us -you want the easy approach, install our corba services program.

-

This program runs the naming service and provides a builtin webserver to -serve requests to the server application. The documentation details how to get -this running. It should simply be a case of extracting and running.

-

1. Installing the server

-

The first stage is to download and install the server application. The -latest versions of all i-scream applications can be found at the following -URL:

-

http://www.i-scream.org/downloads

-

Once downloaded, the archive should be extracted to a directory of your -choice. The server will run on most Java enabled platforms (including -Windows, Linux and FreeBSD).

-

The archive consists of only a few files and directories. The main file is -the iscream-server.jar archive which contains all the binary code for the -server. The lib directory contains other JAR archives which the server -requires to run. The etc directory contains (or will contain) -configuration for most of the i-scream central monitoring system. The next -step is to configure the server to suit your requirements.

-

2. Configuring the server

-

The configuration is split into two main files. The first, -default.properties can be considered a bootstrap configuration. This means -that it provides basic configuration to get the server started, after -which point the main configuration system takes over. This file should be -checked through, and is pretty well explained by comments.

-

The rest of the server configuration is based on system.conf. This can -hold the entire system configuration, including hosts. It may also specify -other configuration files to be included in the main configuration. This -file is also commented extensively.

-

This step may well take some time to get right, and you can come back to -it at any point. Lots of the configuration can be changed "on the fly" -as well.

-

For fuller and complete details of the configuration system, and the -server in general, please see the Server User Guide in the documentation -section of the website.

-

2a. Setting up the database

-

The i-scream central monitoring system can make use of a database for -generating historical reports. The documentation explains how you would -configure the system to do this. You will need to create a single basic -table yourself, this is also explained in the documentation.

-

3. Starting the server

-

Starting up the server is a trivial task. Usually you can just get away -with running the run script provided. This will boot the server up -displaying some basic information to the console. If something goes wrong, -the error message should point to the cause.

-

4. Setting up hosts

-

Hosts can be run on either Unix (tested with Solaris, FreeBSD and some -Linux distributions) or Windows. Both are equally easy to setup.

-

Firstly, the Unix host is called "ihost". This can be downloaded from the -i-scream website. Once extracted it just needs to be started up. You need two -pieces of information to do this: the filtermanager (part of the server) host -and port number. If you haven't changed much in terms of configuration this will -be the machine the server is running on, and port 4567. To start ihost you -simply type:

- -
ihost.pl server.domain.com port
- -

ihost will then contact the server to obtain it's configuration and start -sending information.

-

The windows host, winhost, is very similar. All you need to do is install it -using the provided installer in the download, and then edit the ini file to -provide the two bits of information above. Running the application starts up -communication with the server and data sending commences.

-

Full details of both of these hosts can be found in the relevant -documentation on the website.

-

5. Using Conient

-

Conient allows you to view, in real time, the data being sent by the -hosts. This is a perfect way to test that all the above steps have -successfully been completed.

-

At present Conient is simply another archive which can be extracted and -run. However, in the near future we hope to have an installer to make life -easier. Conient is a Java application and will run on most Java enabled -platforms.

-

After extracting, the run script can be used to start Conient, or in some -cases the JAR file can be executed manually. The GUI will then load. The -configuration section requires you to enter a host and port for the -server. By default this will be the machine on which the server is running -and port 4510. Conient will then connect upon request and start displaying -information.

-

Assuming data is displayed you have successfully setup the i-scream -central monitoring system. Well done!

-

This is explained in much more detail in the Conient documentation.

-

6. Setting up DBReporter

-

If you are making use of a database you can setup the DBReporter to -generate web-based reports of the information collected. This is just a -case of extracting the archive to a suitable location, configuring it, and -setting it to run on a regular basis (we suggest daily). DBReporter will -also ensure the database is kept relatively clean.

-

Full instructions are available in the DBReporter documentation.

-

7. Setting up the Web Interface

-

The Web interface allows you to view various aspects of the i-scream -central monitoring system's output. These include realtime viewing of data -(much like Conient), links to the DBReporter above, and full displaying of -the alerts that can be generated by the server.

-

The archive contains a series of PHP scripts which should be placed on -your PHP enabled web server. The configuration files allow you to tailor -the setup to suit your needs.

-

Full instructions are available in the relevant documentation.

-

8. Further

-

You may decide to expand your setup to cover a larger network. For example, a -distributed filter arrangement could cut down on the amount of traffic -being sent around the network. The server itself can be distributed to suit your -needs. You may wish to run the database section of the server on the same -machine as the database, while running the rest on another machine.

-

Some discussion about this is available in the server documentation.

-

If you have any questions about any of the above, please don't hesitate to -contact us at dev@i-scream.org. If you find we've missed something out, -again, please let us know.

-

Finally, we'd like to thank you for trying this i-scream product. We realise -that it's still at an early stage, and we therefore appreciate you taking -the time to try it out.

-

The i-scream team. - - - -

- - - diff --git a/www/documentation/index.shtml b/www/documentation/index.shtml deleted file mode 100644 index 6ff0e53..0000000 --- a/www/documentation/index.shtml +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - i-scream documentation - - - - - - - - - - -
- - - - -

i-scream documentation

-

This is the offical documentation for the i-scream central monitoring -system. They should be considered "correct" over any other older -documentation that still exists on the website. They are currently only -available in either Microsoft Word or PDF format.

- -

These documents are correct for the version of code available for download -from this website. However, there may be changes in the CVS version which -are not documented in the code. The link below shows what changes have been -made since the project completion date.

- - -Commits to the "cms" CVS module since project completion (29/03/2001) - -
-

User guides

-(HTML) Getting Started with the i-scream Central Monitoring System
-(Word|PDF) Unix/Linux ihost user guide
-(Word|PDF) Windows WinHost user guide
-(Word|PDF) Conient client user guide
-(Word|PDF) Server user guide
-(Word|PDF) CORBA Services user guide
-(Word|PDF) Web reports user guide
-(Word|PDF) Database reporter user guide
- -

Maintenance documentation for developers

-(Word|PDF) Unix/Linux ihost maintenance
-(Word|PDF) Windows WinHost maintenance
-(Word|PDF) Conient maintenance
-(Word|PDF) Server maintenance
-(Word|PDF) Web reports maintenance
-(Word|PDF) Database reporter maintenance
- -

Specification documents

-(Word|PDF) Original specification & problem domain
-(Word|PDF) TCP Protocol specifications
-(Word|PDF) Expected XML data from host to server
-(Word|PDF) XML recommendations for host to server UDP packets
-(Word|PDF) Document standards
-(Word|PDF) Java coding standards
- -

Other documents

-(Word|PDF) Risk analysis
-(Word|PDF) Estimated time allocation
-(Word|PDF) Implementation phases for our plan
-(Word|PDF) Estimated time allocation (revised)
-(Word|PDF) Meeting Minutes
-(Word|PDF) Use of the website
-(Word|PDF) Use of CVS and automated software builds
-(Word|PDF) Comparison to Big Brother
-
- - - -
- - - diff --git a/www/downloads/index.shtml b/www/downloads/index.shtml deleted file mode 100644 index 4c19706..0000000 --- a/www/downloads/index.shtml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - - - - - - i-scream software builds - - - - - - - - - - -
- - - - - - - - - - - - - - - - -
-

i-scream software builds

- -

All downloads are licensed under the GPL.

-

All new builds will be signed with our PGP key.

- -
-

current builds

- -

These builds are the latest development working copies. They are much - more developed than the downloads you'll find below. We recommend you - start here. This is the codebase from which we'll make a proper release - sometime in the future.

-

Snapshot Server

- -
-

old (but unchanging) builds

- -

These builds are from the end of the project. Development is still - continuing and can be found in the section above. These downloads are - not changing, and will not be updated until a release is made. Unless - you are really sure you want this version, get the one above. - -

Full documentation can be found by following the "Documentation" - link on the left-hand bar. Downloads below are the same, apart from - the archive format - with one exception being the host application.

- -

You will be asked to enter some basic information before - downloading, although this is purely optional. We value feedback - from people testing the i-scream products, so please feel free to - contact us at dev@i-scream.org.

- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build nameWindows downloads
(.zip format)		Unix downloads
(.tar.gz format)
i-scream Conient (GUI client)download download
i-scream host applicationdownload download
i-scream serverdownload download
i-scream PHP web reportsdownload download
i-scream historical database reporterdownload download
CORBA services managerdownload download
- - -
- - - diff --git a/www/features.shtml b/www/features.shtml deleted file mode 100644 index 99dc0ba..0000000 --- a/www/features.shtml +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - - - - Overview and Features - - - - - - - - - - - - -
- - - - - - - - -
- - -

Key Features of The System

- -
    -
  • A centrally stored, dynamically reloaded, system wide configuration system
    • -
  • A totally extendable monitoring system, nothing except the Host (which - generates the data) and the Clients (which view it) know any details about - the data being sent, allowing data to be modified without changes to the - server architecture.
    • -
  • Central server and reporting tools all Java based for multi-platform portability
    • -
  • Distribution of core server components over CORBA to allow appropriate components - to run independently and to allow new components to be written to conform with the - CORBA interfaces.
    • -
  • Use of CORBA to create a hierarchical set of data entry points to the system - allowing the system to handle event storms and remote office locations.
    • -
  • One location for all system messages, despite being distributed.
    • -
  • XML data protocol used to make data processing and analysing easily extendable
    • -
  • A stateless server which can be moved and restarted at will, while Hosts, - Clients, and reporting tools are unaffected and simply reconnect when the - server is available again.
    • -
  • Simple and open end protocols to allow easy extension and platform porting of Hosts - and Clients.
    • -
  • Self monitoring, as all data queues within the system can be monitored and raise - alerts to warn of event storms and impending failures (should any occur).
    • -
  • A variety of web based information displays based on Java/SQL reporting and - PHP on-the-fly page generation to show the latest alerts and data
    • -
  • Large overhead monitor Helpdesk style displays for latest Alerting information
    • -
- -

An Overview of the i-scream Central Monitoring System

- -

- The i-scream system monitors status and performance information - obtained from machines feeding data into it and then displays - this information in a variety of ways. -

- -

- This data is obtained through the running of small applications - on the reporting machines. These applications are known as - "Hosts". The i-scream system provides a range of hosts which are - designed to be small and lightweight in their configuration and - operation. See the website and appropriate documentation to - locate currently available Host applications. These hosts are - simply told where to contact the server at which point they are - totally autonomous. They are able to obtain configuration from - the server, detect changes in their configuration, send data - packets (via UDP) containing monitoring information, and send - so called "Heartbeat" packets (via TCP) periodically to indicate - to the server that they are still alive. -

- -

- It is then fed into the i-scream server. The server then splits - the data two ways. First it places the data in a database system, - typically MySQL based, for later extraction and processing by the - i-scream report generation tools. It then passes it onto to - real-time "Clients" which handle the data as it enters the system. - The system itself has an internal real-time client called the "Local - Client" which has a series of Monitors running which can analyse the - data. One of these Monitors also feeds the data off to a file - repository, which is updated as new data comes in for each machine, - this data is then read and displayed by the i-scream web services - to provide a web interface to the data. The system also allows TCP - connections by non-local clients (such as the i-scream supplied - Conient), these applications provide a real-time view of the data - as it flows through the system. -

- -

- The final section of the system links the Local Client Monitors to - an alerting system. These Monitors can be configured to detect - changes in the data past threshold levels. When a threshold is - breached an alert is raised. This alert is then escalated as the - alert persists through four live levels, NOTICE, WARNING, CAUTION - and CRITICAL. The alerting system keeps an eye on the level and - when a certain level is reached, certain alerting mechanisms fire - through whatever medium they are configured to send. -

- -
- - -
- - - - diff --git a/www/footer.inc b/www/footer.inc new file mode 100644 index 0000000..3e3982d --- /dev/null +++ b/www/footer.inc @@ -0,0 +1,7 @@ + diff --git a/www/header.inc b/www/header.inc new file mode 100644 index 0000000..7b81904 --- /dev/null +++ b/www/header.inc @@ -0,0 +1,2 @@ + diff --git a/www/index.shtml b/www/index.shtml index e3f44ff..c7ae98c 100644 --- a/www/index.shtml +++ b/www/index.shtml @@ -1,37 +1,195 @@ - - - - + - The i-scream Project - - +i-scream homepage + - + - - - - - -
- - - - +
- +
- -
+ - +
+

i-scream homepage

+ +
+ +
+ +

News

+ +

+ [21 March 2004] pystatgrab 0.1 released +

+

+ pystatgrab 0.1 has been released. This + is the first release of pystatgrab; a set of Python bindings for + libstatgrab. +

+ +

+ [10 March 2004] libstatgrab 0.9 released +

+

+ libstatgrab 0.9 + has been released and includes new features and support for new + platforms. +

+ +

+ [11 February 2004] libstatgrab 0.8.2 released +

+

+ libstatgrab + version 0.8.2 brings further platform support and Python bindings. +

+ +

+ [15 July 2003] i-scream support changes +

+

+ We have moved the i-scream support and bug tracking to a new + facility on the i-scream server. For further details please + see our support + page. +

+ +

+ [08 June 2003] server move +

+

+ The i-scream website, email, and CVS facilities are now all + run from a FreeBSD server. +

+

+ + Powered By FreeBSD + +

+ +

Projects

+ +

+ libstatgrab +

+ +

+ libstatgrab is a library and tool set for acquiring system + statistics from the operating system. An API is provided for + other applications to easily accesses a variety of system + statistics, including, amongst other things, CPU usage, VM + usage, disk statistics, and network interface usage. +

+

+ A handful of tools are also provided to make this information + more readily available to users. A curses based tool gives users + a "top like" view of the current state of their system, and a + "sysctl like" tool gives easy access to the statistics for other + applications that can't easily used the C API. +

+

+ Finally scripts are provided to quickly setup MRTG to use + libstatgrab for generating graphs of the available statistics. +

+ +

+ pystatgrab +

+ +

+ pystatgrab is a set of Python bindings for the libstatgrab + library. It provides a set of function calls identical to those + of libstatgrab, and returns data in structures that logically + map on to those of libstatgrab. +

- \ No newline at end of file +

+ Laroona +

+ +

+ Laroona is the new central monitoring system. It's still very + much in the early stages of development, and doesn't have any + code available for download yet. Look at the project page for + more on the development process. +

+ +

+ CMS - Central Monitoring System +

+ +

+ i-scream originally started out with just the CMS (Central + Monitoring System) project. Since then it's moved on to have + other related projects, as well as the CMS. +

+

+ The CMS is no longer being developed. We are now putting our + time into a new project redeveloping the CMS. We're taking the + good ideas from the old CMS, improving some of the weaknesses, + and we'll hopefully produce are far superior product. +

+ +

About

+ +

+ The i-scream group is a causual team of individuals with a + variety of personal interests, working together to produce + software, tools, and libraries that might be of use or interest + to others. +

+ +

+ To find out more about who we are see the Who + We Are webpage. +

+ +

Search

+ +

+ Use this form to search the whole i-scream website, courtesy + of Google. +

+
+ + Google + + + + + + +
+ +
+ + + +
+ + + +
+ + + diff --git a/www/index.xhtml b/www/index.xhtml index e3f44ff..c7ae98c 100644 --- a/www/index.xhtml +++ b/www/index.xhtml @@ -1,37 +1,195 @@ - - - - + - The i-scream Project - - +i-scream homepage + - + - - - - - -
- - - - +
- +
- -
+ - +
+

i-scream homepage

+ +
+ +
+ +

News

+ +

+ [21 March 2004] pystatgrab 0.1 released +

+

+ pystatgrab 0.1 has been released. This + is the first release of pystatgrab; a set of Python bindings for + libstatgrab. +

+ +

+ [10 March 2004] libstatgrab 0.9 released +

+

+ libstatgrab 0.9 + has been released and includes new features and support for new + platforms. +

+ +

+ [11 February 2004] libstatgrab 0.8.2 released +

+

+ libstatgrab + version 0.8.2 brings further platform support and Python bindings. +

+ +

+ [15 July 2003] i-scream support changes +

+

+ We have moved the i-scream support and bug tracking to a new + facility on the i-scream server. For further details please + see our support + page. +

+ +

+ [08 June 2003] server move +

+

+ The i-scream website, email, and CVS facilities are now all + run from a FreeBSD server. +

+

+ + Powered By FreeBSD + +

+ +

Projects

+ +

+ libstatgrab +

+ +

+ libstatgrab is a library and tool set for acquiring system + statistics from the operating system. An API is provided for + other applications to easily accesses a variety of system + statistics, including, amongst other things, CPU usage, VM + usage, disk statistics, and network interface usage. +

+

+ A handful of tools are also provided to make this information + more readily available to users. A curses based tool gives users + a "top like" view of the current state of their system, and a + "sysctl like" tool gives easy access to the statistics for other + applications that can't easily used the C API. +

+

+ Finally scripts are provided to quickly setup MRTG to use + libstatgrab for generating graphs of the available statistics. +

+ +

+ pystatgrab +

+ +

+ pystatgrab is a set of Python bindings for the libstatgrab + library. It provides a set of function calls identical to those + of libstatgrab, and returns data in structures that logically + map on to those of libstatgrab. +

- \ No newline at end of file +

+ Laroona +

+ +

+ Laroona is the new central monitoring system. It's still very + much in the early stages of development, and doesn't have any + code available for download yet. Look at the project page for + more on the development process. +

+ +

+ CMS - Central Monitoring System +

+ +

+ i-scream originally started out with just the CMS (Central + Monitoring System) project. Since then it's moved on to have + other related projects, as well as the CMS. +

+

+ The CMS is no longer being developed. We are now putting our + time into a new project redeveloping the CMS. We're taking the + good ideas from the old CMS, improving some of the weaknesses, + and we'll hopefully produce are far superior product. +

+ +

About

+ +

+ The i-scream group is a causual team of individuals with a + variety of personal interests, working together to produce + software, tools, and libraries that might be of use or interest + to others. +

+ +

+ To find out more about who we are see the Who + We Are webpage. +

+ +

Search

+ +

+ Use this form to search the whole i-scream website, courtesy + of Google. +

+
+ + Google + + + + + + +
+ +
+ + + + + + + + + + + diff --git a/www/javadoc/index.shtml b/www/javadoc/index.shtml deleted file mode 100644 index 87189ba..0000000 --- a/www/javadoc/index.shtml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - - - i-scream javadoc pages - - - - - - - - - -
- - - - -

Java Source code documentation

- -The whole of the server, and parts of the rest of the system have been -written in Java. Making use of the javadoc tool the following pages of -documentation have been automatically generated. - -

Server javadoc pages

-

Conient javadoc pages

-

Corba Service Manager javadoc pages

-

Util Package javadoc pages

- - -
- - - diff --git a/www/laroona/index.shtml b/www/laroona/index.shtml new file mode 100644 index 0000000..6abd061 --- /dev/null +++ b/www/laroona/index.shtml @@ -0,0 +1,66 @@ + + + + + +i-scream Laroona homepage + + + + + +
+ +
+ + + +
+ +

i-scream Laroona homepage

+ + + +

News

+ +

Sunday 21 March 2004

+

+Laroona project page created. +

+ +

What is Laroona?

+ +

+Laroona is a rewrite of the CMS. +

+ + +

Development

+ + +

+Laroona is currently in the early stages of development. Much of our development work is being done on +the i-scream Wiki. +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/laroona/index.xhtml b/www/laroona/index.xhtml new file mode 100644 index 0000000..6abd061 --- /dev/null +++ b/www/laroona/index.xhtml @@ -0,0 +1,66 @@ + + + + + +i-scream Laroona homepage + + + + + +
+ +
+ + + +
+ +

i-scream Laroona homepage

+ + + +

News

+ +

Sunday 21 March 2004

+

+Laroona project page created. +

+ +

What is Laroona?

+ +

+Laroona is a rewrite of the CMS. +

+ + +

Development

+ + +

+Laroona is currently in the early stages of development. Much of our development work is being done on +the i-scream Wiki. +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/left.inc b/www/left.inc deleted file mode 100644 index c826c7f..0000000 --- a/www/left.inc +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - - - - - - - -
- Contents -
-
-

- i-scream homepage -

-
main
- Downloads
- Documentation
- Screen Shots
- Reports Demo
- Features
-
- TODO List
- Javadoc Pages
-
- CVS Repository
- Mailing Lists
- Bug Tracking
- Support
-
- Licensing
-

-

-
other projects
- libstatgrab
- Java ACL's for TCP/UDP
-

-

-
internal papers
- Project Papers/Docs
- Meeting Minutes -

-

-
misc
- Problem Domain
- Who We Are
- PGP Key
- Acknowledgements -

-

-
links
- JacORB
- UKC - Computer Science
- W3 XML Information
- JAXP -

-

-
contact us
- dev@i-scream.org -

-

- - SourceForge Logo - -
- - Powered By FreeBSD - -
-
diff --git a/www/libstatgrab/index.shtml b/www/libstatgrab/index.shtml index ef0f8fc..c8368d0 100644 --- a/www/libstatgrab/index.shtml +++ b/www/libstatgrab/index.shtml @@ -1,39 +1,36 @@ - - - + - i-scream libstatgrab homepage +i-scream libstatgrab homepage + - + - - - - - -
- - - +
- +
-

libstatgrab

+ - +
+ +

i-scream libstatgrab homepage

-

News

 + + +

News

To get notifications of new libstatgrab releases why not subscribe @@ -41,11 +38,20 @@ to our project over on freshmeat?

+

Sunday 21 March 2004

+

+pystatgrab, a new package containing a set of Python bindings, +has been released. Check out it's project +page. +

+ +

Wednesday 10 March 2004

-Wednesday 10 March 2004

-Version 0.9 of libstatgrab has been released.
+Version 0.9 of libstatgrab has been released.
Download it here. +

+

This release brings new features and new platforms. We've added information about network interfaces (duplex, speed, etc) along with further statistics such as i/o packets, i/o errors, and @@ -55,22 +61,26 @@ which libstatgrab needs elevated privileges. See the NEWS file for more information.

+

Wednesday 11 February 2004

-Wednesday 11 February 2004

-Version 0.8.2 of libstatgrab has been released.
+Version 0.8.2 of libstatgrab has been released.
Download it here. +

+

The main focus of this release is adding support for Solaris 6. -We've also added python bindings so you can use libstatgrab directly -from python (see the extras directory). Finally, we've tidied up a +We've also added Python bindings so you can use libstatgrab directly +from Python (see the extras directory). Finally, we've tidied up a few bits of the code.

+

Wednesday 21 January 2004

-Wednesday 21 January 2004

-Version 0.8.1 of libstatgrab has been released.
+Version 0.8.1 of libstatgrab has been released.
Download it here. +

+

This release primarily fixes bugs. On Linux a file descriptor leak was fixed. On Solaris some significant speed increases were made to the disk mapping code, along with some bug fixes for Solaris 7 platforms. @@ -78,11 +88,13 @@ Also, the library part of libstatgrab (but not the tools) is now released under the LGPL instead of the GPL.

+

Tuesday 6 January 2004

-Tuesday 6 January 2004

-Version 0.8 of libstatgrab has been released.
+Version 0.8 of libstatgrab has been released.
Download it here. +

+

This release brings support for Linux 2.6 and partial support for Cygwin. On Solaris libstatgrab now returns disk names using cNtNdNsN names rather than the older sdN names. There are also a bunch of fixes and optimisations @@ -91,11 +103,13 @@ quicker to drop any elevated privileges libstatgrab may require on some operating systems.

+

Wednesday 22 October 2003

-Wednesday 22 October 2003

-Version 0.7 of libstatgrab has been released.
+Version 0.7 of libstatgrab has been released.
Download it here. +

+

The most significant change in this release is support for NetBSD 1.6.x. Parts of the FreeBSD code have been optimised, and an initialise function has been added to allow programs to drop any extra privileges @@ -105,44 +119,50 @@ saidar has been tweaked to work even if it can't get all the statistics.

+

Saturday 18 October 2003

-Saturday 18 October 2003

-Version 0.6.1 of libstatgrab has been released.
+Version 0.6.1 of libstatgrab has been released.
Download it here. +

+

This release brings support for FreeBSD 5 on sparc 64, and some bugfixes in FreeBSD memory statistics. Also, some fixes to saidar, and statgrab.

+

Friday 10 October 2003

-Friday 10 October 2003

-Version 0.6 of libstatgrab has been released.
+Version 0.6 of libstatgrab has been released.
You can download it from our mirror site here. +

+

This release includes some exciting new tools, support for FreeBSD 5.1, and documentation in manpages. Plus some major bugfixes and packaging enhancements.

+

Tuesday 09 September 2003

-Tuesday 09 September 2003

-We're pleased to announce a new release of libstatgrab.
+We're pleased to announce a new release of libstatgrab.
You can download version 0.5.1 from here.

+

Monday 25 August 2003

-Monday 25 August 2003

-We're pleased to announce a new release of libstatgrab.
+We're pleased to announce a new release of libstatgrab.
You can download version 0.5 from here. +

+

This release provides both documentation and examples, which we hope will make the package more useable. Stay tuned for the next release with some useful tools.

-

What is libstatgrab?

 +

What is libstatgrab?

libstatgrab is a library that provides cross platform access to @@ -171,12 +191,12 @@ a script to generate an MRTG configuration file to use statgrab.

-

Downloading

 +

Downloading

The latest version of libstatgrab can be downloaded from our primary download -mirror. +mirror. All downloads are pgp signed using our PGP Key.

@@ -188,20 +208,21 @@ contained within the archive. If you're using port to install libstatgrab for you.

-

Documentation

 +

Documentation

The only online documentation we have at the moment is the manual pages converted in to HTML format. It's probably best to start with the overview manual page: +

-

Then we have the manual pages for each function: +

-

-

Screenshot

 +

Screenshot

Here's what saidar looks like when it's running:

-saidar screenshot +saidar screenshot

+
+ + + +
- + - -
+ diff --git a/www/libstatgrab/index.xhtml b/www/libstatgrab/index.xhtml index ef0f8fc..c8368d0 100644 --- a/www/libstatgrab/index.xhtml +++ b/www/libstatgrab/index.xhtml @@ -1,39 +1,36 @@ - - - + - i-scream libstatgrab homepage +i-scream libstatgrab homepage + - + - - - - - -
- - - +
- +
-

libstatgrab

+ - +
+ +

i-scream libstatgrab homepage

-

News

 + + +

News

To get notifications of new libstatgrab releases why not subscribe @@ -41,11 +38,20 @@ to our project over on freshmeat?

+

Sunday 21 March 2004

+

+pystatgrab, a new package containing a set of Python bindings, +has been released. Check out it's project +page. +

+ +

Wednesday 10 March 2004

-Wednesday 10 March 2004

-Version 0.9 of libstatgrab has been released.
+Version 0.9 of libstatgrab has been released.
Download it here. +

+

This release brings new features and new platforms. We've added information about network interfaces (duplex, speed, etc) along with further statistics such as i/o packets, i/o errors, and @@ -55,22 +61,26 @@ which libstatgrab needs elevated privileges. See the NEWS file for more information.

+

Wednesday 11 February 2004

-Wednesday 11 February 2004

-Version 0.8.2 of libstatgrab has been released.
+Version 0.8.2 of libstatgrab has been released.
Download it here. +

+

The main focus of this release is adding support for Solaris 6. -We've also added python bindings so you can use libstatgrab directly -from python (see the extras directory). Finally, we've tidied up a +We've also added Python bindings so you can use libstatgrab directly +from Python (see the extras directory). Finally, we've tidied up a few bits of the code.

+

Wednesday 21 January 2004

-Wednesday 21 January 2004

-Version 0.8.1 of libstatgrab has been released.
+Version 0.8.1 of libstatgrab has been released.
Download it here. +

+

This release primarily fixes bugs. On Linux a file descriptor leak was fixed. On Solaris some significant speed increases were made to the disk mapping code, along with some bug fixes for Solaris 7 platforms. @@ -78,11 +88,13 @@ Also, the library part of libstatgrab (but not the tools) is now released under the LGPL instead of the GPL.

+

Tuesday 6 January 2004

-Tuesday 6 January 2004

-Version 0.8 of libstatgrab has been released.
+Version 0.8 of libstatgrab has been released.
Download it here. +

+

This release brings support for Linux 2.6 and partial support for Cygwin. On Solaris libstatgrab now returns disk names using cNtNdNsN names rather than the older sdN names. There are also a bunch of fixes and optimisations @@ -91,11 +103,13 @@ quicker to drop any elevated privileges libstatgrab may require on some operating systems.

+

Wednesday 22 October 2003

-Wednesday 22 October 2003

-Version 0.7 of libstatgrab has been released.
+Version 0.7 of libstatgrab has been released.
Download it here. +

+

The most significant change in this release is support for NetBSD 1.6.x. Parts of the FreeBSD code have been optimised, and an initialise function has been added to allow programs to drop any extra privileges @@ -105,44 +119,50 @@ saidar has been tweaked to work even if it can't get all the statistics.

+

Saturday 18 October 2003

-Saturday 18 October 2003

-Version 0.6.1 of libstatgrab has been released.
+Version 0.6.1 of libstatgrab has been released.
Download it here. +

+

This release brings support for FreeBSD 5 on sparc 64, and some bugfixes in FreeBSD memory statistics. Also, some fixes to saidar, and statgrab.

+

Friday 10 October 2003

-Friday 10 October 2003

-Version 0.6 of libstatgrab has been released.
+Version 0.6 of libstatgrab has been released.
You can download it from our mirror site here. +

+

This release includes some exciting new tools, support for FreeBSD 5.1, and documentation in manpages. Plus some major bugfixes and packaging enhancements.

+

Tuesday 09 September 2003

-Tuesday 09 September 2003

-We're pleased to announce a new release of libstatgrab.
+We're pleased to announce a new release of libstatgrab.
You can download version 0.5.1 from here.

+

Monday 25 August 2003

-Monday 25 August 2003

-We're pleased to announce a new release of libstatgrab.
+We're pleased to announce a new release of libstatgrab.
You can download version 0.5 from here. +

+

This release provides both documentation and examples, which we hope will make the package more useable. Stay tuned for the next release with some useful tools.

-

What is libstatgrab?

 +

What is libstatgrab?

libstatgrab is a library that provides cross platform access to @@ -171,12 +191,12 @@ a script to generate an MRTG configuration file to use statgrab.

-

Downloading

 +

Downloading

The latest version of libstatgrab can be downloaded from our primary download -mirror. +mirror. All downloads are pgp signed using our PGP Key.

@@ -188,20 +208,21 @@ contained within the archive. If you're using port to install libstatgrab for you.

-

Documentation

 +

Documentation

The only online documentation we have at the moment is the manual pages converted in to HTML format. It's probably best to start with the overview manual page: +

-

Then we have the manual pages for each function: +

-

-

Screenshot

 +

Screenshot

Here's what saidar looks like when it's running:

-saidar screenshot +saidar screenshot

+
+ + + +
- + - -
+ diff --git a/www/license.shtml b/www/license.shtml index 0acebd1..82aa75e 100644 --- a/www/license.shtml +++ b/www/license.shtml @@ -1,34 +1,30 @@ - - - + - i-scream licensing +i-scream licensing + - + + +
+ +
- - - - - -
- - - + -

i-scream central monitoring system licensing

+
+

i-scream software licensing

-

+

Unless explicitly mentioned the i-scream central monitoring system is licensed under the GNU General Public License (GPL). The full license can be found here, but is also given below for reference. -

+

 		    GNU GENERAL PUBLIC LICENSE
@@ -372,11 +368,15 @@ consider it more useful to permit linking proprietary applications with the
 library.  If this is what you want to do, use the GNU Library General
 Public License instead of this License.
+
+ + + + + + - -
+
diff --git a/www/license.xhtml b/www/license.xhtml index 0acebd1..82aa75e 100644 --- a/www/license.xhtml +++ b/www/license.xhtml @@ -1,34 +1,30 @@ - - - + - i-scream licensing +i-scream licensing + - + + +
+ +
- - - - - -
- - - + -

i-scream central monitoring system licensing

+
+

i-scream software licensing

-

+

Unless explicitly mentioned the i-scream central monitoring system is licensed under the GNU General Public License (GPL). The full license can be found here, but is also given below for reference. -

+

 		    GNU GENERAL PUBLIC LICENSE
@@ -372,11 +368,15 @@ consider it more useful to permit linking proprietary applications with the
 library.  If this is what you want to do, use the GNU Library General
 Public License instead of this License.
+
+ + + + + + - -
+
diff --git a/www/logos/centrepoint.jpg b/www/logos/centrepoint.jpg new file mode 100644 index 0000000..9639054 Binary files /dev/null and b/www/logos/centrepoint.jpg differ diff --git a/www/logos/eye.jpg b/www/logos/eye.jpg new file mode 100644 index 0000000..7d5667e Binary files /dev/null and b/www/logos/eye.jpg differ diff --git a/www/logos/fanafjord.jpg b/www/logos/fanafjord.jpg new file mode 100644 index 0000000..dca097b Binary files /dev/null and b/www/logos/fanafjord.jpg differ diff --git a/www/logos/flower.jpg b/www/logos/flower.jpg new file mode 100644 index 0000000..419b11e Binary files /dev/null and b/www/logos/flower.jpg differ diff --git a/www/logos/garedunord.jpg b/www/logos/garedunord.jpg new file mode 100644 index 0000000..26b948b Binary files /dev/null and b/www/logos/garedunord.jpg differ diff --git a/www/logos/lakegeneva.jpg b/www/logos/lakegeneva.jpg new file mode 100644 index 0000000..ea09aa2 Binary files /dev/null and b/www/logos/lakegeneva.jpg differ diff --git a/www/logos/lightning.jpg b/www/logos/lightning.jpg new file mode 100644 index 0000000..a2e811f Binary files /dev/null and b/www/logos/lightning.jpg differ diff --git a/www/logos/railwall.jpg b/www/logos/railwall.jpg new file mode 100644 index 0000000..6ee162c Binary files /dev/null and b/www/logos/railwall.jpg differ diff --git a/www/logos/roadrise.jpg b/www/logos/roadrise.jpg new file mode 100644 index 0000000..b3594f8 Binary files /dev/null and b/www/logos/roadrise.jpg differ diff --git a/www/logos/sea.jpg b/www/logos/sea.jpg new file mode 100644 index 0000000..07c3674 Binary files /dev/null and b/www/logos/sea.jpg differ diff --git a/www/logos/snowshed.jpg b/www/logos/snowshed.jpg new file mode 100644 index 0000000..c160c4c Binary files /dev/null and b/www/logos/snowshed.jpg differ diff --git a/www/logos/soho.jpg b/www/logos/soho.jpg new file mode 100644 index 0000000..16b793f Binary files /dev/null and b/www/logos/soho.jpg differ diff --git a/www/logos/street.jpg b/www/logos/street.jpg new file mode 100644 index 0000000..000ad91 Binary files /dev/null and b/www/logos/street.jpg differ diff --git a/www/logos/sun.jpg b/www/logos/sun.jpg new file mode 100644 index 0000000..569c98d Binary files /dev/null and b/www/logos/sun.jpg differ diff --git a/www/logos/sunset.jpg b/www/logos/sunset.jpg new file mode 100644 index 0000000..f6311ea Binary files /dev/null and b/www/logos/sunset.jpg differ diff --git a/www/logos/towerbridge.jpg b/www/logos/towerbridge.jpg new file mode 100644 index 0000000..a0d9580 Binary files /dev/null and b/www/logos/towerbridge.jpg differ diff --git a/www/logos/water.jpg b/www/logos/water.jpg new file mode 100644 index 0000000..a6b08cb Binary files /dev/null and b/www/logos/water.jpg differ diff --git a/www/mailinglists.shtml b/www/mailinglists.shtml index bab6884..c20803d 100644 --- a/www/mailinglists.shtml +++ b/www/mailinglists.shtml @@ -1,31 +1,23 @@ - - - - + - i-scream mailing lists - - +i-scream mailing lists + - + + +
+ +
- - - - - -
- - - + - -

i-scream Mailing Lists

+
+

i-scream Mailing Lists

i-scream runs a number of mailing lists geared towards both developers and users of i-scream products. At the present time the lists are generic to all @@ -35,8 +27,8 @@ per-project mailing lists. Here are a current lists.

dev@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/dev
-State: Closed
+Information: http://lists.i-scream.org/mailman/listinfo/dev
+State: Closed
Purpose: A discussion forum for developers only. This can also be used to contact the development team as a whole.

@@ -44,8 +36,8 @@ contact the development team as a whole.

commits@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/commits
-State: Open for subscription, but no posts should be sent here.
+Information: http://lists.i-scream.org/mailman/listinfo/commits
+State: Open for subscription, but no posts should be sent here.
Purpose: Daily commit logs from the i-scream CVS repository are sent to this list. If you wish to keep up on development, join this list.

@@ -53,8 +45,8 @@ list. If you wish to keep up on development, join this list.

cvs-all@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
-State: Open for subscription, but no posts should be sent here.
+Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
+State: Open for subscription, but no posts should be sent here.
Purpose: Emails are sent to this list whenever a commit happens to the i-scream cvs repository. If you want to be informed about commits as they happen, join this list. @@ -63,8 +55,8 @@ this list.

users@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/users
-State: Open for subscription and posts.
+Information: http://lists.i-scream.org/mailman/listinfo/users
+State: Open for subscription and posts.
Purpose: For discussion between users, developers, and anyone else. This is the place to ask questions and get support.

@@ -92,14 +84,15 @@ MailScanner to remove viruses before they get sent out to list members. We also use MailScanner to tag spam messages accordingly, and ensure that such messages are moderated.

+
- + - -
+
- + + +
+ diff --git a/www/mailinglists.xhtml b/www/mailinglists.xhtml index bab6884..c20803d 100644 --- a/www/mailinglists.xhtml +++ b/www/mailinglists.xhtml @@ -1,31 +1,23 @@ - - - - + - i-scream mailing lists - - +i-scream mailing lists + - + + +
+ +
- - - - - -
- - - + - -

i-scream Mailing Lists

+
+

i-scream Mailing Lists

i-scream runs a number of mailing lists geared towards both developers and users of i-scream products. At the present time the lists are generic to all @@ -35,8 +27,8 @@ per-project mailing lists. Here are a current lists.

dev@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/dev
-State: Closed
+Information: http://lists.i-scream.org/mailman/listinfo/dev
+State: Closed
Purpose: A discussion forum for developers only. This can also be used to contact the development team as a whole.

@@ -44,8 +36,8 @@ contact the development team as a whole.

commits@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/commits
-State: Open for subscription, but no posts should be sent here.
+Information: http://lists.i-scream.org/mailman/listinfo/commits
+State: Open for subscription, but no posts should be sent here.
Purpose: Daily commit logs from the i-scream CVS repository are sent to this list. If you wish to keep up on development, join this list.

@@ -53,8 +45,8 @@ list. If you wish to keep up on development, join this list.

cvs-all@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
-State: Open for subscription, but no posts should be sent here.
+Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
+State: Open for subscription, but no posts should be sent here.
Purpose: Emails are sent to this list whenever a commit happens to the i-scream cvs repository. If you want to be informed about commits as they happen, join this list. @@ -63,8 +55,8 @@ this list.

users@i-scream.org

-Information: http://lists.i-scream.org/mailman/listinfo/users
-State: Open for subscription and posts.
+Information: http://lists.i-scream.org/mailman/listinfo/users
+State: Open for subscription and posts.
Purpose: For discussion between users, developers, and anyone else. This is the place to ask questions and get support.

@@ -92,14 +84,15 @@ MailScanner to remove viruses before they get sent out to list members. We also use MailScanner to tag spam messages accordingly, and ensure that such messages are moderated.

+
- + - -
+
- + + +
+ diff --git a/www/menu.inc b/www/menu.inc new file mode 100644 index 0000000..eec74c7 --- /dev/null +++ b/www/menu.inc @@ -0,0 +1,54 @@ + diff --git a/www/minutes.shtml b/www/minutes.shtml deleted file mode 100644 index dc73cb2..0000000 --- a/www/minutes.shtml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - - - i-scream meeting minutes - - - - - - - - - - -
- - - - -

i-scream meeting minutes

- -

These are the minutes from all the meetings that took -place during development of the project. It is not expected -that there will be any further meetings during the continued -development of they i-scream central monitoring system.

- -
-
- - - - - -
-

March 2001

- 19 March 2001
- 12 March 2001
- 09 March 2001
- 05 March 2001 - -

February 2001

- 26 February 2001
- 19 February 2001
- 12 February 2001
- 05 February 2001
- -

January 2001

- 29 January 2001
- 22 January 2001
- 15 January 2001
- 08 January 2001 - -

December 2000

- 11 December 2000
- 04 December 2000		 -

November 2000

- 29 November 2000 (Sub meeting)
- 29 November 2000
- 28 November 2000 (Sub meeting)
- 27 November 2000
- 22 November 2000
- 20 November 2000
- 16 November 2000 (Sub meeting)
- 15 November 2000
- 13 November 2000 (Sub meeting)
- 13 November 2000
- 08 November 2000
- 06 November 2000
- 01 November 2000
- -

October 2000

- 30 October 2000
- 23 October 2000
- 18 October 2000
- 17 October 2000
- 05 October 2000
- -

September 2000

- 28 September 2000 -
-
-
- - -
- - - diff --git a/www/oldtodo.shtml b/www/oldtodo.shtml deleted file mode 100644 index 4e96379..0000000 --- a/www/oldtodo.shtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

(old) i-scream central monitoring system TODO list

- -This is the TODO list to be achieved by the end of the "project" period. -A -newer TODO list now exists to cover the future things -we plan to do with the development of the i-scream central monitoring system.

-Server

-
LocalClient Monitors: Users.
-
-Completed:
-----------
-22/03/2001 - FIX the major memory leak and deadlock issues.
-             LocalClient Monitors: Load, Processes, Queues.
-18/03/2001 - LocalClient Monitors: Disks/Memory need MB threshold
-15/03/2001 - Alert dumping needs to be organised better.
-             Running on Windows InetAddress.getHostName() doesn't return the FQDN.
-13/03/2001 - Thread naming, at least at a "what class it is" level.
-             Utilise the ConfigurationProxy throughout the server.
-             Sort out GC & Configuration objects (and CorbaHandlers).
-09/03/2001 - WebFeeder needs to dump Alerts to disk.
-08/03/2001 - WebFeeder needs to dump XML to disk
-             LocalClient Monitors: Disks, Service Checks
-07/03/2001 - Service Checks: FTP, POP3, IMAP, SSH, Telnet
-01/03/2001 - Make it easy to change flags to the java compiler.
-             Configuration groups need implementing.
-28/02/2001 - Queue identification ? Use a hash of the Queue ?
-             Fix the Queue "unlimited" size problem.
-27/02/2001 - (not needed) ClientInterface/DBInterface need to "pull" data ?
-             Builds on the website ?
-             Change build scripts to make iscream-server.java/tar.gz/zip
-25/02/2001 - Move checking of logging verbosity to the servant.
-23/02/2001 - print verbosity level with logging messages
-             functionality added to the LoggerServant
-23/02/2001 - Startup of components - eg. running DBInterface on another machine.
-             Now catches any problems relating to not finding a component if
-             a component has a dependancy.  The component manager will then
-             retry it after a given timeout.
-12/02/2001 - Logging of Queue.status() somehow.
-06/02/2001 - Make use of the PrintWriter "autoflush" feature :)
-28/01/2001 - Add dependency checking for the DOCOPY Makefile target.
-             Client Interface needs more functionality.
-             SQL Driver doesn't work in Windows.
-18/01/2001 - Heartbeats are still dropped.
-             CVS directories get added to build tar/zip file.
-             Problem on FreeBSD with zip file adding more files than it should.
-             Remove Component from util package -> ComponentManager.
-             Remove ReferenceManager from util package -> ComponentManager.
-             Add status methods to the Queue that return just values.
-             Clean up the util package, it shouldn't do logging etc.
-               -- done with the exception of ReferenceManager.
-16/01/2001 - Build a util package JAR file seperately.
-14/01/2001 - Javadoc pages on website ?
-               -- done for the server at least.
-12/01/2001 - Investigate the use of a Queue in the Filter, to replace the
-             current FilterThread setup.
-07/01/2001 - Makefile needs to copy non-java files to JAR (eg. images).
-02/01/2001 - Add making of Javadoc pages to make scripts.
-             Queuing system in the root filter.
-
- -

Conient

-
Completed:
-----------
-18/03/2001 - Switch to using the StringUtil class for the firewall command stuff.
-             Fix bug where it can take up to two packets to display
-             correct information.  This is most visible in service
-             checks, but can also be seen on disk, memory and anything
-             else that uses two data items from the packet for one
-             component.
-01/03/2001 - re-work host display and choosing mechanism (ie, make us 1.1 protocol)
-26/02/2001 - Rework system displaying of components for Swing Event Handling
-             Allow config to be written back to a local file
-             Allow local file config to be changed via the GUI
-05/02/2001 - allow disk components to alter their units
-             have some icons and the i-scream logo on display
-             show errors in windows rather than on the console
-             Fix error in packet stopping update of ALL hosts
-04/02/2001 - Write LOADS more data components
-03/02/2001 - Allow config to be obtained from the server
-30/01/2001 - Add option to handle firewalls
-29/01/2001 - Allow config to be obtained from a local file
-             Fix problem with memory display showing negative values at start
-             Ensure all Swing updates use the Swing Event Handling thread (partial - only data components)
-28/01/2001 - Tidy up network comms and link handling
-
- -

statgrab

-
Completed:
-----------
-20/03/2001 - Linux - CPU %'s not always right, 2 repititions ?
-19/03/2001 - Odd behaviour with more than 1000 processes, on Solaris at least
-             FreeBSD - grabbing memory total
-11/03/2001 - Solaris - If free memory changes to < 10Mb (?) it changes to K rather than M (thus not matched)
-
- -

C++ Host

-
UDP Packet size to 8Kb
-Porting to Linux/FreeBSD (Windows?)
-
- -

Winhost

-
Completed:
-----------
-19/03/2001 - Still needs to send the true uptime.
-             Processor ID should be packet.os.platform
-             Minor version joined with packet.os.version
-             Logo ? Pink icon ?
-             Solve OCX problem
-
- -

ihost

-
Completed:
-----------
-12/03/2001 - Produce a very quick "check script" which can be run by cron.
-
- -

Web Reports

-
Completed:
-----------
-22/03/2001 - Alert/System Summary Page (incl. helpdesk style)
-15/03/2001 - Individual Host Alert Summary Page(s)
-14/03/2001 - Individual Host Lastest Data Page(s) (including service checks)
-
- - -
- - - \ No newline at end of file diff --git a/www/pgpkey.shtml b/www/pgpkey.shtml index 94a945e..5c05749 100644 --- a/www/pgpkey.shtml +++ b/www/pgpkey.shtml @@ -1,68 +1,60 @@ - - - + - i-scream developer pgp key +i-scream PGP keys + - + + +
+ +
- - - - - -
- - - + -

i-scream developer pgp key

+
+

i-scream pgp keys

-

+

i-scream developer pgp key

+ +

This is the public key we use for signing i-scream -software releases.
You can also download a copy +software releases.
You can also download a copy here. -

+

- - - - -
- 
-
-
+
+
+
-

i-scream automated build pgp key

+

i-scream automated build pgp key

-

+

This is the public key we use for signing automated builds on our build server. This key is less trusted as it has no passphrase. We will only use this to sign things such as snapshot builds - all proper releases will be signing with the main key given -above.
You can also download a copy +above.
You can also download a copy here. -

- - - - - -
- 
-
-
- - -
+

+ +
+
+
+
+ + + +
+ + + +
diff --git a/www/pgpkey.xhtml b/www/pgpkey.xhtml index 94a945e..5c05749 100644 --- a/www/pgpkey.xhtml +++ b/www/pgpkey.xhtml @@ -1,68 +1,60 @@ - - - + - i-scream developer pgp key +i-scream PGP keys + - + + +
+ +
- - - - - -
- - - + -

i-scream developer pgp key

+
+

i-scream pgp keys

-

+

i-scream developer pgp key

+ +

This is the public key we use for signing i-scream -software releases.
You can also download a copy +software releases.
You can also download a copy here. -

+

- - - - -
- 
-
-
+
+
+
-

i-scream automated build pgp key

+

i-scream automated build pgp key

-

+

This is the public key we use for signing automated builds on our build server. This key is less trusted as it has no passphrase. We will only use this to sign things such as snapshot builds - all proper releases will be signing with the main key given -above.
You can also download a copy +above.
You can also download a copy here. -

- - - - - -
- 
-
-
- - -
+

+ +
+
+
+
+ + + +
+ + + +
diff --git a/www/powerlogo.gif b/www/powerlogo.gif deleted file mode 100644 index 79948b6..0000000 Binary files a/www/powerlogo.gif and /dev/null differ diff --git a/www/powerlogo_small.gif b/www/powerlogo_small.gif deleted file mode 100644 index 882c6fe..0000000 Binary files a/www/powerlogo_small.gif and /dev/null differ diff --git a/www/probdomain.shtml b/www/probdomain.shtml deleted file mode 100644 index e62b53a..0000000 --- a/www/probdomain.shtml +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - - The i-scream Project Problem Domain - - - - - - - - - - - - -
- - - - - - - - -
- - -

Original Problem

- -

- This is the original specification given to us when we - started the project. The i-scream central monitoring - system meets this specification, and aims to extend it - further. This is, however, where it all began. -

- -

Centralised Machine Monitoring

- -

- The Computer Science department has a number of different machines - running a variety of different operating systems. One of the tasks - of the systems administrators is to make sure that the machines - don't run out of resources. This involves watching processor loads, - available disk space, swap space, etc. -

- -

- It isn't practicle to monitor a large number of machines by logging - on and running commands such as 'uptime' on the unix machines, or - by using performance monitor for NT servers. Thus this project is - to write monitoring software for each platform supported which - reports resource usage back to one centralized location. System - Administrators would then be able to monitor all machines from this - centralised location. -

- -

- Once this basic functionality is implemented it could usefully be - expanded to include logging of resource usage to identify longterm - trends/problems, alerter services which can directly contact - sysadmins (or even the general public) to bring attention to problem - areas. Ideally it should be possible to run multiple instances of - the reporting tool (with all instances being updated in realtime) - and to to be able to run the reporting tool as both as stand alone - application and embeded in a web page. -

- -

- This project will require you to write code for the unix and Win32 - APIs using C and knowledge of how the underlying operating systems - manage resources. It will also require some network/distributed - systems code and a GUI front end for the reporting tool. It is - important for students undertaking this project to understand the - importance of writing efficient and small code as the end product - will really be most useful when machines start run out of processing - power/memory/disk. -

- -

- John Cinnamond (email jc) whose idea this is, will provide technical - support for the project. -

- - -
- - -
- - - - \ No newline at end of file diff --git a/www/projectpapers.shtml b/www/projectpapers.shtml deleted file mode 100644 index 4f81b07..0000000 --- a/www/projectpapers.shtml +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - i-scream project papers & documentation - - - - - - - - - - -
- - - - -

i-scream project papers & documentation

- -

These are documents created during the development of the project. -Many of them are now out of date, and have been superceeded by the -official documentation. Please select the documentation link on the -left to find the official documentation.

- -
-
- - - - -
- - Feature List - the ongoing list of features
- - Time Allocation Plan - the course required us to produce a plan - of what we were going to spend time on
- - Implementation Phases - an initial plan of how we were going to - proceed with development
- - Documentation Strategy - documentation plan with status of each document
-
- - Realtime Spec Outline - an idea of how some parts of the system worked
- - Document Specs - requirements and specification for all documentation
- - XMLviaUDP Specs - format of data to be sent from hosts over UDP
- - System Configuration - details of the initial configuration system
- - Coding Standards - standards for Java code
- - Host: expected data - data the host is expected to send
- - Logging System - details of the logging system
- - Using the Queue - details of the queueing system
- - Protocol Specs - specifications of all the protocols used
-
- - Using CORBA - how to run the server in the corba environment
- - Using CVS (part 1) - how to use CVS (basic)
- - Using CVS (part 2) - how to use CVS (advanced)
- - WBEM, CIM? - some ideas about the WBEM technologies
-
-
-
- - -
- - - \ No newline at end of file diff --git a/www/pystatgrab/index.shtml b/www/pystatgrab/index.shtml new file mode 100644 index 0000000..8db0cda --- /dev/null +++ b/www/pystatgrab/index.shtml @@ -0,0 +1,94 @@ + + + + + +i-scream pystatgrab homepage + + + + + +
+ +
+ + + +
+ +

i-scream pystatgrab homepage

+ + + +

News

+ +

+To get notifications of new pystatgrab releases why not subscribe +to our project over on +freshmeat? +

+ +

Sunday 21 March 2004

+

+Version 0.1 of pystatgrab has been released.
+Download it +here. +

+

+This is the first release of pystatgrab; a set of Python bindings +for the libstatgrab library. Although +lacking in documentation, it's fairly complete feature wise. +

+ +

What is pystatgrab?

+ +

+pystatgrab is a set of Python bindings for the +libstatgrab library. It installs as a module and provides a set of +function calls with identical names to the libstatgrab functions. The +returned data types also map logically on to the structures returned +by libstatgrab. +

+ +

+pystatgrab should work on any platform that libstatgrab will work on. +Currently, pystatgrab requires version 0.9 of libstatgrab to function. +

+ +

Downloading

+ +

+The latest version of pystatgrab can be downloaded from our +primary download +mirror. +All downloads are pgp signed using our PGP Key. +

+ +

+For installation instructions see the README file +contained within the archive. If you're using +FreeBSD you can make use of the +devel/py-statgrab +port to install pystatgrab (and libstatgrab) for you. +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/pystatgrab/index.xhtml b/www/pystatgrab/index.xhtml new file mode 100644 index 0000000..8db0cda --- /dev/null +++ b/www/pystatgrab/index.xhtml @@ -0,0 +1,94 @@ + + + + + +i-scream pystatgrab homepage + + + + + +
+ +
+ + + +
+ +

i-scream pystatgrab homepage

+ + + +

News

+ +

+To get notifications of new pystatgrab releases why not subscribe +to our project over on +freshmeat? +

+ +

Sunday 21 March 2004

+

+Version 0.1 of pystatgrab has been released.
+Download it +here. +

+

+This is the first release of pystatgrab; a set of Python bindings +for the libstatgrab library. Although +lacking in documentation, it's fairly complete feature wise. +

+ +

What is pystatgrab?

+ +

+pystatgrab is a set of Python bindings for the +libstatgrab library. It installs as a module and provides a set of +function calls with identical names to the libstatgrab functions. The +returned data types also map logically on to the structures returned +by libstatgrab. +

+ +

+pystatgrab should work on any platform that libstatgrab will work on. +Currently, pystatgrab requires version 0.9 of libstatgrab to function. +

+ +

Downloading

+ +

+The latest version of pystatgrab can be downloaded from our +primary download +mirror. +All downloads are pgp signed using our PGP Key. +

+ +

+For installation instructions see the README file +contained within the archive. If you're using +FreeBSD you can make use of the +devel/py-statgrab +port to install pystatgrab (and libstatgrab) for you. +

+ +
+ + + +
+ + + +
+ + + diff --git a/www/quotes.shtml b/www/quotes.shtml deleted file mode 100644 index c1a14dc..0000000 --- a/www/quotes.shtml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - Memorable Project Quotes - - - - - - - - - - -
- - - - - -

Memorable Project Quotes

- -

-These are all genuine quotes that came about during our time -developing the i-scream server, hosts, clients and reporting -system. -

- -

-AJ doc'ing and taking the i-scream pun too far -

- "An i-scream client connects to the i-scream and ...." -
-

- -

-AJ -

- "I'm gonna be raptor! grr!" -
-

- -

-Tim -

- "I'm not going to draw on the board with some fizzy jerks." -
-

- -

-Tim -

- "It's just programming, innit?" -
-

- -

-Paul -

- "Let's sell one sock... Quality." -
-

- -

-Tim -

- "Break my hand... arghhh." -
-

- -

-AJ -

- "But we haven't got any children yet..." -
-

- -

-Tim -

- "Do you like my gender?" -
-

- -

-Paul -

- "Do away with the vowels, damnit. Oh, it's got a 'u' in it, hasn't it..." -
-

- -

-Tim -

- "Long is, in fact, long long." -
-

- -

-Paul -

- "And the fish do their little funky shit." -
-

- -

-Tim -

- "Bloody hell, what are your feet doing over here?!" -
-

- -

-Paul -

- "There's an 'L' in XML, isn't there?" -
-

- -

-AJ -

- "Yeah, we're not paying anything for it, either... we just pay them once a month." -
-

- -

-Ash -

- "Do you want some tissues now?" -
-

- - -

- - - - \ No newline at end of file diff --git a/www/screenshots/alerter-email.gif b/www/screenshots/alerter-email.gif deleted file mode 100644 index 456f270..0000000 Binary files a/www/screenshots/alerter-email.gif and /dev/null differ diff --git a/www/screenshots/alerter-irc.gif b/www/screenshots/alerter-irc.gif deleted file mode 100644 index 01b935d..0000000 Binary files a/www/screenshots/alerter-irc.gif and /dev/null differ diff --git a/www/screenshots/conient-config.gif b/www/screenshots/conient-config.gif deleted file mode 100644 index 13f9d7e..0000000 Binary files a/www/screenshots/conient-config.gif and /dev/null differ diff --git a/www/screenshots/conient-main.gif b/www/screenshots/conient-main.gif deleted file mode 100644 index de70ef7..0000000 Binary files a/www/screenshots/conient-main.gif and /dev/null differ diff --git a/www/screenshots/conient-platform-info.gif b/www/screenshots/conient-platform-info.gif deleted file mode 100644 index 052d06e..0000000 Binary files a/www/screenshots/conient-platform-info.gif and /dev/null differ diff --git a/www/screenshots/conient-queues.gif b/www/screenshots/conient-queues.gif deleted file mode 100644 index 551f0d7..0000000 Binary files a/www/screenshots/conient-queues.gif and /dev/null differ diff --git a/www/screenshots/ihost-main.gif b/www/screenshots/ihost-main.gif deleted file mode 100644 index 47e8ec1..0000000 Binary files a/www/screenshots/ihost-main.gif and /dev/null differ diff --git a/www/screenshots/index.shtml b/www/screenshots/index.shtml deleted file mode 100644 index ef073f7..0000000 --- a/www/screenshots/index.shtml +++ /dev/null @@ -1,241 +0,0 @@ - - - - - - - - i-scream screenshots / overview - - - - - - - - - - - - - -
- - - - - - - - -
-
- - - - -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

i-scream - screenshots

-

(or the two minute - tour)

- -

This page provides a sequence of - screenshots to help you to gain a better understanding of the i-scream - distributed central monitoring system and how it may be applied in - networked environments.  Click on the thumbnails to view the full - size screenshots.

-

 

click to enlarge! -

 

Reports Centre - (Web)
- The i-scream reports centre provides a central access point to all - web-based reports that are provided by the i-scream system.  Reports - are available to display information about the current status of an - individual machine and any alerts pertaining to either an individual - machine, or a summary of alerts for all machines.  Historical - information about monitored machines may also be accessed from this point. -

 

click to enlarge! -

 

Latest Information - (Web)
- Here we are viewing the latest information provided by a host.  Bars - are used to represent values such as disk space and free memory as this - makes it easier to spot casual problems.  The small graph icons link - to historical reports of each field for the previous day.  The choice - of fields to display on this page is stored in a separate configuration - file. -

 

click to enlarge! -

 

Conient (Multiplatform - real-time client)
- Conient is a real-time client that - can hook into an i-scream server to allow the user to view host - information as it passes through the server.  The client displays - information provided by the hosts as well as the results of service checks - performed by the server on each host (eg FTP, Telnet, etc).  Conient - is written in Java and can thus be run on most operating systems. -

 

click to enlarge! -

 

Conient (Viewing - extra data)
- Less important host information may be viewed in a seperate window to - avoid clutter in Conient's display.  Details of the protocol for - host-to-server communications are freely available to developers.  - The protocol itself is extensible and client programs such as Conient - display even unrecognised data from modified host programs. -

 

click to enlarge! -

 

Conient - (Configuration)
- Conient is fully configurable from within the program itself.  - Multiple configurations may be saved.  Conient can also be configured - to connect to a server through a firewall via an SSH tunnel or suchlike. -

 

click to enlarge! -

 

ihost (Unix/Linux - host)
- The ihost is currently the main Unix/Linux/FreeBSD host application for - i-scream.  ihost is centrally configured by the server it connects to - and periodically sends information about the machine on which it is - running.  The ihost is written in Perl, so can be easily altered to - send extra information to your i-scream server. -

 

click to enlarge! -

 

WinHost (Windows - host)
- The WinHost is similar in concept to the ihost, however, this one runs on - Windows NT/2000 servers.  Again, the configuration is dynamically - obtained from the server.  The WinHost is typically only present in - the Windows system tray.  Double clicking on the system tray icon - will bring up a small window that allows data to be viewed and to force - reconfiguration with the server. -

 

click to enlarge! -

 

Alerts (Email)
- The i-scream server includes many alerting mechanisms.  Simple email - alerts may be sent out if desired.  Alert levels and frequencies may - be configured for the server.  This screenshot shows the format of a - typical alert; the contents of which are of course configurable. -

 

click to enlarge! -

 

Alerts (IRC bot)
- Another i-scream alerter comes in the form of an interactive IRC bot.  - This may reside in an IRC (Internet relay chat) channel and broadcasts - alerts if told to do so.  This screenshot shows a typical interaction - with a user in the "Bersirc" IRC client. -

 

click to enlarge! -

 

Alerts (Web page)
- Individual alerts and a summary of all alerts raised by the i-scream - server may be viewed on the alerts web pages.  These show the - different levels of alerts in configurable colours and provides specific - details about the alerts being raised for each machine. -

 

click to enlarge! -

 

Alerts (Public - helpdesk display)
- The reports centre also provides a - page that may be useful in configuring non-interactive public displays of - alerts.  These displays automatically refresh the page periodically - and supported web browsers may also automatically scroll the page to allow - a large font to be employed for easier reading from a distance. -

 

click to enlarge! -

 

Conient (Server queue - monitoring)
- The Conient client may also be used - to monitor information about the i-scream server itself.  Here we are - viewing the status of the internal queues within the server.  This - shows that the server is performing healthily and that there are no - bottlenecks. 
click to enlarge! -

 

Historical reports - (Web)
- Historical information is collated - by the i-scream server into (typically) a MySQL database.  A separate - program is used to produce the historical web reports These may be browsed - via this web-based interface (see screenshot).  The reports to be - generated for each machine and the size of the page are of course - configurable. -

 

click to enlarge! -

 

Historical reports - (Metadata)
- The historical report generation - also produces a number of other files that may be useful for third party - analysis tools.  The chart itself is written as a GIF image, as well - as a small file suitable for including on PHP pages that specifies the - minimum and maximum values during the 24 hour period.  A file - containing the raw plot data is also produced to enable the use of third - party on-the-fly plotting tools. -

 

click to enlarge! -

 

The i-scream server
- The server is distributed and may - therefore have multiple points of data entry and run on more than one - machine.  This helps to reduce the amount of host traffic over large - networks and reduces potential bottlenecks.  The server is written in - Java to allow it to run on most operating systems.  This exciting - screenshot shows the i-scream server running ;-) -

 

-
-
- - - - -
- - - diff --git a/www/screenshots/reports-alerts-all.gif b/www/screenshots/reports-alerts-all.gif deleted file mode 100644 index bbed02b..0000000 Binary files a/www/screenshots/reports-alerts-all.gif and /dev/null differ diff --git a/www/screenshots/reports-main.gif b/www/screenshots/reports-main.gif deleted file mode 100644 index 3cc4c28..0000000 Binary files a/www/screenshots/reports-main.gif and /dev/null differ diff --git a/www/screenshots/reports-public-autoscroll.gif b/www/screenshots/reports-public-autoscroll.gif deleted file mode 100644 index 366c76a..0000000 Binary files a/www/screenshots/reports-public-autoscroll.gif and /dev/null differ diff --git a/www/screenshots/reports-raptor-latest-misc.gif b/www/screenshots/reports-raptor-latest-misc.gif deleted file mode 100644 index 2df5d54..0000000 Binary files a/www/screenshots/reports-raptor-latest-misc.gif and /dev/null differ diff --git a/www/screenshots/reports-raptor-load15.gif b/www/screenshots/reports-raptor-load15.gif deleted file mode 100644 index 068fb9e..0000000 Binary files a/www/screenshots/reports-raptor-load15.gif and /dev/null differ diff --git a/www/screenshots/reports-raptor-users.gif b/www/screenshots/reports-raptor-users.gif deleted file mode 100644 index 7a84e3e..0000000 Binary files a/www/screenshots/reports-raptor-users.gif and /dev/null differ diff --git a/www/screenshots/server-main.gif b/www/screenshots/server-main.gif deleted file mode 100644 index 7622e14..0000000 Binary files a/www/screenshots/server-main.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-alerter-email.gif b/www/screenshots/thumbnail-alerter-email.gif deleted file mode 100644 index e6e93c1..0000000 Binary files a/www/screenshots/thumbnail-alerter-email.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-alerter-irc.gif b/www/screenshots/thumbnail-alerter-irc.gif deleted file mode 100644 index d652765..0000000 Binary files a/www/screenshots/thumbnail-alerter-irc.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-conient-config.gif b/www/screenshots/thumbnail-conient-config.gif deleted file mode 100644 index 7b851ec..0000000 Binary files a/www/screenshots/thumbnail-conient-config.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-conient-main.gif b/www/screenshots/thumbnail-conient-main.gif deleted file mode 100644 index 592331f..0000000 Binary files a/www/screenshots/thumbnail-conient-main.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-conient-platform-info.gif b/www/screenshots/thumbnail-conient-platform-info.gif deleted file mode 100644 index ffcd3b1..0000000 Binary files a/www/screenshots/thumbnail-conient-platform-info.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-conient-queues.gif b/www/screenshots/thumbnail-conient-queues.gif deleted file mode 100644 index adf3425..0000000 Binary files a/www/screenshots/thumbnail-conient-queues.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-ihost-main.gif b/www/screenshots/thumbnail-ihost-main.gif deleted file mode 100644 index 3f23760..0000000 Binary files a/www/screenshots/thumbnail-ihost-main.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-alerts-all.gif b/www/screenshots/thumbnail-reports-alerts-all.gif deleted file mode 100644 index 3396177..0000000 Binary files a/www/screenshots/thumbnail-reports-alerts-all.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-main.gif b/www/screenshots/thumbnail-reports-main.gif deleted file mode 100644 index 1c8624e..0000000 Binary files a/www/screenshots/thumbnail-reports-main.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-public-autoscroll.gif b/www/screenshots/thumbnail-reports-public-autoscroll.gif deleted file mode 100644 index 5ad6dcd..0000000 Binary files a/www/screenshots/thumbnail-reports-public-autoscroll.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-raptor-latest-misc.gif b/www/screenshots/thumbnail-reports-raptor-latest-misc.gif deleted file mode 100644 index 31dab42..0000000 Binary files a/www/screenshots/thumbnail-reports-raptor-latest-misc.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-raptor-load15.gif b/www/screenshots/thumbnail-reports-raptor-load15.gif deleted file mode 100644 index 0f45ac6..0000000 Binary files a/www/screenshots/thumbnail-reports-raptor-load15.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-reports-raptor-users.gif b/www/screenshots/thumbnail-reports-raptor-users.gif deleted file mode 100644 index c87b4bf..0000000 Binary files a/www/screenshots/thumbnail-reports-raptor-users.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-server-main.gif b/www/screenshots/thumbnail-server-main.gif deleted file mode 100644 index fddaa67..0000000 Binary files a/www/screenshots/thumbnail-server-main.gif and /dev/null differ diff --git a/www/screenshots/thumbnail-winhost-main.gif b/www/screenshots/thumbnail-winhost-main.gif deleted file mode 100644 index 44e595e..0000000 Binary files a/www/screenshots/thumbnail-winhost-main.gif and /dev/null differ diff --git a/www/screenshots/winhost-main.gif b/www/screenshots/winhost-main.gif deleted file mode 100644 index 13ad719..0000000 Binary files a/www/screenshots/winhost-main.gif and /dev/null differ diff --git a/www/skeleton.shtml b/www/skeleton.shtml new file mode 100644 index 0000000..67a28f4 --- /dev/null +++ b/www/skeleton.shtml @@ -0,0 +1,35 @@ + + + + + +skeleton + + + + + +
+ +
+ + + +
+

Skeleton Page

+

Section

+

Content

+

Body Text

+
+ + + +
+ + + +
+ + + diff --git a/www/skeleton.xhtml b/www/skeleton.xhtml new file mode 100644 index 0000000..67a28f4 --- /dev/null +++ b/www/skeleton.xhtml @@ -0,0 +1,35 @@ + + + + + +skeleton + + + + + +
+ +
+ + + +
+

Skeleton Page

+

Section

+

Content

+

Body Text

+
+ + + +
+ + + +
+ + + diff --git a/www/style.inc b/www/style.inc new file mode 100644 index 0000000..67346f6 --- /dev/null +++ b/www/style.inc @@ -0,0 +1,2 @@ + + diff --git a/www/styles/print.css b/www/styles/print.css new file mode 100644 index 0000000..7f85f3c --- /dev/null +++ b/www/styles/print.css @@ -0,0 +1,46 @@ +html { + margin: 0; + padding: 0; +} + +body { + background: white; + color: black; + margin: 0; + padding: 0; +} + +/* Contains the menu */ +#menu { + display: none; +} + +/* Contains the header */ +#header { + display: none; +} + +/* Contains the footer */ +#footer p { + text-align: center; + font-size: x-small; +} + +/* Contains the body text of the page */ +#contents h1 { + border-top: 3px solid #000066; + border-bottom: 3px solid #000066; +} +#contents h2 { + border-bottom: 2px solid #000066; +} +#contents h3 { + border-bottom: 1px solid #000066; +} +#topnav { + display: none; +} + +img { + border: 0; +} diff --git a/www/styles/style.css b/www/styles/style.css new file mode 100644 index 0000000..5a4c3bf --- /dev/null +++ b/www/styles/style.css @@ -0,0 +1,131 @@ +html { + margin: 0; + padding: 0; +} + +body { + background: white; + color: black; + font-family: sans-serif; + font-size: small; + margin: 0; + padding: 0; +} + +/* Contains the entire of the page */ +#container { + padding: 0px; +} + +/* Contains the menu */ +#menu { + float: left; + position: absolute; + top: 0px; + left: 0px; + width: 150px; + background: #eeeeFF; + border-right: 1px solid #000066; + border-bottom: 1px solid #000066; +} +#menu .cornerlogo { + margin: -3px; + margin-bottom: 1px; +} +#menu .heading { + background: #000066; + color: white; + margin: 0px; + padding: 3px; +} +#menu p { + margin: 5px; + padding: 5px 0 5px 0; + text-align: center; +} +#menu .logo { + margin: 0; + text-align: center; +} + +/* Contains the main page - including header and footer */ +#main { + margin-left: 151px; + padding: 0px; + position: relative; +} + +/* Contains the header */ +#header { + padding: 0px; + display: none; +} + +/* Contains the footer */ +#footer { + padding: 60px 0 5px 0; +} +#footer p { + text-align: center; + font-size: x-small; +} + +/* Contains the body text of the page */ +#contents { + padding: 0 15px 0 15px; +} +#contents .top { + margin-top: 0px; +} +#contents h1 { + padding: 5px; + margin: 30px -15px 20px -15px; + background-color: #eeeeff; + border-bottom: 5px solid #000066; + color: #000066; + text-align: right; +} +#contents h2 { + padding: 4px; + margin: 20px -10px 20px -10px; + background-color: #eeeeff; + border-bottom: 2px solid #000066; +} +#contents h3 { + padding-top: 5px; + margin: 10px -5px 10px -5px; + border-bottom: 1px solid #000066; +} +#contents pre { + border-left: 2px solid red; + margin-left: 5px; + padding-left: 5px; + background-color: #f0f0f0; + font-size: larger; +} +#topnav { + margin: -15px -10px 0 0; + padding: 0px; + text-align: right; + background-color: transparent; +} +#topnav ul { + padding-left: 0; + margin-left: 0; + display: inline; +} +#topnav li { + padding: 3px; + list-style: none; + display: inline; +} + +/* All images have no border */ +img { + border: 0; +} + +/* For when we want to hide something to CSS browsers */ +.invisible { + display: none; +} diff --git a/www/support.shtml b/www/support.shtml index eb070af..338fc4c 100644 --- a/www/support.shtml +++ b/www/support.shtml @@ -1,35 +1,27 @@ - - - - + - i-scream Support - - +i-scream support + - + + +
+ +
- - - - - -
- - - + - -

i-scream Support

+
+

i-scream Support

i-scream uses RT to track support requests. We've set up two addresses to help seperate the two main -types of requests. +types of requests.

bugs@i-scream.org

@@ -53,14 +45,15 @@ sort out you problem. Please make sure you read the documentation Once your email has been received you will get an acknowledgement by email and details of how to view your tickets over the web.

+
- + - -
+
- + + +
+ diff --git a/www/support.xhtml b/www/support.xhtml index eb070af..338fc4c 100644 --- a/www/support.xhtml +++ b/www/support.xhtml @@ -1,35 +1,27 @@ - - - - + - i-scream Support - - +i-scream support + - + + +
+ +
- - - - - -
- - - + - -

i-scream Support

+
+

i-scream Support

i-scream uses RT to track support requests. We've set up two addresses to help seperate the two main -types of requests. +types of requests.

bugs@i-scream.org

@@ -53,14 +45,15 @@ sort out you problem. Please make sure you read the documentation Once your email has been received you will get an acknowledgement by email and details of how to view your tickets over the web.

+
- + - -
+
- + + +
+ diff --git a/www/title.inc b/www/title.inc deleted file mode 100644 index a22c39a..0000000 --- a/www/title.inc +++ /dev/null @@ -1,8 +0,0 @@ - - - - -

\ No newline at end of file diff --git a/www/todo.shtml b/www/todo.shtml deleted file mode 100644 index f706cfd..0000000 --- a/www/todo.shtml +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

i-scream central monitoring system TODO list

- -

This page lists the things we plan to do with the -i-scream central monitoring system in the future.

- -

TODO: -

    -
  • monitoring of users logging in & out
    • -
  • web-based configuration system
    • -
  • cleaner separation of some of the CORE functions (such as configuration - and logging) as independent services
    • -
  • grouping of hosts in frontends using server config groups
    • -
  • security of filters - ACL's
    • -
- -

To view the older TODO list from the project -please click here.

- - -
- - - diff --git a/www/toucan.gif b/www/toucan.gif deleted file mode 100644 index 432d65d..0000000 Binary files a/www/toucan.gif and /dev/null differ diff --git a/www/welcome.inc b/www/welcome.inc deleted file mode 100644 index 0311fc5..0000000 --- a/www/welcome.inc +++ /dev/null @@ -1,30 +0,0 @@ - - - -

-

- - - - -
- Description -
- -

- - Welcome to the i-scream Central Monitoring System.
- The i-scream system provides a free, centrally configurable distributed - server to monitor the status and performance of Solaris, Linux, FreeBSD - and Windows machines on a network. The server can raise alerts using - email, IRC or a large public information display. Information may also - be browsed interactively via the web or using our multi-platform client. - -

- -
-
-
diff --git a/www/who.shtml b/www/who.shtml index 071aa10..c2f3d22 100644 --- a/www/who.shtml +++ b/www/who.shtml @@ -1,88 +1,77 @@ - - - - + - Who We Are - - - +skeleton + - + - - - - - -
- - - +
- - - - -
- - -

Who We Are

+
-

- We started as a group of four 3rd year - Computer Science students - at the University of Kent doing our final year project. Since - then we've had a few changes in developers, but we're moving - the project on. Here's who we are. + + +

+

Who We Are

+ +

+ We started out as a group of four final year Computer + Science students at the University of Kent doing our final year project. During that year + we developed the CMS package more or less as it stands today. +

+

+ Since the end of that year we've had a few changes in members, but we're still developing + software. We've taken the CMS and developed it further, and we've written + libraries to support it. We're now working on a new system to replace it known currently as Laroona.

-

Current developers

+

Current team

-

- Tim Bishop - tim@i-scream.org -

+

+ Tim Bishop - tdb@i-scream.org

+ -

- Alex Moore - aj@i-scream.org +

+ Alex Moore - ajm@i-scream.org

-

+

Adam Sampson - ats@i-scream.org -

+ -

- Pete Saunders - pajs@i-scream.org -

+

+ Peter Saunders - pajs@i-scream.org

+ -

+

Group Mailing List - dev@i-scream.org

- - -
+
- -
+ - + + + + + + diff --git a/www/who.xhtml b/www/who.xhtml index 071aa10..c2f3d22 100644 --- a/www/who.xhtml +++ b/www/who.xhtml @@ -1,88 +1,77 @@ - - - - + - Who We Are - - - +skeleton + - + - - - - - -
- - - +
- - - - -
- - -

Who We Are

+
-

- We started as a group of four 3rd year - Computer Science students - at the University of Kent doing our final year project. Since - then we've had a few changes in developers, but we're moving - the project on. Here's who we are. + + +

+

Who We Are

+ +

+ We started out as a group of four final year Computer + Science students at the University of Kent doing our final year project. During that year + we developed the CMS package more or less as it stands today. +

+

+ Since the end of that year we've had a few changes in members, but we're still developing + software. We've taken the CMS and developed it further, and we've written + libraries to support it. We're now working on a new system to replace it known currently as Laroona.

-

Current developers

+

Current team

-

- Tim Bishop - tim@i-scream.org -

+

+ Tim Bishop - tdb@i-scream.org

+ -

- Alex Moore - aj@i-scream.org +

+ Alex Moore - ajm@i-scream.org

-

+

Adam Sampson - ats@i-scream.org -

+ -

- Pete Saunders - pajs@i-scream.org -

+

+ Peter Saunders - pajs@i-scream.org

+ -

+

Group Mailing List - dev@i-scream.org

- - -
+
- -
+ - + + + + + +