Revision 1.30 - (view) (annotate) - [select for diffs]
Sun Aug 1 10:40:45 2004 UTC (19 years, 9 months ago) by tdb
Branch: MAIN
CVS Tags: HEAD
Changes since 1.29: +3 -3 lines
Diff to previous 1.29

Catch a lot of old URL's and update them. Also remove a couple of old files
that aren't used.

OK - I can still program Java, I just can't remember how this works :-)

Revision 1.28 - (view) (annotate) - [select for diffs]
Thu Jan 15 13:41:47 2004 UTC (20 years, 3 months ago) by tdb
Branch: MAIN
Changes since 1.27: +5 -2 lines
Diff to previous 1.27

Assuming I can still program in Java, these changes allow monitoring to
be disabled at a per-host level or a per-host-per-monitor level.

Changed the server to use the external util package. Quite a minor change,
but does affect a lot of files.

Revision 1.26 - (view) (annotate) - [select for diffs]
Tue May 21 16:47:16 2002 UTC (21 years, 11 months ago) by tdb
Branch: MAIN
Changes since 1.25: +3 -2 lines
Diff to previous 1.25

Added URL to GPL headers.

i-scream is now licensed under the GPL. I've added the GPL headers to every
source file, and put a full copy of the license in the appropriate places.
I think I've covered everything. This is going to be a mad commit ;)

Revision 1.24 - (view) (annotate) - [select for diffs]
Tue May 29 17:02:34 2001 UTC (22 years, 11 months ago) by tdb
Branch: MAIN
Branch point for: SERVER_PIRCBOT
Changes since 1.23: +9 -9 lines
Diff to previous 1.23

Major change in the java package naming. This has been held off for some time
now, but it really needed doing. The future packaging of all i-scream products
will be;

uk.org.iscream.<product>.<subpart>.*

In the case of the central monitoring system server this will be;

uk.org.iscream.cms.server.*

The whole server has been changed to follow this structure, and tested to a
smallish extent. Further changes in other parts of the CMS will follow.

Fully javadoc'd all the monitors. Also made a few little changes here and there,
removing code that had been duplicated by copying other monitors, and tidying
up any silly little things (such has hardcoded integer values).

Revision 1.22 - (view) (annotate) - [select for diffs]
Thu Mar 22 17:57:05 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.21: +22 -20 lines
Diff to previous 1.21

Modified to use the new style queuing in the local client

Added new Monitor's for Load and Process counts.

Revision 1.20 - (view) (annotate) - [select for diffs]
Wed Mar 21 23:58:43 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.19: +4 -4 lines
Diff to previous 1.19

Now uses the new register attribute support to allow specific thresholds for cpu attributes

The whole server package structure has been changed.
Old Package: uk.ac.ukc.iscream.*
New Package: uk.org.iscream.*

Revision 1.18 - (view) (annotate) - [select for diffs]
Fri Mar 9 03:30:55 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.17: +16 -7 lines
Diff to previous 1.17

TOTALLY re-wrote the Register class and made appropriate changes thoughout.  It
is now much more obvious what is going on in many places.

The problem was probably caused by doing CPU as a first monitor and hard coding
the number of attributes a Register stores.  Now if a monitor wants to store
multiple attributes, it has to do that itself.  This makes alot of things
much more readable and inteligable as a result.

Now displays the attribute name correctly.

Revision 1.16 - (view) (annotate) - [select for diffs]
Tue Mar 6 22:35:01 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.15: +8 -77 lines
Diff to previous 1.15

Changed the existing monitor's to use the skeleton class.

Now passes the time since the first alert for a problem occoured.

Also has support for formatting and displaying this information as obtained from the config

Revision 1.14 - (view) (annotate) - [select for diffs]
Mon Mar 5 12:45:51 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.13: +10 -7 lines
Diff to previous 1.13

Now shows OK alerts if the previous alert exceeded the alerters level

now FINALLY detects reverting to OK levels correctly.

Revision 1.12 - (view) (annotate) - [select for diffs]
Sun Mar 4 03:42:34 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.11: +2 -6 lines
Diff to previous 1.11

now only releases an alert level once the timeout has expired properly.

Revamped monitoring and alert fireing mechanism.
Now takes account of timing of last alerts.
Now uses threshold value a guide to how quickly alerts should be escalated.

Revision 1.10 - (view) (annotate) - [select for diffs]
Fri Mar 2 03:59:25 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.9: +4 -4 lines
Diff to previous 1.9

fixed array bound problems as we're counting backwards now

Totally revamped to handle alerting better.
Designed using the Register class to NOT spam on multiple alerts of the same level.

Revision 1.8 - (view) (annotate) - [select for diffs]
Fri Mar 2 02:47:48 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.7: +27 -13 lines
Diff to previous 1.7

Some checks for null items.

Now has logging lines.
Only monitors data packets.

Revision 1.6 - (view) (annotate) - [select for diffs]
Fri Mar 2 01:07:04 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.5: +3 -3 lines
Diff to previous 1.5

now implements correct interface

now displays errors on configuration

Revision 1.4 - (view) (annotate) - [select for diffs]
Fri Mar 2 01:01:41 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.3: +6 -3 lines
Diff to previous 1.3

Now catches configuration errors and handles properly

It seems we forgot something vital... the source of the message :)

Revision 1.2 - (view) (annotate) - [select for diffs]
Fri Mar 2 00:16:20 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.1: +46 -3 lines
Diff to previous 1.1

CPU__Monitor is now fleshed out.

A bare bones initial Monitor for CPU packets....