Difference between revisions of "Logging"

From BaseX Documentation
Jump to navigation Jump to search
Line 18: Line 18:
 
;Example:
 
;Example:
 
: <pre>16:00:00.094 [127.0.0.1:3920] LOGIN admin OK &#10;16:00:00.104 [127.0.0.1:3920] XQUERY 1 to 10 OK 12.36 ms&#10;16:00:00.114 [127.0.0.1:3920] LOGOUT admin OK</pre>
 
: <pre>16:00:00.094 [127.0.0.1:3920] LOGIN admin OK &#10;16:00:00.104 [127.0.0.1:3920] XQUERY 1 to 10 OK 12.36 ms&#10;16:00:00.114 [127.0.0.1:3920] LOGOUT admin OK</pre>
: Now you can see the 'admin' user has the IP 127.0.0.1 with the socket-port 3920. With this information you can identify each transaction of the corresponding user.
+
: Now you can see the 'admin' user has the IP 127.0.0.1 with the socketport 3920. With this information you can identify each transaction of the corresponding user.

Revision as of 10:04, 8 December 2010

Introduction

The server logs give you the following advantages:

  1. Overview about all processes executed on your server
  2. Tracing of any errors thrown by BaseX
  3. Tracing of wrong modified data
  4. Tracing of all specific user processes
  5. Tracing of time specific processes

The server logs are written in plain-text and can be opened with any editor. Furthermore there are well structured to give you a perfect overview about the processes. In your database folder you can find a folder named '.logs' where all log files are stored with the belonging date.

Logformat

Example
16:00:00.094 [127.0.0.1:3920] LOGIN admin OK 
16:00:00.104 [127.0.0.1:3920] XQUERY 1 to 10 OK 12.36 ms
16:00:00.114 [127.0.0.1:3920] LOGOUT admin OK
Now you can see the 'admin' user has the IP 127.0.0.1 with the socketport 3920. With this information you can identify each transaction of the corresponding user.