View previous topic :: View next topic |
Author |
Message |
MADS
Joined: 09 Feb 2005 Posts: 16
|
Posted: Fri Feb 17, 2006 6:48 am Post subject: Error loggin via ODBC |
|
|
Hey,
We are using the ODBC logging to a SQL for our reporting.
It would be nice to have a status returned on errors while writing the log (insert ...)
Reason is to make sure that a status change IS really written into the SQL.
A repeat until succes would be great....
MaDS |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Fri Feb 17, 2006 2:00 pm Post subject: |
|
|
Quote: | It would be nice to have a status returned on errors while writing the log (insert ...) |
Status returned on errors? Not sure I understand.
If HostMonitor cannot record data into ODBC log, it records error message into regular log.
Quote: | Reason is to make sure that a status change IS really written into the SQL. A repeat until succes would be great.... |
If there is some ODBC error, there are 99% chances next attempt will return the same error. So, what the reason to waste system resources?
Regards
Alex |
|
Back to top |
|
|
MADS
Joined: 09 Feb 2005 Posts: 16
|
Posted: Mon Feb 20, 2006 2:57 am Post subject: |
|
|
No not true....What if there is a time out? It would be great to be SURE the error is logged.
An action on failure (a mail) would be GREAT. I know you log it already in the regular log
Marc |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12795 Location: USA
|
Posted: Mon Feb 20, 2006 11:26 am Post subject: |
|
|
Usually people using ODBC logs to record information about every performed tests. It means 10-100 records per second. Recurrent retries may use too much system resources in case of ODBC failure (especially if there is timeout issue - your system will hung).
E-mail option could be useful. But why just e-mail? Better allow HostMonitor to execute any action profile.
Regards
Alex |
|
Back to top |
|
|
|