我尝试了用rewrite-tag fluent位1.6.0在文档中编写的示例
我能够用Git中提到的修补程序消除下面的警告
[2020/10/19 15:17:31] [ warn] [input chunk] no matching route for input chunk 16817-1603100851.153798000.flb但现在我在输出上一无所获。它挂在后面的线上
...
[2020/10/19 15:42:00] [ info] [engine] started (pid=28286)
[2020/10/19 15:42:00] [ info] [storage] version=1.0.6, initializing...
[2020/10/19 15:42:00] [ info] [storage] in-memory
[2020/10/19 15:42:00] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2020/10/19 15:42:00] [ info] [sp] stream processor started知道为什么吗?
以下是配置文件的内容(与文档中相同)
[SERVICE]
Flush 1
Log_Level info
[INPUT]
NAME dummy
Dummy {"tool": "fluent", "sub": {"s1": {"s2": "bit"}}}
Tag test_tag
[FILTER]
Name rewrite_tag
Match test_tag
Rule $tool ^(fluent)$ from.$TAG.new.$tool.$sub['s1']['s2'].out false
Emitter_Name re_emitted
[OUTPUT]
Name stdout
Match from.*我将配置文件命名为example.conf
我运行它的方式如下
fluent-bit -c example.conf发布于 2020-10-19 18:26:49
有一个已知的回归,请升级到v1.6.1:
$ ../../build/bin/fluent-bit -c conf
Fluent Bit v1.6.1
* Copyright (C) 2019-2020 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
[2020/10/19 12:25:49] [ info] [engine] started (pid=1830124)
[2020/10/19 12:25:49] [ info] [storage] version=1.0.6, initializing...
[2020/10/19 12:25:49] [ info] [storage] in-memory
[2020/10/19 12:25:49] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2020/10/19 12:25:49] [ info] [sp] stream processor started
[0] from.test_tag.new.fluent.bit.out: [1603131950.103238001, {"tool"=>"fluent", "sub"=>{"s1"=>{"s2"=>"bit"}}}]
[0] from.test_tag.new.fluent.bit.out: [1603131951.102535915, {"tool"=>"fluent", "sub"=>{"s1"=>{"s2"=>"bit"}}}]https://stackoverflow.com/questions/64425783
复制相似问题