# Problem with transfer Filebeat 6.1.3 \> Logstash 6.1.3 \> Elasticsearch 6.1.3

**URL:** <https://discuss.elastic.co/t/problem-with-transfer-filebeat-6-1-3-logstash-6-1-3-elasticsearch-6-1-3/136264>\
**Category:** Logstash\
**Created:** [June 18, 2018, 9:03am UTC](https://discuss.elastic.co/t/problem-with-transfer-filebeat-6-1-3-logstash-6-1-3-elasticsearch-6-1-3/136264 "2018-06-18T09:03:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [June 21, 2018, 5:43pm UTC](https://discuss.elastic.co/t/problem-with-transfer-filebeat-6-1-3-logstash-6-1-3-elasticsearch-6-1-3/136264/4 "2018-06-21T17:43:51Z")

</div>

It looks like your index was created with a new version of Beats that is implementing the ECS (Elastic Common Schema), but that the Logstash output isn't quite in the same shape 😩

ECS has a `host.name` field, which corresponds to the host name being output from Logstash. By adding a Mutate filter with a `rename` directive, you can move the `host` field to `host.name` with the field-reference syntax as below to align with the schema that you already have in Elasticsearch:

```auto
filter {
  mutate {
    rename {
      "[host]" => "[host][name]"
    }
  }
}

```

---

_[View the full topic](https://discuss.elastic.co/t/problem-with-transfer-filebeat-6-1-3-logstash-6-1-3-elasticsearch-6-1-3/136264)._