# Filebeat/kibana upgrade issues from 6.x to 7.x

**URL:** https://discuss.elastic.co/t/filebeat-kibana-upgrade-issues-from-6-x-to-7-x/195961
**Category:** Beats
**Tags:** filebeat
**Created:** [August 20, 2019, 2:54pm UTC](https://discuss.elastic.co/t/filebeat-kibana-upgrade-issues-from-6-x-to-7-x/195961 "2019-08-20T14:54:17Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![tenney](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@tenney](https://discuss.elastic.co/u/tenney)
#### Post date: [August 20, 2019, 2:54pm UTC](https://discuss.elastic.co/t/filebeat-kibana-upgrade-issues-from-6-x-to-7-x/195961/1 "2019-08-20T14:54:18Z")

</div>

Upgraded to 7.x and having some issues with our nginx data. One example is response times the fields were moved from nginx.access.response\_code to http.response.status\_code.

I thought enabling the compatibility later would create aliases would fix this?

migration.6\_to\_7.enabled: true

Is this because it is a leaf field? Is there anyway to create an alias for these?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 17, 2019, 2:54pm UTC](https://discuss.elastic.co/t/filebeat-kibana-upgrade-issues-from-6-x-to-7-x/195961/2 "2019-09-17T14:54:19Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
