Log entry format
Log entries, whose values vary depending on the logging type, appear in the following format on one line:
<Log-Type> <TrID: xxxxxxxxxxxxxxxxxxxxxx:xxxxxxx> <TID: xxxxxxxxxx> <RPC ID: xxxxxxxxxx> <Queue: xxxxxxxxxx> <Client-RPC: xxxxxx> <USER: xxxxxxxxxx> /* <timestamp> */ [information]
Depending on the logging type you are using and the actions being executed, the log file might include some or all of the entries shown in the example.
The following table describes possible values for the entries in log files.
Possible values for log entries
Displayed for all types of logs except thread logs; fixed-size, 4-byte string (examples: API, ESCL, FLTR, SQL, USER)
|TrID||A trace ID. It is a common identifier to trace the flow of execution of APIs across log files. A trace ID consists of a Core ID (an alphanumeric string) and a Counter (a positive integer increment).|
The identification number of the thread executing the operation (fixed-size, 10-digit number)
The dispatch ID that identifies the API call of each user in the server (fixed-size, 10-digit number)
The type of queue on which a particular thread lives: admin, alert, fast, list, Flashboards, escalation, or private (10-character string)
The RPC number requested by the client (6 characters)
A 30-character string identifying the user name; blank if no user name (for example, a system call)
The date and time the operation was performed; displayed to 1/10,000 of a second
Entry detail; varies with the type of log
Log files sometimes show Client-RPC 999999 (the 6-digit dispatch ID that identifies the API call of a user in the server). This indicates that internal processes are running or are being caused to run by other processes. For example, this might occur when activities that cause a recache are being logged.
By default, server log files are located in ARSystemInstallDir\Arserver\Db on a Windows server, or ARSystemInstallDir/db on a UNIX server. You can change the path or file name of log files in the AR System Administration: Server Information form.
The following topics provide information on the format of the log entries in the different log files: