You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
[SERVICE]
Flush 1
Log_Level info
Daemon off
Parsers_File parsers.conf
[INPUT]
Name tail
Tag audit.*
Path /var/log/containers/sample.log
Parser docker
DB /var/log/flb_kube.db
Mem_Buf_Limit 5MB
Skip_Long_Lines Off
Refresh_Interval 10
[OUTPUT]
Name file
Match audit.*
Path /var/log/output.txt
[PARSER]
Name docker
Format json
# Command | Decoder | Field | Optional Action
# =============|==================|=================
Decode_Field_As escaped log
Decode_Field_As escaped level_1
Note that I have no problem with {"id":"2", "log":"hello \"AAA\" world"} formmated log. And I can get a correct output as {"id":"2", "log":"hello \"AAA\" world"}
The text was updated successfully, but these errors were encountered:
Hi, fluentbit people. I am facing a double escaping problem which is sort of related to #615
The only difference with #615 is in that the failed log contains nested json string, for example. my log is as follow
I would expect the output as:
but the output is actually:
my fluent-bit-config.yaml is as follows"
Note that I have no problem with
{"id":"2", "log":"hello \"AAA\" world"}
formmated log. And I can get a correct output as{"id":"2", "log":"hello \"AAA\" world"}
The text was updated successfully, but these errors were encountered: