|
Step 7 - Logging & Alerts |
Top Previous Next |
|
File Event Logging
Various types of file collaboration events can be written to a log file and to the Event Log viewer located on the Runtime tab of the File Collaboration Applet. Each file collaboration session will have its own event log file located in the Hub\logs folder of the installation directory and is uniquely identified by the system generated Application ID. Each log file will be named fc_event_log_AppId.txt, where AppId is the unique system generated ID visible under the General Settings tab of the Applet Configuration Panel. All log files are stored in a tab delimited format that can easily be read by Microsoft Excel or other Database applications.
Log Entry Severity Levels
By default all file collaboration session file activity is logged, and for all severity levels. You can enable or disable file event logging as well as select the level of granularity on what to log by clicking on the Logging tab and configuring the following options
Below is a list of logging fields and their descriptions:
Alerts
Various types of alerts will be logged to a log file and to the Alert Viewer table located on the Runtime tab of the File Collaboration Applet. Each file collaboration session will have its own alert log file located in the Hub\logs folder of the installation directory and is uniquely identified by the system generated Application ID. Each log file will be named fc_alert_log_AppId.txt, where AppId is the unique system generated ID visible under the General Settings tab of the Applet Configuration Panel. All log files are stored in a tab delimited format that can easily be read by Microsoft Excel or other Database applications.
The default log level is WARNING which will show any warning or error alerts that occur during a running session. Depending on the severity of the alert, the session may need to be restarted. |