# How to migrate from Kibana 4.5.0 to Kibana 5.0.0?

**URL:** <https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780>\
**Category:** Kibana\
**Created:** [November 11, 2016, 9:18am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780 "2016-11-11T09:18:24Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 9:18am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/1 "2016-11-11T09:18:24Z")

</div>

We're currently running `Elasticsearch 2.3.3` and `Kibana 4.5.0`. We are migrating to `Elasticsearch 5.0.0` and `Kibana 5.0.0`. So far Elasticsearch upgrade is smooth by following the migration helper. But having issues with Kibana dashboards [index mapping not refreshing in management for logstash, dashboards are saying bad request from Elasticsearch 400].

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 11, 2016, 9:20am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/2 "2016-11-11T09:20:15Z")

</div>

Can you show us the complete error?

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 9:48am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/3 "2016-11-11T09:48:44Z")

</div>

This ERR "Bad Request" :

 ![](https://us1.discourse-cdn.com/elastic/original/2X/2/2b849a3324add7c6fd8abc0ac9764f79dc456c51.png)

This is what I'm getting in Kibana Logs :

`respons [09:44:59.020] POST /elasticsearch/.kibana/index-pattern/%5Blogstash-%5DYYYY.MM.DD 400 624ms - 9.0B`

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 9:55am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/4 "2016-11-11T09:55:17Z")

</div>

The point is when I go to management page indices and select `[logstash-]YYYY.MM.DD`, It's not allowing me to refresh index.

In Kibana :

`respons [09:54:44.029] POST /elasticsearch/.kibana/index-pattern/%5Blogstash-%5DYYYY.MM.DD 400 1137ms - 9.0B`

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 10:03am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/5 "2016-11-11T10:03:28Z")

</div>

Further I deleted the Kibana Index and then I tried to create the logstash index again :

 ![](https://us1.discourse-cdn.com/elastic/original/2X/2/2c281696faa9aa1d09dece2346d14b17756b589c.png)

It again fails with 400 code as above

and gives this :

 ![](https://us1.discourse-cdn.com/elastic/original/2X/d/dad0974e87090dcf6db32389b57e50c1e73b3cd3.png)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 11, 2016, 10:08am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/6 "2016-11-11T10:08:08Z")

</div>

AS pointed out in the large orange blob on the screen, it is now recommended to use wildcard patterns in Kibana rather than the older style date patterns. Have you tried specifying the index pattern as `logstash-*` as recommended?

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 10:13am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/7 "2016-11-11T10:13:40Z")

</div>

`respons [10:11:33.375] POST /elasticsearch/.kibana/index-pattern/logstash-* 400 3495ms - 9.0B`

Again a 400.

But something different, now it went all BLANK on all pages :

 ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e82313bb318d34a6dc8d4d8afe2647bfaaa97201.png)

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 10:29am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/8 "2016-11-11T10:29:13Z")

</div>

curl -XGET -vv '[http://data3.dev.evivehealth.com:9201/.kibana/index-pattern/logstash-](http://data3.dev.evivehealth.com:9201/.kibana/index-pattern/logstash-)\*'

- Hostname was NOT found in DNS cache
- Trying 10.13.1.35...
- Connected to [data3.dev.evivehealth.com](http://data3.dev.evivehealth.com) (10.13.1.35) port 9201 (#0)

> GET /.kibana/index-pattern/logstash-\* HTTP/1.1  
> User-Agent: curl/7.37.0  
> Host: [data3.dev.evivehealth.com:9201](http://data3.dev.evivehealth.com:9201)  
> Accept: _/_

\< HTTP/1.1 200 OK  
\< content-type: application/json; charset=UTF-8  
\< content-length: 151  
\<

- Connection #0 to host [data3.dev.evivehealth.com](http://data3.dev.evivehealth.com) left intact  
{"\_index":".kibana","\_type":"index-pattern","\_id":"logstash-_","\_version":1,"found":true,"\_source":{"title":"logstash-_","timeFieldName":"@timestamp"}}

ES is returning 200 and not 400. Is something not configured properly at kibana?

My Kibana yaml says :

elasticsearch.url: "[http://data3.dev.evivehealth.com:9201/](http://data3.dev.evivehealth.com:9201/)"

rest all settings related to es are deafult.

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 11, 2016, 11:15am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/9 "2016-11-11T11:15:43Z")

</div>

Adding to this I tried now putting nginx in front of ES and see what response am getting from ES

Suprisingly :

for : `respons [11:14:35.828] POST /elasticsearch/.kibana/index-pattern/logstash-* 400 928ms - 9.0B`  
I'm getting this in nginx :

`10.13.1.35 - - [11/Nov/2016:16:47:52 +0530] "GET /logstash-*/_mapping/field/*?ignore_unavailable=false&allow_no_indices=false&include_defaults=true HTTP/1.1" 200 14294248 "-" "-" "10.14.1.187" 10.13.1.35 - - [11/Nov/2016:16:47:54 +0530] "POST /logstash-*/_field_stats?fields=*&allow_no_indices=false HTTP/1.1" 200 1712898 "-" "-" "-"`

SO ES is indeed returning 200. something wrong in kibana? [All requests getting 200]

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [November 11, 2016, 10:42pm UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/10 "2016-11-11T22:42:58Z")

</div>

This sounds a lot like a misconfigured proxy. Have you tried connecting Kibana _directly_ to elasticsearch?

---

<div class="post-metadata">

**Author:** ![Jay\_Dihenkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jay_dihenkar/32/26375_2.png) [@Jay\_Dihenkar](https://discuss.elastic.co/u/Jay_Dihenkar)\
**Post date:** [November 17, 2016, 7:14am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/11 "2016-11-17T07:14:42Z")

</div>

As you see in my previous updates, I was not using proxy and then I configured nginx as a proxy.

Moreover after debugging and trials and errors It somehow got resolved when removed a logstash index which I imported from es2.3 to es5.0.

---

<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:** [December 15, 2016, 7:14am UTC](https://discuss.elastic.co/t/how-to-migrate-from-kibana-4-5-0-to-kibana-5-0-0/65780/12 "2016-12-15T07:14:42Z")

</div>

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