Revision as of 10:27, January 8, 2024 by Xavier (talk | contribs)
Jump to: navigation, search

WFM Data Aggregator:Log:x-json-log-archive

x-json-log

Section: Log
Default Value: "" (empty string)
Valid Values: stdout, stderr, [filename with or without path]
Changes Take Effect: After restart
Introduced: 8.5.220.03

Enables the JSON logging for WFM servers, if not empty.

WFM now supports structured logging to the file containing one-line log records formatted in JSON format. This facilitates easy integration with the centralized log aggregation and viewing systems, like Grafana/Loki.

Important

The log level for structured logging is the same as for logging to a file and is defined by a regular Template loop detected: Template:Optionslink option.


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

x-json-log.archive

Default Value: No default value
Valid Values: number, timestamp
Changes Take Effect: After restart
Dependencies: Used if x-json-log option is set
Introduced: 8.5.220.03

The log file's archive mode.

Using the archive property, it is possible to specify how archived log files are named. The following values for the archive property are supported:

  • number: A number, starting with 0, is appended to the name of archived log files. The most recent archived log file always has the number 0. For example, if the log file is named access.log, and if it fulfils the rotation criteria, the file is renamed to access.log.0. If a file named access.log.0 already exists, it is renamed to access.log.1.
  • timestamp: A timestamp is appended to the log file name. For example, if the log file is named access.log, and it fulfils the criteria for rotation, the file is renamed to access.log.20050802110300.

Draft Option

No draft option


Comments or questions about this documentation? Contact us for support!