fatal
error
warn
info
debug
trace
info
, and Fluentd outputs info
, warn
, error
and fatal
logs by default.-v
option sets the verbosity to debug
while the -vv
option sets the verbosity to trace
.-q
option sets the verbosity to warn
while the -qq
option sets the verbosity to error
:<system>
section:@log_level
option sets different levels of logging for each plugin. It can be set in each plugin's configuration file.@log_level
parameter, the plugin will use the global log level.text
(default)json
<log>
directive under <system>
:ignore_repeated_log_interval
(since v1.10.2)ignore_same_log_interval
(since v1.11.3)ignore_repeated_log_interval
ignore_same_log_interval
ignore_repeated_log_inteval
but covers more usecases. For example, if the plugin generates several log messages in one action, logs are not repeated:ignore_same_log_interval
resolves these cases.-o
command line option to specify the file instead:--log-rotate-age AGE
AGE
is an integer or a string:daily
, weekly
, monthly
)--log-rotate-age
is specified on Windows, log files are separated into log-supervisor-0.log
, log-0.log
, ..., log-N.log
where N
is generation - 1
due to the system limitation. Windows does not permit delete and rename files simultaneously owned by another process.--log-rotate-size BYTES
--log-rotate-age
is specified with integer:--log-rotate-size
is specified on Windows, log files are separated into log-supervisor-0.log
, log-0.log
, ..., log-N.log
where N
is generation - 1
due to the system limitation. Windows does not permit delete and rename files simultaneously owned by another process.fluent
tag. You can process Fluentd logs by using <match fluent.**>
(Of course, **
captures other logs) in <label @FLUENT_LOG>
. If you define <label @FLUENT_LOG>
in your configuration, then Fluentd will send its own logs to this label. This is useful for monitoring Fluentd logs.fluent.info
logs to stdout like this:out_forward
to send Fluentd logs to a monitoring server. The monitoring server can then filter and send the logs to your notification system e.g. chat, irc, etc.notify
channel:<label @FLUENT_LOG>
but this feature is deprecated. This feature will be removed in fluentd v2.