Has the status of those hosts changed since SA was started? -Kevin
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook > Sent: Monday, October 27, 2003 10:50 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Statistical database question.... > > I took a quick spin through my Hosts file and if in fact #TLC > and #DLC are the time and date of the last status change, > then they are wrong. That is, they seem to be the time and > date that the current instance was started. > > Mike > > >>> [EMAIL PROTECTED] 10/27/03 10:39AM >>> > That doesn't seem to be working. I'm going to check my > registry again, but no luck so far. > > Thanks!!! > > Mike > > >>> [EMAIL PROTECTED] 10/24/03 12:59PM >>> > Try creating > HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers > Alive\StartUp\LoadStatusfromFile (string) with a value of 1 > And restart SA.... > > > Then just for the test at some point stop SA (the app) and > restart the app, load the hostfile again and restart the checking.... > And tell me if that does what it should do. > > (should already work with the current beta's....it was > something very old that is still in the code...) > > > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook > Sent: Fri Oct 24 4:33 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Statistical database question.... > > > I agree with the concept of slowing down the cycles during off peak > hours, but..... > > We don't have any. We're 24x7x365.24. > > And if why wouldn't I want to build reports around the up/down numbers > (aside from the already mentioned issues)? > > Mike > > >>> [EMAIL PROTECTED] 10/24/03 08:49AM >>> > But you don't want to build reports around the up/down numbers. > Remember, you can change check frequencies, like have 2 minutes per > check during 8am-6pm, 5 minutes per check off hours and > weekends. Plus, > different checks can have different frequencies (some checks are only > done once every 3-4-5 passes). > > If you always had the same check frequency (say, every 5 minutes) and > all of your checks were done every single time, then you'd be fine. I > don't know what the statistics are on how other people use SA, but I > know that I personally run my checks less often after hours, > and I have > several checks that I only check every 3 or 4 or 5 passes. > > Just my two cents. > > > -------------------------------- > Brent Ozar - UniFocus > -------------------------------- > "We're not going to some white collar resort prison. No, no, no!" > Michael Bolton, Office Space > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Shook > Sent: Friday, October 24, 2003 7:32 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Statistical database question.... > > Well, the columns you currently write are fine, BUT.... > > I have been tasked to create monthly / annual UP/DOWN stats for the > major devices. What I do now is sum all of the minutes where the > previousstatus is X. The problem comes in that SA doesn't regularly > output state stats to this table. I only see entries if there > has been a > change in status. So, unless my network is a complete piece of trash, > most of the devices never get any entries. Also, like I said, a > close/open of SA resets all of SA's internal time stamps so that if a > change does occur, the output only reflects from when SA was last > restarted. > > If SA output stats during a graceful shutdown, and on a regular time > schedule (say a few times a day (midnight, noon)) then I can use your > table as is. Otherwise, I need to perform the metrics calculations on > the interchange table, which will be a lengthy process if they ask me > for the last years stats, and I have been writing every 5 minutes. > > I can't see any issue with a previous and current status > entry being the > same, but maybe a new column to explain more exactly why the > record was > written would be helpful. > > Mike > > >>> [EMAIL PROTECTED] 10/24/03 06:04AM >>> > What exact info should be kept? > > > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Shook > Sent: Thu Oct 23 10:40 PM > To: [EMAIL PROTECTED] > Subject: [SA-list] Statistical database question.... > > > If I understand the process correctly, when the first cycle is run on > the start of SA you gather a status and datetime. When the status > changes, the duration is calculated, the datetime is reset, the new > status is recorded. Then an appropriate entry is written to the > database. > > If that's correct, then when SA is stopped/restarted, all of the > "running time" info is lost from the last program start or last status > change. > > Would it be possible to output all of the current "running time" info > for each check to the database before SA shuts down (assuming a > gracefull shutdown)? Maybe record the current status as the same for > both last and new. > > I'm trying to get the most out of this database, but I can't calculate > an accurate quality % if I don't have all of the up times. > > Thanks!!!! > > > > > > > > > > > > > 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 > > > > 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
