Config: Format Section
Last updated
Was this helpful?
Last updated
Was this helpful?
Some of the Fluentd plugins support the <format>
section to specify how to format the record.
The format section can be under <match>
or <filter>
section.
The @type
parameter of <format>
section specifies the type of the formatter plugin. Fluentd core bundles some useful .
Here's the list of built-in formatter plugins:
Third-party plugins may also be installed and configured.
For more details, see plugins documentation.
@type
The @type
parameter specifies the type of the formatter plugin.
time_type
(enum) (optional): parses/formats value according to this
type
Default: float
Available values: float
, unixtime
, string
float
: seconds from Epoch + nano seconds (e.g.
1510544836.154709804)
unixtime
: seconds from Epoch (e.g. 1510544815)
string
: use format specified by time_format
, local time or time
zone
time_format
(string) (optional): processes value according to the
specified format. This is available only when time_type
is string
.
Default: nil
Available time format:
For more details about formatting, see
For more details about parsing, see
%iso8601
(only for parsing)
Use %N
to parse/format with sub-second precision, because
%3N
, %6N
, %9N
, and %L
.
localtime
(bool) (optional): if true
, uses local time. Otherwise,
UTC is used. This is exclusive with utc
.
Default: true
utc
(bool) (optional): if true
, uses UTC. Otherwise, local time is
used. This is exclusive with localtime
.
Default: false
timezone
(string) (optional): uses the specified timezone. One can
parse/format the time value in the specified timezone format.
Default: nil
Available time zone format:
[+-]HH:MM
(e.g. "+09:00") (recommended)
[+-]HHMM
(e.g. "+0900")
[+-]HH
(e.g. "+09")
Region/Zone (e.g. Asia/Tokyo
)
Region/Zone/Zone (e.g. America/Argentina/Buenos_Aires
)
.
.
does not support
If this article is incorrect or outdated, or omits critical information, please . is an open-source project under . All components are available under the Apache 2 License.