ship nginx access logs through filebeats

The format is then applied to a virtual server that enables compression. The following examples define the log format that extends the predefined combined format with the value indicating the ratio of gzip compression of the response. The log format is defined using variables. To override the default setting, use the log_format directive to change the format of logged messages, as well as the access_log directive to specify the location of the log and its format. By default, the access log is located at logs/access.log, and the information is written to the log in the predefined combined format. NGINX writes information about client requests in the access log right after the request is processed. Note: The ability to specify multiple error_log directives on the same configuration level was added in NGINX Open Source version 1.5.2. However, if several error_log directives are specified on the same level, the message are written to all specified logs. In case of an error, the message is written to only one error log, the one closest to the level where the error has occurred. The error_log directive can be also specified at the http, stream, server and location levels and overrides the setting inherited from the higher levels.

Settings in the main context are always inherited by other configuration levels ( http, server, location). To override it, place the error_log directive in the main (top-level) configuration context.

The default setting of the error log works globally. In this case, messages of warn, error crit, alert, and emerg levels are logged.

Ship nginx access logs through filebeats