Inconsistent UDP Message Reception #8776
Replies: 3 comments
-
It looks more like it's reading a field in the message and getting a size of 0 so skipping it - my guess is adding a source port is moving an offset. It should really cope with it fine though. |
Beta Was this translation helpful? Give feedback.
-
I'd like to rephrase. Fluent Bit is able to receive the messages when the application does not listen on the source UDP port. When the application where the source listens on the UDP the messages do not come through with the error I mentioned in my first post. Could you maybe give me more details about how UDP Input works or point me to the code where its implemented? |
Beta Was this translation helpful? Give feedback.
-
I am not able to receive any message on UDP input when I run this code:
Whent I start fluent-bit with format=none ( However, when I start fluentbit with format=json: We are using UDP input for some legacy reporting mechanism and then simple lua script to translate received data to metrics. |
Beta Was this translation helpful? Give feedback.
-
Good morning
I am trying to receive UDP messages using UDP Input. Interestingly, while messages from one application successfully pass through Fluent Bit, I am encountering an issue where Fluent Bit does not accept messages from another application. This is what the unsuccesfull output is:
[2024/04/29 16:42:59] [trace] [input:udp:udp.0 at D:\a\fluent-bit\fluent-bit\plugins\in_udp\udp_conn.c:387] read()=11 pre_len=0 now_len=11
[2024/04/29 16:42:59] [debug] [input chunk] skip ingesting data with 0 bytes
Upon further analysis using Wireshark, there is a slight distinction between the packets that successfully traverse Fluent Bit and those which don't. Specifically, it appears that the messages that successfully pass through Fluent Bit do not contain the source port information in the data byte.
Is it possible that when a UDP message reaches Fluent Bit, Fluent Bit itself attempts to contact back the source or initiates a response? Perhaps, due to the absence of port information in the first application's messages, Fluent Bit allows them to pass through. However, when it attempts to respond to messages from the second application, which include port information, it encounters difficulties, resulting in the messages being marked as empty.
Thanks for any insights to this matter
Beta Was this translation helpful? Give feedback.
All reactions