Not correct. The last real check (that got a result up or down) gets the datetime written.
dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wed Oct 15 6:01 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Feature request Thanks, to clarify the records then, the last successful UP gets the datetime written, each subsequent "can't check because of dependancy" entry gets the datetime of the last successful check. Then the first following UP gets its datetime again. Right? Mike >>> [EMAIL PROTECTED] 10/15/03 11:38AM >>> Maybe you could write an update trigger. This trigger would check if the insert row has the same uniqueID and the same checkdatetime as an existing row and if it does it just doesn't do the insert... dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wed Oct 15 5:33 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Feature request Thanks. I think I see your process tree now. I don't suppose you have any suggestions to assist my issue? Thanks!!! Mike >>> [EMAIL PROTECTED] 10/15/03 11:27AM >>> That's just the whole point of the interchange is to have all entries in it. Also the logging as such doesn't know that there was no check done. The logging (interchange for example) is executed at the end of a cycle and "dumps" all the info into a db. The only way (without having to add a "field" to say we check it during the cycle) to know that a check was done or not, would be to recheck if a check should be done or not, and then again we can get into a situation were when the actual check had to be done that due to the schedule nothing was done and that when we do the interchange logging that the schedule says to do a check. Example scheduled maintenance from 2am until 3am cycle start 2:59:50 -> entry1 is not checked due to it's schedule ... 3:00:05 end of the cycle 3:00:06 start of the interchange logging 3:00:07 check if entry1 had to be checked would give a YES and thus would be logged. So no we're not going to add the option. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wed Oct 15 2:51 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Feature request Then if no read check is performed can I have the option to not put an entry in the database? Mike >>> [EMAIL PROTECTED] 10/15/03 08:41AM >>> I can see the point you're making, but still from my point of view the last check date/time shouldn't change if no read check was performed. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wed Oct 15 2:34 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Feature request I understand that, it's just not usable to have repeated datetimes when trying to graph the performance of the device, because it appears that the device was tested several times at the same time. Another option would be for if the check is not performed, don't put an entry in the database. Also, since I assume you have to check to see if my check is able to be performed, there IS a check done at each cycle, just not necessarily mine. Mike >>> [EMAIL PROTECTED] 10/14/03 05:05PM >>> The field is called checkdatetime and thus gives the datetime of the last check...so it's giving the correct value... dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Michael Shook Sent: Tue Oct 14 9:09 PM To: [EMAIL PROTECTED] Subject: [SA-list] Feature request I am using SA to create a strip chart of pings and response times. I have having some difficulty with checks done as a dependant of another device. Can I request an option to have the interchange output field of checkdatetime be the time of the test that was skipped instead of the time of the last test performed on the device? I can logically turn the extra_info message into a zero value, but I can't recover the date time stamp. Current Field output: status checkdatetime host extra_info additional_info 5 10/14/2003 14:40 www.xxx.yyy.zzz 100% 76.6 ms 3 10/14/2003 14:40 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 3 10/14/2003 14:40 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 3 10/14/2003 14:40 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 5 10/14/2003 14:34 www.xxx.yyy.zzz 100% 73.6 ms 5 10/14/2003 14:13 www.xxx.yyy.zzz 100% 69.8 ms 3 10/14/2003 14:13 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 3 10/14/2003 14:13 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 3 10/14/2003 14:13 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 5 10/14/2003 14:08 www.xxx.yyy.zzz 100% 77 ms Requested output: status checkdatetime host extra_info additional_info 5 10/14/2003 14:55 www.xxx.yyy.zzz 100% 76.6 ms 3 10/14/2003 14:50 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 3 10/14/2003 14:45 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 3 10/14/2003 14:40 www.xxx.yyy.zzz Depends on entry that is NOT up 76.6 ms 5 10/14/2003 14:34 www.xxx.yyy.zzz 100% 73.6 ms 5 10/14/2003 14:28 www.xxx.yyy.zzz 100% 69.8 ms 3 10/14/2003 14:23 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 3 10/14/2003 14:18 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 3 10/14/2003 14:13 www.xxx.yyy.zzz Depends on entry that is NOT up 69.8 ms 5 10/14/2003 14:08 www.xxx.yyy.zzz 100% 77 ms 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 n the device? I can logically turn the 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
