Data logs, Debug logs – Welch Allyn Connex CSK 4.1.X - Installation Guide User Manual
Page 31

Installation guide
Configuration
27
Data logs
To provide assistance in monitoring messages that are processed by Data Catcher,
specifically ones that fail to complete their round-trip delivery, a Data Log option is
available on the left side of the configuration interface. This option will open a new
window and display a list of data messages that have been received from devices by Data
Catcher, but for some reason have not completed their process successfully.
This log displays information contained within the data messages themselves (for
example Patient ID, Date/Time, Serial Number of the device, etc) to help determine if the
error was a result of improper device data, or if it was from an internal processing error.
For the Data Log option to work, Data Catcher must have the Failed Data Cache option
enabled (see
“Local Failed Data Cache directory”
on page 20), and must have XML
formatted data enabled for this option (see
“Local Failed Data Cache file types”
on
page 21). If either of these options are missing or not enabled, the Data Logs will not be
available.
Debug logs
The Data Catcher application generates a running log with debug information as it
executes. It maintains two logs (“DebugLog1.txt” and “DebugLog2.txt”) that store this
information, and writes to the two files in a circular manner. When the application starts, it
opens “DebugLog1.txt” to write first, and continues to write information to this file until it
reaches the specified capacity (10 Megabytes). Once this limit has been reached, the
application opens “DebugLog2.txt” and continues writing until once again the capacity
limit has been reached. Then, the application reopens “DebugLog1.txt”, clears all data
from the file, and continues writing.