Features and Improvements in ArangoDB 3.8
The following list shows in detail which features have been added or improved in ArangoDB 3.8. ArangoDB 3.8 also contains several bug fixes that are not listed here.
The following logging-related options have been added:
--log.use-json-formatto switch log output to JSON format. Each log message then produces a separate line with JSON-encoded log data, which can be consumed by applications.
The attributes produced for each log message JSON object are:
date/time of log message, in format specified by
only emitted if
process id, only emitted if
thread id, only emitted if
thread name, only emitted if
server role (1 character), only emitted if
log level (e.g.
source file name of log message, only emitted if
source file line of log message, only emitted if
source file function name, only emitted if
log topic name
log id (5 digit hexadecimal string), only emitted if
the actual log message payload
--log.processto toggle the logging of the process id (pid) in log messages. Logging the process ID is useless when running arangod in Docker containers, as the pid will always be 1. So one may as well turn it off in these contexts with the new option.
--log.in-memoryto toggle storing log messages in memory, from which they can be consumed via the
/_admin/logHTTP API and by the Web UI. By default, this option is turned on, so log messages are consumable via the API and UI. Turning this option off will disable that functionality, save a tiny bit of memory for the in-memory log buffers and prevent potential log information leakage via these means.