Logging in ClockWatch

Logs provide a detailed, permanent record of ClockWatch activity. 
The logging options include:


Action Log


Action Log shows all time setting activity

The Action Log is a summary view of all current time setting activity. Data is displayed in a list on the main screen and actions are added as they occur.

Each entry shows the origination of the action and the result of action. At startup, the list shows the five most recent events from the setting log. After the program closes, the action detail can be found in the individual logs.

Columns:

Date: Identifying source icon and date and time in yy-mm-dd hh:nn:ss format.

Source: Internet time setting, ClockCard setting, BIOS clock setting , GPS time setting (Star Sync), WWVB time setting (Radio Sync), client time requests (Client/Server) and unauthorized clock changing attempts (Sentry, Server, Client ), are all included in the Action log.

Status: – result of the action.

Time Difference (seconds): – if clock was changed shows the number of seconds time setting. For clock locking shows the attempted time change.

Accuracy (sec/day): – for clock setting, shows the accuracy in terms of seconds/day.

Tip: You can resort by any column by clicking the column header.


Clock Setting Log

The Clock Setting log provides a record of all the settings made on the system. If logging is enabled, a record is written every time server is contacted. The Clock Setting log provides a  record that can be useful in a variety of ways:

  • As a record of system clock performance.
  • As a long-term indicator of system clock "drift" over time.
  • As a source of information on availability of Internet access.
  • As an input to other programs, such as spreadsheet or database programs where further analysis would be done.

Sample Clock Setting Log:

Synchronization Log 11/10/98 2:00:46 PM

Date     Time       Difference Accuracy Status Server
-----    ----       ---------- -------- ------ ------
98-11-10 14:00:45     -36        -36.0     0  time-a.nist.gov
98-12-03 23:59:40     -9         -0.4      0   time-a.nist.gov
98-12-07 10:58:55      3          0.1      0   time-a.nist.gov
98-12-14 07:00:45     -2         -0.3      0   time-b.nist.gov
98-12-22 09:58:02      0          0.0      5   time-a.nist.go
v


Client Log (ClockWatch Server)

ClockWatch Server records all ClockWatch Client requests for time synchronization in the Client Log. The Client Log  reports on all users (clients) accessing the ClockWatch Server, reporting  their IP address, number of accesses, and the last  time each of the clients accessed the ClockWatch server. Totals are also shown since the ClockWatch Server was last started. The Client Log file is available in the main ClockWatch program directory, under the name ClientLog.txt.

Sample Client Log:

Client Access Log for beagleNT
Report Run 12/23/98 4:05:31 PM

Client IP      Times     Last
Number Address Contacted Contact

1   190.30.20.2   2      12/23/98 3:18:50 PM
2   190.30.20.4   3      12/23/98 3:56:11 PM
3   190.30.20.5   1      12/23/98 3:06:07 PM

3   <-TOTALS->    6      12/23/98 3:56:11 PM


Trace Log

ClockWatch includes a detailed trace mode that provides detailed information about connection and communication information.  This feature may be useful in debugging communication problems. You can run ClockWatch in the trace mode, which provides a detailed log to pinpoint problems, by simply adding the debug option to the command line when starting ClockWatch. Following these steps will allow your to run ClockWatch in the trace mode and  view the resulting trace log file, DebugFile.txt.

  1. Run ClockWatch in diagnostic mode by running ClockWatch with the debug option. Usually:
       "C:\Program Files\Beagle Software\ClockWatch\ClockWatch.exe" debug.
  2. Run the problem until the connection fails or problem occurs. Exit ClockWatch.
  3. View the diagnostic trace, DebugFile.txt, usually in the main ClockWatch directory:
        C:\Program Files\Beagle Software\ClockWatch\DebugFile.txt
  4. Check for “ERRORS” or connection problems in the trace.
  5. ClockWatch support personnel can provide detailed analysis of the trace.

Sample Trace Log:

...
02-19 08:31:54 ID: 1 Number: 1 Local Time: 2/18/98 8:31:54 AM Status: 0
02-19 08:31:54 Time Difference: 1 sec, Accuracy: 60.0 sec/day,
02-19 08:31:54 Connecting...
02-19 08:32:00 Connection open
02-19 08:32:01 DataArrived: 50863 98-02-19 14:32:02 00 0 0 50.0 UTC(NIST) *
02-19 08:32:01 Daylight savings time is currently 1 (1 is OFF, 2 is ON)
02-19 08:32:01 Time zone Bias: 360
02-19 08:32:01 DATA ARRIVED Event
02-19 08:32:01 DateTime OK
02-19 08:32:01 System SAYS DST is OFF
02-19 08:32:01 Corrected NIST Time: 02/19/98 08:32:02
02-19 08:32:01 Internal System settings: Local Date: 98-02-19 Time: 08:32:01
02-19 08:32:01 3: Dates OK
02-19 08:32:01 Difference is < 2 seconds, ignore accuracy
02-19 08:32:01 Time Difference: 0.000012 days (1.0 seconds)
02-19 08:32:01 5: Timediff < minimum
02-19 08:32:01 Time difference is 1 sec - setting to 0
02-19 08:32:01 ...No Time difference No time set
02-19 08:32:01 DATA ARRIVED DONE
02-19 08:32:01 NIST SETTING DONE at 2/19/98 8:32:01 AM.


Syslog

ClockWatch Server and ClockWatch Enterprise can send events to a remote syslog server. Syslog servers, common in UNIX and Linux networks, gather messages from a variety of sources such as routers, switches, and any other syslog enabled application or device.  The syslog server filters, stores, displays and forwards messages gathered locally and from the network.

Usage Notes:

  • Remote syslog logging must be enabled on the receiving computer. This allows the Syslog server to receive messages from the network using an Internet domain socket with the syslogd daemon in UNIX/Linux.

  • Syslog uses UDP port 514 for communication. This port must be open on both the sending and receiving computers.

  • ClockWatch sends messages at either the information, warning or error level priorities. Messages are sent to the NTP subsystem of Syslog.


Notification Options in ClockWatch

ClockWatch Main Page

 

 
Copyright 2004 Beagle Software. All rights reserved
Last reviewed September 13, 2004