# Logstash errors after upgrading to filebeat-6.3.0

**URL:** <https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 14, 2018, 6:51pm UTC](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984 "2018-06-14T18:51:00Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [June 29, 2018, 2:22pm UTC](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984/24 "2018-06-29T14:22:02Z")

</div>

Thanks for testing. I need to test this also on my end but an other thing you could try is adding `host` field under and other name and then use the rename processor after you renamed the `host.*` fields. But not 100% sure it will work.

The general problem is that `fields: *` existed before the processor existed which makes it a bit special, meaning you can define the order it is executed. That is why I want to replace it by a processor: [https://github.com/elastic/beats/issues/7350](https://github.com/elastic/beats/issues/7350) If the above does not work, sounds like we should increase the priority for it.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984)._