RE: [SA-list] Uptime stats & DB

[Julian Carr]

Dirk,   Once per cycle until the final version is released when you will be able to select how often the data is logged.  Correct?   J. >>> [EMAIL PROTECTED] 07/09/06 02:25PM >>> The logging is done once per cycle but from a records point of view there is only one record per day, as we update the info in the record. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rowland,David Sent: Sunday, July 09, 2006 8:11 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime stats & DB Ok, misunderstood the frequency of the records, although thinking about it disk space once per day would be good for capacity planning/trending -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: 09 July 2006 16:51 To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime stats & DB As we have 1 record per day/per entry how could we then add performance data?   Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rowland,David Sent: Sunday, July 09, 2006 5:21 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime stats & DB Can the performance data be added as well so we can graph disk/cpu usage etc.. from an SQL database or is this feature already built in for MS SQL? -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: 09 July 2006 15:36 To: Servers Alive Discussion List Subject: [SA-list] Uptime stats & DB I've been thinking some more about the questions we get around uptime stats and db logging and have been "playing" with an idea about it. If we would have the following extra DB logging would that help?     SAID(string)     UNIQUEID (numeric)     nYEAR (numeric)     nMONTH (numeric)     nDAY (numeric)     UPCYCLES (numeric)     DOWNCYCLES (numeric)     MAINTENANCECYCLES (numeric)     TOTALCYCLES (numeric) For each record in the list we would create/update the record with the up/down/maintenance/total cycles AFTER each cycle (or just after the check). And each day would generate a new record. The update will take the value from the DB and add 1 to the correct columns (up/down/maintenance and total).  This means that if you stop SA for a couple of hours during that day that you would this have/get rather correct info.     MYSYSTEM    1    2006    07    08    167    1    1 169     MYSYSTEM    1    2006    07    09    67    1    1 69 We could also "attached" some extra HTML tags to this. For example     sa_stats_up_today     sa_stats_up_yesterday     sa_stats_up_currentmonth     sa_stats_up_previousmonth     ...     And to get the value of it we can then query the db (ODBC) And as always my thinking resulted in some coding too :-)  The logging to db part is already written and "seems" to work.  For the moment it's done after the check, could be that this will be changed to "after the cycle" for performance reasons. Would this logging (and HTML tags) resolve some/most of the uptime stats issues? Dirk Bulinckx. 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. This message has  been scanned by  Node N01 incoming Disclaimer This communication is confidential and intended solely for the use of the individuals to whom it is addressed. Any views or opinions expressed are those of the author and do not necessarily represent those of Allied Bakeries - a division of ABF Grain Products Ltd. If you are not the intended recipient, be advised that you have received this communication in error and that any use, dissemination, forwarding, printing or copying of the contents is strictly prohibited. If you have received this communication in error, please notify Allied Bakeries Service Desk on Freephone 0800  374684 or reply to [EMAIL PROTECTED] This message has been scanned by Node N02 Outgoing 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. This message has  been scanned by  Node N01 incoming Disclaimer This communication is confidential and intended solely for the use of the individuals to whom it is addressed. Any views or opinions expressed are those of the author and do not necessarily represent those of Allied Bakeries - a division of ABF Grain Products Ltd. If you are not the intended recipient, be advised that you have received this communication in error and that any use, dissemination, forwarding, printing or copying of the contents is strictly prohibited. If you have received this communication in error, please notify Allied Bakeries Service Desk on Freephone 0800  374684 or reply to [EMAIL PROTECTED] This message has been scanned by Node N02 Outgoing 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. 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.