|
||
|
Overview
Checklan Control Overview Checklan Alerter use a specific engine to process all controls, each control is logged in a log file named checkengine.log as follow: Checklan Control is installed as a Windows service.
07/10/2004 12:02:25 [Inf] - Starting Controls
07/10/2004 12:02:25 [Inf] - Opening Database 07/10/2004 12:02:28 Inf - Processing Alert 07/10/2004 12:02:30 Inf - Processing Alert 07/10/2004 12:02:33 Inf - Processing Alert 07/10/2004 12:02:35 Inf - Processing Alert 07/10/2004 12:02:36 Inf - Processing Alert 07/10/2004 12:02:39 Inf - Processing Alert 07/10/2004 12:02:39 Inf - Processing Alert 07/10/2004 12:02:39 Inf - Processing Alert 07/10/2004 12:02:41 Inf - Processing Alert 07/10/2004 12:02:41 [Inf] - Closing Database checkengine.txt is either updated permanently and let you capable to double check
07/10/2005 12:02:25 [Inf] - Checking for alert Process PerfCounter 0 07/10/2005 12:02:28 [Inf] - Checking for alert Process PerfCounter 1 07/10/2005 12:02:30 [Inf] - Checking for alert Process PerfCounter 2 07/10/2005 12:02:33 [Inf] - Checking for alert Process PerfCounter 3 07/10/2005 12:02:35 [Inf] - Checking for alert Process SystemProcess 4 07/10/2005 12:02:36 [Inf] - Checking for alert Process SystemShare 5 07/10/2005 12:02:39 [Inf] - Checking for alert Process SystemShare 6 07/10/2005 12:02:39 [Inf] - Checking for alert Process SystemShare 7 07/10/2005 12:02:39 [Inf] - Checking for alert Process PerfCounter 8 Those files are updated permanently, Checklan Watch Dog surveys and ensure that the current date time is regularly increasing. If Checklan Watch Dog is informed that no change has been done for more than 5five minutes the service Checklan Engine is automatically restarted. This is a secure way to double check application and to ensure the liability of Checklan’s processes. Note: Since Checklan Alerter 4.2.x versions the Checklan Watch Dog is automatically installed With Checklan Alerter |
|||||
|
|||||