# Csv columnnames utf-8
**URL:** https://discuss.elastic.co/t/csv-columnnames-utf-8/122065
**Category:** Logstash
**Created:** [March 1, 2018, 1:19pm UTC](https://discuss.elastic.co/t/csv-columnnames-utf-8/122065 "2018-03-01T13:19:02Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@TclasenITVT](https://discuss.elastic.co/u/TclasenITVT)
#### Post date: [March 1, 2018, 1:19pm UTC](https://discuss.elastic.co/t/csv-columnnames-utf-8/122065/1 "2018-03-01T13:19:03Z")
I am trying to use the CSV Filter in my Logstashpipeline. When I try to specify Columnnames that contain ü, ä, § or € the JSon that is display by Kibana shows something like "Anzahl Monate (für NN GP abs. â¬)". Is there any way to make logstash correctly read my conf file? I saved the conf file as UTF-8 and the respective Columnname is "Anzahl Monate (für NN GP abs. €)". I tried finding out if the conf files have to be a special encoding but couldn't find anything on that topic. By the way the content itself is using UTF-8 and is displaying ä, ü ,§ and € correctly. I am using Logstash Version 6.0.1. Same Problem with Logstash 6.2.2.
```
{
...
"Zähler Nr.": "Zähler Nr.",
"Anzahl Monate (für NN GP abs. â¬)": "Anzahl Monate (für NN GP abs. €)",
"Offhore Umlage abs. â¬": "Offhore Umlage abs. €",
"NNE abs. â¬": "NNE abs. €",
"§19 Strom NEV abs.": "§19 Strom NEV abs.",
"@version": "1",
...
},
"fields": {
"@timestamp": [
"2018-03-01T12:38:44.180Z"
]
},
"sort": [
1519907924180
]
}
```
---
### Author:  [@TclasenITVT](https://discuss.elastic.co/u/TclasenITVT)
#### Post date: [March 9, 2018, 2:21pm UTC](https://discuss.elastic.co/t/csv-columnnames-utf-8/122065/2 "2018-03-09T14:21:49Z")
Here is the csv filter part from my .conf-file.
```
filter {
csv{
columns => [
"Zähler Nr.",
"Anzahl Monate (für NN GP abs. €)",
"Offhore Umlage abs. €",
"NNE abs. €",
"§19 Strom NEV abs."
]
separator => ";"
skip_headers=> true
add_field => {
"Version" => "1"
}
}
}
```
Inside of Visual Studio Code everything looks alright. I also tried saving the .conf with the Encoding : "ISO 8859-15" but it resulted in the same Columnnames inside of the JSON in Elasticsearch.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 6, 2018, 2:22pm UTC](https://discuss.elastic.co/t/csv-columnnames-utf-8/122065/3 "2018-04-06T14:22:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.