Changes

The server logs give are written in plain text. In your [[Configuration#Database Directory|Database Directory]], you can find a folder named <code>.logs</code> in which all log files are stored with the according date. Note that, depending on your OS and configuration, files and folders beinning with a <code>.</code> may be hidden. The log directory can be changed via the {{Option|LOGPATH}} option. Some more notes on the logging facility: * HTTP requests are included in the log files.* Logging can be turned on/off via the [[Options#LOG|LOG]] option.* The maximum length of logging messages can be changed via [[Options#LOGMSGMAXLEN|LOGMSGMAXLEN]].* The [[Admin Module]] provides access to the log files from XQuery. ==RESTXQ== Non-trivial web applications provide the ability for users to sign in and out. User handling can be realized with session attributes (see e. g. the [[DBA]] code). By default, RESTXQ code is run with admin permissions. However, as it is more interesting to know which user has called a function, the RESTXQ user string (which is {{Code|admin}} by default, and which will show up in the log data) will be overwritten by the value of an {{Code|id}} session attribute. If the request path includes {{Code|/dba/}}, the {{Code|dba}} session attribute will be assigned. If the following advantagesfunction is called more than once, {{Code|joe}} will appear as user in the second and subsequent log entries: <pre class="brush:xquery">import module namespace Session = 'http://basex.org/modules/session';declare %rest:path('/session-id') function local:f() { Session:set('id', 'joe'), 'I am Joe'};</pre> ==Format== ; Example 1: <pre>01:18:12.892 SERVER admin OK Server was started (port: 1984)01:18:15.436 127.0.0.1:4722 jack REQUEST XQUERY for $i in 1 to 5 return random:double()01:18:15.446 127.0.0.1:4722 jack OK Query executed in 2.38 ms. 2.72 ms01:18:15.447 127.0.0.1:4722 jack REQUEST EXIT01:18:15.447 127.0.0.1:4722 jack OK 0.39 ms</pre> A server has been started and a user <code>jack</code> has connected to the server to perform a query and exit properly. ; Example 2: <pre>01:23:33.251 127.0.0.1:4736 john OK QUERY[0] 'hi' 0.44 ms01:23:33.337 127.0.0.1:4736 john OK ITER[0] 1.14 ms01:23:33.338 127.0.0.1:4736 john OK INFO[0] 0.36 ms01:23:33.339 127.0.0.1:4736 john OK CLOSE[0] 0.21 ms01:23:33.359 127.0.0.1:4736 john REQUEST EXIT01:23:33.359 127.0.0.1:4736 john OK 0.14 ms</pre> A user <code>john</code> has performed an iterative query, using one of the client APIs.

The server logs are written in plain-text and can be opened with any editor<pre>01:31:51.888 127.0.0.1:4803 admin REQUEST [GET] http://localhost:8984/rest/factbookFurthermore there are well structured to give you a perfect overview about the processes01:31:51.In your database folder you can find a folder named '892 127.0.0.1:4803 admin 200 4.logs' where all log files are43 msstored with the belonging date.</pre>

;Example:: <pre>10:06:36.498 [127.0.0.1:49990] LOGIN admin OK&#10;10:06:53.297 [127.0.0.1:49990] XQUERY 1 to 10 OK 17Version 8.89 ms&#10;10:07:03.353 [127.0.0.1:49993] LOGIN testuser OK&#10;10:07:08.259 [127.0.0.1:49993] XQUERY 1 to z Error: Stopped at line 1, column 6: [XPDY0002] No context item set for 'z'. 9.69 ms&#10;10:07:15.505 [127.0.0.1:49990] LOGOUT admin OK&#10;10:07:19.790 [127.0.0.1:49993] LOGOUT testuser OK</pre>* Added: Now you The log directory can see the 'admin' user has the IP 127.0.0.1 be changed with the socketport 49990 and the 'testuser' has the IP 127{{Option|LOGPATH}} option.0.0.1 with the socketport 49993. With this information you can identify each transaction of the corresponding user. The 'testuser' for example executed a query which was aborted by an syntax error* Updated: Include session attributes in log data.