144
Cedex HiRes Analyzer Operator’s Manual
F
F
2 Trace and Logging
Trace and Logging are only required for support and problem detection purposes. Therefore, it is advisable
to restrict access to Trace and Logging to the support team and users with extended permissions (e.g. the
Superuser).
Trace and Logging functionalities should only be activated at the request of an authorized service technician.
In order to avoid an exaggerated use of hard disk space, turn off the Trace and Logging functionalities as soon
as the issue has been located and/or resolved.
To activate or change Trace and Logging parameters, open the Setup menu in the Cedex Control Center.
Clicking on Trace & Logging will open the corresponding window.
The tracing functionality, as well as the logging functionality, can separately be enabled for individual modules
of the Cedex HiRes Analyzer.
Tracing is in the Off state by default. The application has two Trace Levels. The fi rst one (tracing level Normal)
is used for minimal tracing required for time critical problems. The second level (tracing level Extended) is
necessary for a more detailed problem description. To set the Trace Level, click on the current status and a drop-
down menu will appear from which level can be selected. Logging is in Tr ue state by default.
Trace and log records are saved in fi les which are accessible by using Windows Explorer. The records are
found in the C:\Cedex2 directory under CedexLog (CedexLogand_YYYY_MM_DD.log) and CedexTrace
(CedexTrace_YYYY_MM_DD.log).
Target fi les for tracing and logging data can be defi ned in the System Options menu. These fi les will automatically
be created in the Cedex2 folder. The data will then be stored in the default target fi les as well as the newly defi ned
target fi les. Open the Tracing (Logging) tab and enter the desired target fi le path for the TraceOutputPath
( LogOutputPath) parameter in the Va l u e column.
3 The System Audit Trail File
All user-initiated activities, as well as important actions carried out by the Cedex HiRes Software 2.2, are
recorded in the Audit Trail fi le. The system also logs all errors in the audit trail, including information from the
error message.
For each activity the User, Measurement ID, Workarea Name, Reactor Identifi er and Sample Identifi er are given.
The actions are classifi ed by Event Types and a short message provides further explanation.
To support monitoring of user-initiated activities, a search fi lter is available that also allows for defi ning the
period of time which is to be searched.
A report can be printed by clicking on Print Report.
The System Audit Trail File