I tried the rewrite-tag
example written in the documentation with fluent-bit 1.6.0
I was able to get rid of the following warning with the fix mentioned in the Git
[2020/10/19 15:17:31] [ warn] [input chunk] no matching route for input chunk 16817-1603100851.153798000.flb
But now I get nothing on the output. It’s hanging on after following line
...
[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
Any idea why that is?
Following is the content of configuration file (same as in the documentation)
[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.*
I named the configuration file as example.conf
The way I ran it as below
fluent-bit -c example.conf
There is a known regression, please upgrade to v1.6.1: