# Streams - german logs **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** sidecar, winlogbeat\ **Created:** [September 11, 2018, 10:24am UTC](https://community.graylog.org/t/streams-german-logs/6785 "2018-09-11T10:24:58Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![DanSBG](https://avatars.discourse-cdn.com/v4/letter/d/6f9a4e/32.png) [@DanSBG](https://community.graylog.org/u/DanSBG)\ **Post date:** [September 11, 2018, 10:24am UTC](https://community.graylog.org/t/streams-german-logs/6785/1 "2018-09-11T10:24:58Z")
Hi, I have one Server in my datacenter which is in german language. Logs are in german language as well. I use the Op5 Syslog Agent for log forwarding - everything working as expected. Input is a raw udp input. When I receive the logs the text in the “message” field looks weird - there cant be any german letters like Ä Ö Ü displayed. It just shows some question signs where the letters should be. Is there any workaround for my issue ? Regards Daniel ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [September 11, 2018, 10:41am UTC](https://community.graylog.org/t/streams-german-logs/6785/2 "2018-09-11T10:41:30Z")
He @DanSBG may I ask why you are not using Syslog Input? In Addition some kind of encoding might be send with the messages - maybe if you capture with tcpdump you are able to see if that encoding is done during the sending. ---
**Author:** ![DanSBG](https://avatars.discourse-cdn.com/v4/letter/d/6f9a4e/32.png) [@DanSBG](https://community.graylog.org/u/DanSBG)\ **Post date:** [September 11, 2018, 10:48am UTC](https://community.graylog.org/t/streams-german-logs/6785/3 "2018-09-11T10:48:11Z")
Same with the normal syslog input - maybe you are right and the encoding is done before. I will check this. ---
**Author:** ![DanSBG](https://avatars.discourse-cdn.com/v4/letter/d/6f9a4e/32.png) [@DanSBG](https://community.graylog.org/u/DanSBG)\ **Post date:** [September 11, 2018, 11:19am UTC](https://community.graylog.org/t/streams-german-logs/6785/4 "2018-09-11T11:19:31Z")
It seems like the message has been encoded wrong by the syslog agent. Maybe you know another simple and lightweight solution for forwarding windows event logs ? Since it is the only german server in the datacenter so far, I consider taking no more action. ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [September 11, 2018, 11:24am UTC](https://community.graylog.org/t/streams-german-logs/6785/5 "2018-09-11T11:24:53Z")
For Windows Eventlog I would use winlogbeat - as this is the only solution that works without issues and is very light and easy to configure. ---
**Author:** ![DanSBG](https://avatars.discourse-cdn.com/v4/letter/d/6f9a4e/32.png) [@DanSBG](https://community.graylog.org/u/DanSBG)\ **Post date:** [September 12, 2018, 10:05am UTC](https://community.graylog.org/t/streams-german-logs/6785/6 "2018-09-12T10:05:24Z")
Thanks for the hin with winlogbeat, the encoding is still a little bit weird but I will take no more action. The important information I need from the logs does not contain any of the wrong encoded letters. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [September 26, 2018, 10:05am UTC](https://community.graylog.org/t/streams-german-logs/6785/7 "2018-09-26T10:05:34Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.