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 :-)
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.
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 ;)
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).
Modified to use the new style queuing in the local client
Added new Monitor's for Load and Process counts.
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.*
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.
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
Now shows OK alerts if the previous alert exceeded the alerters level
now FINALLY detects reverting to OK levels correctly.
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.
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.
Some checks for null items.
Now has logging lines. Only monitors data packets.
now implements correct interface
now displays errors on configuration
Now catches configuration errors and handles properly
It seems we forgot something vital... the source of the message :)
CPU__Monitor is now fleshed out.
A bare bones initial Monitor for CPU packets....
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.