No External Logging: This selection disables all external logging. Overseer always will maintain its own records of when resources go online/offline.
Log to text file: This selection enables logging to a text file. This is in addition to Overseer's own internal logging. Be sure to specify the full path to the text file, such as c:\program files\overseer\overseer.log. The path must include the name of the file itself.
Log to ODBC Data Source: Overseer supports this option which enables logging to an ODBC data source(such as MySQL, Access, etc.). ODBC DSN's must be setup in the Windows control panel(Admin Tools->Data Sources->System). Overseer needs a "System DSN" and not a "User DSN". The ODBC data source should have a table named "OverseerLog" with the following fields: iResourceType(Integer) - This stores the resource type(1=HTTP, 2=Ping, 3=Service, 4=Event Log, 5=Disk Space, 6=EM1 Sensor) cResourceName(varchar(200)) - This stores the name of the resource. tDateTime(datetime) - This stores the date/time of the event. bSuccess(bit) - This stores the success/failure of the event(1=success, 0=failure) mErrorMessage(mErrorMessage) - This stores the error message for the event
MSSQL Create Table Command:
CREATE TABLE OverseerLog (iResourceType int, cResourceName varchar(200), tDateTime datetime, bSuccess bit, mErrorMessage text);
Log Success: Successful resource checks are written to the log file/database.
Log Failures: Failed resource checks are written to the log file/database.
Log Recovery: Recovery of resources(first success after failures) are written to the log file/database.
