-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Graylog output plugin: full_message
is handled like a custom field
#10024
Comments
Please assign this to me (alespour) if you will. @1tft There is a configuration option |
I dont think full_message_field is necessary, because its a bugfix. Nobody should have expected that full_message field has an underscore, because there exists no Gelf version where this is valid. |
@srebhan Made some tests with telegraf-1.21.0~4737bebc-0.x86_64.rpm and logs successfully transferred to Graylog with all fields. Telegraf graylog output seems now to produce valid gelf. |
So I'll close the issue and also the PR. If you see any issues, please open a new issue or reopen this one. |
Relevent telegraf.conf
System info
Telegraf 1.20
Docker
No response
Steps to reproduce
Graylog output plugin does not handle default gelf field "full_message" as default field. It treates it as custom field and adds "_" at beginning. Thats not correct, like "short_message" field, also full_message field must not start with underscore (see https://docs.graylog.org/en/4.0/pages/gelf.html).
Mentioned by @1tft in #9862.
full_message
"_full_message": "whatever",
Expected behavior
full_message
field name should not be prefixed with underscore.Actual behavior
full_message
field name is prefixed with underscore.Additional info
No response
The text was updated successfully, but these errors were encountered: