I have been struggling with Logstash to be able to apply the windows charset CP1252 in a UDP input listener. I'm running on a windows server 2012 with Logstash 5.2.2.
The charset setup seems does not make effect and after I sent the data I see the character like that:
Sent data : [é ó ção]
Result in Elastic : [\xE9 \xF3 \xE7\xE3o]
The UDP setup follows below.
input
{
udp
{
port => 5140
codec => plain
{
charset => "CP1252"
}
type => "log4net"
}
}
After some more tests, it seems that the problem should be happen when grok apply the filter before it goes to output.
Has anyone experienced this issue?
When I send a given message to logstash, lets say "[é ó ção]" it seems that after the filter process the is performed by a grok codec to transform the message, the initial value that was "[é ó ção]" is wrongly converted to this the characteres "\xE9 \xF3 \xE7\xE3o". I'm not understanding what's the reason of it's behavior . If I remove the filter step, the message arrives in the right way to the output since I can see it in Kibana.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.