-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync behaviour of GELF plugin and Graylog (re: has empty mandatory "short_message") #5171
Comments
I have the same problem with my Graylog 2.4.6 server on Ubuntu Linux (created in AWS from The AMI provided by Graylog). The problematic messages are sent by Graylog itself (or a plugin).
Here are the logs :
Those logs sent by "runit-service" facility may be the same :
|
In GELFMessageTest.java, GELF_JSON has no "short_message". Idem in GELFMessageChunkTest.java : GELF_JSON has no "short_message" nor "version". And Graylog GELF inputs apparently accepts GELF JSON having no "version", which is said to be mandatory ! |
Hi everyone, there is a workaround to this before waiting the bug correction ? |
Hi there! Any news? |
Any updates? |
I have the same problem with my Graylog 4.0.11+e4e88a4, codename Noir. Any update? Here are the logs :
|
I have a lot of such messages too. I read somewhere that it's kinda a white noise. But can we do something with this? It bothers me when I see [ERROR]... |
My setup: Logstash -> GELF -> Graylog 2.4.6
Some of my logfiles contain lines with only whitspace characters (TAB + end of line). This leads to lots of "has empty mandatory "short_message" field" Exceptions in Graylog.
imho this is a bug, because there is a message (the TAB character). GelfCodec.java has this line here:
Would it make sense to change StringUtils.isBlank() to StringUtils.isEmpty()
If not, I would appreciate to sync the behaviour of the GELF Plugin and the GelfCodec in Graylog. I mean, why send messages to Graylog if it rejects it anyway?
The text was updated successfully, but these errors were encountered: