RE: [SA-list] Uptimes Db

[Dirk Bulinckx]

Title: Uptimes Db

sound like a good idea

 

 

Dirk Bulinckx.

 

---

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook
Sent: Tuesday, July 18, 2006 5:11 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Uptimes Db

I would say for the case of a new entry, set the current state seconds and totalseconds to 1 second. That way there's an entry, and the loss of a few seconds won't make much difference over the course of a few weeks or a month. (I think we can safely assume the state was held for least 1 second :-) )

 

Michael D. Shook
Technical Analyst
Saddle Creek Corporation
Michael.Shook@saddlecrk.com
863 668 4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com

 

---

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Tuesday, July 18, 2006 10:31 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Uptimes Db

Did some code check and this is how it works in build 2009:

 

 

 

there is NO record in the DB for that entry/date combination

    * if the previoucheck date/time is known:

            seconds that are added are the difference between the previouscheck and the current check

 

    * if the previoushceck date/time is UNknown (typical for a new entry that is added)

        seconds is the time between the start of Servers Alive and the current check.

        (maybe this should be different, as it could well be that SA is already running for days.... -> suggestions for this one??)

 

there is a record in the db for that entry/date combination

            seconds that are added are the difference between the previouscheck and the current check

 

 

Dirk Bulinckx.

 

---

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook
Sent: Monday, July 17, 2006 11:46 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Uptimes Db

It's almost like the first record has to have all zeros no matter what the state.

 

Michael D. Shook
Technical Analyst
Saddle Creek Corporation
Michael.Shook@saddlecrk.com
863 668 4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com

 

---

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Monday, July 17, 2006 5:11 PM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Uptimes Db

When there is NO record in the db for that day/entry it will use the start of SA as the starttime and calculate the seconds from that time until the time the check is being perform.

hmm I do see a problem with that :-) if SA is started today and tomorrow (while SA is still running) we create a new record it will start with the wrong seconds for that day...will fix that tomorrow.

 

IF a record exists then we will add the seconds between the previous check time and the current check time to the existing number of seconds in the record.

 

 

Dirk Bulinckx.

 

---

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook
Sent: Monday, July 17, 2006 9:06 PM
To: Servers Alive Discussion List
Subject: [SA-list] Uptimes Db

Dirk, how are you calculating the upseconds?

It seems you are using the start time of ServersAlive as the base line. If so will this give false time to checks that are added with out a restart of SA? Also, it adds the time prior to the checks being run ( I start SA at 2:00pm, but don't start checking until 2:02, this gives all the checks at least 120 seconds of uptime.)

Is this how you intended it? I know that there are assumptions that must be made to calculate times like this, I just wanted to be sure I understand what you intended.

Michael D. Shook
Technical Analyst
Saddle Creek Corporation
Michael.Shook@saddlecrk.com
863 668 4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com

--------------------------------------
The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.

--------------------------------------
The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.

--------------------------------------
The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.

To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.