# Dashboards buggy aftar upgrade

**URL:** <https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558>\
**Category:** Kibana\
**Created:** [February 12, 2018, 10:07pm UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558 "2018-02-12T22:07:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![flalar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flalar/32/85777_2.png) [@flalar](https://discuss.elastic.co/u/flalar)\
**Post date:** [February 12, 2018, 10:07pm UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/1 "2018-02-12T22:07:36Z")

</div>

After upgrading our full stack to 6.2 some of the default dashboards seems broken. Eg. this default metricbeat deshboard

 ![dashboard](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22dfacd13c71c28ce7de0a02261ecea18474fdb9.png)

As you can see the Top N Visual Builder visualization for disk and cpu usage is showing just 0% for all nodes. Same goes for a lot of the other visualizations that come with the package.

Any suggestions what has gone wrong?

---

<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:** [February 13, 2018, 6:35pm UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/2 "2018-02-13T18:35:02Z")

</div>

What version did you upgrade from? In the [5.x to 6.x upgrade doc](https://www.elastic.co/guide/en/beats/libbeat/6.2/upgrading-5-to-6.html) the beats team recommends re-importing the default dashboards and suggests that the old ones might not work anymore (breaking change).

---

<div class="post-metadata">

**Author:** ![flalar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flalar/32/85777_2.png) [@flalar](https://discuss.elastic.co/u/flalar)\
**Post date:** [February 13, 2018, 9:45pm UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/3 "2018-02-13T21:45:16Z")

</div>

Upgraded from 6.0 to 6.2 Thingstad wire fine in 6.0

---

<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:** [February 14, 2018, 7:49pm UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/4 "2018-02-14T19:49:22Z")

</div>

Hmm, can you give the re-import a shot?

---

<div class="post-metadata">

**Author:** ![flalar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flalar/32/85777_2.png) [@flalar](https://discuss.elastic.co/u/flalar)\
**Post date:** [February 21, 2018, 11:51am UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/5 "2018-02-21T11:51:36Z")

</div>

Deleted all dashboards searches and visualizations related to metricbeat and re-imported the package... but it is still the same? Any ideas?

---

<div class="post-metadata">

**Author:** ![flalar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flalar/32/85777_2.png) [@flalar](https://discuss.elastic.co/u/flalar)\
**Post date:** [March 6, 2018, 12:34am UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/6 "2018-03-06T00:34:00Z")

</div>

Another update on this. Seems this is just happening for some users. However the buggy graphs are same on different browsers for users that sees the problem.

---

<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:** [April 3, 2018, 12:34am UTC](https://discuss.elastic.co/t/dashboards-buggy-aftar-upgrade/119558/7 "2018-04-03T00:34:05Z")

</div>

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