Ummm, OK , but I need the history. That does raise some othe rpossibilites tho.... Hmmmmmmmm
I want my cake and a sugar-high too! Mike >>> [EMAIL PROTECTED] 10/27/03 10:17AM >>> That's what I've been doing and it works great. Simple, clean, and doesn't bloat SA. I use the interchange data to build a color coded table with each host(by host ID) and the highest alert level for that device. If any check for a host is down the cell will be red, maintenance will be yellow, etc. -Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dewachter Johan > Sent: Monday, October 27, 2003 10:10 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Dreaming of features for version 5..... > > > 2nd thing can be done in another way: > Some months back Dirk added an option to execute a SQL > statement before the insert. > > "...Create > HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers > Alive\Interchange\db_sqlcmd_before (string) and give the > correct SQL statement to execute It will be executed before > the interchange logging starts adding records (the command > won't be executed if the interchange logging is disabled ofcourse)" > > Put "delete * from interchange_table" in this key and you've > got your current status. > > Johan > > -----Original Message----- > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] > Sent: maandag 27 oktober 2003 15:34 > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Dreaming of features for version 5..... > > > The 2nd thing can be done :-) > Use the interchange file export and create an app that insert > this into a db. And instead of doing an append this just > does an update (or add). > This app can then be execute by SA after the generation of > the interchange file. > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook > Sent: Mon Oct 27 3:07 PM > To: [EMAIL PROTECTED] > Subject: [SA-list] Dreaming of features for version 5..... > > > The discussions around the stats table (the regedit of which > is being tested this morning - Thanks Dirk!!!) got me to > thinking about tables that SA could create that would save me > time and effort in the future (especially when I have to > explain SA to the Network team!!!) > > The first is as had been mentioned where SA keeps track of > the timing for all of the states a check has been in for a > given period of time and then sends that to a database on a > regular schedule. > > The second is exactly the same as the current interchange > database table EXCEPT that it only keeps the results of the > last check cycle (like the interchange file). This would also > assist the gentleman who wanted a list of the current hosts > being checked. I love the history, but it's a bit of a > challange to get the latest test results. > > The third is a database with only one record, the fields > being all of what is available via HTML tags for the SA > software itself and the top level group (sa_version, > sa_cycles, sa_group_up_entries, etc....). > > > Here's to dreaming!! > > > > > > > > > Michael Shook > Business Continuity Analyst > Saddle Creek Corporation > 723 Joe Tamplin Industrial Blvd > Macon GA 31217 > 478 742 8740 ext. 105 (work) > 478 256 9318 (mobile) > 478 742 7917 (fax) > [EMAIL PROTECTED] > http://www.saddlecrk.com > > To unsubscribe from a list, send a mail message to > [EMAIL PROTECTED] With the following in the body of the message: > unsubscribe SAlive > > > > To unsubscribe from a list, send a mail message to > [EMAIL PROTECTED] With the following in the body of the message: > unsubscribe SAlive > To unsubscribe from a list, send a mail message to > [EMAIL PROTECTED] With the following in the body of the message: > unsubscribe SAlive > To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
