ForbiddenEra
commented
2 years ago So, after a bit of digging it seems like the difference between the FluentClient's messages and stuff posted from either td-agent or calyptia-fluentd (tried both) is that the content of the message isn't being parsed as a buffer for some reason for messages from fluentd. Messages sent to self w/fluentclient do come up as Unit8array.
message: [
'tag_prefix.tag',
<Buffer 92 ce 62 86 0b 4f 81 a7 6d 65 73 73 61 67 65 a7 6d 65 73 73 61 67 65>,
{ size: 1 }
]
message: [
'fluent.info',
'\x92׀b\x86\x0BP\x1E\x1AZ\x15\x84£pid͢S¤ppid͢N¦worker\x00§messageٵstarting fluentd worker pid=25171 ppid=25166 worker=0',
{ size: 1, compressed: 'text', chunk: 'XfWdomaRnTurg7tBufiwgA==\n' }
]Not sure why this would be happening..? I've tried enabling gzip, no difference.
From my investigation, it seems as though the decode method in the extensionCodec never gets called (in either case), the encode method does get called.
jamiees2
Hi,
Trying to use this as a server/sink to have fluent forward logs into a node app, but nothing seems to get emitted when forwarded in by an actual fluentd..
Using this test code:
I do immediately see the message forwarded into itself with this test app, however I see nothing emitted when my local fluentd connects and flushes it's buffer.
I've tried the config posted in the readme basically; I have my local syslog as a source tagged as system.
I've also tried <match **> for all messages.. I do not ever see a forward-failed file. The fluentd log complains when my node app isn't listening and then shows that it flushed when it does start listening.
I've setup a copy output to copy to the forward for the node sink and to a local file and can indeed see the log entries in the local file.
Perhaps I'm reading it wrong but retry succeeded with a chunk id sounds like it's definitely pushing a chunk but I'm not getting any event emitted while I do when I push it locally from node.
Any ideas what my issue might be? is there a possible version issue or something?
thanks