Getting Information and Statistics from Your System’s Logs
Logs are files of data that record actions or transactions in SirsiDynix Symphony. Each line in a log file represents interaction between a user and some function of SirsiDynix Symphony. There are several types of SirsiDynix Symphony log files, but not all types of logs are utilized on every SirsiDynix Symphony system. WorkFlows reports are used to manage and review transaction logs, and as well as to extract statistical data.
Managing SirsiDynix Symphony Logs and Running Reports
Transaction logs created on your system may require attention for one of the following reasons.
| • | Not enough disk space is available on your server to retain logs indefinitely. Refer to the log type to determine which log files may be removed or copied to tape to reclaim significant disk space. |
Logs are retained in the /Unicorn/Logs directory on your server.
| • | Consolidation is necessary to use the data. Each log type that is designated to contain both a daily and monthly log must be consolidated using the Consolidate Daily Logs (Consolidate) report. If your library uses the SirsiDynix Symphony backup utility, the Backup Daily Files (Dailybackup) report consolidates the files automatically. |
| • | Statistics information must be extracted from historical data. Some reports use history logs in their raw form, but other reports that produce statistical information require statistics logs. Once history logs are consolidated, they need further processing to be made into statistics logs, using the Statistics Log (Statlog) report. |
Several reports extract data from the logs. Some reports allow you to select from four log types when the report is scheduled. The types are History, Print, Statistics, and System logs.
| • | The Print History Logs (Logprint) report prints each of the four types of log, though typically history logs. Each transaction is detailed. |
| • | The Scan History Logs (Logscan) report is the same as the Print History Logs report, except that the user may enter a particular text string to search, and only transactions containing that text are printed. |
| • | The Activity (Activity) report may be run against all four types of logs. For each type, workstation activity is listed. |
| • | More specific reports like the Cash Report Per Workstation (Cash) report, List Titles Used/Unused (Titleuselst) report, and Transaction Statistics (Statistics) report also use the logs to get their data. |
Types of Transaction Logs Created in SirsiDynix Symphony
The following types of transaction logs are created in SirsiDynix Symphony.
| • | Backup Log |
| • | Batch Logs (Daily and Monthly) |
| • | History Logs (Daily and Monthly) |
| • | Report Logs (Daily and Monthly) |
| • | Scanner Logs (Daily and Monthly) |
| • | Statistics Logs (Monthly) |
| • | Status Log |
| • | System Logs (Daily and Monthly) |
| • | WebCat Status Log |
| • | WebCat Connection Logs (Daily and Monthly) |
| • | Z39.50 Connection Log (Daily and Monthly) |
| • | Z39.50 History Log (Daily and Monthly) |
| • | Z39.50 Status Log |
The backup log is a single file containing dated entries entered each time the SirsiDynix Symphony Backup utility is used. The backup log is the file displayed when, in a specified Backup utility function, the STATUS operation is used. Every Backup utility SAVE or VERIFY operation updates the backup log.
Batch Logs (Daily and Monthly)
Batch logs for transactions are created in SirsiDynix Symphony if the library runs circulation workstations using Offline WorkFlows. Batch files are made by the Load Offline Transactions report and consist of multiple files with dated offline transaction entries. The batch files contain offline workstation transactions recorded successfully and integrated into the SirsiDynix Symphony database. The batch log files are compiled into the monthly statistics automatically when the Statistics Log report runs.
History Logs (Daily and Monthly)
The history logs record every workstation transaction that has successfully changed the database. The history logs keep track of which command was sent, the date and time it was sent, which station and user access sent the command, and all of the data entered by the operator to perform that command. If a command or wizard changes one or more databases, it is logged in the history logs.
For example, the history log records all data during a Charge Item command since a charge changes the database. The history log would not record a Search Item command since searching does not change the database.
History logs must periodically be removed from the SirsiDynix Symphony server by copying them to media and using the REMOVE operation, only after statistics logs have been created. Copying old history logs to media and then removing them prevents many problems that may result when there is insufficient disk space available for SirsiDynix Symphony to function properly.
Report Logs (Daily and Monthly)
Report logs keep a record of the following activities.
| • | When a report started |
| • | When a report was added to the finished report list |
| • | When a finished report was automatically printed |
| • | When a finished report was automatically emailed |
| • | When a report finished running |
Until they are consolidated with the Consolidate Daily Logs report, report logs are kept in separate daily files. All report log entries are time and date-stamped.
The SirsiDynix Symphony administrator must review and remove the report logs regularly. Deleting report logs prevents many problems that may result when there is insufficient disk space available for SirsiDynix Symphony to function properly.
Scanner Logs (Daily and Monthly)
When transactions are remotely recorded by a portable scanner, the scanned data is first transferred to the server with the Scanner Upload Utility wizard or the Scanner Transfer Utility wizard. The scanned data may then be integrated into the database using the Load Scanner Transactions report. When a transaction successfully loads into SirsiDynix Symphony, it is added to a history log. When a transaction fails to load into the SirsiDynix Symphony database, the failed transaction and the accompanying error message is put in a scanner log dated for the day of the load. The scanner log also prints in the finished Load Scanner Transactions, so errors can be individually corrected by staff.
The statistics logs are created when the history logs (consolidated by the Consolidate Daily Logs report) are processed by the Statistics Log report. These reports should be run on a regular basis. A statistics log contains many of the same transactions as the history log it was created from, except that each specific user and item transaction is replaced with general demographic information. For each suitable transaction in the history file, SirsiDynix Symphony can take the user ID (if present) and the item ID and pull from the database all of the demographics associated with these two IDs.
|
History Log |
Statistics Log |
|
User ID: 2206 |
ADULT, MALE, INCITY |
|
Item ID: 990022506 |
call number: SF ASI BOOK, GIFT, SCIFIC |
The statistics logs can be used to create various analytical reports for the library, using reports such as the Activity report and Transaction Statistics report.
For more information, refer to FAQs: Getting Tabular Statistics with a Report.
After statistics logs have been created and the required analytical reports have run, deleting statistics logs can prevent many problems that may result when there is insufficient disk space available for SirsiDynix Symphony to function properly.
The status log is a single file with dated entries for workstation server administration activities. These are not workstation transactions.
System Logs (Daily and Monthly)
System logs record every command sent and every response received at a workstation using SirsiDynix Symphony within a particular user access.
System logging is used mainly for training and/or investigative purposes. For example, a system log could be used to show a new workstation operator how they were following incorrect procedures, why their entry was in error, and why the workstation would not process their request.
Each request and response is date and time stamped. System logs can be formatted and printed using the Print History Logs report, or system logs may be scanned for just certain types of information and then only that portion of the logs can be printed with the Scan History Logs report.
System logging is an optional feature and should never be done on a full-time basis, since recording every transaction consumes an enormous amount of disk space on the server. Deleting system logs when the review is complete can prevent many problems that may result when there is insufficient disk space available for SirsiDynix Symphony to function properly.
The WebCat status log is a record of diagnostic messages containing information about when the WebCat server was started and stopped. Error messages related to WebCat may also appear.
WebCat Connection Logs (Daily and Monthly)
WebCat connection logs are a record of all WebCat sessions. They contain the date, time, station, and user IDs of users who have started or ended a WebCat session.
Z39.50 Connection Log (Daily and Monthly)
Each time a Z39.50 client connects to the SirsiDynix Symphony Z39.50 server, that activity is noted in the Z39.50 connection log for that day.
Z39.50 History Log (Daily and Monthly)
After connecting, a Z39.50 client initializes a search session. Once the Z39.50 server responds, the client can start sending search requests and receiving responses. The Z39.50 history log is a file containing dated entries of requests made by clients and responses of the server recorded daily.
The status log is a single file with dated entries for Z39.50 server administration activities. These are not workstation transactions.
Related topics
Load Offline Transactions Report
Cash Report Per Workstation Report