Hi! Thanks for your update! I've opened https://github.com/Graylog2/graylog2-server/issues/550 for this. I think it's worthwhile to support different encodings, as this can be a problem for many non-english applications.
Thanks, Kay On Thu, May 15, 2014 at 12:52 PM, Arkadiy Shinkarev <kewa...@gmail.com>wrote: > Ok, I solved it. > logs encoding was CP1252, so I imlement Logstash and now everything works > fine :) > > > On Monday, May 12, 2014 12:30:00 PM UTC+4, Arkadiy Shinkarev wrote: >> >> Hello all! >> >> We have several log4net instances pointed to syslog and send logs via UDP. >> I forward all from syslog to Graylog2: >> $template GRAYLOGRFC5424,"<%pri%>%protocol-version% >> %timestamp:::date-rfc3339% %HOSTNAME% %app-name% %procid% %msg%\n" >> *.* @127.0.0.1:514;GRAYLOGRFC5424 >> >> When data comes to Graylog2 i see this: >> >> >> <https://lh4.googleusercontent.com/-QiDlAA8NIKI/U3CEEW0iEII/AAAAAAAABOU/KoUYMWGbhqg/s1600/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA.PNG> >> >> Russian text in UTF-8 also broken, but in /var/log/messages all logs >> looks ok. >> Where is the problem? >> >> rsyslog 8.2.1 >> elasticsearch 0.90.13 >> Graylog2 0.20.1 >> >> Thanks! >> > -- > You received this message because you are subscribed to the Google Groups > "graylog2" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to graylog2+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
