fixed some documentation

Documentation/Books/Manual/Administration/Configuration/Logging.mdpp

@@ -80,7 +80,7 @@ To additionally log HTTP request to a file named "requests.log" add the options:
 --log.level requests=info --log.output requests=file:///path/to/requests.log
 ```
 
-!SUBSECTION
+!SUBSECTION Forcing direct output
 
 The option `--log.force-direct` can be used to disable logging in an extra
 logging thread. If set to `true`, any log messages are immediately printed in the

Documentation/DocuBlocks/logApplication.md

@@ -1,9 +0,0 @@
-
-
-@brief log application name
-`--log.application name`
-
-Specifies the *name* of the application which should be logged if this
-item of
-information is to be logged.
-

Documentation/DocuBlocks/logContentFilter.md

@@ -1,7 +0,0 @@
-
-
-@brief log content filter
-`--log.content-filter arg`
-
-Only log message containing the specified string *arg*.
-

Documentation/DocuBlocks/logFacility.md

@@ -1,18 +0,0 @@
-
-
-@brief log facility
-`--log.facility name`
-
-If this option is set, then in addition to output being directed to the
-standard output (or to a specified file, in the case that the command line
-log.file option was set), log output is also sent to the system logging
-facility. The *arg* is the system log facility to use. See syslog for
-further details.
-
-The value of *arg* depends on your syslog configuration. In general it
-will be *user*. Fatal messages are mapped to *crit*, so if *arg*
-is *user*, these messages will be logged as *user.crit*.  Error
-messages are mapped to *err*.  Warnings are mapped to *warn*.  Info
-messages are mapped to *notice*.  Debug messages are mapped to
-*info*.  Trace messages are mapped to *debug*.
-

Documentation/DocuBlocks/logPerformance.md

@@ -1,21 +0,0 @@
-
-
-@brief performance logging
-`--log.performance`
-
-If this option is set, performance-related info messages will be logged
-via
-the regular logging mechanisms. These will consist of mostly timing and
-debugging information for performance-critical operations.
-
-Currently performance-related operations are logged as INFO messages.
-Messages starting with prefix `[action]` indicate that an instrumented
-operation was started (note that its end won't be logged). Messages with
-prefix `[timer]` will contain timing information for operations. Note that
-no timing information will be logged for operations taking less time than
-1 second. This is to ensure that sub-second operations do not pollute
-logs.
-
-The contents of performance-related log messages enabled by this option
-are subject to change in future versions of ArangoDB.
-

Documentation/DocuBlocks/logRequests.md

@@ -1,29 +0,0 @@
-
-
-@brief log file for requests
-`--log.requests-file filename`
-
-This option allows the user to specify the name of a file to which
-requests are logged. By default, no log file is used and requests are
-not logged. Note that if the file named by *filename* does not
-exist, it will be created. If the file cannot be created (e.g. due to
-missing file privileges), the server will refuse to start. If the
-specified
-file already exists, output is appended to that file.
-
-Use *+* to log to standard error. Use *-* to log to standard output.
-Use *""* to disable request logging altogether.
-
-The log format is
-- `"http-request"`: static string indicating that an HTTP request was
-logged
-- client address: IP address of client
-- HTTP method type, e.g. `GET`, `POST`
-- HTTP version, e.g. `HTTP/1.1`
-- HTTP response code, e.g. 200
-- request body length in bytes
-- response body length in bytes
-- server request processing time, containing the time span between
-fetching
-  the first byte of the HTTP request and the start of the HTTP response
-

Documentation/DocuBlocks/logSourceFilter.md

@@ -1,8 +0,0 @@
-
-
-@brief log source filter
-`--log.source-filter arg`
-
-For debug and trace messages, only log those messages originated from the
-C source file *arg*. The argument can be used multiple times.
-