Closed atefhaloui closed 3 years ago
Seems similar to #2717 which was closed (stale)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
hi, I met the similar issue using 1.9.9, is there any workaround for this issue?
found a "WA" for this, like below, read the content from file, modify some to that, then print that out to another file, reload from that file, send to rsyslog, that is not good one since there is additional read/write to filesystem. but that seems only option before upstream enhance this part.
''' [INPUT]
Name tail
Path /tmp/container-log/*.log
Exclude_Path *.gz,*.zip
storage.type filesystem
DB /tmp/fluentbit.db
Read_from_Head True
Refresh_Interval 30
Tag raw-log
Key log
[INPUT]
Name tail
Path /tmp/temp-log/*.log
Exclude_Path *.gz,*.zip
storage.type filesystem
DB /tmp/fluentbit2.db
Read_from_Head True
Refresh_Interval 30
Tag clog
[FILTER] Name record_modifier Match raw-log Record product something
[OUTPUT] Name file Match raw-log Path /tmp/temp-log File temp.log Format plain Mkdir True Match raw-log
[OUTPUT] name syslog match clog host 1.5.4.52 port 2516 mode tcp syslog_format rfc5424 syslog_maxsize 2048 syslog_message_key log '''
@danielzhanghl where you ever able to configure this w/o the workaround? I can't seem to get it w/o the workaround? [SERVICE] Flush 1 Daemon Off Log_Level info Parsers_File parsers.conf
[INPUT] Name tail Path /var/log/containers/.log Parser docker Tag kube. Refresh_Interval 5 Rotate_Wait 5 Mem_Buf_Limit 5MB Skip_Long_Lines On DB /var/log/flb_kube.db DB.Sync Normal
[OUTPUT]
Name syslog
Match *
Host
Is your feature request related to a problem? Please describe. I've tried to send a json log entry through the syslog output without any luck. The structure of the json entry is:
My parser is:
my config file:
When I append a new entry to my log file, the message sent is empty :(
My fluent-bit output:
and in my rsyslog I have:
Describe the solution you'd like The message sent must be the content of the
syslog_message_key
even if it's a json object. Frommsgpack_to_syslog
, I can see that this function does not accept MSGPACK_OBJECT_MAP for messages while, imho, it should serialize the content of the json object and send it.