RE: [5] RE: [SA-list] change in state

[Kevin Kruithof]

Title: Message

Dirk,   Saving SA's monitor states would be useful to us also, so I've been watching this discussion carefully.   Since SA's config is a flat file with index numbers for each monitor, could you create another file in the SA directory that keeps track of monitor states?  All it would contain is the index of the monitor and the monitor's state.  You could then write this out at the end of every check (or maybe even make it user configurable for when it's written out).  When SA starts back up, you could pull the file in to get the states of the monitors (this could also be an option).    One problem with doing it this way (I'm sure you can think of more :-) ) is that you'll have to disable this feature if the user changes the config without saving it.  If the index gets out of sync between the state file and the config file, it would be a Bad Thing if SA were to try to open the file if it's closed and restarted.  Once the user saves the the config, the feature can be re-enabled.  If there are still problems with the two files getting out of sync, you could tag them both with a version number that's incremented everytime the config file is changed.   As always, I appreciate your openess to extending SA and the effort you put into implementing user requests.  You're the man.   Kevin   -----Original Message----- From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 2:25 PM To: [EMAIL PROTECTED] Subject: RE: [5] RE: [SA-list] change in state I suppose that an alert 'action' that would puts an entry into maintenance would help?   dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Jason Passow Sent: Wed Sep 03 10:56 PM To: [EMAIL PROTECTED] Subject: RE: [5] RE: [SA-list] change in state The problem is…. how does SA know that you knew that it was still down.    Perhaps you are doing maintenance from afar (using vnc or term serv) and reboot the server.  When it comes up you have assumed (which I am sure no one on this list would do) it is fixed and did not get an alert letting you know (because you already got one and you told Dirk to change it so it didn't send you another one).    This is the dilemma and I believe it is better to err on the side of caution.    Putting these entries into maintenance mode would be the best option.  If you know they are still broke quit monitoring them until they are fixed (or at least you think they are).  Once put back into active mode you will get an alert saying it is still down if you were wrong and it still does not work.  If it is up you will not get a down alert and your problem is now solved.  This is how it should work and I am sure that this why there is such a thing as maintenance mode.