Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
The server logs 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.==Introduction==
Some changes have been introduced The server logs 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 beginning with a <code>.</code> may be hidden. The log directory can be changed via the {{VersionOption|7.4LOGPATH}}:option.
* The If BaseX is used in a [[Web Application]], all trace output (generated via {{Code|fn:trace}}, {{Function|Profiling|prof:dump}} and similar functions) will be stored in the logs as well. Some more notes on the logging format has been revised.facility: * HTTP requests are now included in the log files.* Logging can be turned on/off via the [[Options#LOG{{Option|LOG]] }} option.* The maximum length of logging messages can be changed via [[Options#LOGMSGMAXLEN{{Option|LOGMSGMAXLEN]]}}.* An The [[Admin Module]] provides access to the log files from XQuery. Since {{Version|9.5}}, if a proxy is used, the original IP address of the client will be added to the logs. ==RESTXQ== By default, RESTXQ code is executed with the {{Code|admin}} user. As a result, this user will be displayed in the logs for all RESTXQ requests. In a web application with a custom user management, however, the name of the actual user who has sent a request is often more relevant. When log data is written during the processing of a RESTXQ function, the following is looked up as follows: # The current request is checked for an {{Code|id}} attribute. The attribute can be assigned via RESTXQ and the {{Function|Request|request:set-attribute}} function, and it is the recommended approach for stateless requests as all request attributes will be dropped after the finalization of a request.# If none is found, the {{Code|id}} attribute is looked up in the current user session. The attribute can be assigned via {{Function|Session|session:set}} (see e. g. the [[DBA]] code for sessions and user handling). If the request path contains a {{Code|dba}} segment, a {{Code|dba}} session attribute will be looked up instead.# If none is found, the default path will be taken, and the user of the current database context will be included in the logs.
→Introduction
This article is part of the [[Advanced User's Guide]]. It describes how client operations are logged by the server.The server logs can e.g. be used to get an overview of all processes executed on your server, trace any errorsor compile performance statistics.
==Format==
<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 ms
An admin user has accessed the <code>factbook</code> database via REST.
=Changelog= ;Version 9.5* Updated: Show IP address behind proxy. ;Version 9.3* Updated: Store trace output in database logs* Updated: [[Category:Server#RESTXQ|RESTXQ]]: The request attributes will be checked for a user id. ;Version 8.6* Added: The log directory can be changed with the {{Option|LOGPATH}} option.* Updated: Include session attributes in log data.
