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 [email protected]
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.
