-
Notifications
You must be signed in to change notification settings - Fork 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
Charset and encoding #1431
Comments
Is it possible that your MongoDB instance has a weird charset configured? |
No feedback in a long time, please re-open if this is still an issue with a recent release. Thank you! |
This is a stupid humanoid error. I also got the same error. This was caused because I had configured RAW/plaintext UDP input plugin when my output plugin in Fluentd was gelf. Deleted the RAW/plaintext UDP input plugin and recreated a new GELF UDP input plugin in gray log solved the issue. |
Hi, all!
I have a problem with charset or encoding. First of all, I wish to make grok pattern to my logs. I had written the regular expression, added it to grok pattern.
When I try it in online decoders, it works perfectly. But when I try it to use in my GrayLog - it doesn't work.
For my opinion, it doesn't work because when I want to create extractor, I have bad encoding:
But at the same time, in Search it looks pretty good.
I know that Graylog Collector that I installed on my Windows Server had default UTF-8 charset, I changed it to Windows-1251, but it also didn't help. At the screen with bad charset shows KOI8 charset (I'm from Ukraine and logs sometimes have Cirrilic characters).
Can anyone help me with my problem?
Thanks, a lot.
The text was updated successfully, but these errors were encountered: