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

Revision 1.21 - (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.20: +42 -43 lines
Diff to previous 1.20

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.19 - (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.18: +3 -2 lines
Diff to previous 1.18

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.17 - (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.16: +5 -5 lines
Diff to previous 1.16

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.

Now allows the use of a default timeout value for all Monitors

Revision 1.15 - (view) (annotate) - [select for diffs]
Thu Mar 22 00:31:24 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.14: +9 -4 lines
Diff to previous 1.14

Now checks both attribute and default if the config isn't there for the attribute.

Now has support for using a specific attribute threshold

Revision 1.13 - (view) (annotate) - [select for diffs]
Thu Mar 15 03:25:41 2001 UTC (23 years, 1 month ago) by tdb
Branch: MAIN
Changes since 1.12: +6 -4 lines
Diff to previous 1.12

Now an OK alert will have an initialAlertTime that follows from the alert it is
giving on OK for.

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

Revision 1.11 - (view) (annotate) - [select for diffs]
Fri Mar 9 03:30:54 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.10: +56 -83 lines
Diff to previous 1.10

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.

What can I say ? (it was his fault!)

Revision 1.9 - (view) (annotate) - [select for diffs]
Tue Mar 6 20:03:50 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.8: +3 -3 lines
Diff to previous 1.8

Fixed it properly this time :) The logic was slightly flawed...

A logic error in the escalation method. It would go to FINAL if it was anything
*other* than the one before final.

Revision 1.7 - (view) (annotate) - [select for diffs]
Tue Mar 6 19:24:25 2001 UTC (23 years, 2 months ago) by tdb
Branch: MAIN
Changes since 1.6: +6 -3 lines
Diff to previous 1.6

Fix to stop the escalation (to a lower level) when we are already on the FINAL
level.

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.5 - (view) (annotate) - [select for diffs]
Tue Mar 6 01:40:24 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.4: +51 -4 lines
Diff to previous 1.4

Now has support for reaching the FINAL alert level.
This counts the number of times the highest alert level has been
reached, and then escalates to a FINAL if it exceeds
reachFINALcount.  If that value isn't configured, or is mis-configured, it will
ignore FINAL's.

Error catching in the configuration sections.

Revision 1.3 - (view) (annotate) - [select for diffs]
Sun Mar 4 05:23:41 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.2: +33 -2 lines
Diff to previous 1.2

now FINALLY detects reverting to OK levels correctly.

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.1 - (view) (annotate) - [select for diffs]
Fri Mar 2 03:56:06 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN

Added the new utility class Register for use by monitors