Using the client with Graylog hosted on Azure Kubernetes I found out that big log messages were missing on my stream.
Troubleshooting it I notice that messages longer than 1493 bytes were never being received in the UDP port. To be sure of it I dropped the Graylog Input listener and used netcat to start listening on the same UDP port and submitted messages of different sizes.
Running Graylog on a VirtualBox machine I could not reproduce this issue, only when its running on AKS.
Using the client with Graylog hosted on Azure Kubernetes I found out that big log messages were missing on my stream. Troubleshooting it I notice that messages longer than 1493 bytes were never being received in the UDP port. To be sure of it I dropped the Graylog Input listener and used netcat to start listening on the same UDP port and submitted messages of different sizes. Running Graylog on a VirtualBox machine I could not reproduce this issue, only when its running on AKS.
I found this related issue on Graylog repository: https://github.com/Graylog2/graylog2-server/issues/4317 Quoting joschi:
Expanding the code I notice that the max chunk size is defined in a constant, making it impossible to configure the client to my network issue.
My environment
Graylog version: 4.0.2 Hosting: Azure AKS Client: .NET Core 3.1 + Windows