Skip to content

Commit 2679199

Browse files
authored
Merge pull request #310 from kanga333/fix_include_time_key_example
Fix documentation with invalid include_time_key setting
2 parents bf1cdcf + 790bd55 commit 2679199

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

README.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -422,16 +422,16 @@ Change one line format in the S3 object. Supported formats are "out_file",
422422

423423

424424
At this format, "time" and "tag" are omitted. But you can set these
425-
information to the record by setting "include_tag_key" / "tag_key" and
426-
"include_time_key" / "time_key" option. If you set following configuration in
425+
information to the record by setting `<inject>` option. If you set following configuration in
427426
S3 output:
428427

429428
# v1
430429
<format>
431430
@type json
432-
include_time_key true
433-
time_key log_time # default is time
434431
</format>
432+
<inject>
433+
time_key log_time
434+
</inject>
435435
# v0.12
436436
@format json
437437
include_time_key true
@@ -441,15 +441,14 @@ then the record has log_time field.
441441

442442
{"log_time":"time string",...}
443443

444+
See also [official Inject Section article](https://docs.fluentd.org/configuration/inject-section).
445+
444446
* ltsv
445447

446448
key1:value1\tkey2:value2
447449
key1:value1\tkey2:value2
448450
...
449451

450-
451-
"ltsv" format also accepts "include_xxx" related options. See "json" section.
452-
453452
* single_value
454453

455454

0 commit comments

Comments
 (0)